My pc keeps blue screening?

Hi all,
I have a really weird problem on my pc it keeps blue screening when i run certain applications eg, dvds or pc cillin.

At first i thought it was a dvd drive issue so i insatlled a different dvd player but still the problem came up, it blue screens like 20-30 mins into dvd!
So after that i decided to run my pc cillin just incase it was a virus and it blue screened again like 20mins into scan?
I can run games with no problems with all settings on high etc etc?

What can this problem be? and how do i find out exactly what the problem is?
After my pc restarts it gives me a report saying windows recovered from a serious error.

My pc spec is in sig, all drivers are up to date!
I just dont want to have to do a full format as i have alot of stuff on my hdd, and i dont really fancy putting it all onto disks!

Any help welcome cheers in advance
Dave.

Hi, walker2009.

What is the message on the blue screen? The 20-30 min. before the error likely indicates over-heating.

From your specs the machine seems fairly new, but you could still clean all fans, and run it with the cover off with a floor fan blowing at it from the side that the M/B is screwed on to.

It definatly isnt a heat problem as i have a zalman 6000cu cpu cooler applied with artic silver 3 and 4 zalman case fans! my cpu runs @ 35-45oC @ full load depending on a hot day

This is the error discription in admintools/eventviewer/system-

Error code 000000d1, parameter1 901d1718, parameter2 00000002, parameter3 00000000, parameter4 f87e8e6f.

Apparently its a driver or hardware related issue but its hard to tell which driver as i dont know exactly how long i have had this prob, and i havnt recently installed any new drivers or hardware?

WOW! I echo that!

Sorry I can't be of more help.

A pointer here...

----------------------------------------------------------


.........from eventid............

Source System
Type Error
Description Error code <error code>, parameter1 <param 1 value>, parameter2 <param 2 value>, parameter3 <param 3 value>, parameter4 <param 4 value>.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Comments Adrian Grigorof
Most of the problems leading to this event indicate faulty hardware, bugs in device drivers or incompatible hardware.

A troubleshooting approach from a newsgroup post: "Boot from CD to start the Recovery Console, then read setuplog.txt, and setupapi.log, to see what happens when it boots.

Another newsgroup posts suggests that this error requires the debugger to look at the parameters of the error. Usually this is some hardware driver failure. Running 'verifier' may identify it. Article Q244617 - How to Use Driver Verifier to Troubleshoot Device Drivers in Windows 2000 may help."
--------------------------------------------------------------

Thanks for ur help anyway m8 cheers, i think im just going to do a full format. :(

Pure speculation, but if it's hardware I doubt whether format is the course to take. Uninstalling/changing drivers seems to me the better option.

However....

but from a full format i can decipher which driver/hardware is the problem! as it is now i would just be stabbing in the dark?

Got it! Absolutely. My mind was set on the 'format-OS' relationship.