Question BSOD | Stop code: IRQL_NOT_LESS_OR_EQUAL | What failed: ntoskrnl.exe ?

[alxiden]

Hello! The last few days this issue continues to happen. I can be on the lock screen just after a BSOD and 5 second later it will BSOD again and restart. Sometimes I can use my PC for an hour. I have not been able to find any specific trigger for it and event viewer is not helpful.

Things I have tried (at least some):

• Updated every app/driver I can find
• DDU > reinstalled AMD graphics drivers
• Reinstalled AMD chipset drivers
• sfc /scannow (many times)
• DISM scan/check/restorehealth
• replaced RAM
• Disabled EXPO
• Reinstalled Windows (via the settings option, trying to avoid a complete reset if possible, but can do if necessary)

There are probably other things I have tried but might be forgetting. I'm at a total loss here.

Any help would be much appreciated. Thank you!

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

 

[alxiden]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

Hey mate -- thank you so much for responding. Seems I resolved that exact issue by replacing my usb-c to ethernet adapter (from a ugreen to a belkin). However, now the former issue to the one I had before has reoccured a day later... which is random disconnects from the internet (while still knowing windows is connected to something). The only way to temporarily fix is to unplug and replug the ethernet (doesn't need to be the adapter) or to have windows troubleshooter restart the device (basically just disabling and re-enabling the device). (I had to stop using the internal NIC due to other issues... either dropping connection, upload not working, etc... Intel I225-V on an Asus board.... sooooo lots of issues anyways. Already tried installing the newest drivers manually which did not solve issue). Would it be better to start a new thread for this? Again, very much appreciate the help!

 

[Colif]

You might need to get a newer adapter, get one marked

• WIFI6
  
• AX
  
• AC2100
  

and it shouldn't have driver issues for a few years.