BSOD - REGISTRY_ERROR (51) - When logging into Server 2008 R2 Standard
Hi,
We have a server 2008 r2 standard box that is running Hyper-v. This box has been running fine until last week.
When I attempt to login to the box either at the console or using RDP it BSOD with REGISTRY_ERROR.
If I then power off/on it will boot successfully and the VMs running within Hyper-V all start fine. As soon as I attempt to login again same thing happens.
One fo the VMs is running a critical SQL application and I am vary of trying anything drastic until I now excatly what the issue is.
I have managed to remove a memory.dmp file from the server and have ran the windows debugger on it and get the following results...
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may 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.
Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a000023200, (reserved)
Arg3: 0000000000939000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 0000000000000374, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Any help or advise would be much appreciated.
Thanks
We have a server 2008 r2 standard box that is running Hyper-v. This box has been running fine until last week.
When I attempt to login to the box either at the console or using RDP it BSOD with REGISTRY_ERROR.
If I then power off/on it will boot successfully and the VMs running within Hyper-V all start fine. As soon as I attempt to login again same thing happens.
One fo the VMs is running a critical SQL application and I am vary of trying anything drastic until I now excatly what the issue is.
I have managed to remove a memory.dmp file from the server and have ran the windows debugger on it and get the following results...
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may 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.
Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a000023200, (reserved)
Arg3: 0000000000939000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 0000000000000374, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Any help or advise would be much appreciated.
Thanks
ASKER
Hi,
Attached is the detail returned from debugger.
I have copied the DMP from the 2008 r2 server onto my local Windows 7 desktop.
Installed 64bit Debugger and windows7\Server 2008 r2 symbols.
Full-Debug.txt
If you could have a look and see what you think.
Thanks
Attached is the detail returned from debugger.
I have copied the DMP from the 2008 r2 server onto my local Windows 7 desktop.
Installed 64bit Debugger and windows7\Server 2008 r2 symbols.
Full-Debug.txt
If you could have a look and see what you think.
Thanks
it has "THIS DUMP FILE IS PARTIALLY CORRUPT" all over!
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE. i'd say again disk problem. backup / checkdisk (only with that order!)
good luck.
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE. i'd say again disk problem. backup / checkdisk (only with that order!)
good luck.
Check the pagefile location once and try to debug again. Its something pagefile corruption msg...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looks like faulting NIC drives may have caused the issue.
backup and checkdisk .
do you have symbols for srv2008? not many details in your dmp.
please feedback