irql not less or equal

[j8choi]

I get this blue screen of death every so often. changed video cards and updated drivers still happens.
-also is 70 degrees celsius too high for cpu temperature? i have athlon xp 2000+

[revil]

i got that problem a lot when i was on an xp1700 and using bittorrent a lot. i also got pnf bluescreens. I wish I knew.

[g222leav]

Originally posted by revil
i got that problem a lot when i was on an xp1700 and using bittorrent a lot. i also got pnf bluescreens. I wish I knew.

i got that screen a bunch of times when on my 1700+ it was only when i was reformatting though. i figured it had something to do with the chip/board...cause my 2600+ gave/gives me no problems. and again, i have no idea why.

[bachviet]

Originally posted by j8choi
I get this blue screen of death every so often. changed video cards and updated drivers still happens.
-also is 70 degrees celsius too high for cpu temperature? i have athlon xp 2000+

70C is way too high for any CPU. You should be running under 50C (full load).

[cheapie]

ahahaha...i thought the thread title was IRAQ not less or equal.

[seqiro]

Whenever I've encountered that error, it's been caused by a screwy driver or faulty hardware.

Does the message give you any indication of which file caused the STOP?

[Bires]

Originally posted by seqiro
Whenever I've encountered that error, it's been caused by a screwy driver or faulty hardware.

Yep. This is usually one of those errors that once you get it...reinstall, because system stability is a thing of the past.

I have found, both with Win2k and WinXP, video card and especially RAID card drivers are the most frequent offenders.

[petabyte]

yep.. I'd agree that drivers (especially video) as well as heat, memory and really a whole slew of other things can cause this. I suppose you have to take it one step at a time.. start by getting your cpu temps down.

you never really said any details.. like what the error was after you see a "STOP" in the error message. What comes after that "STOP" will give more clues.

Here are a few links that explain things a bit better.

http://support.microsoft.com/default...b;en-us;810093

http://support.microsoft.com/default...Fwct072001.asp

and then this thread (I'm linking to the last page of it as it has most of the relevent "fixes" but see the other pages of it too)
http://www.hardwareanalysis.com/cont...ic/5695/?o=100