BSOD Registry Error 0x51

Hello,

We have been experiencing BSOD's periodically. We run server 2003 sp2 standard as vm guest on a server 2008r2 machine. I've installed windbg and have pasted the output. Any help would be appreciated. Thank you.

Mike

Loading Dump File [C:\WINDOWS\Minidump\Mini042513-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Thu Apr 25 13:52:16.443 2013 (UTC - 7:00)
System Uptime: 7 days 18:17:52.549
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {3, 1, 3366000, d7465660}

Probably caused by : ntoskrnl.exe ( nt!KiServiceTable+1f7 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 00000003, (reserved)
Arg2: 00000001, (reserved)
Arg3: 03366000, depends on where Windows bugchecked, may be pointer to hive
Arg4: d7465660, depends on where Windows bugchecked, may be return code of
    HvCheckHive if the hive is corrupt.

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0x51

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 808bdc00 to 80827cb3

STACK_TEXT: 
f7906c94 808bdc00 00000051 00000003 00000001 nt!KiServiceTable+0x1f7
f7906ccc 808bf358 d72d8a80 00019b30 f7906d18 nt!PpIrpQueryID+0x4d
f7906d28 808bfd33 00000002 d72d8a80 d72d8d78 nt!IopSetDeviceSecurityDescriptors+0xd
f7906d3c 808c1281 d72d8a01 8b17dda8 808a4828 nt!ArbpUpdatePriority+0xc7
f7906d58 808ca9d3 00000000 d72d8d78 f7906d78 nt!IopSetLegacyDeviceInstance+0xc0
f7906d80 808804eb 00000000 00000000 8b17dda8 nt!NtSetSystemInformation+0x94e
f7906dac 80949c7e 00000000 00000000 00000000 nt!MiDbgTranslatePhysicalAddress+0x1e
f7906ddc 8088e132 80880400 00000001 00000000 nt!IopDeleteLegacyKey+0x1ea
f7906de8 00000000 0000027f 00000000 00000000 nt!ExReleaseRundownProtectionCacheAwareEx+0x1f


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiServiceTable+1f7
80827cb3 5d              pop     ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiServiceTable+1f7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50ea1ab7

FAILURE_BUCKET_ID:  0x51_nt!KiServiceTable+1f7

BUCKET_ID:  0x51_nt!KiServiceTable+1f7

Followup: MachineOwner
---------


|

Hi Mike,

 

The Microsoft Answers community focuses on the consumer environment. Please reach out to the IT Professional community in the TechNet forum linked below:

Refer to the link.

http://social.technet.microsoft.com/forums/en-us/category/windowsserver

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated August 24, 2021 Views 1,057 Applies to: