Long occurring BSOD with many forms

zamadatix · 14 Oct 2013

I've had a random BSOD problem for a very long time now and I've upgraded most of the components so I'm not sure what it could be... I'll start by saying what is new since the BSODs started:
Motherboard (ASRock Extreme4, with updated firmware)
Hard Drive (ADATA SP900 120 GB)
Audio Card (ASUS Xonar DG)
RAM (2x 8GB Crucial sticks @1333mhz)
Case (Thor V2)
CPU (AMD 8320 Vishera)
PSU (PC Power and Cooling Silencer MK II 950 Watt)

And things that have stayed the same:
1TB WD Green
AMD Radeon 6950

All hardware is at factory clocks and power, I haven't OC'd anything in this computer.

History and tests:
I have tried unplugging the 1TB WD Green, Swapping the 6950 with a know working 7770 from another computer, removing the Audio Card, and reinstalling Windows. This issue existed on a Windows 7, 8, and 8.1 install. It used to occur if I booted to Linux (which I'll have to try out and reinstall to see if it still happens). The new MB and CPU came at the same time. I have run MEMTEST overnight with all tests enabled and there were no errors (2 passes completed in that time). Prime 95 runs for an hour without issue, I've run Furmark for an hour also. With CPU & GPU at 100% for 20 minutes CPU temp is 70C and GPU temp is 80C.

Causes (from most to least likely to cause a crash):
Flash game - 15 minutes
Video games - 10 min - 6 hours
Web browsing - 2-8 hours
No activity - 8-24 hours

I'll attach all dumps since 9/18 in one zip. Sometimes the problem seems to go away for a few days then others it happens multiple times. The latest minidump had the driver verifier running on all non-windows drivers but I didn't see anything new in it.

Please help me figure this out!

Arc · 15 Oct 2013

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95
______________________________________________________________________________________________

Code:

BugCheck 50, {fffff78000010360, 0, fffff80074afbf0d, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PpmIdlePrepare+ed )

Followup: MachineOwner
------------------------------------------------------------------------
BugCheck A, {1d8977f937c, d, 0, fffff80087100c87}

Probably caused by : ntkrnlmp.exe ( nt!KiCallInterruptServiceRoutine+e7 )

Followup: MachineOwner
---------

zamadatix · 15 Oct 2013

I have already run Memtest86+ (with every test enabled) for ~13 hours and there were no errors, I'll swap out the RAM with known good RAM and see if the BSODs still occur just to rule that out for sure though.

Very rarely the computer will just freeze (or even more rarely reboot without saving the crash dump). I thought it might be power related but I just bought a new one (the 950 Watt) and I have even tested using a known good PSU from another computer in the house (issue still occuring). This is all in a new case so it's not likely a wiring or contact issue.

As for power source I borrowed an APC 1500 RM UPS from work for a night and the issue still occurred even though the UPS indicated the power source was still in a healthy range for wattage and frequency.

Thanks for the help, I'll swap out the RAM and report back.

zamadatix · 15 Oct 2013

Known good RAM from another computer and still a crash. I even tried switching slots (I normally use 2 and 4 (which are paired on the MB), I switched to 1 and 3 (the other pair) when I tested the good RAM.

Things I have tried known good versions of:
RAM
PSU
GPU

Things I have tried with being removed:
Sound card
WD HDD

This leaves the SSD, CPU, and motherboard. The problem existed before I bought any of these 3, I bought the CPU and MB at the same time (new socket) so the old MB couldn't have damaged the new CPU or vice versa. I'll test with a Linux install tomorrow to rule out drivers and the SSD... I'm at my wits end :).

Thank you.

EDIT: I upgraded the BIOS firmware (second time since I bought this MB) and it has yet to crash *yet* even though I have been running things that normally cause a crash. I'll report back in a couple of days if all keeps going well.

Arc · 16 Oct 2013

If it still crash after updating the BIOS, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

zamadatix · 18 Oct 2013

Motherboard update seems to have fixed things :) thanks for the help!

Arc · 19 Oct 2013

Good to know :)

Let us know for any further issue.