The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Alienware m17x r4 BSOD, repeating, after reinstall

    Discussion in 'Alienware 17 and M17x' started by naldor, Aug 10, 2012.

  1. naldor

    naldor Notebook Consultant

    Reputations:
    162
    Messages:
    117
    Likes Received:
    27
    Trophy Points:
    41
    Hej, I am having like every 1 or 2 houers a bluescreen, did I miss up my drivers twice? I have an m17x r4 3610qm, hd 7970m, is my gpu having hardware failure? Could some1 please look in my dump file? Thank you in advance!!!

    View attachment dmp files.zip
     
    naldor, Aug 10, 2012
    #1
  2. naldor

    naldor Notebook Consultant

    Reputations:
    162
    Messages:
    117
    Likes Received:
    27
    Trophy Points:
    41
    Updated, attached dmp files after few failures ;P
     
    naldor, Aug 10, 2012
    #2
  3. MickyD1234

    MickyD1234 Notebook Prophet

    Reputations:
    3,159
    Messages:
    6,473
    Likes Received:
    1,165
    Trophy Points:
    331
    They are all the same, except the last two. One that states 'user initiated' and one saying 'plug and play'

    Looks like you're correct about the video drivers. Try a complete removal and reinstall using the dell ones before trying any later versions?

    On Mon 06/08/2012 16:50:44 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\080612-29281-01.dmp
    This was probably caused by the following module: atikmpag.sys (atikmpag+0x8FD8)
    Bugcheck code: 0x116 (0xFFFFFA8006C0E360, 0xFFFFF8800754EFD8, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys .
    Google query: atikmpag.sys VIDEO_TDR_ERROR

    I've seen this exact problem with NV as well, seems to be a problem with the video driver interacting with the hardware and is specific to windows versions later than XP. MS changed the HAL. You can find registry hacks to increase the timeout but this will just stop the bluescreen, you will still get an error. Better to find the root cause ;)

    Good Luck.
     
    MickyD1234, Aug 11, 2012
    #3
  4. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    Here are your dump files in order as they happened. I'll include my suggested steps after each.

    BSOD #1 from Sat Jul 21 07:12:08.891 2012 (UTC - 4:00)
    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {f010012, 1d10e1, 12bc0000, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Netwsw00.sys ( Netwsw00+92af8 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MANUALLY_INITIATED_CRASH1 (deaddead)
The user manually initiated this crash dump.
Arguments:
Arg1: 000000000f010012
Arg2: 00000000001d10e1
Arg3: 0000000012bc0000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xDEADDEAD

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff880094b9af8 to fffff8000349a1c0

STACK_TEXT: 
fffff800`00b9c258 fffff880`094b9af8 : 00000000`deaddead 00000000`0f010012 00000000`001d10e1 00000000`12bc0000 : nt!KeBugCheckEx
fffff800`00b9c260 00000000`deaddead : 00000000`0f010012 00000000`001d10e1 00000000`12bc0000 00000000`00000000 : Netwsw00+0x92af8
fffff800`00b9c268 00000000`0f010012 : 00000000`001d10e1 00000000`12bc0000 00000000`00000000 00000000`000007ff : 0xdeaddead
fffff800`00b9c270 00000000`001d10e1 : 00000000`12bc0000 00000000`00000000 00000000`000007ff 00000000`00000000 : 0xf010012
fffff800`00b9c278 00000000`12bc0000 : 00000000`00000000 00000000`000007ff 00000000`00000000 00000000`00000000 : 0x1d10e1
fffff800`00b9c280 00000000`00000000 : 00000000`000007ff 00000000`00000000 00000000`00000000 00000000`00000000 : 0x12bc0000


STACK_COMMAND:  kb

FOLLOWUP_IP:
Netwsw00+92af8
fffff880`094b9af8 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Netwsw00+92af8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Netwsw00

IMAGE_NAME:  Netwsw00.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f42904f

FAILURE_BUCKET_ID:  X64_0xDEADDEAD_Netwsw00+92af8

BUCKET_ID:  X64_0xDEADDEAD_Netwsw00+92af8

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

0: kd> lmvm Netwsw00
start             end                 module name
fffff880`09427000 fffff880`09f6b000   Netwsw00 T (no symbols)          
    Loaded symbol image file: Netwsw00.sys
    Image path: \SystemRoot\system32\DRIVERS\Netwsw00.sys
    Image name: Netwsw00.sys
    Timestamp:        Mon Feb 20 13:26:23 2012 (4F42904F)
    CheckSum:         00AF64AA
    ImageSize:        00B44000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Bugcheck code 0xDEADDEAD indicates MANUALLY_INITIATED_CRASH1 meaning the BSOD was trigger manually either through the kernel or using a keystroke. More info here: Bug Check 0xDEADDEAD: MANUALLY_INITIATED_CRASH1. In the dump, it mentioned that the faulting driver was Netwsw00.sys which is the Intel WiFi adapter driver. Please see if there is an updated version. If not, reinstall the driver.
    ----------------------------------
    BSOD #2 from Wed Aug 1 17:43:14.128 2012 (UTC - 4:00)
    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CA, {b, fffffa800a1fc050, 3, 0}

*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : iaStor.sys

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 000000000000000b, Deleted PDO reported as relation
	One of the removal relations for the device being removed has
	already been deleted.
Arg2: fffffa800a1fc050, Related PDO
Arg3: 0000000000000003, Removal relations
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xCA_B

DEVICE_OBJECT: fffffa800a1fc050

DRIVER_OBJECT: fffffa80064d6060

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ed5a567

MODULE_NAME: iaStor

FAULTING_MODULE: fffff88001250000 iaStor

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800038c58a3 to fffff8000348b1c0

STACK_TEXT: 
fffff880`039697f8 fffff800`038c58a3 : 00000000`000000ca 00000000`0000000b fffffa80`0a1fc050 00000000`00000003 : nt!KeBugCheckEx
fffff880`03969800 fffff800`038c5701 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff880`03969af8 : nt!PnpProcessRelation+0x473
fffff880`03969870 fffff800`038c5701 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff880`03969af8 : nt!PnpProcessRelation+0x2d1
fffff880`039698e0 fffff800`038c61c9 : 00000000`00000002 fffff880`00000002 fffff880`00000001 fffff880`03969af8 : nt!PnpProcessRelation+0x2d1
fffff880`03969950 fffff800`03901455 : 00000000`00000000 fffffa80`09430d90 fffff8a0`0dda2bf0 fffff880`03969b78 : nt!PnpBuildRemovalRelationList+0x69
fffff880`039699a0 fffff800`039023bc : fffff880`03969b78 00000000`00000000 fffff8a0`0cdfd010 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x325
fffff880`03969ae0 fffff800`037eb64e : 00000000`00000000 fffffa80`0a599380 fffff8a0`0dda2bf0 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`03969b10 fffff800`03494841 : fffff800`036f0760 fffff8a0`0dda2bf0 fffff800`036282d8 9f74b23f`807c2dd9 : nt! ?? ::NNGAKEGL::`string'+0x5ab8b
fffff880`03969b70 fffff800`03721e6a : c0f8e1a5`aedf8f0f fffffa80`05b44b50 00000000`00000080 fffffa80`05a73b30 : nt!ExpWorkerThread+0x111
fffff880`03969c00 fffff800`0347bec6 : fffff880`03774180 fffffa80`05b44b50 fffff880`0377f0c0 35a8b9c5`1a8e27dd : nt!PspSystemThreadStartup+0x5a
fffff880`03969c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xCA_B_IMAGE_iaStor.sys

BUCKET_ID:  X64_0xCA_B_IMAGE_iaStor.sys

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

4: kd> !devobj fffffa800a1fc050 f
fffff80003632fb0: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800a1fc050) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\iaStor DriverObject fffffa80064d6060
Current Irp 00000000 RefCount 0 Type 0000002d Flags 00005050
DevExt fffffa800a1fc1a0 DevObjExt fffffa800a1fd310
ExtensionFlags (0x00000800) 
                             Unknown flags 0x00000800
Device queue is not busy.
4: kd> !drvobj fffffa80064d6060 f
fffff80003632fb0: Unable to get value of ObpRootDirectoryObject
fffff80003632fb0: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa80064d6060) is for:
 \Driver\iaStor
Driver Extension List: (id , addr)

Device Object list:
fffffa800a1fc050  fffffa8006ba4050: Could not read device object


DriverEntry:   fffff880015ef008	iaStor
DriverStartIo: 00000000	
DriverUnload:  fffff8800127d704	iaStor
AddDevice:     00000000	

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff8800127e048	iaStor+0x2e048
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff80003470100	nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE                       fffff8800127e048	iaStor+0x2e048
[03] IRP_MJ_READ                        fffff80003470100	nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE                       fffff80003470100	nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION           fffff80003470100	nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION             fffff80003470100	nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA                    fffff80003470100	nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA                      fffff80003470100	nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS               fffff80003470100	nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff80003470100	nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff80003470100	nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff80003470100	nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff80003470100	nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL              fffff8800129cc50	iaStor+0x4cc50
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff880012a1168	iaStor+0x51168
[10] IRP_MJ_SHUTDOWN                    fffff880012c5df0	iaStor+0x75df0
[11] IRP_MJ_LOCK_CONTROL                fffff80003470100	nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP                     fffff80003470100	nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT             fffff80003470100	nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY              fffff80003470100	nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY                fffff80003470100	nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER                       fffff880012c4ee8	iaStor+0x74ee8
[17] IRP_MJ_SYSTEM_CONTROL              fffff880012c5f28	iaStor+0x75f28
[18] IRP_MJ_DEVICE_CHANGE               fffff80003470100	nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA                 fffff80003470100	nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA                   fffff80003470100	nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP                         fffff880012c27f8	iaStor+0x727f8

4: kd> lmvm iaStor
start             end                 module name
fffff880`01250000 fffff880`015f4000   iaStor   T (no symbols)          
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Tue Nov 29 22:39:19 2011 (4ED5A567)
    CheckSum:         0009778C
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Bugcheck code 0xCA indicates PNP_DETECTED_FATAL_ERROR which means the BSOD was triggered by an error with the plug and play manager. This is usually caused by a driver issue. In this case it was caused by iastor.sys which is your Intel Matrix Storage Manager. Please update this driver in safe mode using Intel® Driver Update Utility. If the driver is up to date, reinstall it.
    -----------------------------------------------
    BSOD #3,4,5 from Mon Aug 6 12:50:44.813 2012 (UTC - 4:00), Thu Aug 9 06:48:06.813 2012 (UTC - 4:00), and Thu Aug 9 17:50:27.475 2012 (UTC - 4:00)
    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006c0e360, fffff8800754efd8, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+8fd8 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006c0e360, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800754efd8, 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+8fd8
fffff880`0754efd8 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`0c5aa888 fffff880`10562000 : 00000000`00000116 fffffa80`06c0e360 fffff880`0754efd8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c5aa890 fffff880`10561d0a : fffff880`0754efd8 fffffa80`06c0e360 fffffa80`0bdc6010 fffffa80`0b760010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0c5aa8d0 fffff880`0f60ff07 : fffffa80`06c0e360 00000000`00000000 fffffa80`0bdc6010 fffffa80`0b760010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0c5aa900 fffff880`0f639b75 : 00000000`ffffffff 00000000`0008cd59 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0c5aa9e0 fffff880`0f6382bb : 00000000`00000102 00000000`00000008 00000000`0008cd59 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0c5aaa10 fffff880`0f60b2c6 : ffffffff`ff676980 fffffa80`0b760010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0c5aaab0 fffff880`0f637e7a : 00000000`00000000 fffffa80`0b753330 00000000`00000080 fffffa80`0b760010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0c5aabc0 fffff800`03774e6a : 00000000`fffffc32 fffffa80`0bde3610 fffffa80`05a73b30 fffffa80`0bde3610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0c5aac00 fffff800`034ceec6 : fffff880`03690180 fffffa80`0bde3610 fffff880`0369b0c0 00000000`00000020 : nt!PspSystemThreadStartup+0x5a
fffff880`0c5aac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8fd8
fffff880`0754efd8 4055            push    rbp

SYMBOL_NAME:  atikmpag+8fd8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fce3b74

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`07546000 fffff880`075a5000   atikmpag T (no symbols)          
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Jun 05 13:01:40 2012 (4FCE3B74)
    CheckSum:         00066F34
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800be5c4e0, fffff88001008fd8, 0, 2}

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

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800be5c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88001008fd8, 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+8fd8
fffff880`01008fd8 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`0c5a0888 fffff880`104e4000 : 00000000`00000116 fffffa80`0be5c4e0 fffff880`01008fd8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c5a0890 fffff880`104e3d0a : fffff880`01008fd8 fffffa80`0be5c4e0 fffffa80`0a8cd960 fffffa80`0bccf010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0c5a08d0 fffff880`1058af07 : fffffa80`0be5c4e0 00000000`00000000 fffffa80`0a8cd960 fffffa80`0bccf010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0c5a0900 fffff880`105b4b75 : 00000000`ffffffff 00000000`0004691e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0c5a09e0 fffff880`105b32bb : 00000000`00000102 00000000`00000008 00000000`0004691e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0c5a0a10 fffff880`105862c6 : ffffffff`ff676980 fffffa80`0bccf010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0c5a0ab0 fffff880`105b2e7a : 00000000`00000000 fffffa80`0c9f82f0 00000000`00000080 fffffa80`0bccf010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0c5a0bc0 fffff800`0376be6a : 00000000`fffffc32 fffffa80`0a8d3a00 fffffa80`05aef040 fffffa80`0a8d3a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0c5a0c00 fffff800`034c5ec6 : fffff880`03690180 fffffa80`0a8d3a00 fffff880`0369b0c0 00000000`00000020 : nt!PspSystemThreadStartup+0x5a
fffff880`0c5a0c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8fd8
fffff880`01008fd8 4055            push    rbp

SYMBOL_NAME:  atikmpag+8fd8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fce3b74

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

7: kd> lmvm atikmpag
start             end                 module name
fffff880`01000000 fffff880`0105f000   atikmpag T (no symbols)          
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Jun 05 13:01:40 2012 (4FCE3B74)
    CheckSum:         00066F34
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009c804e0, fffff880078a3fd8, 0, 2}

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

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009c804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880078a3fd8, 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+8fd8
fffff880`078a3fd8 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`0c5af888 fffff880`104e5000 : 00000000`00000116 fffffa80`09c804e0 fffff880`078a3fd8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c5af890 fffff880`104e4d0a : fffff880`078a3fd8 fffffa80`09c804e0 fffffa80`0a860d50 fffffa80`0bcb1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0c5af8d0 fffff880`1058bf07 : fffffa80`09c804e0 00000000`00000000 fffffa80`0a860d50 fffffa80`0bcb1010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0c5af900 fffff880`105b5b75 : 00000000`ffffffff 00000000`0001d36e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0c5af9e0 fffff880`105b42bb : 00000000`00000102 00000000`00000008 00000000`0001d36e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0c5afa10 fffff880`105872c6 : ffffffff`ff676980 fffffa80`0bcb1010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0c5afab0 fffff880`105b3e7a : 00000000`00000000 fffffa80`0bd34490 00000000`00000080 fffffa80`0bcb1010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0c5afbc0 fffff800`03768e6a : 00000000`fffffc32 fffffa80`0a867b50 fffffa80`05a73b30 fffffa80`0a867b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0c5afc00 fffff800`034c2ec6 : fffff800`03644e80 fffffa80`0a867b50 fffff800`03652cc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`0c5afc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8fd8
fffff880`078a3fd8 4055            push    rbp

SYMBOL_NAME:  atikmpag+8fd8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fce3b74

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

4: kd> lmvm atikmpag
start             end                 module name
fffff880`0789b000 fffff880`078fa000   atikmpag T (no symbols)          
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Jun 05 13:01:40 2012 (4FCE3B74)
    CheckSum:         00066F34
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    All three of these were 0x116 VIDEO_TDR_ERROR. These aren't true stop errors in that it's actually a feature of Windows that was introduced in Vista. The purpose of the TDR (Timeout Detection and Recovery) is to recover the GPU driver without having to restart. If the system is unable to recover the driver after a number of attempts, it will trigger a BSOD. More info here: Timeout Detection and Recovery of GPUs through WDDM . The advice that MickyD1234 gave is sound and is what I suggest as well.

    Hope this helps.
     
    aznpos531, Aug 11, 2012
    #4