Strange comp problem

[TheoPetro]

ok so about 4 days ago i noticed my proc temp jumped from 32 to 45 while idle. but when i moved the mouse it dropped back down to 35. its now at a constant 35. ive been running this system at a stable oc for a week before this happened. now it started freezing up every now and then. the first time it froze i reboted and the bios wouldnt detect 2 of my hard drives. now i checked teh cables and everything (temps are 28-33) and its all fine. now i dont think its the HDDs because they both went out. not just one. there IDE on a master slave cable. i reboted and they came back. but when it froze again they disappeared. and then came back after a few more rebots. any ideas?

 

[Robotoer]

How are you getting your temperature readings? If it's by temperature probes, you might want to not rely on those. I've had experiences in my computer where my temp probes read about 10-15 degrees C less than the embeded temperature monitor in it does. Also, you should check all the cables related to the harddrives such as the power cable, the whole IDE controller and cable. I've had an IDE controller go completely out when i was building a computer. Everything else worked, like i could boot off of floppy and a usb drive, but the ide controller was completely gone.

 

[Duckzilla]

Maybe your overclock isn't all that stable. Does it do it at stock speed? If it does try doing a memory test:

http://www.memtest86.com/

 

[TheoPetro]

memory is fine. ill try a diff IDE cable but would that make it freeze? my OS is on the SATA HDD. it doesnt do it at stock speeds but i had it OCed to 2.45 then i got my swiftech block and bumped it to 2.5. the thing is it worked fine, no freezes or anything remotely unstable. prime 95 was fine overnight. im using speedfan to check temps.

 

[Robotoer]

a different IDE cable won't make any difference as long as you connect it Exactly the same as your previous cable.

 

[Jiggz]

The million dollar question is "Does it do it when it is running on stock speed?" If it does then the problem is not able your OC'ing. Bit if it doesn't obviously it has something to do with your oc'ing. Try re-creating the problem again at stock speed and post again.