Tech Support banner

Status
Not open for further replies.
1 - 14 of 14 Posts

·
Registered
Joined
·
7 Posts
Discussion Starter · #1 ·
Hello,

at the beginning it's important to say that i'm german, so I apologize for my bad english :smile:.

My computer shows various bluescreens and colored screens (->>related to the video card driver?) every time I start playing games (such as Call of Duty 4, which I played competitive). The scenario is as follows: I start the game, join a match and after loading the map the monitor becomes black or colored (e.g. pink or sth.).
After investigating for days, I found out that the bluescreens that sometimes appear leads to the aspect, that the video card driver (Catalyst 12.9 beta) is corrupt. As you can see on the picture, I got the error several times in the past:




The bluescreen code I got was this one:

- System - Provider [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4} EventID 41 Version 2 Level 1 Task 63 Opcode 0 Keywords 0x8000000000000002 - TimeCreated [ SystemTime] 2012-09-19T12:36:49.356020700Z EventRecordID 26161 Correlation - Execution [ ProcessID] 4 [ ThreadID] 8 Channel System Computer Daniel-PC - Security [ UserID] S-1-5-18 - EventData BugcheckCode 0 BugcheckParameter1 0x0 BugcheckParameter2 0x0 BugcheckParameter3 0x0 BugcheckParameter4 0x0 SleepInProgress false PowerButtonTimestamp 0
At that time I was so stupid and didn't mention the minidump file :banghead:

Now I will continue with the steps that are explained from jcgriff2:

My system:

  • Windows 7 Home Premium x64 SP1 OEM (original installed; came pre-installed
  • System is 2 years old
  • I reistalled Windows three times, yesterday was the last re-installation
  • CPU: AMD Phenum II X4 955 (4x3,2 Ghz)
  • ATI Radeon HD 5770 Video Card (Catalyst 12.9 beta driver (newest one))
  • Motherboard: MSI 770-C45
  • Power Supply: be quiet! Pure Power 530W
The computer itself runs very well when I don't play games. I found out that the file "atikmdag.sys" could be the activator for this issue. Also I found many theories how to fix that, such as increasing the voltage of the RAM etc. etc.

The files that you want are attached in a zip file :)

I hope you can help me :blush:

Yours sincerly,

Daniel Fischer
 

Attachments

·
Registered
Joined
·
3,036 Posts
Recommendations:
If you have increased voltages, etc., please enter your BIOS and reset to default/optimized settings to clear the CMOS.


The crashes were DirectX/graphics card related. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

  • If you are overclocking any hardware, please stop.

  • Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. If you hae errors, proceed to
    To determine which files could not be repaired by the System File Checker tool, follow these steps:
    in SFC /SCANNOW Command - System File Checker and upload the sfcdetails.txt file.


Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

  1. Download the drivers you want for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For AMD:
    • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
    • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
      1. Click Start Menu
      2. Right Click My Computer/Computer
      3. Click Manage
      4. Click Device Manager from the list on the left
      5. Expand Display adapters
      6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      Alternatively:
      1. Login as an adminstrative user
      2. Click Start Menu
      3. Click Control Panel
      4. Click Hardware and Sound
      5. Click Device Manager (the last link under Devices and Printers)
      6. Expand Display adapters
      7. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  6. Restart your computer after uninstalling drivers for all display cards
  7. Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:
Code:
[FONT=lucida]**************************Sun Oct 14 10:20:10.629 2012 (GMT-6)**************************
xusb21.sys                  Thu Aug 13 16:10:17 2009 (4A848F49)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
Rt64win7.sys                Fri Jun 10 00:33:15 2011 (4DF1BAAB)
AODDriver2.sys              Thu Apr  5 03:23:37 2012 (4F7D6499)
AtihdW76.sys                Fri May 11 02:25:40 2012 (4FACCD04)
atikmpag.sys                Thu Sep 13 15:55:39 2012 (5052565B)
atikmdag.sys                Thu Sep 13 16:54:58 2012 (50526442)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 13 14:07:35.772 2012 (GMT-6)**************************
Rt64win7.sys                Thu Feb 26 02:04:13 2009 (49A65B0D) ([B][COLOR=Red]Already updated...[/COLOR][/B])
amdxata.sys                 Tue May 19 11:56:59 2009 (4A12F2EB) ([B][COLOR=Red]Already updated...[/COLOR][/B])
amdiox64.sys                Thu Feb 18 08:17:53 2010 (4B7D5A21)
AODDriver2.sys              Tue Mar  6 02:55:00 2012 (4F55DEF4)
atikmpag.sys                Tue Jun 26 09:22:10 2012 (4FE9D3A2)
atikmdag.sys                Tue Jun 26 10:04:19 2012 (4FE9DD83)
[/FONT]
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=amdiox64.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys



Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
Code:
[FONT=lucida]**************************Sun Oct 14 10:20:10.629 2012 (GMT-6)**************************
Loading Dump File [C:\Users\writhziden\Documents\BSODDmpFiles\noxz\Windows7_Vista_jcgriff2\101412-28376-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:31:15.816[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck Code: [B]BugCheck A0000001, {5, 0, 0, 0}[/B]
Probably caused by :[B]atikmdag.sys ( atikmdag+223c2 )[/B]
BugCheck Info: [B]Unknown bugcheck code (a0000001)[/B]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA0000001
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xA0000001_atikmdag+223c2[/B]
  BIOS Version                  V1.15
  BIOS Release Date             03/04/2011
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 13 14:07:35.772 2012 (GMT-6)**************************
Loading Dump File [C:\Users\writhziden\Documents\BSODDmpFiles\noxz\Windows7_Vista_jcgriff2\WD-20121013-2207-02.dmp]
Windows 7 Kernel Version [B]7600 [/B]MP (4 procs) Free x64
Built by: [B]7600[/B].16385.amd64fre.win7_rtm.090713-1255
System Uptime:[B]0 days 0:19:24.115[/B]
BugCheck Code: [B]BugCheck 117, {fffffa8005190160, fffff88003eb2250, 0, 0}[/B]
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :[B]atikmpag.sys ( atikmpag+9250 )[/B]
BugCheck Info: [B]VIDEO_TDR_TIMEOUT_DETECTED (117)[/B]
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
BUGCHECK_STR:  0x117
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x117_IMAGE_atikmpag.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]
 

·
Registered
Joined
·
7 Posts
Discussion Starter · #3 · (Edited)
Hello,

I not overclocking hardware, i addition to this I ran sfc /scannow with your instructions - with no result.

My DirectX seems to be good, dxdiag was successful.

Moreover I installed an older version of the Catalyst Driver (12.6). Now I've tried all versions up to the current one.

One thing I don't understand is your bluescreen analysis: To put it in a nutshell, the bluescreen is VIDEO_TDR_TIMEOUT_DETECTED related. I investigated about this, but there is no fix for that issue.

All in all I don't know what to do know. After the boot today I got some pixel issues, after installing the new driver they're away, but the problem persists...

I hope you can help me!

Yours sincerly,

Daniel Fischer

edit: Windows displayed, that the Fusion Utility Service is not available:

Beschreibung
Pfad der fehlerhaften Anwendung: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe

Problemsignatur
Problemereignisame: APPCRASH
Anwendungsname: Fuel.Service.exe
Anwendungsversion: 1.0.0.0
Anwendungszeitstempel: 4fd626ed
Fehlermodulname: Device.dll
Fehlermodulversion: 4.1.0.0
Fehlermodulzeitstempel: 4f55e10b
Ausnahmecode: c0000005
Ausnahmeoffset: 00000000000033c1
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031
Zusatzinformation 1: dea7
Zusatzinformation 2: dea79fb6329ed5d2a07e58a7b4c512d8
Zusatzinformation 3: eccb
Zusatzinformation 4: eccb532074d65e1adb418f780f8aa0ca
 

·
Registered
Joined
·
3,036 Posts

·
Registered
Joined
·
7 Posts
Discussion Starter · #5 ·
Hello,

RealTemp dislplayed, that it doesn't support my CPU, so I decided to use Core Temp instead.

CPU Temp when I don't play games: 42 degrees
GPU Temp when I don't play games: 32 degrees

CPU Temp during games: max. 60 degrees
GPU Temp during games: 56 degrees

Here's a pic of HWiNFO:



Regards,
 

·
Registered
Joined
·
3,036 Posts
Your temperatures are a bit on the high side. For your processor, you should be running at mid to high 30s on idle and mid 50s max during stress (prefer low 50s or even high 40s under stress). 60 C is dangerously close to the 62 C max temp of that processor.

AMD Processors for Desktops: AMD Phenom


When was the last time you cleaned dust out of the system?

Dust Removal:
To remove dust, follow the subsequent general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
  5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
  6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
  7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
  8. Start the computer and see if performance is better.



Easier Laptop steps:

  1. Get a can of compressed air...
  2. Shut down and turn off your system...
  3. Unplug the system from any docking stations...
  4. Remove the AC Adapter and then remove the battery...
  5. Hold down the power button for 30 seconds to ensure all power is drained from the components. This closes the circuit and allows any remaining power to dissipate; it also clears the temporary memory of corruption and resets hardware/software connections. No permanent changes are made to the system doing this step...
  6. Use the can of compressed air to blow into every vent, crevice, keyboard key, USB port, VGA/monitor port, etc...
  7. Replace the battery and then plug in the AC Adapter...
  8. Replace the docking station...
  9. See how the system runs after doing all these steps...

WARNING: Never use a vacuum cleaner or hair drier to clean dust out of your system!!
 

·
Registered
Joined
·
7 Posts
Discussion Starter · #7 ·
Hello,

my computer is very prone to dust, so it's not remarkable that I have to clean it at least every two months. The last time I've done it was before three days.

Also I'm very thoroughly when I clean my computer, I'm extracting every component of it etc. etc.

Today I started playing the game again, but before that I have done a clean installation of the Catalyst driver without it's Control Center Part (ATI video cards - DRIVER ONLY installation procedure).

Nevertheless I got a black screen and two dump files (see attachment), and because I was bored I investigated how to analyse this kind of files. I used WinDbg with the !analyze -v varialbe and saw that:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (117)
Unknown bugcheck description
Arguments:
Arg1: fffffa80079134e0
Arg2: fffff880042eedb8
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x117

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800453b5f7 to fffff8800190f577

STACK_TEXT:  
fffff880`03db5630 fffff880`0453b5f7 : fffffa80`079134e0 fffff800`02ad9f90 00000000`00000010 00000000`00010202 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03db5b50 fffff880`0453c2bc : fffff8a0`081a50b0 fffff8a0`081a50b0 00000000`00000080 fffffa80`079134e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03db5ba0 fffff880`045106b3 : 00000000`00000001 fffffa80`0631a000 00000000`00000000 00000000`00000094 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`03db5bd0 fffff880`0453ce0f : fffffa80`04237a58 ffffffff`fffe7960 fffffa80`079134e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`03db5c80 fffff880`04437ec1 : fffffa80`04c97110 00000000`00000080 00000000`00000000 fffffa80`04237410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03db5d00 fffff800`02d6ee5a : 00000000`1114a527 fffffa80`05dd8b50 fffffa80`0398a990 fffffa80`05dd8b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03db5d40 fffff800`02ac8d26 : fffff880`02f64180 fffffa80`05dd8b50 fffff880`02f6efc0 00000006`c7f65400 : nt!PspSystemThreadStartup+0x5a
fffff880`03db5d80 00000000`00000000 : fffff880`03db6000 fffff880`03db0000 fffff880`08507cb0 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
dxgkrnl!TdrUpdateDbgReport+cb
fffff880`0453b5f7 488983e00a0000   mov     [rbx+0xae0],rax

SYMBOL_STACK_INDEX:  1

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  dxgkrnl!TdrUpdateDbgReport+cb

MODULE_NAME:  dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x117_dxgkrnl!TdrUpdateDbgReport+cb

BUCKET_ID:  X64_0x117_dxgkrnl!TdrUpdateDbgReport+cb

Followup: MachineOwner
---------
I got two Dumpfiles with nearly the same content, but the second one had another segment at the end of the name (WD-20121016-1412.dmp and WD-20121016-1412-01.dmp).

Furthermore DRIVER_FAULT can logically be identified as a driver corruption. X64_0x117_dxgkrnl!TdrUpdateDbgReport+cb though is related to DirectX, and the game is DirectX 9 based. I googled that "TdrUpdateDbgReport" has the same indications as my matter: Pink/Black screens e.g.

But I haven't found out how to fix that.

Regards,

Daniel Fischer
 

Attachments

·
Registered
Joined
·
7 Posts
Discussion Starter · #9 ·
The first file replied that I have already installied a newer version and the second one haven't shown effect. I got the same Bluescreen as usual. I will post it in the attachment, maybe you have further instructions for me :)

Regards,
 

Attachments

·
Registered
Joined
·
3,036 Posts
I would recommend monitoring temperatures and running FurMark to stress test the display / graphics card. This will help determine whether the display card hardware is at fault.

FurMark Display Card Stress Test:

  1. First, download and install the latest version of FurMark from FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net.

  2. Run FurMark with full administrator access.

    How do I run an application once with a full administrator access token?

    Some legitimate applications require a full administrator access token to perform their functions or tasks. The User Account Control (UAC) message is displayed to request consent or credentials to allow an application to use the full administrator access token in any of the following circumstances:

    To... run an application with a full administrator access token, use the following procedure.

    To perform this procedure, you must be logged on as a local administrator or provide the credentials of a member of the local Administrators group.

    To run an application one time with a full administrator access token

    1. Locate the program icon or a shortcut in Windows Explorer.

    2. Right-click the program icon or shortcut, and then click Run as administrator.

    3. When the UAC message is displayed, do one of the following:
      • If you are logged on as a standard user, or if UAC is configured to always require credentials, enter the appropriate administrative credentials, and then click OK.

      • If you are logged on as an administrator and UAC is not configured to always require credentials, click Yes to start the application.



  3. Find your display resolution by right clicking the Desktop and clicking Screen resolution and enter it into FurMark's options:



  4. Change FurMark's settings as in the image. You want to run it for 20 minutes or until it reaches the alarm temperature you set up. 90 is a good number for AMD display cards, 80 or 85 is probably best for NVIDIA cards. The best method to set the temperature alarm is the maximum temperature of your card minus 10 C. If you do not know the maximum temperature, and you cannot find it through a Google search, ask the people helping you to find it for you.




  5. Run the Benchmark with user's settings and stop it once the temperature reaches a constant temperature, once the card reaches the alarm temperature, or once the video shows artifacts or strange colors.

 

·
Registered
Joined
·
7 Posts
Discussion Starter · #11 ·
I want to thank you for your help, the card is completely broken. I can't even start the computer without a blackscreen. My dad has the same card, and he allowed me to use it for testing purposes.
I will post the result here!

Thanks!
 

·
Registered
Joined
·
7 Posts
Discussion Starter · #13 ·
Time for a update: My computer runs well with the new card, everything seems to be fine. This leads to the aspect, that my old card was the activator.

One point is important: My CPU has 42 degrees in normal mode. I think I should clean it, because the maximum degree is 63.

Regards,
 
1 - 14 of 14 Posts
Status
Not open for further replies.
Top