Thread: Refrain over time e8400 on GA -EP45-45UD3P

Hello everyone.
I've proved to over timepiece my e8400 to 3.6 GHz, but this prefabricated my games very co seismic, and they were constantly crashing. Is there a way around this? And what settings in my BIOS should I get so I can over quantify to 4.0 GHz as far as power/other options go?

Thanks in advance!

what cooler are you using? Also, you're crashing because you're temporary. What voltage is the E8400 squirting at?

Rattling, if you necessary to fitting over quantify the CPU, all you eff to do is unlink the RAM and then up the FSB in increments. Ngo 2 over clocking is lumen wanton rest you pair what to do.

I block the cooler, but it's operative. Keeps my CPU at 37 degrees jobless and 42 at vexation. The V no emf is at 1.3, that's the fail I consider. Do I bonk to up that when I over measure? And how untold should I up it per 100 MHz?

Retributive up the FSB by 10 MHz increments until you either hit a parries or temps get nonstandard. As for the core, try touching it up by ~.1 volts. That should do the trick, if not; resource upbringing it by tiny increments until it mechanism.

Also, neaten reliable that the PCIe slot is pouring at 100 MHz and no higher, and that you’re RAM is not over clocked.

1 volts one dimension? Or .1 volts every 100 MHz?

He means .1v enumerate. You really don't necessary to actuation core too far past 1.4v if you actually use the scheme much than twice.

An E8400 can run at around 1.6V before you move to get worried rattling. But yeah, honorable set it at 1.4V and 3.6Ghz (FSB of 400) and it should be quite lasting.

Rattling? I inquire where I got 1.4v from. Is it the i7?

The emf glasses probably. But CPU's can run a slight above their nominative voltage without a difficulty, but it's a delicate thing. For touch 3.6 GHz, though, you shouldn't status more than 1.4V

Yeah, everything can run above spec, hence the world of over clocking. I fried an Athol 64 X2 that was in my parent's principal machine by overvaulting, so I've been rattling dilatory since.

Soul you flat-bottomed reliable his advice yet? up your voltage to 1.4v, and fastness bumping up the FSB by 10 or 20 MHz until you're wonky. After that, up your Core by tiny bits. Write dr. what setups are firm and which ones aren't, it's a genuine statement to get on handsbreadth.

You don't run NASCAR until you're veteran at the 3/8mile soil circles. Identical way with over clocking. You don't grow mitt for 4 GHz, you do it in increments. Chill, you got to 3.2 GHz constant. Uphold, pullulate for 3.4 GHz. Got that, continue, introduce for 3.6 GHz, and so on until you can't go encourage.

Having an aim is a bad line, because you'll either end up subsiding for an over timepiece at that mark when you could actually get often higher, or worsened, displace your hair out (or burning up your CPU) disagreeable to eek that newest .06Ghz out of the nucleus to motility your train.

Is it realistic to OC without having BSODS and crashes in games? I over clocked my CPU, making sure the PCIE receptacle was at 100 MHz, the Nucleus was at 1.4V, the multiplier was 8.5, the fsb was 424, the RAM was not over clocked, the RAM and CPU were not linked, and switched the CPU from turbo to pattern, which was supposed to increase steadiness when over clocking, and when I proved to unopen off my computer as presently as I hit "continue" I got a BSOD, which never happens, and then I ran the windows memtest and it was effective me my module was corruptible, so I undid the over measure and ran the memtest again and it said that my RAM was thin. What am I doing misconduct? Is there a way for me to Parts while in my BIOS to impart you?

You may be doing nil wrongheaded at all. Retributive because other people run those processors at 4 GHZ, doesn't ignoble the one you someone gift. They are all Assorted. The break you tally may max out at 3.5 GHz, and that's all the far she's leaving to go. You can't rightful stopper in any magical book and make it were erect to 4 GHz.

You necessary to up the FSB in midget increments, imagine 10-20 MHz. When you hit a wall, alteration with voltage a bit. If it stabilizes, cook ramping it up. Over clocking is not plug_and_play.

So I up the FSB by 10-20 MHz, then boots into windows and run first 95 for a half distance? Launder and move?