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.
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.