what is holding my OC back? X58 Sabertooth + E5640 (followed miahallens tut)

[tiro_uspsss]

First test the rams with HCI MemTest for windows , run eg 8 instances of 512Mb. If that passes 100% the rams are okay. If not lower bclock back to 200 and up the CPU multiplier to 20. To test QPI volts run Hyperpi 32M 8 threads...

how long do I run HCI MemTest for?

[Leeghoofd]

at least 100% - 200% is better....

[tiro_uspsss]

at least 100% - 200% is better....

ok cool.. well I left them running till they reached ~150%

now running hyperpi

[Leeghoofd]

If that passes, lower QPI volts to eg 1.33ish till you find the lowest stable setting till Hyperpi locks... then add QPI again...

For Vcore quick test with 30 mins of Prime 95 custom test 12K -12K set...

[Leeghoofd]

If that passes, lower QPI volts to eg 1.33ish till you find the lowest stable setting till Hyperpi locks... then add QPI again...

For Vcore quick test with 30 mins of Prime 95 custom test 12K -12K set...

[tiro_uspsss]

passed hyperpi! max temp was 55C

I'll run HCI memtest again till all instances reach at least 200%

[tiro_uspsss]

just in the middle of running HCI memtest again.....BSOD

[Leeghoofd]

Wich error code ?

[tiro_uspsss]

Wich error code ?

don't know sorry.. I've changed my settings so that it doesn't auto restart so I can take note of which code

[Leeghoofd]

0124 is QPI, 001 Vcore,...

[tiro_uspsss]

0124 is QPI, 001 Vcore,...

is there anyway to bring up BSOD info from the previous BSOD?

I'm running 8x HCImt.. I have unequal amounts of RAM assigned to each instant.. some instances are well past 600%.. others haven't even reached 200.. then there are 2 instances which I stopped after they reached 500%, assigned more RAM to them, then started again (I closed a few programs so more RAM was available)

so far..no BSOD

[tiro_uspsss]

well.. waited till the every instant went past 200% (others were @ 900+%).. no BSOD

[tiro_uspsss]

finally.. not that I wanted it - I got a BSOD in the 3rd test of prime95: 0x00000124 (*insert truckload of numbers & letters here*)

I took a pic with my phone if need be - but I'm guessing that first set of numbers is what is important?

0124 - that's QPI as you said - increase volts to QPI?

btw, where do you learn what BSOD code(s) mean what?

[Leeghoofd]

trial and error... try lowering it to 1.3 does it boot ? if not up to 1.375

[Albertini]

is there anyway to bring up BSOD info from the previous BSOD?

if minidumps are enabled (they are by default) one of the most comfortable ways to inspect dump files maybe this free tool:

http://www.resplendence.com/whocrashed