BSOD Errors after installing Windows 10: IRQ Not Equal and others

Since upgrading to Windows 10 from Windows 7, I have experienced BSOD (or in Windows 10's case, sad face) errors with increasing frequency, to the point that I am considering reverting back to Windows 7.

What happens? (one of the following):

• Computer screen/everything freezes and emits a hum/buzzing noise; or
• Blue sad face screen appears identifying unspecified error, indicating that the computer will reboot (but nothing happens); or
• Blue sad face screen appears identifying IRQ-Not_Equal error, indicating that the computer will reboot (but nothing happens); or
• Blue sad face screen appears identifying (something like) Execute-Non-Execute error, indicating that the computer will reboot (but nothing happens).

I am then forced to turn the power bar off and then back on in order to restart the computer.

In my own (initial) attempts to address this, I did check for a memory problem (answer: no) and I updated my graphics driver. The problem has persisted - and has possibly become more frequent.

As directed, I downloaded and ran the diagnostic program. The resulting file is attached.

Any help fixing this would be MUCH appreciated. I would prefer not to revert to Windows 7 OR buy a new computer (although it might be time to do do...)

Unfortunately there are no crash dump files in the attachment. There is also very little information in your system specs. Please fill these in as much as you can - see here for a tutorial.

Check that you are setup to save the crash dump files and please redo the log file collector when you get another BSOD.

philc43 said:

Unfortunately there are no crash dump files in the attachment. There is also very little information in your system specs. Please fill these in as much as you can - see here for a tutorial.

Check that you are setup to save the crash dump files and please redo the log file collector when you get another BSOD.

Can you please indicate what kind of dump files are required? Right now, my computer would appear to be set up to create the kernel ones, so I don't know why it would not have done so. (Each time it hangs, however, it fails to reboot/restart on its own, so perhaps that is why).

I would go for the automatic memory dump which is the default setting for W10.

philc43 said:

I would go for the automatic memory dump which is the default setting for W10.

Attached is the file generated following the most recent crash.
I suspected either Play TV and/or Raptr of creating a problem. As I don't need either, I have uninstalled both.

Once again the crash dump failed. There are no records of any BSOD in the dxdiag.txt either.

Code:

Event[8534]:
  Log Name: System
  Source: volmgr
  Date: 2016-08-25T17:12:55.600
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: User-PC
  Description: 
Crash dump initialization failed!

Sometimes this can happen if your paging file is too small. It needs to be large enough to capture the memory data for the crash. Might be worth checking this in Advanced System Settings.

Attachment 98198

Mine is set at 1856 MB. I presume that is ok. I have tried again.

And another...

Still no crash dump files

Do you have your settings as shown below?

Attachment 98263

Where might I find that?