Daemon Tools, Alcohol 120% and Power Archiver Pro uses
SCSI Pass Through Direct (
SPTD), which is a well known BSOD causer. Uninstall
Daemon Tools at first. Then download SPTD standalone installer from
Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:
-
- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
A stop ox116 is a display/graphics related BSOD. And your display driver seems to be out of date.
Code:
Image name: atikmpag.sys
[COLOR=Red] Timestamp: Fri Mar 23 07:42:25 2012[/COLOR] (4F6BDC09)
Update your ATI/AMD display driver to the latest WHQL.
You can get it from the link in our forum,
http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to
AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.
During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.
Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of
Speccy.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Let us know the results.
_________________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800c10d4e0, fffff8800409c9f0, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+79f0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c10d4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800409c9f0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+79f0
fffff880`0409c9f0 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`093bd888 fffff880`04147140 : 00000000`00000116 fffffa80`0c10d4e0 fffff880`0409c9f0 00000000`00000000 : nt!KeBugCheckEx
fffff880`093bd890 fffff880`04146e4a : fffff880`0409c9f0 fffffa80`0c10d4e0 fffffa80`09e43910 fffffa80`0a3cd410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`093bd8d0 fffff880`0537bf13 : fffffa80`0c10d4e0 00000000`00000000 fffffa80`09e43910 fffffa80`0a3cd410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`093bd900 fffff880`053a5cf1 : 00000000`ffffffff 00000000`00100930 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`093bd9e0 fffff880`053a4437 : 00000000`00000102 00000000`0000000c 00000000`00100930 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`093bda10 fffff880`053772d2 : ffffffff`ff676980 fffffa80`0a3cd410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`093bdab0 fffff880`053a3ff6 : 00000000`00000000 fffffa80`07b97090 00000000`00000080 fffffa80`0a3cd410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`093bdbc0 fffff800`03b712ea : 00000000`fffffc32 fffffa80`0a3b6b50 fffffa80`06fdb040 fffffa80`0a3b6b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`093bdc00 fffff800`038c58e6 : fffff880`009c0180 fffffa80`0a3b6b50 fffff880`009cafc0 00000000`00000002 : nt!PspSystemThreadStartup+0x5a
fffff880`093bdc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+79f0
fffff880`0409c9f0 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+79f0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f6bdc09
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
3: kd> lmvm atikmpag
start end module name
fffff880`04095000 fffff880`040ea000 atikmpag T (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Mar 23 07:42:25 2012 (4F6BDC09)
CheckSum: 0005ABFC
ImageSize: 00055000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4