• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

have I fried my cpu?

I

imported_soswin

Junior Member
Hello,

Just built a new PC but the CPU fan stopped spinning so it got rather hot and shutdown. When I checked the bios it showed a temp of 100 degrees C!!! I plugged the fan straight into the PSU so it works now (mobo must be playing up, stupid MSI board) and it seems ok but I've had a random shutdown since the incident. Not sure if its the CPU or just a general driver issue as I'm still sorting it all out (got windows x64 Pro + a radeon 1800XT). Does anyone know how a burnt out CPU behaves? If it withstands a few hours in CPU Burn does that mean its ok or can a faulty CPU still cause intermittent reboots? Not sure whether to buy another CPU or not, hoping to avoid it as I cant really afford another 4200+ X2.

any advice appreciated

thanks

Stephen
 
You had xp-64 pro before the incident and there was no random shutdowns of anything?

If so i would say yes, the chip may well be damaged, these chips shouldnt go above 65*C ever. 100*C is crazy, it shouldve shut itsself down long before that happened, even with no fan as long as there is a heatsink it will still take a little time to overheat. Did you test it with prime?
 
The machine is a whole new build, had the problem on the first night so I cant work out where the problem is (only existing parts are memory / HDD / DVD), its my first experience of XP x64. I think the temp monitoring in the mobo is screwed, hence the fan not staying on. Do you know if the shutdown is issued by the CPU or the motherboard? If its the board I guess I'm in trouble.

Not tried prime, currently got 2 instances of CPU burn running. Been about 30 minutes so far, not crashed yet.
 
The bios is supposed to shut it down at around the 65°C mark (default in most bios'). It sounds like thats what happened. It's a bit strange that you could boot up right after to see the bios stating 100°C. At idle, even without fan, you're not likely to hit the 65°C mark - what did you do before it shut down?

 
I was installing various essential apps (war craft 🙂 ). I reckon it spent about 30 minutes without the fan, as I'd left it installing XP. In theory the CPU wasnt being stressed, perhaps the temp control is reporting incorrect readings. Still running cpu burn, seems ok.....
 
So the fan failed on the first day - or possibly the motherboard? Can't you return the CPU/mobo for replacement?

If it really did reach 100C it may be shot, but a mobo's default settings will shut down the system at 65-75C. Unless you turned that off, it's the mobo's fault the CPU is burned. Maybe MSI would pay for it if you were able to prove it?

Anyway, if it did shut down at below 75C I'd have a hard time believing it's damaged.
 
Fans ok, its the mobo not performing. Been offered a replacement board but I bought the CPU from someone else.

I didnt turn cpu shutdown off, but I had flashed the BIOS as it wasnt detecting the dual core. now I think about it, flashing it had turned off the onboard lan fore some reason. I'll check. CPU Burn has been running for 5 hours now, no problems. Maybe I got away with it.
 
Flashing a new BIOS should not turn off the temp protection. That's proably one of the top 3 important settings to have set on your mobo. I can't imagine MSI would have it off by default under any circumstances, and if they did, they should pay for the CPU. It's their mobo that failed and their mobo that didn't alert you.
 
Originally posted by: soswin
Fans ok, its the mobo not performing. Been offered a replacement board but I bought the CPU from someone else.

I didnt turn cpu shutdown off, but I had flashed the BIOS as it wasnt detecting the dual core. now I think about it, flashing it had turned off the onboard lan fore some reason. I'll check. CPU Burn has been running for 5 hours now, no problems. Maybe I got away with it.
Click to expand...


If prime95 also runs a couple hours without problems, you most likely were lucky.
However, I wouldnt trust that motherboard any longer. It might have almost killed your CPU or just reported false information... if I was you, I'd get a new one. Preferably a different model as well. 🙂
 
its probably okay, i have had this happen on a p4 of mine, works perfectly still

bad idea touching the heatsink though, the thing was hot as an iron
 
ran cpu burn for 5 hours and it was ok. Still reboots though, but it only seems to be in warcraft. Was able to play COD 2 fine. Ordered an ABIT motherboard, Nforce chipset this time, I no longer trust ATI motherboard chipsets.
 
Originally posted by: soswin
Ordered an ABIT motherboard, Nforce chipset this time, I no longer trust ATI motherboard chipsets.
Click to expand...

Next time I upgrade, I'll grab an ATI board. 🙂

Had about enough of nvidias broken features.
I mean, the active armor disaster, the IDE sw driver story and a only semi-functional NV gigabit lanport on my DFI NF4 is a bit too much..

Never had an ATI chipset before, but it can hardly be worse than nforce (which I been using since NF2).

 
Ahh, yes.. the tried-and-true 440BX chipset. The LX chipset that preceded it wasn't bad.. it just didn't bring 100mhz FSB to the table like the BX did. Other very good recent ones include the 815 and 865/875.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top