Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Conflict with Flashget and ati2dvag.dll


  • Please log in to reply
2 replies to this topic

#1 rooster_1569

rooster_1569

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 27 July 2009 - 06:42 PM

Hello peoples!

I recently installed windows XP Home on a new HDD, and when I use Flashget (version 1.73), very shortly after initializing the application, my screen seems to freeze. Typical behaviour is for the mouse pointer, shortly afterwards, to also freeze.

At this point, I get a message on a blue screen:

A problem has been detected and windows has shut down to prevent damage to your computer. The problem seems to have been caused by the following file:
ati2dvag. If this is the first time you have seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
The device driver got stuck in an infinite loop. This usually indicates problems with the device itself, or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.

So, I thought I'd try rolling back to an older version of Flashget (1.72). This seemed to temporarily fix the problem, and I could run Flashget without the error screen appearing. But tonight, it's back to the same old thing happening!! I had previously used the exact same version of Flashget (1.73) with the exact same hardware and motherboard, with the drivers installed from cd-roms that came with the motherboard and graphics card. The only difference now is a new HDD (I now have SATA, and previously had IDE), but everything else is now the same, as mentioned, same graphics card & motherboard, and same drivers installed from same cd-roms!

Can anyone offer any insight into this problem, it would be very much appreciated!

Thanks.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,870 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:11 PM

Posted 27 July 2009 - 07:50 PM

Interesting commentary, http://www.modernstreet.com/general/ati2dvag-problem/

Now, my two cents :thumbsup:.

ATI drivers and user problems with such...are quite common. Good hardware, suspect drivers in many situations.

I've had a few ATI AIWs and other graphics chipsets...my approach is to simply remove everything from the system that smacks of "ATI"....then reinstall the driver package.

Official AMD/ATI guidance: http://support.amd.com/us/kbarticles/Pages...TISoftware.aspx

http://www.bleepingcomputer.com/uninstall/...ll-Utility.html

My advice...never try to just update the drivers in question.

Remove the old, then...install new, undamaged drivers. Note that I do not necessarily say "update"...I update when I believe I will gain functionality by so doing. If the old drivers worked fine for 9 months and then becaume damaged (probably through no fault of their own)...why go away from drivers which have been known to work?

Louis

#3 rooster_1569

rooster_1569
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 29 July 2009 - 12:33 PM

Interesting commentary, http://www.modernstreet.com/general/ati2dvag-problem/

Now, my two cents :thumbsup:.

ATI drivers and user problems with such...are quite common. Good hardware, suspect drivers in many situations.

I've had a few ATI AIWs and other graphics chipsets...my approach is to simply remove everything from the system that smacks of "ATI"....then reinstall the driver package.

Official AMD/ATI guidance: http://support.amd.com/us/kbarticles/Pages...TISoftware.aspx

http://www.bleepingcomputer.com/uninstall/...ll-Utility.html

My advice...never try to just update the drivers in question.

Remove the old, then...install new, undamaged drivers. Note that I do not necessarily say "update"...I update when I believe I will gain functionality by so doing. If the old drivers worked fine for 9 months and then becaume damaged (probably through no fault of their own)...why go away from drivers which have been known to work?

Louis


My thoughts exactly, Louis! That's why I didn't actually try to update the drivers, which was something I forgot to mention in my initial post.

Anyway, thanks a lot for replying Louis, I think I'll try what you've mentioned. I'll let you know how I get on.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users