ati2dvag.dll infinite loop problem
(+5 rating, 1 votes)
Loading ...Apparently thousands of machines are effected by this “infinite loop” error. What happens most often is, during game play, or watching a video - the screen blurs, blinks, buzzes, and shows odd bars of random color all over it. Upon restarting, you get a BSOD (Blue screen of death), with a stop error.
” … the device driver was caught in an infinite loop…..”.
What is that supposed to mean? You can restart, and restart, and restart your computer, and nothing happens. Same error over and over again. It’s caused by ATI2DVAG.DLL . So far, it corrupts many machines on different platforms, with different video cards and interfaces (however AGP/PCI seem to be the most effected).
ATI/AMD seem to have no fix, or any real information on it. Some of the posts about this error date back 3-4 even 5 years now! And still… it goes unfixed by ATI/AMD.
There’s a post over at the TechSpot forum
however, where a user that goes by the name of - Cobrakaun posted a fix. He posts this fix all over the internet, on every forum he can find that discusses this issue. The fix however, drastically reduces your video cards performance, by running it in a sort of PCI mode (if you’re already on a PCI card, this does not apply, and you could use his fix if you so decided to).
I had this problem, and was able to fix it. After many nights of head scratching, after trying every knock-off, random ass driver variant I could.
How did I fix it? Here are the steps I took to fix it…
I started off with the error of course.
- Started my computer in safe mode. I removed all of my ATI drivers.
- Ran CC Cleaner to remove all of the Registry entries and left over files from ATI.
- Restarted my computer.
- -This time the computer booted properly without needing to be started in safe mode.
- This is the important step- I installed an older version of the drivers. For me, Catalyst 7.4 worked for me.
- Restarted.
- No more issue!
Simply downgrading to an older version of the catalyst drivers fixed my issues. If you stumble upon this and it works, please let me know. If you have any questions, just leave me a comment!
Andrew said,
Wrote on January 13, 2008 @ 12:42 pm
Wow.. I’ve been having this problem with my girlfriend’s computer for weeks now. We finally got the STOP error after weeks of buggy graphics and many attempted fixes.
If this fixes the problem, you will be my hero for life.
I also was so suprised at how young this thread is. Usually googling errors gets you things from 2005 :p
Menekali said,
Wrote on January 13, 2008 @ 10:36 pm
Let me know if you have any issues beyond this point. The 7.4 drivers like I said for me, and many other people, have created the final solution to the issue.
Goathead9000 said,
Wrote on February 16, 2008 @ 8:24 pm
I have had this prob my self for a month or so 1st started with my ATi 1300x doing the multi color glitchy thing then it just got so bad I thought it was just going out so I got the Ati HD 2600xt but then I get this hole Inf Loop @#!^@^#@&#*$&* sorry just a little P O ed. like every 1 els I have looked and looked and looked but no fix till I see this post and it made me think Awww yes every time I uninstaled all driver and ati files my pc seemed so much clearer but I seamed to all ways update driver and BAM!!!!!! same F’n thing Blue screen of Piss me the F off or screen go multi color then Black and pc have no respawns what so ever so that means hit the old powwer strip switch and hope to HolyLeapingJesus nothing els go’s wrong. Well did you have the black sceen? Also when it would go in to the blank screen it would be when trying to load norm in the select a profile screen for windows. Any who, so for so good but will let you know if not please post more info on this if you get any.
Veejay said,
Wrote on March 23, 2008 @ 12:43 am
Hey guys;
Used to have the same problem, but then I found the Omega drivers !
http://www.omegadrivers.net/
Check it out. It works for my ATI X1400 M , *not sure if it will work for you, but it’s worth a go.
So far, no problems with games like COD4, Battlefield 2142 and WOW.
Menekali said,
Wrote on March 23, 2008 @ 12:46 am
I initially tried those as well VeeJay. If that fixed your issue, then that means your system was not actually being plagued by the same issue, as the Omega and OneUP drivers, are powered by ati2dvag.dll, they’re just altered settings.
Furry Raccoon said,
Wrote on April 19, 2008 @ 6:08 am
I’ve gotten the ati2dvag error once in a while when I play a game called “jewels of cleopatra”. But a couple of days ago it started showing up almost constantly. Once I didn’t even get the game loaded before it showed up again. Other times I could load up a level and within 5 or so minutes, it would crash.
Luckily, I remembered my most recent change that I made. I was trying to load an online casino game and it kept defaulting to 60hz refresh rate - too flickery for me. So I went to the catalyst CC and forced the refresh rate to 85hz. It was after that change when I really started getting crashes in “jewels of cleopatra”.
Realizing that the 85hz change may be causing problems, I lowered it to 75hz and it worked better…but…still got the crashes…just not as often.
But to me it seemed it has something to do with the refresh rate so my next attempt was to change the “wait for vertical refresh” option in the catalyst CC. I had it set to “performance - always OFF” and have changed it now to “quality - always ON” - and am happy to say that after a couple days of intense testing, I haven’t had any ati2dvag crashes.
Funny thing is, I can run FSX for hours without a problem, but a simple match 3 game like “jewels of cleopatra” causes a crash. Though the difference there is the FPS rate. On FSX, the FPS on my computer is locked at 35fps. But “jewels” might be going much much higher 100+ and that’s where the “wait for vertical refresh set to quality always on” option may be helping out.
By the way, I am running XP pro SP2 and HD 2600 XT.
UPDATE - It’s been a couple days since I made the above post. I should probably say that when I mention “ati2dvag crash”, that I’m talking about the “infinite loop” BSOD. After searching on the net, there seems to be some other types of problems that can occur with ati2dvag.
Also, my system has been running perfectly and no matter how hard I try, I cannot get it to crash. I have made one change since my post above, I have upped my refresh from 75hz to 85hz with no negative effects.
I did find one post on gamespot about a year ago where someone suggested a possible correlation between vsync and ati2dvag - unfortunately, that theory was ignored and the PCI-bridge method was instead suggested.
http://www.gamespot.com/pages/forums/show_msgs.php?topic_id=25618246
John said,
Wrote on April 24, 2008 @ 7:30 am
I am getting this error, but my problem is before windows loads. I am getting lines through the display when the computer is in its startup sequence. Then I get random characters on the display. Windows XP starts to load and then I get a black screen with white writing telling me there was an error, windows could not load and gives me the “ati2dvag.dll” file as the culprit.
Any help would be appreciated!