Computer Freezing

D

Dan17

Limp Gawd
Joined
Nov 8, 2004
Messages
264
Alright my computer was overclocked at 2.2GHz and was running fine for a couple weeks and then i went away for the weekend. When i came back I used my computer for a few hours it suddenly froze. I decided to reset the computer to stock settings to see if it would fix it. Again it froze later. The specs of my computer are in my profile.

I overclocked my computer with these settings:
FSB -->stock was 166mhz -->raised to 175mhz
Vcore--> stock was 1.650 --->raised to 1.700

Ram and FSB were running asynchronus as they do when they are at stock settings.

I'm thinking that may'be upping the vcore could have messed up the processor or something because this didnt happen at all before i decided to overclock.

Any help would be greatly appreciated
 
Hmm, change anything else at all? Maybe memory timings or something?

Upping the vcore can be problematic to a processor, mainly because it increases the heat a lot more than a simple frequency increase. However, that should be a pretty safe range for a 2800+. Some people have been known to push their bartons up to 1.9 or so on air cooling (better be darned good air cooling!) Mine actually rises a bit above 1.8 under severe conditions even. (It uses what it needs as it needs it down to a minimum of 1.725 or so -- set 1.70, but the board overvolts by 0.025 or so.)
 
Well, maybe the heatsink isn't seated well enough or something so that it was just right to keep it barely ok for stock but when overclocked it was too much. However, if I were you I'd be inclined to check and make certain that there aren't any virii or spyware or anything. At this point, software problems or hardware conflicts or such aren't entirely ruled out.

One thing you may wish to try is a bootable prime95 like linked to here: http://www.mersenneforum.org/showthread.php?t=2098 That will remove the os and basically everything else software from the equation. Also, maybe run memtest and see if you find anything, though a messed up CPU can also cause memory errors just as easily as messed up memory (got any spare memory around?) Of course, if you get no errors in either one, that probably means you have windows to blame or something. I guess let it run a good while (I remember back when I had some memory that was only just barely unstable it'd take over an hour to catch a bug due to it.)
 
I doubt the 0.5V increase could do any harm... you said you're running your ram asynchronous to FSB - is the memory running faster? try running memtest86 - if you get errors - set memory to run synchro with FSB and run memtest86 again..
 
Wait, why is the memory asynchronous?

I don't think you should get errors though. I've run asynchronous before. Thing is, nForce 2 has horrible latencies when you do that. Maybe it's ok in things where bandwidth isn't going to be a big issue (such as watching videos in ffdshow with very high settings in resize and such) but, in things like games it will be pretty bad. Outside of games you won't get any advantage from the memory running higher if that's what you're trying to do. Synchronize that memory again whether you have to lower the clocks of your CPU or you are underclocking the memory... You'll STILL get better results.
 
Alright, i figured out the problem. It ended up something went screwy with a device driver in windows (go figure...). I tested this by using a spare hard drive and installing it in my pc and installing windows. Booted up and ran without freezing, no problems. Now I just have to reformat.

So thanks for all your help you guys.

...Dan
 
You must log in or register to reply here.
Back
Top