Что-то зачастили бсоды BAD POOL HEADER, почти каждый день стали вылазить. По инструкциям открыл минидамп программой WinDbg, не могу в её выводе разобраться, в чём проблема. В примерах в интернете в строке "Probably caused by" явно указан проблемный драйвер, а у меня там: "Probably caused by : Pool_Corruption ( nt!ExFreePool+bb4 )", а на это гугл ничего вразумительного не пишет. В чём может быть дело? Кто-нибудь сталкивался?
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030415-49781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff803`c6405000 PsLoadedModuleList = 0xfffff803`c66de250
Debug session time: Wed Mar 4 18:50:23.338 2015 (UTC + 8:00)
System Uptime: 0 days 2:09:32.059
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {d, ffffd0002269a230, 122a5321b6, 6e6c467c6b48af62}
Probably caused by : Pool_Corruption ( nt!ExFreePool+bb4 )
Followup: Pool_corruption
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 000000000000000d,
Arg2: ffffd0002269a230
Arg3: 000000122a5321b6
Arg4: 6e6c467c6b48af62
Debugging Details:
------------------
BUGCHECK_STR: 0x19_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff803c66aa8a0 to fffff803c65559a0
STACK_TEXT:
ffffd000`3290b4e8 fffff803`c66aa8a0 : 00000000`00000019 00000000`0000000d ffffd000`2269a230 00000012`2a5321b6 : nt!KeBugCheckEx
ffffd000`3290b4f0 fffff803`c66a884e : ffffe000`3a605010 ffffe000`3d297c60 00000000`00000000 00000000`00000002 : nt!ExFreePool+0xbb4
ffffd000`3290b570 fffff803`c6509c7b : 00000000`00000001 ffffd000`3290b760 ffffc001`c6d8c1f8 ffffc001`00000024 : nt!ExFreePoolWithTag+0x84e
ffffd000`3290b660 fffff803`c6490665 : 00000000`00000000 ffffd000`24f76a78 ffffe000`3ddfcd5c ffffe000`3ddfcd40 : nt!MiFlushSectionInternal+0x653
ffffd000`3290b870 fffff803`c643d41b : 00000000`00079709 00000000`00000000 00000000`00100000 7ffff803`c6761000 : nt!MmFlushSection+0xa9
ffffd000`3290b930 fffff803`c643db3b : ffffe000`3a398a68 00000000`00000000 ffffe000`00000001 00000000`00000000 : nt!CcFlushCachePriv+0x493
ffffd000`3290ba40 fffff803`c64b03ac : ffffe000`3c98c640 ffffe000`3b567101 ffffe000`00000000 00000000`00004f26 : nt!CcWriteBehindInternal+0x17b
ffffd000`3290bad0 fffff803`c64dd280 : fffff803`c6761a00 ffffe000`3b567040 00000000`00000080 ffffe000`3b567040 : nt!ExpWorkerThread+0x28c
ffffd000`3290bb80 fffff803`c655bfc6 : fffff803`c6708180 ffffe000`3b567040 fffff803`c6761a00 ffffc001`b580bb80 : nt!PspSystemThreadStartup+0x58
ffffd000`3290bbe0 00000000`00000000 : ffffd000`3290c000 ffffd000`32905000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+bb4
fffff803`c66aa8a0 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+bb4
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 6.3.9600.17630
MODULE_NAME: Pool_Corruption
BUCKET_ID_FUNC_OFFSET: bb4
FAILURE_BUCKET_ID: 0x19_d_nt!ExFreePool
BUCKET_ID: 0x19_d_nt!ExFreePool
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x19_d_nt!exfreepool
FAILURE_ID_HASH: {26ec571f-9df1-2f7e-a60a-2144f95f5f9f}
Followup: Pool_corruption
---------
3: kd> lmvm Pool_Corruption
start end module name