Blue Screen While Playing

[Untriggered]

Hi recently while playing I have been receiving Blue Screens or just a frozen black screen. But at startup Windows reported a Blue screen, however after the most recent 2 or 3 screens no error report has appeared at reboot.

After a little research I found that it probably is related to the GPU/graphics drivers (+ since it appears when playing games, CoD4 & MW2) So I reinstalled the graphics drivers but it didn't help.

I hope you guys can help me but maybe It's a lost cause.

[i]Is Windows 7 . . .
- x86 (32-bit) or x64 ?[/i]
x64
[I]- the original installed OS on the system?[/I]
Yes
[I]- an OEM or full retail version?[/I]
 It came pre-installed on the laptop
[I]- What is the age of system (hardware)?[/I]
bought in February
[I]- What is the age of OS installation (have you re-installed the OS?)  [/I]
No re-installation, as old as hardware

 

[zigzag3143]

Hi recently while playing I have been receiving Blue Screens or just a frozen black screen. But at startup Windows reported a Blue screen, however after the most recent 2 or 3 screens no error report has appeared at reboot.

After a little research I found that it probably is related to the GPU/graphics drivers (+ since it appears when playing games, CoD4 & MW2) So I reinstalled the graphics drivers but it didn't help.

I hope you guys can help me but maybe It's a lost cause.

[I]Is Windows 7 . . .
- x86 (32-bit) or x64 ?[/I]
x64
[I]- the original installed OS on the system?[/I]
Yes
[I]- an OEM or full retail version?[/I]
 It came pre-installed on the laptop
[I]- What is the age of system (hardware)?[/I]
bought in February
[I]- What is the age of OS installation (have you re-installed the OS?)  [/I]
No re-installation, as old as hardware

Your suspicion that it is your video driver is correct. These crashes were caused by the directX portion of the driver.

When you upgraded the driver did you remove all traces of the current driver before installing the new copy? Most mfrs. have "uninstall" tools to ensure it

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


Loading Dump File [C:\Users\K\Desktop\New folder\071310-22900-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`03292e50
Debug session time: Mon Jul 12 20:46:07.964 2010 (GMT-4)
System Uptime: 0 days 13:40:32.884
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, fffff88004212d85, fffff88005edbee8, fffff88005edb750}

Probably caused by : atikmdag.sys ( atikmdag+35ed85 )

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

0: 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: fffff88004212d85, The address that the exception occurred at
Arg3: fffff88005edbee8, Exception Record Address
Arg4: fffff88005edb750, Context Record Address

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

 

[usasma]

IMO this is most likely a hardware problem with your video card (as you've updated your drivers already).
Since the system was purchased in February, it should still be under warranty.

Have you blown the vents out with canned air? (Don't use a vacuum or an air compressor as they'll damage the system)

To test your video card, please run this free stress test:

FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Please remove Daemon Tools as the SPTD.sys driver has been known to cause BSOD's.
BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 25 12:33:39.113 2010 (UTC - 4:00)
System Uptime: 0 days 3:23:30.908
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1000007E, {ffffffffc0000094, fffff8800417ed85, fffff88005f2cf78, fffff88005f2c7e0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 17:40:25.987 2010 (UTC - 4:00)
System Uptime: 0 days 9:28:03.782
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 1000007E, {ffffffffc0000094, fffff880041a5d85, fffff88005ef2ee8, fffff88005ef2750}
Probably caused by : atikmdag.sys ( atikmdag+35ed85 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 08:23:43.955 2010 (UTC - 4:00)
System Uptime: 0 days 1:15:18.874
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 1000007E, {ffffffffc0000094, fffff880041b4d85, fffff88005f25ee8, fffff88005f25750}
Probably caused by : atikmdag.sys ( atikmdag+35ed85 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 20:46:07.964 2010 (UTC - 4:00)
System Uptime: 0 days 13:40:32.884
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 1000007E, {ffffffffc0000094, fffff88004212d85, fffff88005edbee8, fffff88005edb750}
Probably caused by : atikmdag.sys ( atikmdag+35ed85 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 15:10:15.156 2010 (UTC - 4:00)
System Uptime: 0 days 11:24:09.076
BugCheck A, {0, 2, 0, fffff800030d169f}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Untriggered]

First thank you for the quick responses.

When you upgraded the driver did you remove all traces of the current driver before installing the new copy? Most mfrs. have "uninstall" tools to ensure it

I removed CCC and used Driver Sweeper to remove what was left. Then Installed CCC and updated the drivers through the Device Manager, and ofc i rebooted inbetween.

Have you blown the vents out with canned air? (Don't use a vacuum or an air compressor as they'll damage the system)

No I have not :/

To test your video card, please run this free stress test:

Can this be dangerous for the card? My friend said that when he ran it his 5850 temp went higher than with any other game. And when playing mw2 everest showed the GPU peaking 100 degrees Celsius.

I ran 3DMark 06 the other day without any BSOD. which is a bit weird?

Uninstalled Daemon tools.

 

[usasma]

It's a stress test, it's supposed to stress your card.
I wouldn't let it go higher than 90ºC (but that's just a guess on my part). If it's going any higher than that, I'd say it was overheating and that it was a part of your problems.

Uninstall CCC if you're not using it - there have been problems with it on some Win7 systems

 

[Untriggered]

Everest
I closed the test when temps reached this:

GPU Diode (DispIO)	94 °C  (180 °F)
GPU Diode (MemIO)	90 °C  (158 °F)

From the temp.xml which i found isn't making any sense. 5700 Series?

  <?xml version="1.0" encoding="Windows-1252" standalone="yes" ?> 
- <!-- * GPU Temperature tracking generated by:
* FurMark 1.8.0 - http://www.ozone3d.net/benchmarks/fur/

  --> 
- <gpuTemperature graphics_card="ATI Radeon HD 5700 Series">
  <temperature gpu="0" celcius="53.50" fahrenheit="128.30" seconds="0.00" /> 
  <temperature gpu="0" celcius="65.50" fahrenheit="149.90" seconds="5.99" /> 
  </gpuTemperature>

The only temperature info FurMark_0001.log contained was this:

<->[NORMAL]#00000004#Tue Jul 27 00:06:22 2010#Physical GPU 0 temperature: 0.000°C

 

[usasma]

Get it looked at by the service center for a warranty repair.
The GPU shouldn't be that hot.