Yoshi, can you give any more information about when it happens and under what circumstances. For example, is it while performing a specific task, or using a specific program? Have you added any new hardware or software just before it began?
The last BSOD was a Video TDR error and was a code 116 which is always a graphics error. What it means is the graphics driver crashed and did not recover in time, which is what a TDR error means (Time Delay and Response) This is quite common in laptops with switchable graphics and is usually caused when the drivers are switching between the Internal graphics and a dedicated GPU.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR]
[COLOR=red]Attempt to reset the display driver and recover from timeout failed.[/COLOR]
Arguments:
Arg1: fffffa801345d4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd23c84, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
One of the biggest problems is that each Vendor has specific implementation of the switching and almost all are a little different. In most cases, a driver from Nvidia does not seem to work.
The rest of yours that I checked were a stop code 9F, which is a driver power state failure and they list different drivers, but almost always, the graphics driver is listed somewhere.
Code:
iusb3xhc
start end module name
fffff880`0522f000 fffff880`052f3000 iusb3xhc T (no symbols)
Loaded symbol image file: iusb3xhc.sys
Image path: iusb3xhc.sys
Image name: iusb3xhc.sys
Timestamp: Thu Jan 05 05:54:45 2012 (4F058F85)
CheckSum: 000C5CCE
ImageSize: 000C4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
But later in the stack was
Code:
[COLOR=red]igdkmd64[/COLOR]
start end module name
fffff880`05009000 fffff880`053c2000 igdkmd64 T (no symbols)
Loaded symbol image file: igdkmd64.sys
Image path: igdkmd64.sys
Image name: igdkmd64.sys
Timestamp: Fri May 16 23:17:35 2014 (5376E2DF)
CheckSum: 0039E1ED
ImageSize: 003B9000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
That is your internal Graphics adaptor.
Also listed was a Windows Update driver which I believe was a victim and not a cause.
Code:
ACPI
start end module name
fffff880`00ee0000 fffff880`00f37000 ACPI (pdb symbols) c:\symcache\acpi.pdb\4CCAFC55779D45F49D63AD1C8D245D701\acpi.pdb
Loaded symbol image file: ACPI.sys
Mapped memory image file: c:\symcache\ACPI.sys\4CE7929457000\ACPI.sys
Image path: ACPI.sys
Image name: ACPI.sys
Timestamp: Sat Nov 20 03:19:16 2010 (4CE79294)
CheckSum: 0005ACF6
ImageSize: 00057000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ACPI.sys
OriginalFilename: ACPI.sys
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: ACPI Driver for NT
LegalCopyright: © Microsoft Corporation. All rights reserved.
Could you please do a clean install of both your dedicated graphics driver and your integrated graphics driver and see if that makes a difference in your problem?
Failing that is making a choice of whether to disable either your internal or dedicated graphics . The trade off is that your dedicated graphics will give you better graphics, but it will also cut down your battery life.
