In need of OC help! Please?

CrazyMike said:
now i have the voltage on auto, what should i try it at? I want to try and keep my FSB the same, lol.
Click to expand...

You want to raise it a 100th at a time. so depending on how your voltage settings work (I didn't look at that part) you'll either set it to +.01 or if it's at say, 1.4, you'll raise it to 1.41.
 
Troncoso said:
You want to raise it a 100th at a time. so depending on how your voltage settings work (I didn't look at that part) you'll either set it to +.01 or if it's at say, 1.4, you'll raise it to 1.41.
Click to expand...

Ya i tried going by what CPUZ says: 1.256 went up one notch, i got blue screen. so i am just gonna go ahead and try 377 for FSB.
 
Does anyone know what a Blue Screen that flashes and restarts my computer mean? (all i can read is memory dumps)

I start windows, runs fine for a while, then as i am opening up CPUZ, REALTEMP, and PRIME, the screen pops up and restarts my computer.
 
Sorry to be the one to keep answering your post. Haha. It can mean a lot of things. To find out the actual STOP error, go to

control panel > administrative tools > event viewer > Windows Logs > System

Then in the middle window, just scroll down looking for red circles in the "level" column. That tells you a critical error occurred. there will be a couple for each blue screen. the most recent couple should give you the STOP error that you are getting.

Though I can tell you, it's probably just cause your trying to OC. I got those a lot while doing it myself.
 
Troncoso said:
Sorry to be the one to keep answering your post. Haha. It can mean a lot of things. To find out the actual STOP error, go to

control panel > administrative tools > event viewer > Windows Logs > System

Then in the middle window, just scroll down looking for red circles in the "level" column. That tells you a critical error occurred. there will be a couple for each blue screen. the most recent couple should give you the STOP error that you are getting.

Though I can tell you, it's probably just cause your trying to OC. I got those a lot while doing it myself.
Click to expand...

I know it is deffinately because i am trying to overclock. I just need to know what it is, so i can adjust accordingly. I have a feeling it is my voltage. But unsure.
 
CrazyMike said:
I know it is deffinately because i am trying to overclock. I just need to know what it is, so i can adjust accordingly. I have a feeling it is my voltage. But unsure.
Click to expand...

Well just look up the error code in the event viewer and post it here.

For me it was usually cause my voltage was too low.
 
Well, what a failure. Here is the information about your error message.

Reading around, it's cause your OC isn't stable. Of course, you can fix that with a higher voltage or lower FSB
 
Not much i can do but laugh..... I got it going again, but showing errors in prime.

I guess i will just keep upping the voltage until stable. I read not to go over 1.5V though
 
Made it to 3.4GHz at 1.45V ---- The problem i am facing is high temps (around 60C under load) and an error occured in Prime95 around 1.5Hours into it. Tonight I'll raise voltage and try again. Figuring out something to compensate for high temps.
 
Got a rock solid overclock at 3.4GHz

Everything seems to be running perfect. Ran Prime95 for 10 hours, max temps 63C. Zero errors occured. I am going to look into different options of cooling, maybe take it further. At least now i understand on what to do with situations I had. I feel confident that when i complete my new build, I will be able to overclock with ease :)

Would like to thank everyone who helped. Mainly Linkin (the information crusher lol) and Troncoso. You both helped me out a lot. If you were around I'd take ya out for some suds.

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