Vista and 7.3 Display driver atikmdag stopped responding error

australis

Let's change it a little bit as:
IF "HD* 512 GDDR3" THEN GOTO :hell
so that it includes my ati too ahaha

TheJakeOtt

lol. I'm so... I don't even know what to freakin say. I backed up my clock speeds, and thought everything was all good - THEN?!! I played Crysis on max DX10 settings for about 3 hours and guess what I get...

Just guess.

HA! Nope, no TDR...A DAMN BLUESCREEN citing ATIKMDAG as the faulting module. I swear to god this crap is getting OLD! LIKE A DAMN YEAR NOW DEALING WITH THIS ERROR WTFFFFFFFFFFFFF

TheJakeOtt

/\ Same thing again today...
|| No TDRs, just a page fault bsod after playing Crysis
Warhead for an extended length of time with the reduced
clocks (670/879).

Not a single TDR though.

I'd say, as a general rule, watch your GPU clock.
Compare it's default levels to whatever is factory specs
for whatever GPU your specific card sports...Underclock
it even. 10-15MHz can make a difference in some cases,
it did in mine. Negligible performance decrease for a
fairly signifigant reduction in your GPU temp and an
equally significant reduction in the number of errors
you'll see.

PenrynHD

Hi friend's,
I haven't been here for long time and now I'm.
I think that I have fixed this shitty problem.

Guess how?

I have installed this drivers:
http://www.asustreiber.de/downloads/...01e_vista_asus

Before installing this I have removed another drivers and removed my card from system and I have restarde my laptop.

Next I have installed this drivers and no bsod's for 3 weeks

I recommend to clean a registry because I had one freeze but atikmdag recorver skill.
I have cleaned my registry by Rec Cure and no freeze too.

Greetings from Poland!

Raduque

I finally fixed my TDRs.

How you ask?

Well, it's simple: I put my second monitor in storage.

PenrynHD

Ok, after 3 weeks I get my sucked atikmdag.sys BSOD
I have mailed to Asus Corporation again...

But, I have found another solution. Cleaning registry everyday after using....
I will check it. Maybe it's working

Your sincerely,
Atikmdag.sys BSOD REGULARY USER

EDIT on 1/04/2009 14:25:
I have send my .dmp to Asus Poland, and enginier from Asus reply to me that he will send me atikmdag.sys file to overwrite, because he had the same problem as me and this fix it for him. I will post this file here when I get it.

jason50

Hi all

My first time on driverheaven just bought a new dell studio had it for about a month with out any hiccups but now this this damb thing happens about 4 times a day Tried all fixes and just dont know how to correct this tried new drivers tried setting the fan just completely tired of this problem and its only been two weeks.What can i do to rectify this annoying problem.

BadMouth

First of all, for all new members of this forum look at this thread for information that may help you find your cure to TDR. Sure you may have no time because you are too busy picking your nose or solving your other life problems, but if you have the time for those things, then read the 1 + 53 pages of this thread as done by most of us members and try some of our members solutions before asking for help. I hate the fact that some posters say they do not have time to read all this thread, well man, then I guess you don’t have time to fix this annoying problem as well. Don’t expect anyone to do your work, because most of them still have the problem and some of them don’t have the time to explain all solutions nor do they have the time to mind read, when posting make sure you post with full facts, such as your system specs, when it started, and when it occurs the most often.
This would surely help you get more answers to your questions.
B.M

TheJakeOtt

DUDE!!!! Now, that sounds interesting. Can't wait for your post!

The.Rat

well my errors have finally stopped (I hope). How? Well I've updated to the latest unified drivers the catalyst 9.3. Finally I can watch a video file without filling my event viewer with atikmdag errors.

cheers

al_dh

Is it a miracle?! I have been TDR free for 2 weeks since installing Cat. 9.3. I may have had one instance of it, but I can't say because it may have been another problem. I turned on my monitors after Vista already had been loaded and one monitor was in standby and the other was a black screen, so it had a tdr-like symptom but it also sounds like a problem that others have. I wonder if this relates to my thought on if these tdr problems relate to the interaction between the monitors and drivers.

I installed 9.3, new Audigy drivers, and did a Windows Update that had updates going back to december. So far so good. I haven't done or changed anything else. I read another person over at the AMD forum says 9.3 has sort of fixed it for them too, so hopefully more people will try 9.3 and see how successful it might be.

Good luck to anyone who wants to try!

hauser69

Hi all, just some useful information from my experience. I was getting the "Driver stopped responding" error every few minutes with my Club3D HD4850 card (Asus P5Q-E Mobo) on a newly installed Vista 64-bit. Tried every driver version and every trick and "solution" with no success. I have now solved the problem. Because I was using DDR2 HyperX memory running at 1250MHz I had to jack up the VDIMM to 2.42V. The computer ran stable like this, however Prime95 would fail. I dropped the speed down to 800MHz but forgot to put the VDIMM back down to 1.8V and that was exactly the problem. As soon as I set the the VDIMM to 1.8V I was driver crash free and Prime95 steady.

Hope this helps some people. As soon as I get more time I will attempt to up the mem speed and VDIMM and see how high it can go without problems.

Happy Easter everyone.

australis

anything new with the latest catalyst? it seems I have fewer tdr's but not solved completely.

videodj

Hi all

New to the forum, but been experiencing this error for about a month now, according to my event log, it first occured 10/03/2009, this is a new rig I built on 02/02/2009 and did not have any problems for over 5 weeks, which makes me thing it's possibly software/driver related.

I am running dual screens, 1 is an LCD TV via HDMI, I have tried with the second screen and the errors still occur. I have the latest drivers (9.3) installed have tried the MSConfig fix. This seems to suppress the error message, but something is still causing the system to freeze up, usually while using the desktop or browsing my hard drive.

I have yet to try a different graphics card as I do not have a spare one, but that is next on my list. I ran Prime95 for 12 hours yesterday and didn't cause and problems, all memory tests are ok and I have tried with 1 stick of RAM as well, which still gives the error.

I am planning on leaving the hard drives on all the time to see if this helps, as my issues seem to be non gaming related. I played Total War on Max settings for 6 hours without any issues, although when I quit the game and returned to the desktop the error occured. I have yet to turn off areo, but will also give it a go.

I am at a loss how it was fine 1 minute, but not the next, I have even tried a clean install with the same results.

theheckwithyou

Hello fellow ATI video card users
I too have this problem, so i tired everything
re-installed vista several times using all possible drivers from the one vista installs automatically to the latest 9.4 and still crashed every time i load up any type of gaming program

I already RMA'd the card
Called HIS (the manufacture of the card) they said it was the drivers.
Called AMD (this is where really angers me)they said its my computer, not the drivers. and i should start replacing my computer. I told him that windows tells me its the ATI drivers, his answer that the last set of instructions that windows runs is the graphic drivers so it could be any part of the computer that is causing it. which is total BS.

I find this very disturbing that AMD's answer is to blame the end users computer parts that has been fine up to the point where they install their product.

SO EVERYONE! ITS NOT AMD'S DRIVERS! ITS YOUR COMPUTER SO START REPLACING YOUR PARTS

I'm thinking about installing xp to replace vista.

btw you guys have a great forum!!

Randomhero204

POSSIBLE FIX!!!






I have an ati radeon hd3870 video card. I got the atikmdag error awhile back and I solved it by removing the windows update (KB952287). This solved my problem till about 4-5 days ago. I've spent atleast 8 hours a day trying to solve it since. I solved it again by removing a Microsoft .net frameworks hotfix or update. I decided to try to do this because I was browsing endless forums and someone said it was a possible solution, due to ATI using it to do something. So this is not my fix I didnt bookmark the page so I cant give a link to the person who came up with it. I removed the update/hotfix w/e it was, the past 5 days are a blur lol and it was fixed. Only acted up once when I was playing battlefield heroes after 5mins and it was just for a second. Then went away and haven't had it since. Before this the second I turned on my computer, my screen was flickering with red and stuff like it does when atikmdag error kicks in. (btw i forgot to put this in I went back to the 8.7 drivers and just installed the display driver CCC is gone)

Randomhero204

That's why I just fixed it again right lol. Damn AMD is freaking stupid. If it was my hardware how would removing certain things fix it?

OldBuzzard

@ theheckwithyou

@ Randomhero204

I assume that neither of you are aware that nVidia owners have the same issue with TDR's?

Yes, it IS in a way, a hardware issue to the extent that for some unknown reason, certain hardware combinations seem to trigger this issue.

However, the CORE problem and and where the true 'cure' will come from is within Vista and Windows 7. Yes, WIndows 7, because it too has the same problems.

I would note that, for you folks that tried the MSCONFIG FIX and are still getting occasional TDR's, you should try turning off AERO. That can make a difference.

__________________
When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY

theheckwithyou

OldBuzzard, yes i am aware that nVidia has the same problem. I was upset that AMD rep told me it was my comp components is causing the issue, rather than the Rep telling me that there is an issue between the drivers and windows vista.

Yes i agree that hardware may have caused the conflict but it doesn't make any sense because I had my 4850 running with cat 9.2 under vista without any TDR issues. This lasted about 2 weeks, but once windows updated it self the problem occured, and i have tried to follow the same steps that lead to the card working properly but i had no luck.

What i should have done was do a system restore from the day before the windows update.

My solution: went back to XP.

Mac Daddy

Odd you mentioned that was benchmarking with Win7 Ultimate X64 build 7100 on the weekend and Win7 automatically turned off Aero and "adjusted desktop settings" before running 3dmark6 and Vantage.

__________________
"My mom said the only reason men are alive is for lawn care and vehicle maintenance." - Tim Allen

Randomhero204

Same with me my card was fine untill a windows update. I removed the update and I was good for a bit then it came back. After spending 5 days trying to fix it I went back to XP. It sort of solved my problem I have to use rivatuner and keep my fan at a fixed speed. I really wish I could fix this problem its very annoying. Starting today even with rivatuner sometimes it does it. Also I do know nvida owners have this problem to. Like someone else said his computer was fine untill an update then BAM. This goes for me too my computer was fine for almost a year then after that update it all went down hill. Therefore I just dont see how its a hardware issue.

TheJakeOtt

Keep in mind that this is a very general type of error...it can be reproduced under many different circumstances with many different hardware configurations. With mine, I neutralized powerplay by setting all the different clock settings to the same speeds and disabled fan speed sloping with a bios editor and flashed the video card's bios. I also found that advice I had received from my RAM's manufacturer's forums about latency and voltage were incorrect, so I corrected that and I've been TDR free for quite some time now. I can play a game (assassains creed) while a video plays in a media player in the background and I'm running Vista x64 with aero on and 2 monitors hooked up - NO TDRs whatsoever. I found that I CANNOT overclock my video card at all without having these errors...In my specific case, changing these things completely freed me from the tyranny of TDRism.

Things I've read suggest it could also be a result of heat damage (or just overheating), the card might not be getting enough voltage, some manufacturers overclock their cards incorrectly right out of the factory (high clocks with low volts), it could be memory error related, hardware incompatibility, wrong blood type...seriously it could be a millionbillion things, you just have to examine your situation closely to determine what things might be out of place by paying attention to what exactly is going on when the error occurs...even then you might not be able to make an accurate hypothesis (like in randomhero's case). I just started trying different things based on what I read of other users' experiences until I found what worked. I, personally, feel I found a solution because I actually have WAY TOO MUCH time on my hands.

Your best bet is to start by undoing any overclocking there might be on the card, and see if that helps...Compare your card's current clock speeds to AMDs specs for that specific GPU. If you're already over that line, cut it down until you can do whatever you're doing for longer than you could before and move forward from there. Otherwise, there's 50 different directions you could head from there.

If this error bothers you enough, you'll read through this entire thread. There's lots of things in here that can point you in a good direction.

Randomhero204

possible fix



Well after trying a ton of things on vista 32 bit I went back to xp and still had this issue. I then went back to vista but 64 bit this time and nothing worked. I went to windows 7 today tried playing a game (w/out installing any drivers just using the windows driver) and had the same problem. I then went and got the newest DNA windows 7 drivers and it amazingly worked *knock on wood* normally i went into the game and as soon as the fan on my gpu kicked up atikmdag driver has stopped responding blah blah blah. After i got windows 7 and the newest dna drivers the fan goes up np all is well thank god i have hopefuly fixed my problem *knock on wood*. DNA has vista drivers too. I think the new vista and windows 7 drivers are the same actually so im thinking its windows 7 that fixed it.

E-D@N

yo guys...
it's been a long time since i visited here... seems like not much changed...

just wanted to share some knowledge with you :

some1 here said that ATI told him that the problem is not really the card,
well he is kinda right... maybe you should replace some parts in your computer...
---- HARDWARE ISSUE: (MAIN ISSUE)
first of all i recommend you all to update the chipset of your motherboard to the latest drivers... also update the BIOS if there is an update... it's very important...
also check your memory sticks for errors... (search google for tools) - faulty memory can cause many issues...

second thing... check the PSU... a good PSU is very very very important for these cards... make sure you have a real good PSU in order to get the maximum performance out of your card... and to insure its stability...
AMD Certified Power Supplies - search for your card there...
(look for the 12V+ rail... make sure it's high enough [above 18]... the higher the better...)

Cooling guys! avoiding overheat conditions is also very important to maintain your system at highest shape... so invest some cash and buy a better cooling fans or whatever to your CPU and even just put another fan on your chassis...

keep your PC cleaned, open your computer like 3 times a year and clean the dust...
for LAPTOP users... if you don't know how to clean your laptop - google it or ask...
---- OS ISSUE:
yap - sometimes OS can be the problem, and as said tweaks like MSCONFIG boot stuff or turning off AERO can do the job... just try to keep after the HOTFIXES... and you'll be okay...
---- DRIVERS ISSUE:
drivers... at first i thought that this is the main problem - now i'm not so sure...
sometimes it feels that some drivers are working better then others...
what can i say... try to stick with what that works good for you... that's all...
(DNA drivers are okay... if you are an AGP user - i think that DNA is a good choice)
as for stability - if you have problem with 1 set of drivers - you will probably have problems with all sets...
drivers are definitely not the main issue...
---- 3rd PARTY TOOLS:
sometimes these things can do the trick also...
i can tell from my experience that i've underclocked my GPU speed - and it worked nice... almost like 100% stable... almost didn't notice the effect of it also...

i've fixed my problem by getting a more powerful PSU... no more TDRs since then...

OldBuzzard

Hey E-D@N, welcome back

Good summery. I'll add that this is a VISTA and unfortunately, WINDOWS 7 problem as well. "True" TDR's in XP were handled by the video drivers as opposed to the OS. In XP you would have gotten VPU RECOVER errors.

If you have problems in Vista, go back to XP, and still have the same issues, then it's NOT a TDR issue. You have some other sort of problem.

__________________
When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY

E-D@N

thanks for the fix OldB...

I would like to add something also...
If you had good times in XP... probably you won't have any problems in VISTA also...
I moved to Vista because i had problem with XP... and i saw that they made that VPU Recover for Vista... and so i left XP...
"True" TDRs or not... to tell you the truth - in XP i had like 0% of recovery...
in Vista - i actually did saw that VPU Recover stuff... spared me few times from using the reset button... but since i got the PSU from a friend... no TDRs... no crashes...
the GPU temperature is also much lower then before... and I'm very happy

so all that summery up there - is for you guys... there are still some ppl in these world that are enjoying fully workable ATI cards... and that's because they got luck with their PC configuration...

The.Rat

Sorry but I don't know how anyone can say it isn't the drivers when I've been getting the same error since my system was brand new in August last year and I finally fixed it by updating to the catalyst 9.3 drivers (and I don't intend to ever change them). Before the 9.3 drivers I had tried every release put out with no luck. I've tested all my hardware and it's all good. The problem is the drivers (for me anyway).

E-D@N

as said by my friend Old B... TDRs and VPU recoveries are now handled by VISTA...

I'm not saying that drivers can't be the issue... and i'm glad you found that 9.3 are good for you... but it's not really the problem... it could have been a windows HOTFIX that solved your problem.
Anyway... now that your system works great, sit back and enjoy

movingincircles

I've launched a website about this error. Hopefully you'll find a few fixes there that may help with the atikmdag error.
atikmdag.com

OldBuzzard

I checked out your site, and I see that you are missing the one that works for me and quite a few others.

Actually I 'think' that it may have been E-D@N that first brought it to aour attention in this thread. I may be wrong about that, but at my advanced age, 'being wrong' is nothing new

MSCONFIG/BOOT FIX:
1. Run MSCONFIG in a command prompt.
2. Click the BOOT tab
3. Click on ADVANCED options.
4. Put a CHECK in "Number of Processors", and then select the number of processors your system has. 1 for a single, 2 for a dual core, 4 for a quad.
5. Put a CHECK in "Maximum memory", and key in amount of RAM you have.
6. Click OK, Click APPLY, and re-boot when prompted.

If you still get the occasional TDR, turning off AERO seems to help as well.

__________________
When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY