Hi, my computer's been crashing to a bsod or freezing while playing graphics intensive games. Here's my config- cpu-c2d e4500 at factory clock ram-corsair 2X1gb 4-4-4-12 twinxms2 2.1v psu- ocz stealthxstream 600W gpu- msi 8800gt oc mobo-msi p35neo2-fr hdd-samsung 320gb 7200rpm sata 2 At first I thought it was the RAM so i replaced it with kingston's 2x1gb 5-5-5-18 value ram running at 1.8v. but it still crashes.I checked the temperatures with speed fan and apparently the f71882f(maybe the model number's wrong) super io chip is idle at 50 degrees celsius and reaches till 55-60 while gaming!Moreover I have noticed that when playing fifa09 multiplayer matches my comp never crashes whereas if I am playing anything else it does.Could it be that either my power supply or my motherboard is faulty?or could it be the cpu chip?
I say the PSU. Because you say when you play games it happens ( plays games = Load = More draw power ) so if you have extra psu that you can test your computer with go head. also did you try clean windows install ? lasted drivers ?? bios update ? Otherwise I really don't know what is wrong with your pc
Did you get the number of the error when BSODed? (the Stop0x..... #) Usually that is helpful when troubleshooting things, sometimes not. I'm gonna make some assumptions, and please correct/update us if I'm wrong: 1) This is a computer that has been running steadily for a while, not a fresh built one. 2) You NEVER get this BSOD when solely websurfing, using office applications, or otherwise not playing heavy graphics intensive games. Your pc only gives this error when playing intense games. (not fifa09) 3) You're not overclocking the GPU, or CPU or RAM. 4) you're using XP I think hardware is less of a problem, and that maybe drivers might be the culprit. Specifically video drivers. that said, I'm not sure what that chip you're talking about is and if that's a reasonable temp for it. (I did a quick google, and it appears the f71882f chip you mention is the hardware monitoring/sensor chip. It could be reading erroneously, but it seems that's not too high a temp for it- http://www.lavalys.com/forum/lofiversion/index.php/t2607.html) Here's a link re: the BSOD errors: http://labmice.techtarget.com/windowsxp/TroubleshootingXP/error.htm If you can't see the screen long enough to write it down, you have to disable automatic restarting on errors in Windows. Do you know how to use eventvwr? (You can run it by typing "eventvwr" (minus quotes, of course) in the run dialog box. You could also find it by right clicking the My Computer icon and choosing Manage.) Look for errors in the system around the time you notice the problem and follow those event id codes.
If you want to rule out video problems, you can always run a stress test like Prime95, that will put the CPU and memory through the grinder but won't touch the video card: http://files.extremeoverclocking.com/file.php?f=103
@ModMinded- 1.The computer's been like this for sometime.I had been busy with work so I wasnt able to look into the matter till now. 2.I once got the BSOD when playing a song in winamp.Otherwise I have got it only while playing games.I have managed to run folding@home gpu version continously for 3 days after which my system rebooted. 3.I am not overclocking any component. 4.I am using winxp. By the way, how do I disable automatic restarting on errors?
should have just editted the above post, but .... meh.... I still think it's the drivers rather than hardware at this point. The BSOD error code will help. I'd also try seeing if there are updated stable drivers for your video and sound cards/devices.
I am getting the following error message: IRQL_NOT_LESS_OR_EQUAL alongwith a long line of hex addresses. u guys reckon its a problem with the cpu or psu?
IRQ... that is going to be a software problem that is not the hardware. IIRC, IRQ is for memory access and the error message is saying that it is being given a bad memory address. I use to get a lot of these in linux with crappy drivers (not BSODs but IRQ errors). Check your drivers. Linky http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6077.mspx
If I suspected drivers, I'd probably just download and replace all drivers thus ruling that out. It doesn't take very long, and even if it wasn't the problem, at least you know you have the latest drivers anyway.
When the computer BSOD's what is the driver that it lists beneath the stop code? Example: The culprit in this image is SPCMDCON.SYS
Great answer, and great link... Isaac, check that llink out and try the User Actions section suggestions. True Dat! This is why the code itself is so important for troubleshooting.
