Häufig BSOD Registry Error (nach KB3093266 ?)

Seit einigen Tagen habe ich gehäuft BSOD - Registry Error. Es hat nach der Installation von KB3093266 begonnen, ein zufälliges Zusammentreffen des Zeitpunkts ist sehr unwahrscheinlich, da ich um diese Zeit keine andere Software installiert habe.

Gefühlsmäßig tritt das Problem gehäuft dann auf, wenn der PC alleine läuft (ich habe es noch nie bemerkt solange ich aktiv arbeite, auch mehrere Stunden), nach 5 Minuten oder 1 Stunde, kommt aber sicher.


Aus dem Memory Dump:


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16515.amd64fre.th1.150916-2039
Machine Name:
Kernel base = 0xfffff800`efc11000 PsLoadedModuleList = 0xfffff800`eff36010
Debug session time: Mon Oct 12 21:05:25.875 2015 (UTC + 2:00)
System Uptime: 0 days 2:51:59.568
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`eb90e018). Type ".hh dbgerr001" for details
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {1, ffffc0001a6fd000, 92b37b87, 2d2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+52ada )

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

2: 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: 0000000000000001, (reserved)
Arg2: ffffc0001a6fd000, (reserved)
Arg3: 0000000092b37b87, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000000000002d2, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.

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


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x51

PROCESS_NAME: ngen.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800f021682a to fffff800efd5f240

STACK_TEXT:
ffffd001`bb146798 fffff800`f021682a : 00000000`00000051 00000000`00000001 ffffc000`1a6fd000 00000000`92b37b87 : nt!KeBugCheckEx
ffffd001`bb1467a0 fffff800`f00da610 : ffffc000`2a4cf980 ffffd001`bb146870 ffffc000`2a4cf980 ffffc000`00000004 : nt! ?? ::NNGAKEGL::`string'+0x52ada
ffffd001`bb146810 fffff800`f00d9cc5 : ffffc000`1a6fd000 ffffc000`1a6fd000 ffffc000`00000000 ffffc000`1a6fd000 : nt!HvFreeCell+0x1bc
ffffd001`bb1468b0 fffff800`f00d8eaf : ffffe000`ffffffff 00000000`00000000 00000000`ffffff01 00000000`00000000 : nt!CmpFreeValue+0x49
ffffd001`bb1468e0 fffff800`f006d3b5 : 01d10520`07208588 01d10520`f3dad477 ffffd001`bb1469a9 00000000`ffffffff : nt!CmpFreeKeyByCell+0x117
ffffd001`bb146940 fffff800`f006d0d1 : ffffc000`2e6914d0 ffffd001`00000001 ffffd001`bb146a01 00000000`ffffffff : nt!CmDeleteKey+0x211
ffffd001`bb146a10 fffff800`efd69863 : ffffe000`cdfad080 ffffe000`cdfad080 00000000`00000228 00000000`00000000 : nt!NtDeleteKey+0x2a1
ffffd001`bb146b00 00007ff9`d3bc414a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000043`2640e4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`d3bc414a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+52ada
fffff800`f021682a cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+52ada

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 55fa569b

BUCKET_ID_FUNC_OFFSET: 52ada

FAILURE_BUCKET_ID: 0x51_nt!_??_::NNGAKEGL::_string_

BUCKET_ID: 0x51_nt!_??_::NNGAKEGL::_string_

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x51_nt!_??_::nngakegl::_string_

FAILURE_ID_HASH: {e5bde1d4-9584-25e7-f283-f0bca450261c}

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

Weiterlesen...