BSOD on "Wake up" win 7 ult 64

[brbrown13]

I get a BSOD whenever Windows 7 wakes up from sleep. I have updated ALL drivers to the latest versions. Im pretty sure it has to do with Catalyst Control Center 9.10. Im running crossfired radeon HD 4870x2 cards, CCC detects all 4 GPU's but under the ATI Overdrive tab the window "blinks". I was running Vista Home Premium 32bit with absolutley no problems. Switched to Win 7 ultimate 64 on a new HD and this issue is the only problem I have.

I will post the dump files when I get home, I can't figure out how to read them.

This may or may not have anything to do with it but if someone has knowledge on the 4870x2 cards, on vista 3 of the 5 LED's would light up at start up then turn off but on win7 only one of them lights up and turns off. I don't get lines or hang ups, the cards work fine just the BSOD on wake up.

I Would greatly appreciate any assistance in this matter.

 

[Lordbob75]

Posting the minidump will really help. I will not have any more help for you until I can see that, or get the stop code.

~Lordbob

 

[brbrown13]

Minidump

I had to wait until I got home from work. Here are the minidump files that are related to this crash. Again any help is greatly appreciated.

 

[Lordbob75]

Bad graphics driver. Have you updated them?

~Lordbob

 

[brbrown13]

Yes, I am using the latest driver package from AMD.

 

[zigzag3143]

I had to wait until I got home from work. Here are the minidump files that are related to this crash. Again any help is greatly appreciated.

Hi and welcome to seven forums

I took a qick look at the 4 dumps they were almost identical. thats the good news. all four pointed to your video driver. in fact the file that probably caused the crash was atikmdag.sys.

I would
update the videodriver, and BIOS while you are at it.
If you are overclocking stop
download memtestx86 and run for a long time (prefer overnight)
run a system file check
type cmd in search>right clicka nd run as admin>sfc /scannow

let us know the results

Hope this helps

Ken J



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


Loading Dump File [C:\Users\K\Desktop\110709-29281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
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`02a0c000 PsLoadedModuleList = 0xfffff800`02c49e50
Debug session time: Sat Nov 7 22:22:40.408 2009 (GMT-5)
System Uptime: 0 days 1:20:47.000
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009631010, fffff8800467a6a0, 0, 2}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+126a0 )

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: fffffa8009631010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800467a6a0, 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:
atikmdag+126a0
fffff880`0467a6a0 48895c2408 mov qword ptr [rsp+8],rbx

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`06b382e8 fffff880`04cffef8 : 00000000`00000116 fffffa80`09631010 fffff880`0467a6a0 00000000`00000000 : nt!KeBugCheckEx
fffff880`06b382f0 00000000`00000116 : fffffa80`09631010 fffff880`0467a6a0 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`06b382f8 fffffa80`09631010 : fffff880`0467a6a0 00000000`00000000 00000000`00000002 00000000`00000282 : 0x116
fffff880`06b38300 fffff880`0467a6a0 : 00000000`00000000 00000000`00000002 00000000`00000282 00000000`00000000 : 0xfffffa80`09631010
fffff880`06b38308 00000000`00000000 : 00000000`00000002 00000000`00000282 00000000`00000000 fffff880`04cffc02 : atikmdag+0x126a0


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+126a0
fffff880`0467a6a0 48895c2408 mov qword ptr [rsp+8],rbx

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: atikmdag+126a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4abaa755

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys

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

 

[brbrown13]

All of my drivers are up to date according to Windows and I am not overclocking. I am running the latest version of catalyst control center (9.10) and it is incredibly buggy, the window resets every 5 seconds. I have uninstalled/reinstalled several times with the same result and it is the only version recommended for win7 64. ASUS does not have a BIOS driver package for windows 7 that I can find. I will try what you suggested as AMD and ASUS have been very unhelpful thus far.

 

[Lordbob75]

Try an older driver.

~Lordbob

 

[brbrown13]

I ran memtestx86, 4x2047, for 8 hours. Got up to 312% on each with 0 errors. Ran the system scan and "Windows Resource Protection did not find any integrity violations."

So im guessing that is good but its still crashing on wake up.

I attempted to use an older driver but none of them will install because they wont install on a 64x system (tried every version from 9.9 all the way back to 8.1). I dialed my CCC back to 9.8 from 9.10 and that version doesnt "blink/flicker" but my cards still just want to sleep forever and when I wake them up BSOD time lol.

 

[Deadlift315]

Exact same issue. clearly a windows 7 64 Bit problem

I am encountering the exact same issue. A blue screen of death calling out the video drivers when the computer is "awakened" from sleep mode. I am running an ATI HD4870 512MB DDR5.

I tested the exact same hardware setup with the 32 bit version of windows 7 and the problem does not occur. However this is not an adequate solution as I require a 64 bit operating system to fully utilize software such as Maya and Zbrush.

I am using the most current drivers, BIOS, and windows updates. I have tested several previous ATI drivers and encountered the same issue.

This is clearly an issue that needs to be addressed by both Microsoft and ATI.

As a temporary work around I have disabled the computers sleep function.

Moderators please pass this on to your engineers and repair this issue as soon as possible.

 

[Lordbob75]

Deadlift, it is interesting that you mention it occurring only with x32 systems... I have not noticed this myself, but I might check it.

This points to a problem with the OS...

~Lordbob

 

[Deadlift315]

I totally agree Bob.

I just wanted to clarify that that I am having this issue with the 64 bit OS.

the 32 bit version of windows 7 does not have this problem.

 

[Lordbob75]

I totally agree Bob.

I just wanted to clarify that that I am having this issue with the 64 bit OS.

the 32 bit version of windows 7 does not have this problem.

It is interesting that none of us have noticed this before...

It is also really annoying.

~Lordbob