Vista and 7.3 Display driver atikmdag stopped responding error

TayRoc · Dec 16, 2008, 02:06 AM

i'm just a normal guy who wants his computer to work like its supposed to and i don't understand any of this compuspeak. if there is in fact a solution at all, could you explain it to me in human terms?

BadMouth · Dec 16, 2008, 02:33 AM

JCKSON79:
If your system is not detecting the correct memory installed, then you may have a ram problem, which maybe the TDR cause. Just for clarity and to inform users that if your system does not detect the actual ram installed in your system and I mean even if it’s 1 percent off, then you may have a problem with ram. Below is the actual maximum ram each type of vista operating system can use:

32-bit versions of Windows Vista:
Home Basic 4GB
Home Premium 4GB
Home Business 4GB
Enterprise 4GB
Ultimate: 4GB
Vista Starter: 1GB

64-bit versions of Windows Vista:
Home Basic 8GB
Home Premium 16GB
Business 128GB
Enterprise 128GB
Ultimate 128GB

Again, if your system does not fully detect your ram installed, you need to check what can be causing this problem it is vital that all systems detect the proper amount of ram installed.
B.M

grog · Dec 16, 2008, 02:48 AM

Sure.

For the TDR issues which this thread is dealing with there are some things a user can do.

TDR = Timeout Detection and Recovery of GPUs.
When a timeout occurs the error "Display driver atikmdag stopped responding and has successfully recovered" will either be displayed as a pop-up or you will see the warning message in the event logs.

What this means is Vista was able to prevent a possible system hang by catching the fault. Now if the timeout values are too low then we may see the TDR occur when it should not.

It appears that users with more than one active monitor have seen the TDR events during what would be idle times.

If the user desires he can adjust the default timeout value to see if the TDR's will go away. The only way to do this is to add keys to the registry. Microsoft has information on how to do this but it is not for the faint of heart.

Timeout Detection and Recovery of GPUs through WDDM

So if I am a normal human how can I fix the issue if I don't want to edit the registry.

Find a friend who is able to help
Remove the secondary monitor until the issue is officially resolved.

Others are having problems when overclocking or using custom heatsinks. If you are overclocking then simply don't overclock if stabiliy is what you desire and TDR's is what you see.

If you are not using dual monitors and you are not overclocking or using custom heatsinks then you might have a faultly card. In this case RMA the card would be in order.

But now to the real issue here.
Let me put it in normal terms.

Let's say your car was not running right. You call to find someone to repair it and tell you what is wrong with the car. You say 'I don't know cars, I just it fixed'. How can the mechanic tell you how much the repair might cost if he does not know the make of the car or what you think the problem is?

If the issue of this thread is what you are seeing I can guess but I am not sure what your actual problem is.

If you have a problem with Dual monitors and when you plan Crysis you get a TDR then for now remove the secondary monitor when you play that game.

The TDR issue is being looked at by Microsoft, ATI and NVIDIA. The concept is a good one but some users are having issues.

The number of users effected with the TDR problem is very small.

Quote:

Originally Posted by TayRoc

i'm just a normal guy who wants his computer to work like its supposed to and i don't understand any of this compuspeak. if there is in fact a solution at all, could you explain it to me in human terms?

Raduque · Dec 16, 2008, 04:45 AM

Has anybody else installed the 8.12s? I've been running for nearly 12 hours now with no TDR, with previous versions I would get them within minutes of enabling Aero and within minutes of waking up the monitors. I'll see what it looks like after I get home from work.

I'm using dual monitors with different resolutions, but the SAME refresh rate (both are 60hz LCDs).

The.Rat · Dec 16, 2008, 07:20 AM

@grog,

Very interesting reading. According to your definition I do NOT suffer from TDR's. At present all I get is a loop of 16 errors in Event Viewer every time I play any form of video or a FLAC audio file. The error in Event Viewer is an EventID 52236, Source - Atikmdag. The description shows as "CPLIB :: General - Invalid Parameter".

Apart from my Event Viewer filling with thousands of these errors I do not appear to be suffering any ill-effects on my system at all.

Can you or anyone else here suggest a fix for these annoying errors?

cheers

grog · Dec 16, 2008, 08:07 AM

You are correct. Your problem is not the TDR issue.
The CLIB library appears to be used mainly for DRM protection layer.
The messages from the CLIB:: component normally refer to HDCP issues.

Do a google search for 'cplib hdcp' and you will see.

cplib hdcp - Google Search

Here are a couple examples of warning messages for CPLIB:: you might see in the event viewer other than the ones you have seen:

Code:

CPLIB :: HDCP - Failed HDCP key binding verification.
CPLIB :: General - Failed to authenticate output protection.

As I said before, the CPLIB:: events can be ignored.
I could go into more technical details with this issue but NDA will only allow me to give you public available data which I think is enough to show the cause of the event.

Quote:

Originally Posted by The.Rat

@grog,

Very interesting reading. According to your definition I do NOT suffer from TDR's. At present all I get is a loop of 16 errors in Event Viewer every time I play any form of video or a FLAC audio file. The error in Event Viewer is an EventID 52236, Source - Atikmdag. The description shows as "CPLIB :: General - Invalid Parameter".

Apart from my Event Viewer filling with thousands of these errors I do not appear to be suffering any ill-effects on my system at all.

Can you or anyone else here suggest a fix for these annoying errors?

cheers

The.Rat · Dec 16, 2008, 11:52 AM

Quote:

Originally Posted by grog

You are correct. Your problem is not the TDR issue.
The CLIB library appears to be used mainly for DRM protection layer.
The messages from the CLIB:: component normally refer to HDCP issues.

Do a google search for 'cplib hdcp' and you will see.

cplib hdcp - Google Search

Here are a couple examples of warning messages for CPLIB:: you might see in the event viewer other than the ones you have seen:

Code:

CPLIB :: HDCP - Failed HDCP key binding verification.
CPLIB :: General - Failed to authenticate output protection.

As I said before, the CPLIB:: events can be ignored.
I could go into more technical details with this issue but NDA will only allow me to give you public available data which I think is enough to show the cause of the event.

Thanks for the explanation. I'll just ignore them as they aren't causing me any problems.

I will make one last observation tho. It appears to me that the errors in Event Viewer seems to be pointing to an error in the drivers such as a Parameter missing or an incorrect Parameter. Whether the "renegade" Parameter (wherever it is to be found in the drivers) is invalid because of a change in the way X4000 series deal with it or whether it is the way Vista, or a Vista update or even the Vista SP1 handles it.

Whatever the reason, I'm sure the guys at ATI could fix the drivers to ensure the error doesn't occur.

I'll leave it at that and leave this topic to those that really do have TDR problems.

cheers

australis · Dec 16, 2008, 12:26 PM

I've been having tdr issues, when I play games. At 2D no problem with aero and installing 8.12 didn't help. I regret the day that I build this pc, especially choosing ati. None of my nvidia owner friends have this issue. (and yes I know there are some out there) Still waiting for new "solutions"(!).

*CATALYSTCATCHER* · Dec 16, 2008, 12:38 PM

Quote:

Originally Posted by The.Rat

Whatever the reason, I'm sure the guys at ATI could fix the drivers to ensure the error doesn't occur.

I'll leave it at that and leave this topic to those that really do have TDR problems.

cheers

But also consider that the player could be providing bad parameters to the driver. The codecs could be providing bad parameters. There are also other possibilites. You are correct that the driver could fix bad parameters if the driver were producing them. But the driver is just the messenger and only honors the requests and assumes the parrameters are valid, which may not be a good assumption. And in a similar way the driver could do bounds checking on the parameters (coming from eleswhere) and if they are incorrect a workaround could possibly be created, This is quite common in many drivers but tends to slow things down, so it is only done when there is no alternative. But to figure it out the developers must debug and completely understand the fault, which is the toughest part of the equation.

Your event log entries may be worth investigating, but they are certainly not as painfull as the TDR message and mini dump scenario. So I suggest you take a break for the holiday and then keep searching for more clues regarding the player issues you are seeing.

Raduque · Dec 16, 2008, 02:33 PM

Two minutes shy of 23 hours since I installed the cat 8.12s and I just got a TDR while reading a page in FF3.

The.Rat · Dec 16, 2008, 02:36 PM

Quote:

Originally Posted by CATALYSTCATCHER

But also consider that the player could be providing bad parameters to the driver. The codecs could be providing bad parameters. There are also other possibilites. You are correct that the driver could fix bad parameters if the driver were producing them. But the driver is just the messenger and only honors the requests and assumes the parrameters are valid, which may not be a good assumption. And in a similar way the driver could do bounds checking on the parameters (coming from eleswhere) and if they are incorrect a workaround could possibly be created, This is quite common in many drivers but tends to slow things down, so it is only done when there is no alternative. But to figure it out the developers must debug and completely understand the fault, which is the toughest part of the equation.

Sorry I disagree it could be the player as I only use PowerDVD 8 and Windows Media Player, two very commonly used players. If that was the case the problem would be more widespread.

Quote:

Your event log entries may be worth investigating, but they are certainly not as painfull as the TDR message and mini dump scenario. So I suggest you take a break for the holiday and then keep searching for more clues regarding the player issues you are seeing.

I agree fully, my problem is minor in comparison to the TDR issues.

cheers

grog · Dec 16, 2008, 08:20 PM

What makes you think this is a isolated case?
I get CPLIB:: events too.

Here is a quick test that will help you see how this works.

Note: All test cases done under Vista 64 Ultimate.

Test case - PowerDVD 7 - HDCP test --- Test case 1
Main Display: Non HDCP display (DVI)
Seconday Display: HDCP display (HDMI)

Start PowerDVD on an external HDMI/HDCP display.
Play a protected DVD.
Check the events logs.

In this case no CPLIB:: messages were produced.
Why? Because the HDCP handshake was accepted.

Start PowerDVD on an primary DVI display.
Play a protected DVD.
Check the events logs.

In this case CPLIB:: message are produced.
Why? Because the HDCP handshake failed.

Technically there is no difference on the video signal interface between DVI and HDMI. The software has no way to know that HDCP should not be tried.

In the above test however only the external HDMI display can respond to a HDCP hello packet. My main display is not HDCP and thus will fail.

So above test case shows that HDMI/HDCP is involved in the production of the CPLIB:: messages.

Play DVD - VLC Media Player -- Test case 2
Let's try a different player.

In this case we will play the same DVD using the VLC Media Player.

Using VLC media player 0.9.6 Girshenko

VLC media player - Overview

Start VLC on an external HDMI/HDCP display.
Play a protected DVD.
Check the events logs.

No CPLIB:: warnings in event viewer.

Start VLC on an primary DVI display.
Play a protected DVD.
Check the events logs.

Still no CPLIB:: warnings in event viewer.

So the player used can make a difference.
So why does VLC work? It works because it does not support HDCP.

So what have we learned

CPLIB:: messages are HDMI/HDCP where HDCP attempt failed.
Monitors which support HDCP will not see the messages.
Players that do not send HDCP hello messages will not produce event log messages of the type 'CPLIB::'.

And the main thing we know...

CPLIB:: messages are not TDR's.

Quote:

Originally Posted by The.Rat

Sorry I disagree it could be the player as I only use PowerDVD 8 and Windows Media Player, two very commonly used players. If that was the case the problem would be more widespread.

I agree fully, my problem is minor in comparison to the TDR issues.

cheers

SV110MHH · Dec 16, 2008, 08:34 PM

Quote:

Originally Posted by Raduque

Two minutes shy of 23 hours since I installed the cat 8.12s and I just got a TDR while reading a page in FF3.

I bet ya FF3 overheated your GPU!

Note sarcasm here....

TayRoc · Dec 17, 2008, 08:42 AM

thanks Grog, that actually helped a lot. next issue: my comp IS overclocked (whatever that means; my friend suggested it, and did it for me) and i have no idea how to ...de-overclock(?) it

test1 · Dec 18, 2008, 05:28 AM

I'm fine with editing the registry but could you explain what the values need to be changed to?

grog · Dec 18, 2008, 06:36 AM

Timeout Detection and Recovery of GPUs through WDDM

TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
• TdrLevelOff (0). – Detection disabled.
• TdrLevelBugcheck (1) – Bug check on detected timeout, for example, no recovery.
• TdrLevelRecoverVGA (2) – Recover to VGA (not implemented).
• TdrLevelRecover(3) – Recover on timeout. This is the default value.

TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold.
The default value is 2. The new value is 16 (10 hex).

TdrDdiDelay: REG_DWORD. The number of seconds that the operating system allows threads to leave the driver. After a specified time, the operating system bug checks the system with the code VIDEO_TDR_FAILURE (0x116). The default value is 5.

TdrDebugMode: REG_DWORD: The debugging-related behavior of the TDR process.
• TDR_DEBUG_MODE_OFF (0) breaks to kernel debugger before the recovery to allow investigation of the timeout.
• TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.
• TDR_DEBUG_MODE_RECOVER_NO_PROMPT (2) recovers without break into the debugger. This is the default value.
• TDR_DEBUG_MODE_RECOVER_UNCONDITIONAL (3) recovers even if some recovery conditions are not met (for example, recovers on consecutive timeouts).

Create Registry Key Files
tdr-set.reg - Add TDR registry keys
tdr-clear.reg - Remove TDR registry keys
Use the cut-and-paste code shown below to create the two registry files.
Once the two registy files are created you can double click on the one desired to add or remove the TDR registry keys.

Add/Change TDR Debug Registry Keys

Code:

### Cut and Paste to tdr-set.reg ###
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
"TdrLevel"=dword:00000003
"TdrDelay"=dword:00000010
"TdrDdiDelay"=dword:00000005
"TdrDebugMode"=dword:00000002

Remove TDR Debug Registry Keys

Code:

### Cut and Paste to tdr-clear.reg ###
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
"TdrLevel"=-
"TdrDelay"=-
"TdrDdiDelay"=-
"TdrDebugMode"=-

Quote:

Originally Posted by test1

I'm fine with editing the registry but could you explain what the values need to be changed to?

sparkies · Dec 18, 2008, 04:24 PM

yes, 8.12 works fine for me on Vista/32 ATI Mobility Radeon 2600 HD with two screens.

JCKSON79 · Dec 20, 2008, 09:35 PM

Quote:

Originally Posted by BadMouth

JCKSON79:
If your system is not detecting the correct memory installed, then you may have a ram problem, which maybe the TDR cause. Just for clarity and to inform users that if your system does not detect the actual ram installed in your system and I mean even if it’s 1 percent off, then you may have a problem with ram. Below is the actual maximum ram each type of vista operating system can use:

32-bit versions of Windows Vista:
Home Basic 4GB
Home Premium 4GB
Home Business 4GB
Enterprise 4GB
Ultimate: 4GB
Vista Starter: 1GB

64-bit versions of Windows Vista:
Home Basic 8GB
Home Premium 16GB
Business 128GB
Enterprise 128GB
Ultimate 128GB

Again, if your system does not fully detect your ram installed, you need to check what can be causing this problem it is vital that all systems detect the proper amount of ram installed.
B.M

I am no longer having any TDR or atikmdag issues because I removed my card and I am using onboard only. I am simply just having a problem getting Vista to recognize a new stick of ram.

rychas · Dec 21, 2008, 06:14 PM

Simple question here:

Has anyone succesfully stopped having these crashes by reverting back to XP?

I've heard the problems still persist. If so, then there must be something wrong with the hardware, it doesn't make sense!

SV110MHH · Dec 21, 2008, 08:28 PM

I think people have had problems with XP as well.

As stated... there cannot be that much bad hardware out there....

This HAS to be a programming issue no matter what anyone "in the know" preaches.

rychas · Dec 21, 2008, 10:12 PM

Quote:

Originally Posted by SV110MHH

I think people have had problems with XP as well.

As stated... there cannot be that much bad hardware out there....

This HAS to be a programming issue no matter what anyone "in the know" preaches.

True that, but if this happening due to some programming error (either on Windows or ATI drivers) pretty much everyone would be having this problem. That's not the case.

I'm going to try to revert my OS to Windows XP to see if I get any lucky. If the problem still persists, then it can't be a Windows problem.

I ask again: if someone has solved these crashes by using XP, please let me know.

E-D@N · Dec 21, 2008, 10:56 PM

Quote:

Originally Posted by rychas

Simple question here:

Has anyone succesfully stopped having these crashes by reverting back to XP?

I've heard the problems still persist. If so, then there must be something wrong with the hardware, it doesn't make sense!

no more TDRs or crashes here since i've changed my PSU to 450W...
and working with the DNA 8.11...

as u can see in my specs... i 2 have HD 2600...
2 weeks ago i got that PSU from a friend, and now the card works hell better!

i see u have a laptop... give DNA 8.11 a try... maybe it will help you, before u go back to XP...

*** also, before installing the DNA 8.11 i recommend to uninstall the drivers u already have using the DNA.bat uninstaller... and then install the drivers the normal way...

rychas · Dec 21, 2008, 11:25 PM

Quote:

Originally Posted by E-D@N

no more TDRs or crashes here since i've changed my PSU to 450W...
and working with the DNA 8.11...

as u can see in my specs... i 2 have HD 2600...
2 weeks ago i got that PSU from a friend, and now the card works hell better!

i see u have a laptop... give DNA 8.11 a try... maybe it will help you, before u go back to XP...

I did now know about DNA drivers, thanks mate, will give them a try for sure. Altough I don't believe it can be that simple... even with aero off and no external display I still crash using 3D applications.

I will post back my results in the following days

E-D@N · Dec 21, 2008, 11:34 PM

sure...
anyway - i had lots of crashes when i had a 280W PSU...

i've tried many things to stop these crashes...
the only thing that really helped me was to underclock my card to the minimum...
it gave me 100% stability... but now that i have a better PSU, there is no need of that...

also, i found that the 8.12 drivers are no good for me... even with the "new" PSU i still have crashes and stuff - but these DNA drivers did the job... so probably it's also a driver issue...

BTW... have u installed the latest chipset drivers for your laptop?
it is very important!

rychas · Dec 21, 2008, 11:43 PM

Quote:

Originally Posted by E-D@N

sure...
anyway - i had lots of crashes when i had a 280W PSU...

i've tried many things to stop these crashes...
the only thing that really helped me was to underclock my card to the minimum...
it gave me 100% stability... but now that i have a better PSU, there is no need of that...

also, i found that the 8.12 drivers are no good for me... even with the "new" PSU i still have crashes and stuff - but these DNA drivers did the job... so probably it's also a driver issue...

BTW... have u installed the latest chipset drivers for your laptop?
it is very important!

Funny that you mention it, I just downloaded them a few minutes ago. I'm running under an Intel 965 chipset, the drivers date back to December 2007. Tomorrow I'll try to update those, and the DNA drivers. 'Hope all hell doesn't break loose

OldBuzzard · Dec 22, 2008, 05:36 AM

Quote:

Originally Posted by rychas

Simple question here:

Has anyone succesfully stopped having these crashes by reverting back to XP?

I've heard the problems still persist. If so, then there must be something wrong with the hardware, it doesn't make sense!

Short answer = Maybe.

A "true" TDR is what would have been a VPU Recovery in XP. With Vista, the OS is "supposed" to do that, so there is no VPU Recovery implemented for the Vista drivers.

With my system, that has multiple OSs, including Viasta 32 bit, Vista 64 bit, XP 32 bit, and XP 64 bit, I only have issues in the Vista ones. The XP partitions are rock solid. No crashes, re-boots, BSODS, or VPU Recoveries.

I have been TDR free since I did the "msconfig/boot fix", and disabled Aero.

There are very few people that still have problems if they go back to XP, and in that case it's almost always bad hardware. That's going to happen as no manufacturer makes 100% perfect hardware. There are always going to be a small percentage that are defective. That's why they have warranties and RMAs.

Also, it does no good, to point the finger at ATI's drivers or hardware as being the problem, as there are nVidia owners that suffer from TDRs as well. For every ATI owner that has switched to nVidia to become TRD free, there is an nVidia owner that switched to ATI to find relief.

TDR's are a VISTA problem. The sad fact of the matter is that, in the grand scheme of things, there are so few of us that have TDR issues that I doubt that we will ever see MS address the TDR issue.

E-D@N · Dec 22, 2008, 03:08 PM

you know...
the reason i moved to Vista is because i had problems with my card on XP, and i thought maybe if i move to Vista things will get better...

and guess what - i was wrong... in the middle of some game - the monitor went black and said "SIGNAL LOST" all the time... the same things that i had with XP...

only that in XP - in the event viewer it told me something about infinite loop and stuff...
and in Vista it's just died, saying that the video drivers caused an error...

i wish there was a single pattern for all these problems... something that u could point a finger on it and say: "Here is the problem!"... but as u can see - it's not...

what can i say OldB... we are just lucky?

Rayline TWB · Dec 22, 2008, 05:38 PM

Quote:

Originally Posted by rychas

Simple question here:

Has anyone succesfully stopped having these crashes by reverting back to XP?

Yes, I can confirm this.

I changed from a rock stable XP 32 bit to Vista Home Premium x64, and got TDRs in abundance. When I reverted back to XP 32 bit again the TDRs were gone (as I stated in one of my earlier posts some 20 pages back).

However, I chose to stay with Vista since I wanted to be on Vista OS for several reasons, but instead I took out my ATI card and bought a nVidia 8800 GT card, and all my TDRs were gone - and they have stayed away since my card swap.

E-D@N · Dec 22, 2008, 06:39 PM

Quote:

instead I took out my ATI card and bought a nVidia 8800 GT card, and all my TDRs were gone - and they have stayed away since my card swap.

yey... i don't think he can replace the video card.. he have a laptop...

Rayline TWB · Dec 22, 2008, 08:41 PM

I know, I just confirmed his question about reverting to XP.....:-)

Dec 16, 2008, 02:06 AM	#1411
TayRoc DriverHeaven Newbie Join Date: Dec 2008 Posts: 2 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error i'm just a normal guy who wants his computer to work like its supposed to and i don't understand any of this compuspeak. if there is in fact a solution at all, could you explain it to me in human terms?

Dec 16, 2008, 02:33 AM	#1412
BadMouth DriverHeaven Junior Member Join Date: Apr 2008 Posts: 32 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error JCKSON79: If your system is not detecting the correct memory installed, then you may have a ram problem, which maybe the TDR cause. Just for clarity and to inform users that if your system does not detect the actual ram installed in your system and I mean even if it’s 1 percent off, then you may have a problem with ram. Below is the actual maximum ram each type of vista operating system can use: 32-bit versions of Windows Vista: Home Basic 4GB Home Premium 4GB Home Business 4GB Enterprise 4GB Ultimate: 4GB Vista Starter: 1GB 64-bit versions of Windows Vista: Home Basic 8GB Home Premium 16GB Business 128GB Enterprise 128GB Ultimate 128GB Again, if your system does not fully detect your ram installed, you need to check what can be causing this problem it is vital that all systems detect the proper amount of ram installed. B.M

Dec 16, 2008, 04:45 AM	#1414
Raduque DriverHeaven Junior Member Join Date: Oct 2004 Posts: 32 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error Has anybody else installed the 8.12s? I've been running for nearly 12 hours now with no TDR, with previous versions I would get them within minutes of enabling Aero and within minutes of waking up the monitors. I'll see what it looks like after I get home from work. I'm using dual monitors with different resolutions, but the SAME refresh rate (both are 60hz LCDs).

Dec 16, 2008, 07:20 AM	#1415
The.Rat DriverHeaven Junior Member Join Date: Nov 2008 Posts: 22 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error @grog, Very interesting reading. According to your definition I do NOT suffer from TDR's. At present all I get is a loop of 16 errors in Event Viewer every time I play any form of video or a FLAC audio file. The error in Event Viewer is an EventID 52236, Source - Atikmdag. The description shows as "CPLIB :: General - Invalid Parameter". Apart from my Event Viewer filling with thousands of these errors I do not appear to be suffering any ill-effects on my system at all. Can you or anyone else here suggest a fix for these annoying errors? cheers

Dec 16, 2008, 12:26 PM	#1418
australis DriverHeaven Newbie Join Date: Dec 2008 Posts: 15 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error I've been having tdr issues, when I play games. At 2D no problem with aero and installing 8.12 didn't help. I regret the day that I build this pc, especially choosing ati. None of my nvidia owner friends have this issue. (and yes I know there are some out there) Still waiting for new "solutions"(!).

Dec 16, 2008, 02:33 PM	#1420
Raduque DriverHeaven Junior Member Join Date: Oct 2004 Posts: 32 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error Two minutes shy of 23 hours since I installed the cat 8.12s and I just got a TDR while reading a page in FF3.

Dec 17, 2008, 08:42 AM	#1424
TayRoc DriverHeaven Newbie Join Date: Dec 2008 Posts: 2 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error thanks Grog, that actually helped a lot. next issue: my comp IS overclocked (whatever that means; my friend suggested it, and did it for me) and i have no idea how to ...de-overclock(?) it

Dec 18, 2008, 05:28 AM	#1425
test1 DriverHeaven Newbie Join Date: Dec 2008 Posts: 1 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error I'm fine with editing the registry but could you explain what the values need to be changed to?

Dec 18, 2008, 04:24 PM	#1427
sparkies DriverHeaven Junior Member Join Date: Apr 2008 Posts: 23 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error yes, 8.12 works fine for me on Vista/32 ATI Mobility Radeon 2600 HD with two screens.

Dec 21, 2008, 06:14 PM	#1429
rychas DriverHeaven Junior Member Join Date: Jun 2008 Location: Portugal Posts: 39 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error Simple question here: Has anyone succesfully stopped having these crashes by reverting back to XP? I've heard the problems still persist. If so, then there must be something wrong with the hardware, it doesn't make sense!

Dec 21, 2008, 08:28 PM	#1430
SV110MHH HardwareHeaven Junior Member Join Date: Nov 2008 Posts: 32 Rep Power: 0	Re: Vista and 7.3 Display driver atikmdag stopped responding error I think people have had problems with XP as well. As stated... there cannot be that much bad hardware out there.... This HAS to be a programming issue no matter what anyone "in the know" preaches.

Dec 21, 2008, 11:34 PM	#1434
E-D@N DriverHeaven Junior Member Join Date: May 2008 Posts: 72 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error sure... anyway - i had lots of crashes when i had a 280W PSU... i've tried many things to stop these crashes... the only thing that really helped me was to underclock my card to the minimum... it gave me 100% stability... but now that i have a better PSU, there is no need of that... also, i found that the 8.12 drivers are no good for me... even with the "new" PSU i still have crashes and stuff - but these DNA drivers did the job... so probably it's also a driver issue... BTW... have u installed the latest chipset drivers for your laptop? it is very important!

Dec 22, 2008, 03:08 PM	#1437
E-D@N DriverHeaven Junior Member Join Date: May 2008 Posts: 72 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error you know... the reason i moved to Vista is because i had problems with my card on XP, and i thought maybe if i move to Vista things will get better... and guess what - i was wrong... in the middle of some game - the monitor went black and said "SIGNAL LOST" all the time... the same things that i had with XP... only that in XP - in the event viewer it told me something about infinite loop and stuff... and in Vista it's just died, saying that the video drivers caused an error... i wish there was a single pattern for all these problems... something that u could point a finger on it and say: "Here is the problem!"... but as u can see - it's not... what can i say OldB... we are just lucky?

Dec 22, 2008, 08:41 PM	#1440
Rayline TWB DriverHeaven Junior Member Join Date: Apr 2008 Location: Norway Posts: 51 Rep Power: 0 System Specs	Re: Vista and 7.3 Display driver atikmdag stopped responding error I know, I just confirmed his question about reverting to XP.....:-) __________________ Dancing your souls away...........