0x51 Registry_error

G

Guest

Hi,

OK - before I start, I know *how* to fix this (reimage, or repair). What I
want to know is *why* this is happening - it's eating all my time at work
now, and becoming very annoying. I'm after suggestions, however ridiculous.
I'll try anything ;)

The symptom:
- XP (any service pack) Machines on our network (Win2k Domain) seem to
randomly develop a stop error. 0x00000051 REGISTRY_ERROR. When this
happens, it's terminal - the machine stops, then reboots, stops, then
reboots, over and over until we reimage it.

This happens on any of our XP machines, regardless of manufacturer,
regardless of date of purchase (we just got 52 new machines, it happens on
them too), regardless of specification. It happens more often on NTFS
drives, but it *can* happen on FAT32 drives too - albeit much more
infrequently.

The FAT32 machines we have (20 or so) always seem to do a disk check when
they boot up (regardless of whether or not the machine was shut down
correctly). Now, recently, one of these FAT32 machines had a stuck key that
was causing the machine to skip the disk check - shortly thereafter, it
developed an 0x00000051 REGISTRY_ERROR.

Being FAT32, we were able to boot from a DOS boot disk, and run scandisk -
and it >FIXED IT<. It booted again. If only we could do that on NTFS
machines, eh?

I analysed the crash dump from the FAT32 machine with windbg, and didn't
find anything of interest. Similarly, there was nothing in the event log
either (except a record of the bugcheck, which I'll paste):

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000051
(0x00000003, 0x00000001, 0x00003000, 0xe178f030).

My question is: Why on earth would this be happening? Surely we can't be
the only people in the world this happens to, can we? Does anyone have any
suggestions, or pointers, or vaguely related anecdotes?

Any help *greatly* appreciated.

Neil.
 
C

Carey Frisch [MVP]

List of base operating system fixes in Windows XP Service Pack 2
http://support.microsoft.com/kb/838213/EN-US/

TROUBLESHOOTING WINDOWS STOP MESSAGES
http://aumha.org/win5/kbestop.php

How to troubleshoot a "STOP 0x00000051 REGISTRY ERROR" error message
http://support.microsoft.com/kb/282501/

"STOP 0x00000051" or "STOP 0x0000001E" error message when you start
Configuration Manager in Windows 2000 Server or in Windows XP
http://support.microsoft.com/?kbid=815265

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

:

| Hi,
|
| OK - before I start, I know *how* to fix this (reimage, or repair). What I
| want to know is *why* this is happening - it's eating all my time at work
| now, and becoming very annoying. I'm after suggestions, however ridiculous.
| I'll try anything ;)
|
| The symptom:
| - XP (any service pack) Machines on our network (Win2k Domain) seem to
| randomly develop a stop error. 0x00000051 REGISTRY_ERROR. When this
| happens, it's terminal - the machine stops, then reboots, stops, then
| reboots, over and over until we reimage it.
|
| This happens on any of our XP machines, regardless of manufacturer,
| regardless of date of purchase (we just got 52 new machines, it happens on
| them too), regardless of specification. It happens more often on NTFS
| drives, but it *can* happen on FAT32 drives too - albeit much more
| infrequently.
|
| The FAT32 machines we have (20 or so) always seem to do a disk check when
| they boot up (regardless of whether or not the machine was shut down
| correctly). Now, recently, one of these FAT32 machines had a stuck key that
| was causing the machine to skip the disk check - shortly thereafter, it
| developed an 0x00000051 REGISTRY_ERROR.
|
| Being FAT32, we were able to boot from a DOS boot disk, and run scandisk -
| and it >FIXED IT<. It booted again. If only we could do that on NTFS
| machines, eh?
|
| I analysed the crash dump from the FAT32 machine with windbg, and didn't
| find anything of interest. Similarly, there was nothing in the event log
| either (except a record of the bugcheck, which I'll paste):
|
| The computer has rebooted from a bugcheck. The bugcheck was: 0x00000051
| (0x00000003, 0x00000001, 0x00003000, 0xe178f030).
|
| My question is: Why on earth would this be happening? Surely we can't be
| the only people in the world this happens to, can we? Does anyone have any
| suggestions, or pointers, or vaguely related anecdotes?
|
| Any help *greatly* appreciated.
|
| Neil.
 
G

Guest

Hi,

Thanks for the response.

Most of the machines already have XPSP2, and the issue still occurs.

The list of stop errors (http://aumha.org/win5/kbestop.php) is something
I've looked at already, and done everything it suggests at the top, and
checked all the Microsoft support links, none of which apply.

http://support.microsoft.com/kb/282501/ <-- We don't have an emergency
repair disk - we haven't just installed new hardware - the hardware is
compatible with the HCL - we have RAM far in excess of the requirements and
Last Known Good crashes out with 0x51, as do the recovery console and repair
options on the XP CD.

As for the final link, it doesn't seem to apply.

Thanks,
Neil.
 
C

Carey Frisch [MVP]

You may wish to contact Microsoft support directly:
http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=3518&gprid=185522

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

:

| Hi,
|
| Thanks for the response.
|
| Most of the machines already have XPSP2, and the issue still occurs.
|
| The list of stop errors (http://aumha.org/win5/kbestop.php) is something
| I've looked at already, and done everything it suggests at the top, and
| checked all the Microsoft support links, none of which apply.
|
| http://support.microsoft.com/kb/282501/ <-- We don't have an emergency
| repair disk - we haven't just installed new hardware - the hardware is
| compatible with the HCL - we have RAM far in excess of the requirements and
| Last Known Good crashes out with 0x51, as do the recovery console and repair
| options on the XP CD.
|
| As for the final link, it doesn't seem to apply.
|
| Thanks,
| Neil.
 
G

Guest

I use my Dell computer at home and have run into this same problem. However,
I have no idea how to fix it. Were you able to resolve the issue with
Microsoft? Any help you can offer would be greatly appreciated!

Sue
 
G

Guest

Thanks for the suggestion. However, if I can't boot the computer, I can't
load the drivers ... I have already called Dell and they want $99 to talk to
me. When I dida live chat with the Dell Hardware folks, they said it is a
Windows problem ... I really hate this finger-pointing to the other company!
I just want to be able to use my PC!
 
G

Guest

So sorry ... I spoke too soon. I went to the dell site and it looks like I
might be able to do this ... thanks very much for the suggestion.

Sue
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top