New
#1
BSOD IRQL_NOT_LESS_OR_EQUAL Storport.sys
I put together a brand new build and am struggling with reoccurring BSODs.
BSOD #1:
Stop 0xOOOOOO1E
BSOD #2:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Storport.sys
Specs:
Windows 7 Ultimate x64
Intel 3930k
Asus P9x79 Pro
EVGA 680 FTW+
GSKILL Ripjaws 32gb RAM
Corsair H80i CPU Cooler
2 x Samsung 840 Pros 256gb
Sound Blaster Z
Corsair HX750 PSU
Lite-On DVD-ROM ODD IDE (using IDE to Sata adaptor)
WhoCrashed report:
Any help is much appreciated!Code:On Tue 1/29/2013 3:40:31 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: iastora.sys (iaStorA+0x63AA8) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800169A0D2) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\iastora.sys product: Intel Rapid Storage Technology Enterprise driver company: Intel Corporation description: Intel Rapid Storage Technology Enterprise driver - x64 Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastora.sys (Intel Rapid Storage Technology Enterprise driver - x64, Intel Corporation). Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL On Tue 1/29/2013 3:40:31 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\012813-17534-01.dmp This was probably caused by the following module: storport.sys (0xFFFFF8800169A0D2) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800169A0D2) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\storport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Storage Port Driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.