Sign in with
Sign up | Sign in
Your question

Unexpected reboot while backing up registry

Tags:
  • Registry
  • Servers
  • Windows
Last response: in Windows 2000/NT
Share
Anonymous
February 28, 2005 3:59:03 AM

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

HELP!!
Can't figure it out... When backing up system state in Windows 2000 Server,
the backup operates normaly until it gets to the registry then performs
memory dump with a registry error. I have already ran chkdsk on all affected
drives with no luck. Any ideas??

Josh
IT Manager

More about : unexpected reboot backing registry

Anonymous
February 28, 2005 9:32:12 AM

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

On Mon, 28 Feb 2005 00:59:03 -0800, Joshua Renoe <JoshuaRenoe@discussions.microsoft.com> wrote:

>HELP!!
>Can't figure it out... When backing up system state in Windows 2000 Server,
>the backup operates normaly until it gets to the registry then performs
>memory dump with a registry error. I have already ran chkdsk on all affected
>drives with no luck. Any ideas??
>
>Josh
>IT Manager

Most people here would be willing to try to help if you provided a clue, like
the exact error and STOP code and parameters.
See tip 726 in the 'Tips & Tricks' at http://www.jsiinc.com

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
Anonymous
February 28, 2005 4:53:06 PM

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

Thanks ... does this mean anything to anyone?

C:\WINNT>dumpchk memory.dmp
****************************************************************
**
** Windows 2000 Crash Dump Analysis
**
****************************************************************
*
Filename . . . . . . .memory.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x3e0e5000
PfnDataBase. . . . . .0x90092000
PsLoadedModuleList . .0x80484b80
PsActiveProcessHead. .0x804862e8
MachineImageType . . .i386
NumberProcessors . . .2
BugCheckCode . . . . .0x00000051
BugCheckParameter1 . .0x0000000c
BugCheckParameter2 . .0xc0000005
BugCheckParameter3 . .0xbcd7da48
BugCheckParameter4 . .0xbcd7d6a0

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x8051411d



**************
**************--> Validating the integrity of the PsLoadedModuleList
**************
**************
**************--> No errors in the module list.
**************
**************
**************--> This dump file is good!
**************



"Jerold Schulman" wrote:

> On Mon, 28 Feb 2005 00:59:03 -0800, Joshua Renoe <JoshuaRenoe@discussions.microsoft.com> wrote:
>
> >HELP!!
> >Can't figure it out... When backing up system state in Windows 2000 Server,
> >the backup operates normaly until it gets to the registry then performs
> >memory dump with a registry error. I have already ran chkdsk on all affected
> >drives with no luck. Any ideas??
> >
> >Josh
> >IT Manager
>
> Most people here would be willing to try to help if you provided a clue, like
> the exact error and STOP code and parameters.
> See tip 726 in the 'Tips & Tricks' at http://www.jsiinc.com
>
> Jerold Schulman
> Windows Server MVP
> JSI, Inc.
> http://www.jsiinc.com
>
Anonymous
March 1, 2005 11:25:21 AM

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

If you are not running SP4, apply it.

http://support.microsoft.com?kbid=282501 "How to troubleshoot a #34STOP 0x00000051 REGISTRY ERROR#34 error message "
http://support.microsoft.com?kbid=321771 "You Receive a #34Stop 0x51 #40REGISTRY_ERROR#41#34 Error Message "
http://support.microsoft.com?kbid=810558 "#34Stop 0x00000051 REGISTRY_ERROR#34 Error Message When You Back Up the Registry Hive "
http://support.microsoft.com?kbid=815265 "#34STOP 0x00000051#34 or #34STOP 0x0000001E#34 error message when you start Configuration Manager in Windows 2000 Server or in Windows XP "
http://support.microsoft.com?kbid=834728 "You receive a #34Stop 0x00000051#34 error message during registry restoration "


On Mon, 28 Feb 2005 13:53:06 -0800, Joshua Renoe <JoshuaRenoe@discussions.microsoft.com> wrote:

>Thanks ... does this mean anything to anyone?
>
>C:\WINNT>dumpchk memory.dmp
>****************************************************************
>**
>** Windows 2000 Crash Dump Analysis
>**
>****************************************************************
>*
>Filename . . . . . . .memory.dmp
>Signature. . . . . . .PAGE
>ValidDump. . . . . . .DUMP
>MajorVersion . . . . .free system
>MinorVersion . . . . .2195
>DirectoryTableBase . .0x3e0e5000
>PfnDataBase. . . . . .0x90092000
>PsLoadedModuleList . .0x80484b80
>PsActiveProcessHead. .0x804862e8
>MachineImageType . . .i386
>NumberProcessors . . .2
>BugCheckCode . . . . .0x00000051
>BugCheckParameter1 . .0x0000000c
>BugCheckParameter2 . .0xc0000005
>BugCheckParameter3 . .0xbcd7da48
>BugCheckParameter4 . .0xbcd7d6a0
>
>ExceptionCode. . . . .0x80000003
>ExceptionFlags . . . .0x00000001
>ExceptionAddress . . .0x8051411d
>
>
>
>**************
>**************--> Validating the integrity of the PsLoadedModuleList
>**************
>**************
>**************--> No errors in the module list.
>**************
>**************
>**************--> This dump file is good!
>**************
>
>
>
>"Jerold Schulman" wrote:
>
>> On Mon, 28 Feb 2005 00:59:03 -0800, Joshua Renoe <JoshuaRenoe@discussions.microsoft.com> wrote:
>>
>> >HELP!!
>> >Can't figure it out... When backing up system state in Windows 2000 Server,
>> >the backup operates normaly until it gets to the registry then performs
>> >memory dump with a registry error. I have already ran chkdsk on all affected
>> >drives with no luck. Any ideas??
>> >
>> >Josh
>> >IT Manager
>>
>> Most people here would be willing to try to help if you provided a clue, like
>> the exact error and STOP code and parameters.
>> See tip 726 in the 'Tips & Tricks' at http://www.jsiinc.com
>>
>> Jerold Schulman
>> Windows Server MVP
>> JSI, Inc.
>> http://www.jsiinc.com
>>


Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
!