SPCR

Just recently I'm starting to get blue screen on XP
I really don't know why it does that, or maybe it's because it's the newly fan I replaced (panaflo L-series). I checked my BIOS it says my CPU temp runs at 36C/96-96.5F
Is this temp too high?

Thanks

36C is a very low temperature...when did you get this reading? Did you just turn the computer on and enter you bios and read this temperature? If so, then it doesn't mean much.

It takes time for the temperature to go up and then stabalize. One way to get relatively accurate temperature readings is to leave the computer on for at least 15-20 mins, then reboot and read the temp from the bios. Another way to use software like speedfan to read the temp while the OS is running (you should see the temp go up if you launch the program as soon as the OS starts).

Did the blue screens start shortly after you swapped the fans? What are the rest of your system's specs like? CPU? Case? PSU? HD?

No. If I could keep my processors at 36C, I'd be jumping for joy. BSODs could be an indication of memory errors or other problems. I would try running Memtest86 for a while and see what comes up.

That's the reading I got after leaving my system on for the whole day. I just checked that it actually went up around 39-41C/103-104F..

I wonder if it's still too high. If not, why could be the cause of my blue screen? Perhaps drivers?

I doubt that those temps are too high...

More likely it is some software problem...could be anything (including drivers)...BSOD are caused by so many different things.

My advice is to write down the error message you get and then google it. You might be able to find the cause, or at least get an idea.

If 36C is your processor temp and not your case temperature, it's very fine. Assuming your processor isn't defected or something, anyway. The best way to test the stability of your processor outside of windows is to leave it running memtest86, http://www.memtest86.com

intx wrote:If 36C is your processor temp and not your case temperature, it's very fine. Assuming your processor isn't defected or something, anyway. The best way to test the stability of your processor outside of windows is to leave it running memtest86, http://www.memtest86.com

Actually memtest doesn't stress your cpu much, it is designed to stress memory.
For CPU stability testing most use prime95 torturetest, however I think this is just a windows issue with conflicting drivers or some such: next time you get BSOD write down the error code then do a google search for it you'll probably find a description and in best case a solution as well.

zed939 wrote:

intx wrote:If 36C is your processor temp and not your case temperature, it's very fine. Assuming your processor isn't defected or something, anyway. The best way to test the stability of your processor outside of windows is to leave it running memtest86, http://www.memtest86.com

Actually memtest doesn't stress your cpu much, it is designed to stress memory.

No it doesn't, but bad RAM can be a prime cause of BSOD's so it's a real good idea to check for it.

Actually, sorry for the wrong info. After leaving my computer on, my BIOS shows my temp running around 40-41C/104-105F, is this still too high?

I just reinstalled my OS once again, so far I've only gotten on reboot. I don't used to get this kind of problem at all, but now all of sudden...

try running memtest86. 40-41C should be fine assuming those are accurate readings. Unless you're overclocking, there shouldn't be any stability problems under 55C.

I have the Asus motherboard (P4P800) and I use its AI overclock by 5%. But I didn't think 5% would cause this problem. In fact, I never had any of problem until recently...This is driving me nuts....blue screen comes up all different everytime.

EDIT:
I just ran the mamtest thing, I had 99% pass in 12 Test and on Test 12, it seems like it was stuck at 6% for almost 40 mins. So, I rebooted my computer. Should I let it finish?

Try (temporarily) running at stock speeds and see if memtest86 still fails - let it run for 24 hours, just to be sure. If it does, you've got some bad RAM in there - try removing one stick at a time and retesting, to see which stick is bad.
memtest86 shouldn't fail within 24 hours. If it does, you have memory problems - of some sort.

Jliao wrote: EDIT:
I just ran the mamtest thing, I had 99% pass in 12 Test and on Test 12, it seems like it was stuck at 6% for almost 40 mins. So, I rebooted my computer. Should I let it finish?

RTFM.

From Memtest86's website:

Memtest86 Test Descriptions wrote:Test 12 [Bit fade test, 90 min, 2 patterns]

The bit fade test initializes all of memory with a pattern and then sleeps for 90 minutes. Then memory is examined to see if any memory bits have changed. All ones and all zero patterns are used. Since this test takes 6+ hours to complete plan to let this one run overnight.

Ooops!

I actually get it run last night. It finished about 12 pass with no error.