(New built) IRQL NOT LESS OR EQUAL, Random BSODs

The most recent dump indicates a problem with Qcamain10x64.sys.

Code:

ffff8600`4a19a270  fffff809`4874f552*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for Qcamain10x64.sys
 Qcamain10x64+0x14f552

This belongs to your Qualcomm Atheros QCA61x4A Wireless Network Adapter. The one currently installed is dated 2/24/2016 12:20:49 PM.

See if there is a newer version available.

Code:

fffff801`3a3473a8  fffff80a`d8d289fd*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for Qcamain10x64.sys
 Qcamain10x64+0x1289fd

Qualcomm Atheros QCA61x4A Wireless Network Adapter

Code:

fffff801`3a347758  fffff80a`d8f54c14*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x84c14

Intel Graphics Accelerator Drivers for Windows

Code:

	
Code:
	
BugCheck A, {0, 2, 0, fffff803ec87b248}

Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::NotificationDpc+1f1 )

All over the place, Wireless, Video and Audio. Check your PSU voltages. You can usually do this in BIOS Setup.

Remove all over clocking, CPU and RAM.

Voltages look okay. Only way to tell if a PSU is bad is to replace it but I don't think that is warranted in this case.

I would not use Drive Easy. Better to find and download updates manually.

Also would be a good idea to test your ram. For 16GB it can take 10 to 14 hours so run it overnight.
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

If there are newer BIOS versions available, update to the latest one. Won't hurt, may help.

You can try enabling Driver Verifier, see if that gives us any better idea of the cause of these problems.

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to
PART TWO
and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.

The 2/7 4:11Pm dump shows this:

Code:

BugCheck C9, {21f, fffff80a3061b174, ffff840c90996570, 0}
*** WARNING: Unable to verify timestamp for ScpVBus.sys
*** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys
Probably caused by : memory_corruption

Known to cause BSODS, see an post I made awhile ago here: Error code c0000005 - Not a BSOD