Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSSI\Downloads\Compressed\LEART-PC-Mon_03_30_2015_160423_66\033015-42546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c1b000 PsLoadedModuleList = 0x82d5b230
Debug session time: Mon Mar 30 19:25:20.199 2015 (UTC + 6:00)
System Uptime: 0 days 0:03:07.449
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 D4, {903e9cc8, 2, 1, 82c72188}
Probably caused by : atikmdag.sys ( atikmdag+3b6cc8 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD (d4)
A driver unloaded without cancelling lookaside lists, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
An attempt was made to access the driver at raised IRQL after it unloaded.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 903e9cc8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82c72188, address which referenced memory
Debugging Details:
------------------
FAULTING_IP:
atikmdag+3b6cc8
903e9cc8 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD4
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFFFFF80DE3000
STACK_TEXT:
80de2db4 82c72188 badb0d00 00000001 00000102 nt!KiTrap0E+0x2cf
80de2e34 82c75d1e 86c2ad60 80de2e74 80dc2120 nt!KiUnlinkWaitBlocks+0x41
80de2e50 82c72543 00000000 00000000 80dc3a80 nt!KiProcessThreadWaitList+0x26
80de2f38 82c72418 80dc2120 80de2f78 00000000 nt!KiProcessExpiredTimerList+0xe9
80de2fac 82c707ce 00002edc 9524da7c 00000000 nt!KiTimerExpiration+0x25c
80de2ff4 82c6ff9c 9524da2c 00000000 00000000 nt!KiRetireDpcList+0xcb
80de2ff8 9524da2c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82c6ff9c 00000000 0000001a 00d6850f bb830000 0x9524da2c
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmdag+3b6cc8
903e9cc8 ?? ???
SYMBOL_NAME: atikmdag+3b6cc8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0xD4_UNLOADED_MODULE_atikmdag+3b6cc8
BUCKET_ID: 0xD4_UNLOADED_MODULE_atikmdag+3b6cc8
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xd4_unloaded_module_atikmdag+3b6cc8
FAILURE_ID_HASH: {f16d10ce-fb49-43e6-5c34-1f523f462ba9}
Followup: MachineOwner
---------
1: kd> lmvm atikmdag
start end module name