Windows 10 Various BSoD with different errors

kemical said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffbf4, 0, fffff802cf6b69a0, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup:     memory_corruption

Hi,
although memory corruption is being blamed by at least two of the dump files this is probably a driver issue.

I started checking your drivers and quickly noticed how uniform in date they were.

This usually means some sort of application or download has been used to find the drivers.

XQHR0.r0

XQHR0.r0 Wed Sep 16 04:29:49 2015: BigNox VirtualBox Windows Driver package

I found the above driver at the end of the driver files and if correct is probably the root of your issue (your last dump file even named it). Downloads and applications of this kind do you no favours and your far better off sourcing the drivers yourself.

Most of your drivers can be found via your motherboard manufacturers support page:
Asrock Z68 Pro3

So remove the BigNox application or package and update your drivers via the motherboard page. If there are any drivers you can't find, post them up and we'll take a look.

I forgot to mention, post any new dump files.

Click to expand...

kemical said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffff998d4b8f2cc0, 2, fffff801a021fe8f, 2}

*** WARNING: Unable to verify timestamp for XQHR0.r0
*** ERROR: Module load completed but symbols could not be loaded for XQHR0.r0

Could not read faulting driver name
Probably caused by : hardware ( XQHR0+1fe8f )

Followup:     MachineOwner

Hi,
aah so it's an android emulator.. Thank you. I still feel it's to blame however and as you can see from the above dump file it's getting plenty of mentions:

Code:

PROCESS_NAME:  NoxVMHandle.exe

Code:

PRIMARY_PROBLEM_CLASS:  IP_MISALIGNED_XQHR0.r0

It's also mentioned in the Call stack.

Is it possible for you to remove the Nox software and see if it helps at all?

If it doesn't we can try other things like testing the 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

Click to expand...

kemical said:

Thanks for the update Windoof.

Unfortunately yes you could wait that long or try running the driver verifier. In order to run the verifier you must first ensure you have some way of getting back into safe mode so that the verifier can be turned off. This is because on the odd occasion the Driver verifier will cause a boot loop so it's definitely needed.
Link Removed

Now it's safe to run the verifier and the following guide will explain how:
Link Removed

Click to expand...