IRQ conflict in Windows 10 but option to change interrupt grayed out

Just by way of contrasting experience, I have had a computer where nearly every device was using the same IRQ and there were no IRQ conflict related BSODs. With virtually the whole range of IRQ's vacant and available to be used, neither the BIOS nor Windows could ever be induced to change the IRQ assignments. That scenario seems to have been unique to that specific motherboard as others (same model, still on the shelf) that I checked all assigned IRQs normally. Anyhow I ran that computer for about 12 years in that state, with Windows versions starting at XP Media Center Edition up through Windows 10, until a capacitor blew on the motherboard late last year.

Not that it cannot still happen but the last time I found hardware IRQ conflicts to be much of an issue was in pre-XP versions of Windows. These days I'd look for software or driver issues as likely causes, or defective hardware. Check that your graphics card driver is either all from Nvidia or all from Microsoft update. Allowing the two sources to mix can cause the drivers to be corrupted. Software incompatibilities can also mimic hardware issues. One thing that can cause random BSODs is software that installs or uses obsolete versions of DLL files. Some program or process causes an old DLL to be loaded, which stays loaded, and then at some random time later a different process makes a call to that DLL for a function that isn't supported in the old file version and Windows does a face-plant.

Thank you for getting back to us. This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

To help you fix this, you can follow the steps provided on this link. Or, if the same issue persists, please consider performing a Reset so that we can totally remove whatever is causing the error. Make sure to visit this link on how to perform a backup before resetting Windows.

Let us know if this resolves your concern.

Thank you for helpful information. Please run a system file checker so we can find and fix some corrupted system files due to unexpected shutdown occur on your computer. Head over to this link for the instructions. Also, perform a Safe Mode to diagnose if this is a problem with the services, drivers, or configuration. Visit this link for the instructions.

Keep us posted with the result.

Thank you for the reply. Based on what you have mentioned, you are using a different kind of antivirus on your computer. That is a big factor of system failure because different antivirus can have a conflict with there functionality that can affect the whole operating system. We suggest uninstalling different kind of antivirus and let the Windows Defender do the scan for you.

Let us know if this resolves your concern.

I uninstalled Norton and re-enabled Windows Defender. I got another random crash today.

Here is the screen of the Dell Support Assistant system failures tab.  It was not able to identify the reason for the crash.

Note the previous crashes.  On the days in which there were no incidents, the computer often was shut down due to there being no power during electrical upgrading at our house.  As I mentioned above, I can have crashes occur almost daily. 

I believe my troubles could well be due to software or driver conflicts, but I remain skeptical that there is an issue caused by my choice of AV software. 

Just by way of contrasting experience, I have had a computer where nearly every device was using the same IRQ and there were no IRQ conflict related BSODs. With virtually the whole range of IRQ's vacant and available to be used, neither the BIOS nor Windows could ever be induced to change the IRQ assignments. That scenario seems to have been unique to that specific motherboard as others (same model, still on the shelf) that I checked all assigned IRQs normally. Anyhow I ran that computer for about 12 years in that state, with Windows versions starting at XP Media Center Edition up through Windows 10, until a capacitor blew on the motherboard late last year.

Not that it cannot still happen but the last time I found hardware IRQ conflicts to be much of an issue was in pre-XP versions of Windows. These days I'd look for software or driver issues as likely causes, or defective hardware. Check that your graphics card driver is either all from Nvidia or all from Microsoft update. Allowing the two sources to mix can cause the drivers to be corrupted. Software incompatibilities can also mimic hardware issues. One thing that can cause random BSODs is software that installs or uses obsolete versions of DLL files. Some program or process causes an old DLL to be loaded, which stays loaded, and then at some random time later a different process makes a call to that DLL for a function that isn't supported in the old file version and Windows does a face-plant. 

  

Ralf, thanks.  See my response to MS, above.  I've done endless, extensive testing of hardware and driver updating.  The diagnostics and BSOD error messages suggest IRQ conflicts, memory conflicts, and driver issues, but I haven't figured out anything that would be causing this.  That's why the IRQ issue seemed to be worth exploring.