Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffff999b13b2a290, 0, fffff802a82bb69d, 2}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!RealSuccessor+11 )
Followup: MachineOwner
Hi,
Bugcheck 50 as well as 1A can be memory related and some dump files do point to it being hardware although software can easily be just much to blame.
Basically either the driver or data or the memory it's being written to is corrupted.
Bugcheck 50 can also be caused by Anti-Virus suites. I couldn't see if you were running anything other than Defender (apart from Malwarebytes) but if you are please remove and just use Defender and Malwarebytes.
You do have a lot of old drivers stemming from 2011 and in fact driver support for your motherboard stops at Windows 8.1:
P5Q-E | Motherboards | ASUS Global
See if you can at least update the chipset drivers
AsIO.sys Mon Apr 6 08:21:08 2009: Asus PCProbe Utility please update or remove.
P5Q-E | Motherboards | ASUS Global
ADIHdAud.sys Thu May 21 09:21:06 2009: SoundMAX Digital HD Audio Driver
Link Removed This driver was originally released for Windows 7. I'm not sure there is an available update..
mv61xx.sys Wed Feb 9 09:28:49 2011: Marvell Thor Windows Driver
mv61xxmm.sys Wed Feb 9 09:28:40 2011: Marvell 61xx RAID controller
http://www.marvell.com/support/downloads/search.do
tapoas.sys Mon Jul 12 01:31:59 2010: OpenVPN Virtual Network Driver
http://openvpn.net/
yk63x64.sys Wed Jan 9 15:46:56 2013: NDIS6.30 Miniport Driver for Marvell Yukon Ethernet Controller
http://www.marvell.com/support/downloads/search.do
If you get really stuck updating the drivers let us know and we'll help.
Do Not use any type of driver finding application as they invariably get it wrong.
File scans- See if they clear up any corruption.
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
If the bsod continues after the above changes then first create a Windows 10
Link Removed.
Run the driver verifier which will stress each program on start up to see if it will blue screen. If it does then a dump file is created (usually Bugcheck C4) with the culprits name attached.
This process can also induce the pc to 'boot-loop' which is where the Recovery stick comes in. You can boot from the Recovery stick, enter safe mode and turn the verifier off.
Here's a handy guide:
Link Removed
Post any new dump files.
Least it's still under warranty for the next 6 weeks!
