BSOD After Installing AIDA64

boogieboy said:

I Just got a BSOD before and i have attached the Dump file. Everything was running absolutely fine before without any problems and im running my CPU on stock as well. When i installed AIDA64 and restarted my PC today and when i tried to went into the BIOS by pressing Del button i got "CPU Fan Error Press F1 to Resume" and i got into BIOS and everything was running fine. I then boot up in windows and after some mins i ran Assassin's Creed Brotherhood just to check if the CPU is ok so as soon as i tried to load the game from menu i got this BSOD PC restarted automatically and then i ran in safe mode and it gave me a error saying "Your system has recovered from a serious error" something like that. I uninstalled AIDA64 and restarted PC again from safe mode and now running windows again also tried AC: Brotherhood and it ran ok.

Also i downloaded Prime95 just after installing AIDA64 and i never used Prime95 before so when i opened it so it asked me a couple of things i just pressed ok and it started the stress test and i saw my CPU meter gadget gone 100% and right after few seconds i stopped the test and restarted PC to see into BIOS and got this CPU fan error first and then later which i have mentioned above. I wanted to OC my CPU today just to check but i did'nt even touched anything other than installing AIDA64 and running Prime95 for less then a minute. Please check and let me know what was wrong

Classic TDR video reset.

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\061711-17394-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;srv*e:\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`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Thu Jun 16 16:06:57.374 2011 (GMT-4)
System Uptime: 0 days 0:07:55.419
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800415f010, fffff88006a36cb0, 0, c}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+23cb0 )

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: fffffa800415f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006a36cb0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000c, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
igdkmd64+23cb0
fffff880`06a36cb0 4889542410      mov     qword ptr [rsp+10h],rdx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  ACBSP.exe

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0693e138 fffff880`07276000 : 00000000`00000116 fffffa80`0415f010 fffff880`06a36cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0693e140 fffff880`07275c7c : fffff880`06a36cb0 fffffa80`0415f010 fffffa80`0512e920 fffffa80`036d7010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0693e180 fffff880`0731cf07 : fffffa80`0415f010 00000000`0000770a fffffa80`0512e920 fffffa80`036d7010 : dxgkrnl!TdrIsRecoveryRequired+0x114
fffff880`0693e1b0 fffff880`0734ad5a : fffffa80`ffffffff 00000000`0000768a fffff880`0693e300 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0693e290 fffff880`07330bb1 : fffffa80`05626000 ffffffff`feced300 00000000`00000000 00000000`00000001 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0693e2d0 fffff880`0733d91c : 00000000`00005782 00000000`00000000 fffff880`0693e7d8 fffffa80`04188010 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`0693e3d0 fffff800`0332cd38 : ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0xe0
fffff880`0693e440 fffff880`0734294c : 00000000`19b40000 fffff880`0693e718 00000000`00000000 fffff8a0`00000002 : nt!MmRotatePhysicalView+0x6e8
fffff880`0693e680 fffff880`0733ceb8 : fffffa80`05626c60 00000000`00100000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0x148
fffff880`0693e710 fffff880`0732e904 : fffffa80`05135870 fffff8a0`02c69e50 fffffa80`05626c01 fffff880`0693e800 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x6f8
fffff880`0693e880 fffff880`0732e7e3 : fffffa80`05626000 fffff880`0732e6e8 00000000`00000000 fffffa80`03f30810 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x40
fffff880`0693e8c0 fffff880`0732b70d : 00000000`000001fc 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x43
fffff880`0693e910 fffff880`0734565d : 00000000`00000000 fffff8a0`020b96c0 fffffa80`00000000 fffffa80`03f30810 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xc79
fffff880`0693eae0 fffff880`07345398 : fffff800`043d9080 fffff880`07344d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0693ecd0 fffff880`07344e96 : 00000000`00000000 fffffa80`03f63920 00000000`00000080 fffffa80`036d7010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0693ed00 fffff800`03165166 : 00000000`017843ea fffffa80`05128b60 fffffa80`0366b9e0 fffffa80`05128b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0693ed40 fffff800`02ea0486 : fffff800`0303ae80 fffffa80`05128b60 fffff800`03048c40 fffff880`0124f534 : nt!PspSystemThreadStartup+0x5a
fffff880`0693ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd64+23cb0
fffff880`06a36cb0 4889542410      mov     qword ptr [rsp+10h],rdx

SYMBOL_NAME:  igdkmd64+23cb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a01d55b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

Followup: MachineOwner
---------