Phenom II Bluescreen & random lock ups and reboots?

[Zak33]

Lo dudes

If you've got a Phenom II like me, and you're getting weird lockups.. with a cool cpu, good PSU, quality mobo , good graphics card etc....

then check your ram timings.. and knock it down from DDR1600 to 1333, because although your ram maybe rated right... the Phenom II is a bit weird... and just doesn't like it.

That is all.

PS.. oh perfmance hit?.... barely noticeable. tighten the timings if you like.... having slowed the ram it's tightenable.

[Goobley]

This is exactly what I did with my Athlon II a few months ago when I was experiencing crashes in Cinema 4D. For RAM to be entirely stable @ 1600MHz+ on a Stars system the FSB needs to be overclocked. I found it on G.Skills forum, unfortunately my Athlon wont take it, so I knocked the speed down and tightened it to CAS 8

[Zak33]

it definately varies from cpu to cpu... my previous 905e was rock solid at 1600... but this new hex core wobbled a lot...and yet was cool as a cucumber so wasn't overheating.

I think the memory controller on the cpu's vary...

can't blame the motherboard.. it's the same one... can't blame the ram.. it's the same one... can't blame the psu or the sound card or the graphics card.. all the same ones.

[Max Tractor]

x00000101 - increase vcore
0x00000124 - increase vtt or vcore (you will have to test each one)
0x0000009c - increase vcore
0x0000000A - raise/lower vtt or dimm
0x00000050 - raise/lower dimm (usually, can also be vtt related)



0x00000124 - low vcore or cores unstable (Deneb)
0x0000008E - vcore or cores unstable IIRC (Thuban)
0x0000007F - Memory instability (Heka, Callisto, Deneb)

IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
DRIVER_IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
BAD_POOL_HEADER - CPUNB or RAM
MEMORY_MANAGEMENT - CPUNB or RAM


0x00000124 - low vcore or cores unstable (Deneb)
0x0000008E - vcore or cores unstable IIRC (Thuban)
0x0000007F - Memory instability (Heka, Callisto, Deneb)

IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
DRIVER_IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
BAD_POOL_HEADER - CPUNB or RAM
MEMORY_MANAGEMENT - CPUNB or RAM


Heka, Callisto, Deneb - 0x0000007F Memory instability


picked these up from thread on xs

[Zak33]

x00000101 - increase vcore
0x00000124 - increase vtt or vcore (you will have to test each one)
0x0000009c - increase vcore
0x0000000A - raise/lower vtt or dimm
0x00000050 - raise/lower dimm (usually, can also be vtt related)



0x00000124 - low vcore or cores unstable (Deneb)
0x0000008E - vcore or cores unstable IIRC (Thuban)
0x0000007F - Memory instability (Heka, Callisto, Deneb)

IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
DRIVER_IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
BAD_POOL_HEADER - CPUNB or RAM
MEMORY_MANAGEMENT - CPUNB or RAM


0x00000124 - low vcore or cores unstable (Deneb)
0x0000008E - vcore or cores unstable IIRC (Thuban)
0x0000007F - Memory instability (Heka, Callisto, Deneb)

IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
DRIVER_IRQL_NOT_LESS_OR_EQUAL - CPUNB or RAM
BAD_POOL_HEADER - CPUNB or RAM
MEMORY_MANAGEMENT - CPUNB or RAM


Heka, Callisto, Deneb - 0x0000007F Memory instability


picked these up from thread on xs

dya think we can trust these Tractor? Cos if so I will knock the ram back up and wait for the crash and compare the results

[Max Tractor]

I would give it a try, personally found these to be relevant 0x00000124 - low vcore or cores unstable (Deneb)
0x0000008E - vcore or cores unstable IIRC (Thuban)
0x0000007F - Memory instability (Heka, Callisto, Deneb)

CPUNB or RAM

I would try upping the cpu-nb volts

cheers

[Zak33]

I've been a bit wet and not bothered so far as all my games are lightning fast and rock steady

[Terbinator]

Just to clarify, it definitely shouldn't be the RAM speed as the Thuban's controller is very good.