Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {50, 2, 0, fffff803a183a7d1}
Probably caused by : memory_corruption ( nt!MiZeroFault+211 )
Followup: MachineOwner
Hi,
all your bugchecks were different with one dump file too corrupt to read. Most were like the above and possible causes can range from a driver , faulty system service or bios. It's also possible that memory may be at fault but testing will prove either way.
Looking through your drivers they seem fine apart from:
mcdbus.sys Tue Feb 24 10:34:07
2009: MagicISO SCSI Host Controller driver. This is a little old for Windows 10 and if you don't use it anymore please remove.
BiosVersion = P2.30
BiosReleaseDate = 01/13/2016
BaseBoardManufacturer = ASRock
BaseBoardProduct = 970 Extreme3 R2.0
You also have a Bios update for better PCIE compatibility:
ASRock > 970 Extreme3 R2.0 If the bsod continues then you'll need to test your RAM. Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool See how you go on with the above. If nothing comes from the above we'll go on to do other things, post any new dump files.
