Driver IRQL Not Less or Equal Windows 10

The log files in the latest post had unusual dates  August 2081

Were you able to check them before posting?

There was no msinfo32 in the zip.

For the next BSOD please check the dates.

Run the administrative command prompt command multiple times if necessary to make sure the msinfo32 is included in the zip.

Plan to find a nvlddmkm.sys driver with a different version than what is within the msinfo32,

If there are multiple misbehaving nvlddmkm the next step will be to check to see whether the hardware can be removed from computer using only the motherboard hardware for the display.  If there is no display usng only the motherboard then a swap is needed to rule in or rule out a malfunctioning Nvidia video card.

Do not uninstall the driver until the next set of logs are posted with msinfo32.

.

.

.

.

.

.

.

.

Event[31125]:

  Log Name: System

  Source: Display

  Date: 2018-11-25T00:31:42.832

  Event ID: 4101

  Task: N/A

  Level: Warning

  Opcode: Info

  Keyword: Classic

  User: N/A

  User Name: N/A

  Computer: BenX

  Description:

Display driver nvlddmkm stopped responding and has successfully recovered.

Event[30464]:

  Log Name: System

  Source: Microsoft-Windows-WHEA-Logger

  Date: 2018-11-24T05:16:17.861

  Event ID: 19

  Task: N/A

  Level: Warning

  Opcode: Info

  Keyword: N/A

  User: S-1-5-19

  User Name: NT AUTHORITY\LOCAL SERVICE

  Computer: BenX

  Description:

A corrected hardware error has occurred.

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Cache Hierarchy Error

Processor APIC ID: 0

The details view of this entry contains further information.

bugcheck was: 0x0000000a

bugcheck was: 0x0000007f

bugcheck was: 0x0000003b

bugcheck was: 0x0000000a

bugcheck was: 0x000000fc

bugcheck was: 0x000000d1

bugcheck was: 0x00000050

bugcheck was: 0x000000c4

bugcheck was: 0x0000001e

bugcheck was: 0x00000133

bugcheck was: 0x00000101

bugcheck was: 0x0000009c

bugcheck was: 0x00000124

bugcheck was: 0x0000007e

bugcheck was: 0x00000139

bugcheck was: 0x0000009f

Hello I encountered another BSOD after changing to an older Nvidia driver after performing the DDU uninstall.

Here are the files.

https://drive.google.com/file/d/1UmzxEgsAZWuUAXk3OTxe2YxP2BRidUob/view?usp=sharing

The debugging of the most recent dump files displayed the Nvidia GPU drivers.

The drivers need to be replaced with an alternative driver.

If they no longer crash then that could conclude the troubleshooting.

If the Nvidia GPU drivers continue to appear in the debugging of the dump files and there are no other drivers the GPU hardware must be checked.

Do you suspect the misbehaving driver to be from the GPU rather than the PCI-e USB Host Controllers?

I will do the above tests and report back any updates.

Thanks!

1. There was a recurrent misbehaving driver in multiple dump files.

Perform the following steps:

2. Temporarily turn off Windows updates of non-Microsoft drivers

https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html

3. Uninstall and reinstall Nvidia GPU drivers nvlddmkm.sys
4. Make sure that the new driver is a version other than Driver Version    25.21.14.1694
5. Use DDU to uninstall (see prior post)
6. Use the Nvidia website as the source for another driver
7. Make sure the clean install method is used (see prior post)
8. If there are no more BSOD this will complete the troubleshooting
9. If there are more BSOD and the misbehaving driver is again the Nvidia drivers (using another version) see what you can do to swap the Nvidia card.

See if you can find a friend, neighbor, relative, or local computer store to make the swap.

Then perform two tests.

a) test a new card in the problematic computer

b) test the card from the problematic computer in another computer.