Quote:
|
Originally Posted by Ollii
Thanks again for your reply. Actually became way too tempted for 4.5Ghz, kept settings like I had them at 4.0Ghz, bumped multi (with 1.25v) = bsod 124, bumped vcore 1.275v = bsod 3B, bumped vcore 1.30v = omgawd magic.
I haven't tested much yet, did a few benches, ran interlburn (no prime yet...but this one really feels stable, nothing odd happening, not in games either. I'll start testing both 4.0 and 4.5 for 2h each. It still isn't enough to be sure, I know, but it's my only computer that can handle what I need to do on computers  . I can't miss it for 12h (except when I'm asleep/at school, though if anything happens...i'd rather be awake). Got a few pics. I'm restoring back to stock for the rest of the day, don't want any unexpected bsod erase my homework  .My temps go a bit higher now but they seem really stable. never go above/reach 57°C. They can fluctuate between 45-56, which is a big difference. (while stress testing only btw). But that was enough tweaking for today  really need to finish my tasks haha. Be seeing you next week then  |
Dont' do prime testing in your main OS especially if you have important documents etc, that is where a partition can be handy, better yet use a different HDD if you can, just load up the OS with the mobo driver, no intenernet connection or antivurs and do all your testing on that. If the OS corrupts its not a big problem as you can reinstall it as many times as you want lol.
I would forget about intel burn test, imho it's a load of crap, all it does is heats the cpu far more than prime blend (which is stupid because nothing will stress the cpu more than prime so no reason to use IBT), however in this case it hasn't done so because you need to be using the up to date intel burn test which has the updated linkpack with the avx instructions that SP1 (Windows 7 service pack 1) can utilise.
As explained above using a different hdd or temporary OS, you can run a 12hour prime test while your asleep. It'll either restart the rig or just stay at the blue error screen (bsod) unless you configure it restart when it does receive a bsod. Eother way you shoudl be able to retrieve an error code, via the bsod screen or in windws when it restarts.
Hopefully next week we can get you to a nice stable overclock with decent temps and voltages
it looks alive
(17 items) |
Antec HTCP
(9 items) | 
Sandy Transformed
(69 photos) |
| CPU | Motherboard | RAM | Hard Drive |
|---|---|---|---|
| AMD Phenom II X2 550 BE | ASUS M4A785TD-M EVO | Kingston HyperX 4GB 1333mhz | 160GB 7200RPM Hard drive |
| Optical Drive | Cooling | OS | Power |
| DVD ReWriter | Scythe Shiruken | Windows 7 x64 | Antec Earthwatts 380w |
| Case | |||
| Antec NSK2480 (Silver) | |||
| View all | |||
|
it looks alive
(17 items) |
Antec HTCP
(9 items) |
Sandy Transformed
(69 photos) |
| CPU | Motherboard | RAM | Hard Drive |
|---|---|---|---|
| AMD Phenom II X2 550 BE | ASUS M4A785TD-M EVO | Kingston HyperX 4GB 1333mhz | 160GB 7200RPM Hard drive |
| Optical Drive | Cooling | OS | Power |
| DVD ReWriter | Scythe Shiruken | Windows 7 x64 | Antec Earthwatts 380w |
| Case | |||
| Antec NSK2480 (Silver) | |||
| View all | |||
Well I'm not sure exactly what my ambient temps were but they were reasonably cool. As you can see my temps peaked at 75C just short of an hour on prime. This is when i opened my window for the night and it was a pretty cold night. A good frosting on the ground outside.
