Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\Desktop\033010-21824-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 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02850000 PsLoadedModuleList = 0xfffff800`02a8de50
Debug session time: Mon Mar 29 18:33:24.661 2010 (GMT-4)
System Uptime: 0 days 22:00:27.378
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {22, fffff8a000d12000, 1, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : atipmdag.sys ( atipmdag+277a8 )
Followup: MachineOwner
---------
0: 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: 0000000000000022,
Arg2: fffff8a000d12000
Arg3: 0000000000000001
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x19_22
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af80e0
fffff8a000d12000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002919330 to fffff800028c1f00
STACK_TEXT:
fffff880`031cb288 fffff800`02919330 : 00000000`00000019 00000000`00000022 fffff8a0`00d12000 00000000`00000001 : nt!KeBugCheckEx
fffff880`031cb290 fffff800`029f5518 : 00000000`00000000 fffff880`031cb3e0 fffff880`031cb350 fffff8a0`00000001 : nt! ?? ::FNODOBFM::`string'+0x7338
fffff880`031cb320 fffff880`048507a8 : 00000000`00000000 fffffa80`04a6f000 00000000`00000001 fffffa80`00000001 : nt!ExFreePoolWithTag+0x468
fffff880`031cb3d0 00000000`00000000 : fffffa80`04a6f000 00000000`00000001 fffffa80`00000001 00000000`00000002 : atipmdag+0x277a8
STACK_COMMAND: kb
FOLLOWUP_IP:
atipmdag+277a8
fffff880`048507a8 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: atipmdag+277a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atipmdag
IMAGE_NAME: atipmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b733006
FAILURE_BUCKET_ID: X64_0x19_22_atipmdag+277a8
BUCKET_ID: X64_0x19_22_atipmdag+277a8
Followup: MachineOwner
---------