Random Black Screen Of Death

Like I said, I updated the video driver to the current one with that initial build and the problem came back. I don't know if it just an ATI driver issue or if there is a conflict, what that conflict is with the current driver.

The other problem is that if you downgrade the driver with the current build, the problem still exists.

So confusing.

Stucatz said:

Like I said, I updated the video driver to the current one with that initial build and the problem came back. I don't know if it just an ATI driver issue or if there is a conflict, what that conflict is with the current driver.

The other problem is that if you downgrade the driver with the current build, the problem still exists.

So confusing.

Downgrading still may not work because remnants exist and the damage has already been done. It may also be that one of the other driver updates you made is interfering with the downgraded version causing the same issues. That is why I recommended going back to the system image created previously and testing each driver update to determine which might be conflicting with the display card.

On the old image, it happens as soon as I upgrade the video drivers (which was the firs t thing that I did). Given that the behavour is exactly the same, I'd rather work on the current image as that's what I'm using anyway.

Given that it's Christmas eve and going through each of the drivers is going to take a bit of time I might not be able to post results for a few days. I was hoping that the dump file, on the one time that it did crash after black screening, would tell us something.

Stucatz said:

On the old image, it happens as soon as I upgrade the video drivers (which was the firs t thing that I did). Given that the behavour is exactly the same, I'd rather work on the current image as that's what I'm using anyway.

Given that it's Christmas eve and going through each of the drivers is going to take a bit of time I might not be able to post results for a few days. I was hoping that the dump file, on the one time that it did crash after black screening, would tell us something.

I understand. I'll be here after Christmas, as well, and I'm subscribed to the thread, so it will let me know via e-mail when you post again.

As to the one dmp file, it points to your graphics driver as being the culprit, so there was no real useful information other than those drivers I recommended you update. Here is the analysis of the dmp file:

Code:

BugCheck 116, {fffffa801398c010, fffff88004b578b8, ffffffffc00000b5, a}

*** 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+78b8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa801398c010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b578b8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+78b8
fffff880`04b578b8 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`07bf9a58 fffff880`06316000 : 00000000`00000116 fffffa80`1398c010 fffff880`04b578b8 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`07bf9a60 fffff880`06315ddb : fffff880`04b578b8 fffffa80`1398c010 fffffa80`13689930 fffffa80`15708010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07bf9aa0 fffff880`063bcf07 : fffffa80`1398c010 00000000`c00000b5 fffffa80`13689930 fffffa80`15708010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`07bf9ad0 fffff880`063ead5a : fffffa80`ffffffff 00000000`00006a16 fffff880`07bf9c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07bf9bb0 fffff880`063b829e : fffffa80`15708010 ffffffff`feced300 fffffa80`13689930 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07bf9bf0 fffff880`063e4e7a : 00000000`00000000 fffffa80`13689930 00000000`00000080 fffffa80`15708010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07bf9d00 fffff800`03527cce : 00000000`0285fc68 fffffa80`1572d4d0 fffffa80`12d88890 fffffa80`1572d4d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07bf9d40 fffff800`0327bfe6 : fffff880`03164180 fffffa80`1572d4d0 fffff880`0316f1c0 fffff880`01462384 : nt!PspSystemThreadStartup+0x5a
fffff880`07bf9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78b8
fffff880`04b578b8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ed65628

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

A TDR fault is informative to some extent, but we have already exhausted pretty much every test for it. See: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

That error was from 18 days ago; were you having black screen issues that far back?

Yes. Stupid drivers.

So it just points to the video drivers and no conflicts ? Damn....

You could run Driver Verifier one non-microsoft driver at a time. I did that once to determine a bad driver myself.

*sigh* Today, while playing Batman Arkham City, it black screened and I had to manually reboot. When I restarted and tried to play again, it crashed and actually dumped which is rare.

Find attached. Mini dump attached and and full dump file link below.

MEMORY20111228.rar - download now for free. File sharing. Software file sharing. Free file hosting. File upload. FileFactory.com

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Stucatz\Windows_NT6_BSOD_jcgriff2\120611-16426-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0320a000 PsLoadedModuleList = 0xfffff800`0344fe90
Debug session time: Mon Dec  5 19:55:05.806 2011 (UTC - 7:00)
System Uptime: 0 days 0:07:21.178
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa801398c010, fffff88004b578b8, ffffffffc00000b5, a}

*** 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+78b8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa801398c010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b578b8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+78b8
fffff880`04b578b8 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`07bf9a58 fffff880`06316000 : 00000000`00000116 fffffa80`1398c010 fffff880`04b578b8 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`07bf9a60 fffff880`06315ddb : fffff880`04b578b8 fffffa80`1398c010 fffffa80`13689930 fffffa80`15708010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07bf9aa0 fffff880`063bcf07 : fffffa80`1398c010 00000000`c00000b5 fffffa80`13689930 fffffa80`15708010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`07bf9ad0 fffff880`063ead5a : fffffa80`ffffffff 00000000`00006a16 fffff880`07bf9c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07bf9bb0 fffff880`063b829e : fffffa80`15708010 ffffffff`feced300 fffffa80`13689930 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07bf9bf0 fffff880`063e4e7a : 00000000`00000000 fffffa80`13689930 00000000`00000080 fffffa80`15708010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07bf9d00 fffff800`03527cce : 00000000`0285fc68 fffffa80`1572d4d0 fffffa80`12d88890 fffffa80`1572d4d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07bf9d40 fffff800`0327bfe6 : fffff880`03164180 fffffa80`1572d4d0 fffff880`0316f1c0 fffff880`01462384 : nt!PspSystemThreadStartup+0x5a
fffff880`07bf9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78b8
fffff880`04b578b8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ed65628

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Stucatz\Windows_NT6_BSOD_jcgriff2\122811-12573-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03a07000 PsLoadedModuleList = 0xfffff800`03c4ce90
Debug session time: Tue Dec 27 07:00:55.006 2011 (UTC - 7:00)
System Uptime: 0 days 0:21:40.974
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000094, fffff880059b4969, fffff88007b9d848, fffff88007b9d0a0}

Probably caused by : atikmdag.sys ( atikmdag+f8969 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff880059b4969, The address that the exception occurred at
Arg3: fffff88007b9d848, Exception Record Address
Arg4: fffff88007b9d0a0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
atikmdag+f8969
fffff880`059b4969 41f7f0          div     eax,r8d

EXCEPTION_RECORD:  fffff88007b9d848 -- (.exr 0xfffff88007b9d848)
ExceptionAddress: fffff880059b4969 (atikmdag+0x00000000000f8969)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88007b9d0a0 -- (.cxr 0xfffff88007b9d0a0)
rax=0000000000d46700 rbx=fffff88007b9dad0 rcx=0000000000d46700
rdx=0000000000000000 rsi=fffffa8015534400 rdi=fffff880058bc000
rip=fffff880059b4969 rsp=fffff88007b9da80 rbp=0000000000000026
 r8=0000000000000000  r9=00000000000074e2 r10=fffff88007b9dad0
r11=fffff88005ec2a30 r12=0000000000000000 r13=00000000ffffffff
r14=00000000000009dd r15=00000000000009de
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
atikmdag+0xf8969:
fffff880`059b4969 41f7f0          div     eax,r8d
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

LAST_CONTROL_TRANSFER:  from fffffa801557d7dc to fffff880059b4969

STACK_TEXT:  
fffff880`07b9da80 fffffa80`1557d7dc : fffff880`05bcf452 00000000`00000081 fffffa80`155dd188 fffff880`07b9db60 : atikmdag+0xf8969
fffff880`07b9da88 fffff880`05bcf452 : 00000000`00000081 fffffa80`155dd188 fffff880`07b9db60 fffff880`059b3ac5 : 0xfffffa80`1557d7dc
fffff880`07b9da90 00000000`00000081 : fffffa80`155dd188 fffff880`07b9db60 fffff880`059b3ac5 00000000`00000027 : atikmdag+0x313452
fffff880`07b9da98 fffffa80`155dd188 : fffff880`07b9db60 fffff880`059b3ac5 00000000`00000027 00000000`00000000 : 0x81
fffff880`07b9daa0 fffff880`07b9db60 : fffff880`059b3ac5 00000000`00000027 00000000`00000000 00000013`00000040 : 0xfffffa80`155dd188
fffff880`07b9daa8 fffff880`059b3ac5 : 00000000`00000027 00000000`00000000 00000013`00000040 00000081`00000002 : 0xfffff880`07b9db60
fffff880`07b9dab0 00000000`00000027 : 00000000`00000000 00000013`00000040 00000081`00000002 fffff880`07b9db60 : atikmdag+0xf7ac5
fffff880`07b9dab8 00000000`00000000 : 00000013`00000040 00000081`00000002 fffff880`07b9db60 fffffa80`15534400 : 0x27


FOLLOWUP_IP: 
atikmdag+f8969
fffff880`059b4969 41f7f0          div     eax,r8d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+f8969

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ee12bed

STACK_COMMAND:  .cxr 0xfffff88007b9d0a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+f8969

BUCKET_ID:  X64_0x7E_atikmdag+f8969

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

The blue screen was due to your display card driver again. I also noted that your Samsung printer driver is very old and recommend updating it (Driver Reference).

The printer is an old printer and the driver hasn't been updated in over a year. I'm fairly sure I have the latest driver:
Support for CLP-500

Stupid driver.

Hi and a Happy New Year to all.

Still no luck with this. I tried some Driver Verifier testing tonight. Firstly, I tried all the drivers by AMD. It rebooted fine but it still black screened when I ran Furmark. Then I tried gearaspiwmd.sys, genericmount.sys and sptd.sys. This time on reboot, it crashed during the Windows splash screen. BUT, then testing each one individually, it booted up fine. I've updated gearaspiwmd.sys to the latest version (my dvd drive needs it to be recognised) but the black screen crash occurs anyway.

I did have another crash dump today which pointed to atikmpag.sys again. I just don't understand how I went from a stable system to this.