SF diagnostic tool info ZIP attached.
After logging in, about 10-20sec later, I get a BSOD with 0x51 REGISTRY_ERROR.
I do not have a system restore point.
I have tried most of all of the things found when googling this: chkdsk, ccleaner, scf /scannow, etc...
Starts up fine in safe mode. I tried turning off all services and startups and still crashes.
Thanks in advance.
More info:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 51
BCP1: 0000000000000001
BCP2: FFFFF8A000024010
BCP3: 0000000001877000
BCP4: 0000000000000374
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Also ran TDSSKiller and it came up with no threats.
More info from osronline.com (analysis of my .dmp file). I do not know how to interpret this. Thanks in advance:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0360c000 PsLoadedModuleList = 0xfffff800`0384f890
Debug session time: Tue Nov 25 16:59:54.174 2014 (UTC - 5:00)
System Uptime: 0 days 0:12:24.033
*******************************************************************************
* *
* 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: 0000000000000001, (reserved)
Arg2: fffff8a000024010, (reserved)
Arg3: 0000000001877000, 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.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x51
PROCESS_NAME: services.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800039b2158 to fffff80003681bc0
STACK_TEXT:
fffff880`0d0b72f8 fffff800`039b2158 : 00000000`00000051 00000000`00000001 fffff8a0`00024010 00000000`01877000 : nt!KeBugCheckEx
fffff880`0d0b7300 fffff800`0391ac95 : 00000000`0001c887 00000000`0000c3b7 00000000`000073bf fffff8a0`00000004 : nt! ?? ::NNGAKEGL::`string'+0x9d9a
fffff880`0d0b7360 fffff800`0391aa6c : fffff8a0`00024010 fffff8a0`00024010 fffff8a0`00033cc0 00000000`000e6b76 : nt!HvMarkDirty+0x176
fffff880`0d0b73c0 fffff800`038de01b : 00000000`00000001 fffff8a0`083fc15c fffff8a0`085e8b54 fffff8a0`00024010 : nt!HvMarkCellDirty+0x150
fffff880`0d0b7410 fffff800`038dddf4 : fffff8a0`085e8b54 00000000`ffffffff fffff8a0`085e8b54 fffff8a0`00024010 : nt!CmpMarkKeyValuesDirty+0x14b
fffff880`0d0b74b0 fffff800`038dd4fa : fffff8a0`00024010 00000000`ffffffff fffff8a0`085e8b54 fffff8a0`00024010 : nt!CmpFreeKeyValues+0x24
fffff880`0d0b74e0 fffff800`038dd228 : fffff8a0`00024010 00000000`00e27bc8 fffff8a0`085e8b54 fffff8a0`00e77b50 : nt!CmpSyncKeyValues+0x7a
fffff880`0d0b75c0 fffff800`038df4de : fffff8a0`1596c000 00000000`003fa3b8 fffffa80`00000000 00000000`00000000 : nt!CmpCopySyncTree2+0x2a8
fffff880`0d0b7670 fffff800`038df3f7 : 00000000`00000000 00000000`00000002 fffff8a0`06236e20 fffff8a0`1562b6b0 : nt!CmpCopySyncTree+0x6e
fffff880`0d0b76c0 fffff800`038defc6 : fffff8a0`1524b360 00000000`00000000 00000000`00000001 00000000`00000000 : nt!CmpSaveBootControlSet+0x307
fffff880`0d0b78a0 fffff800`03680e53 : fffffa80`15292060 00000000`00000000 fffff880`0d0b7970 00000000`00000001 : nt!NtInitializeRegistry+0xc6
fffff880`0d0b78f0 fffff800`0367d410 : fffff800`038def6f 00000000`00000220 00000000`0134e6a8 00000000`0134e9d8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0d0b7a88 fffff800`038def6f : 00000000`00000220 00000000`0134e6a8 00000000`0134e9d8 00000000`000a001f : nt!KiServiceLinkage
fffff880`0d0b7a90 fffff800`03680e53 : fffffa80`15292060 fffff880`0d0b7b60 fffff880`0d0b7b60 00000000`00000002 : nt!NtInitializeRegistry+0x6f
fffff880`0d0b7ae0 00000000`778f205a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0134e958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778f205a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+9d9a
fffff800`039b2158 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+9d9a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
FAILURE_BUCKET_ID: X64_0x51_nt!_??_::NNGAKEGL::_string_+9d9a
BUCKET_ID: X64_0x51_nt!_??_::NNGAKEGL::_string_+9d9a
Followup: MachineOwner
---------
Also, full computer diagnostic (memory, disk, etc) came up negative.
Quote