Memtest+ Unexpected Interrupt - Halting

[danhazelwood]

I've been having problems with BSOD / Freezes / Crash Restarts for the last several weeks. my original post on the issue is:

http://www.tomshardware.com/forum/323233-31-random-freeze-crash


The reason i'm posting here now is I ran MemTest+ over night and below are my results:


IMAG0147


IMAG0146


Is this my RAM, CPU or Mother Board causing the error?

 

[dr_Fell]

Hey dr_fell,

I troubleshooted mine for months. My solution ended up being as simple as adjusting my ram latencies and downclocking the ram to 1333 mhz, which happens to be a speed that the phenom 925 likes a lot. I would add that it did most of the time take an hour of stress before it would crash, even though it wasn't a heating problem. So double check all of your ram settings and be sure you're running it at speeds with which your new processor is compatible. Maybe do some reading about the 965 and what ram speeds it likes.

Have you run prime 95? I was able to isolate the ram as the problem by running the 3 tests, one stress memory the most, one stresses the cpu the most and one stresses their cooperative performance. can't remember which is which but I'm sure its in the documentation/prime 95 forum.

What processor where you running before the upgrade?

Hello. Thanks. I ran Athlon X2 64 before (so I have DDR2 RAM). Today I put my athlon back into socket and the problem still exists - so it is rather hardware damage (that started some days after CPU change) than mem settings. (I have four DDR2 800 chips clocked at 800, tried many different settings, that worked before). The problem appears much more often and sooner with GEIL Ultra than with Twinmos Twister memory (I have two of both). With Athlon (that puts less stres on the mobo and psu) it is very hard to recreate this error with Twinmos and still easy with Geil. With Phenom II system gets unstable with both Geil and Twinmos, but much faster with Geil. This memory worked with this mobo for over a year so I'd rather say some part got damaged and it seems it is MOBO (although tommorow I will check RAM with other computer to be sure and try diferent RAM settings once more, as You sugested).
I will try prime 95 too, thx.