New
#1
BSOD running when running intel driver update utility and more apps
hello sorry if my post isnt great im a newbie here but for some time now ive been getting BSODs and finally figured out how to debug it with WinDbg (x86) and set the symbols for windows but i cant read the text. ive tried reinstalling my GPU and Java but no luck. when i try to run intel driver update utility as soon as i run it i get a BSOD ive got the minidump here if anyone knows how to read it, so here you go.
Microsoft (R) Windows Debugger Version 6.2.8400.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\kalye\Desktop\081212-36504-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16988.x86fre.win7_gdr.120401-1505
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b7f810
Debug session time: Sun Aug 12 20:25:10.542 2012 (UTC - 7:00)
System Uptime: 0 days 1:07:15.119
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, b93e5810, b93e5810, 4c0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+336 )
Followup: Pool_corruption
---------
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: 00000003, the pool freelist is corrupt.
Arg2: b93e5810, the pool entry being checked.
Arg3: b93e5810, the read back flink freelist value (should be the same as 2).
Arg4: 000004c0, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82b568aa to 82b57996
STACK_TEXT:
8a703bc0 82b568aa 84a70000 00000000 86ff78c8 nt!ExDeferredFreePool+0x336
8a703c28 82a9dc72 b9621008 00000000 000c0000 nt!ExFreePoolWithTag+0x8a4
8a703c9c 82c68f6e 86ff7878 86ff7878 86ff78a0 nt!MiDeleteSegmentPages+0x313
8a703ccc 82a62f19 86ff7878 00000000 00000000 nt!MiSegmentDelete+0xec
8a703d28 82a62e31 84b0bab0 00000000 00000000 nt!MiProcessDereferenceList+0xdb
8a703d50 82c45ad1 00000000 aafd5366 00000000 nt!MiDereferenceSegmentThread+0xc5
8a703d90 82af7239 82a62d6a 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+336
82b57996 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+336
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: 0x19_3_nt!ExDeferredFreePool+336
BUCKET_ID: 0x19_3_nt!ExDeferredFreePool+336
Followup: Pool_corruption
---------