ati2dvag.dll

[MatthewA]

Whenever I run a high-graphic program, the computer will bluescreen soon after it starts. Not immediately, soon. For instance, if my screensaver comes on, all is fine. As soon as I close it, bluescreen of death. The following message comes up:

STOP: 0x0000008E (0xC0000005, 0xBF07642E, 0xA311B713, 0x00000000)
***ati2dvag.dll***

I have done research on the topic, and found that the cpu temperature will skyrocket just before it crashes. I haven't however found a solution. Of course there's the usual spyware/drivers/hardware/-format it- sort of things. I really need to use this computer, so I need help urgently. I have run scans on Avast, Ad-aware and spybot s&d.

Computer:
Media Centre 2005 SP3
Chip type - ATI display adapter

According to my dxdiag tool,

I hope that is enough info.

[Fren Banklin]

Well first I'd wonder why your temps are high. Is the CPU fan working ? Is there a fan on the video card ? Is your CPU being run up to 100% by some applications, maybe malware ?

Have you checked your thermal compound ?

Is your PSU adequate for the power draw of your hardware ?

Also, uninstalling & reinistalling your video drivers might help.

[POADB]

Some people have had success with this:

Right click-mouse over My Computer
Properties
Hardware(Tab)
Device Manager(button)
Click [+] next to System devices
right-mouse on CPU to AGP Controller (or whatever your controller is called)
Update Driver(button)

Select Install from a list or specific location (Advanced)
Next(button)
Select Don't search. I will choose the driver to install.
Next(button)
Select PCI standard PCI-to-PCI bridge
Next(button)
Finish(button)
Reboot.

http://www.techspot.com/vb/all/windo...-Loop-Fix.html

[Fren Banklin]

Originally Posted by MatthewA

I have run scans on Avast, Ad-aware and spybot s&d.

It's probably off the immediate topic, but after re-reading your original post, I noticed the above.

The general rule is one AV program, one anti-spyware program. Anything more than that is unnecessarily redundant, and they do sometimes have problems playing with each other. I'd get rid of spybot, and keep ad-aware. Spybot's Tea Timer prevents legitimate registry changes and causes all sorts of havoc, and is more trouble and risk than it is worth, IMO.

[Klint]

Also, what version is your display driver, also what card are you using??

**ati2dvag.dll*** is referring to a display adapter

[Fren Banklin]

Check Device Manager for flags. Show "hidden devices" Uninstall all flagged devices and reboot. Report here all devices that do not reinstall correctly.

[MatthewA]

Originally Posted by POADB

right-mouse on CPU to AGP Controller (or whatever your controller is called)
Update Driver(button)

Select Install from a list or specific location (Advanced)
Next(button)
Select Don't search. I will choose the driver to install.
Next(button)
Select PCI standard PCI-to-PCI bridge
Next(button)
Finish(button)
Reboot.

http://www.techspot.com/vb/all/windo...-Loop-Fix.html

Which controller would that be for me?

[Xura]

Have you tried to completely uninstall ALL display drivers by booting up in safe mode and using Driver Cleaner?

After doing that, try reinstalling the display drivers, NOT the catalyst suit.

[POADB]

Originally Posted by MatthewA

Which controller would that be for me?

Ah - no AGP, I didn't stop to realise.

However, from the same page I linked you to a user sated this:

I have a PCI card but had the same problem ever since I got this computer, and nothing fixed it. I tried your fix. I didn't have the system device "CPU to AGP Controller" but I did find "PCI bridge" available as a driver under the system device "LPC controller", so I set it to that.
That didn't help, but there was also a choice of two "82801FB" controllers, one by Intel, which it had previously been set to, and one by Microsoft. I set it to the Microsoft one and I haven't seen a crash or infinite loop since. I've just played four hours straight of Battlefield2 demo and it worked perfectly. Before, it was crashing every 10 mins in that game.

So I think you're definitely on the right track, even for PCI cards. I never would have thought to try that if I hadn't seen your post. Thanks man.

You have an LPC Interface Controller, but I would try Xura's suggestion first.