Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD - 0x000000a0

I have just built a new PC but I'm having some difficulties with BSOD and the PC more generally, so it'd be great if anyone was able to help.

After running Civilization V, I always get a pop-up saying that Windows has detected that my computer is running slow, so I thought it would be worthwhile to run some hardware diagnostic tests. The GPU is able to cope in FurMark without any problems and the CPU also fares well in IntelBurnTest on maximum, both with relatively low temps (below 50s celsius). The HDD/SDD are also healthy and no errors detected.

However, I keep getting BSOD when I run MemTest. I have left it overnight twice and both times I have come back to the PC having restarted from a BSOD. I sat with the program on last night and it was able to make it to 100%, but as soon as I turned my monitor off and then back on the PC had restarted with an error message that it had a BSOD.

I have two sticks of 8GB DDR3 and have tried them individually, in slots 1 and 3, and together, and I seem to get the same error regardless.

After typing chkdsk /r and rebooting I can't boot into Windows. It loads the mobo screen and then goes to a black screen covered in artefacts.

Any ideas?

All the best,
Stephen

EDIT:

I managed to run chkdsk C: /f /r /x through windows repair which purported to fix several problems with the C: drive and the windows' error checking tool is now showing no errors. I had already downloaded and installed all windows updates before getting the BSOD. Could the problems with C: drive have been related to the BSOD or do you still think it's PSU related?

I've uploaded the DM log collector to my original post.

EDIT 2:

I ran MemTest again and immediately turned my monitor on and off, computer rebooted and then reported a BSOD.