Windows 10: BSOD. friend suspects bad driver at fault

Here is the bugcheck

https://docs.google.com/document/d/1YUXAEGaMKR_zbPFF0BrQR1Hj8UIfTJO_z35a-XhCMbk/edit?usp=sharing

:)

 

[SOLVED] Multiple random BSODs, all pointing to the kernel


No BSODs yet but I haven't been playing World of Warcraft which I suspect to be a possible cause.

Was the driver verifier step necessary or just a suggestion?

 

Friend's desktop BSOD - 0x139 ntkrnlmp.exe


Hello.

You can recommend to your for friend to do these steps:

• Use the event log to see if there are higher level events that occur leading up to this stop code.
• If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
  
• If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
  
• Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
  
• Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
  
• Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows, and resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

Also in the dump file it says that the process that was running when this BSOD happened was game.bin. Does your friend play an outdated game maybe?

 

BSOD fault=Driver IRLQ not Less or Equal - L1C63x64.sys


Hi vaargen,

Welcome to the 10forums.

According to the dump there are a few drivers blamed.
The Network In/Output system
The NIC (Network Interface Card) driver

My guess is that Daemon tools is the root of the problem.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window