Windows 10: Intel SCSI 17.11.0.1000 driver causing BSOD problem

I own an Asus Vivobook X509JB. I have been having a BSOD problem for three weeks, and I have tried almost all the solutions I found over the internet. I recently clean installed Windows 11 on my device, and BSOD occurred again within an hour or two.So I analysed the minidump file using Windbg preview, and from there I found this Intel SCSI 17.11.0.1000 driver this is the listed driver for my device on ASUS customer support causing the problem, So I uninstalled it, and there was some different version of the driver got installed by itself. After doing this, it worked fine for a day, bu

:)

 

Intel drivers causing windows to bsod

I was using ms autoruns to get rid of some useless startup programs, when i found a couple of startup programs from intel. why are these so important that they causes windows to bsod if i disable them, and do i really need them to start up with windows?

• Intel rapid storage enterprise driver.
• Intel rapid storage technology enterprise filter driver.
• Intel usb 3.0 host controller switch driver.

 

BSOD randomly browsing internet; ntoskrnl.exe


Hi Kaiketsu,

Please remove MSI software, some are known for causing BSOD's.

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.

The saved dump file is a 0x1A(MEMORY_MANAGEMENT) caused by a driver that tried to write data to the memory.
Code:

Code:

IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffd001b1ebf858, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield :     bit 0 : value 0 = read operation, 1 = write operation     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff802d7cb7320, address which referenced memory

Following is a list of outdated drivers, for about 50% of the drivers I have no update source.
Please check Realtek, Intel and Malwarebytes for updates, other drivers you need to search yourself.
Code:

Code:

WPRO_41_2001 WPRO_41_2001.sys Mon Nov 07 22:04:48 2011 (4EB847F0) //CACE Technologies WinPcap Packet Driver tap0901t tap0901t.sys Wed Sep 16 08:02:43 2009 (4AB07F83) // TAP-Win32 Adapter v9 (wifi) SC808HDV64 SC808HDV64.sys Tue Oct 08 11:33:45 2013 (5253D179) // HD Audio PCI-e Audio device MBfilt64 MBfilt64.sys Fri Jul 31 05:40:32 2009 (4A7267B0) // Realtek HD Audio driver mbam     mbam.sys     Wed Sep 03 19:50:25 2014 (540754E1) // Malwarebytes driver ISCTD64  ISCTD64.sys  Tue Nov 27 20:52:34 2012 (50B51A02) // Intel driver ISCTD64  ISCTD64.sys  Tue Nov 27 20:52:34 2012 (50B51A02) // Intel driver ikbevent ikbevent.sys Tue Jan 08 20:34:06 2013 (50EC74AE) // Intel driver HECIx64  HECIx64.sys  Mon Dec 17 20:32:21 2012 (50CF7345) // Intel driver ew_jubusenum ew_jubusenum.sys Thu Nov 24 12:30:19 2011 (4ECE2ACB) // Huawei mobile driver csravrcp csravrcp.sys Thu Dec 22 17:56:03 2011 (4EF36123) // Bluetooth csrbthav csrbthav.sys Thu Feb 23 08:05:58 2012 (4F45E556) // Bluetooth CsrBtPort CsrBtPort.sys Mon Feb 27 11:27:30 2012 (4F4B5A92) // Bluetooth csrpan   csrpan.sys   Thu Dec 22 17:56:22 2011 (4EF36136) // Bluetooth csrserial csrserial.sys Thu Dec 22 17:56:09 2011 (4EF36129) // SPP device? csrusb   csrusb.sys   Thu Feb 23 08:05:42 2012 (4F45E546) // USB driver for bluetooth csrusbfilter csrusbfilter.sys Thu Feb 23 08:05:43 2012 (4F45E547) // USB filter driver

 

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