Memtest error: "could not start processor"

AntoniSchonken

Honorable
Feb 5, 2014
7
0
10,510
Rig: ASrock 990FX Pro, AMD FX-8350, 4x4GB Corsair Dominator, 1200W Corsair PSU, 2xR2920.

Question:
Lately, my system has been giving a few problems, which I thought was as a result of faulty graphics drivers. When I install catalyst, my system crashes to a black screen. About twice every hour, windows (I use 8.1 pro) hangs for about 30 seconds (usually when Chrome attempts to access the cache) but sometimes for no apparent reason as well.

I decided to run some hardware tests, starting with memtest86. When I run the test using only one memory module at a time and only one core at a time, everything is fine. The moment I add a second module, the test freezes at a random location. When I attempt any test with all cores in parallel or in sequence, I get an error stating that memtest couldn't start cores 3 through 7. It doesn't display the error for cores 0 through 2.

Without using catalyst drivers, I can still boot into Windows and carry on with all my other tasks. CPU intensive tasks, like audio production and processing, run without problems, although things seems somewhat less responsive than I'm used to.

Lastly, running a diagnostic test with Hotcpu caused my system to crash, although the log didn't record when or why.

Is this a problem with the MMU?
 

dmmbbs

Distinguished
Jan 19, 2011
237
0
18,710
multi-thread memtedt may show false +ve result. Going with one core it seems your second module is unstable. My idea is since without catalyst drivers the GPU doesn't stressfully do floating-point math the RAM gets spared.