BSOD and unexpected shutdown in Windows 7 64 Bit

I have been dealing with mostly random shutdowns with the occassional BSOD for quite a while.
I have run Memtest 86+ but cannot get it to scan more than about an hour and a half before it freezes. I am not too familiar with how this program is supposed to work but here is what happens. Computer booths up into memtest 86+ starts to run lasts about 15 seconds and reboots this happened twice more before it finally gets going so far I have gotten one error on one Bit at memory 2178.9 MB the assurance code is 154, if this means anything this error was generated after running for almost 2 Hrs. at this point the computer rebooted and ran for about 2 minutes before freezing the code was then 163. On another occasion that I ran memtest 86 the program froze with the screen showing withe lines on a blue back ground with a red bar at the top and a white bar at the bottom.
I have not been able to install the SF_diagnostic_tool, I get an error (see attached file) I have minidump files but don't know how to get them without sf-diagnostic. I am logged in as administrator
THe computer is as follows:
Motherboard: Asus M5A99X EVO
CPU AMD FX8120
Memory Patriot PSD34G16002
Video Card HIS icecube X AMD Radeon HD6950
Monitor Viewsonic VX24553
C: seagate 1TB
d: backup Westerndigital 1TB
E: Music drive Westerndigital 1TB
I hope someone can help getting very frustrated.
Thank you

Hi :).
A single error is enough in my books the RAM cannot be trusted anymore, so posting the crash dumps wouldn't
be much helpful until we get rid of the failing module.

You describe a situation where you cannot test the RAM without the PC freezing, how are you loading MEMTest86+
i.e. via a CD / USB?

Start testing the modules one at a time and let each module complete between 8-10 passes or until errors are found,
whichever comes first. You can also determine whether it's a particular slot / module following this logic;

Arc said:

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Keep us posted :) .

Ok so there is also the possibility of a bad burn process / faulting hardware (Burner / controller) but we can't tell for curtain unless you try booting from a USB and test the RAM one module at a time.

side-note;
Please try and give as much information as you can and not the ambiguous one-liner, thanks.

Thank you the update :) .
Unfortunately a single pass is not enough to determine that the RAM / slot are healthy.
I know it's time consuming, but you need to run each test session for at least 7 passes or until errors are found whichever comes first.

Other than that you're mentioning you're having issues with freezing and having to restart the test in order
to get it to run.
Which leads me to believe that hardware is at fault either being those particular DIMMs or the motherboard itself
(which I lean towards at the moment).

If you're unable to verify the integrity of the RAM either via MEMtest86+ or by testing on a different motherboard
and the motherboard is still under warranty I'd consider an RMA.

I'm sorry that is the case but at least they approved the RMA :) .
Please do post back :) .

Thanks for the update.
I find the odds of that really to big to be the case, three bad motherboards, doesn't makes sense.
Did you eventually manged to properly test the modules as suggested?