Re: [OT?] Found bug in Windows 2000 registry code

At 14.47 06/02/2002, you wrote:

> STOP: 0x00000051 ( 0x0000000C, 0xC0000005, 0xBE2EDB78, 0xBE2ED70 )
> REGISTRY_ERROR
> as I can afford neither a second machine nor SoftIce. I hope that all those
> funny numbers have some meaning
Install the latest Windbg. It comes with full and latest documentation for
your funny numbers.

ok, found:

"Bug Check 0x51: REGISTRY_ERROR
The REGISTRY_ERROR bug check has value 0x00000051. This bug check indicates
that a severe registry error has occurred.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description

1 Reserved
2 Reserved
3 The pointer to the hive (if available)
4 If the hive is corrupt, the return code of HvCheckHive (if
available)

Cause
Something has gone badly wrong with the registry. If a kernel debugger is
available, get a stack trace.

This error may indicate that the registry encountered an I/O error while
trying to read one of its files. This can be caused by hardware problems or
file system corruption.

It may also occur due to a failure in a refresh operation, which is used
only in by the security system, and then only when resource limits are
encountered."

To me it's clearly a bug. My registry is intact, even after two abnormal
halts, and I see no reason why resource limits should be encountered

The question remains: is there something like xxxxx@microsoft.com?

PS: BTW: "Bug Check 0xDEADDEAD: MANUALLY_INITIATED_CRASH1". ROTFL on
0xDEADDEAD :-)))


You are currently subscribed to ntdev as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-ntdev-$subst('Recip.MemberIDChar')@lists.osr.com