[Brennan C.]

Hello,

I decided to create a new thread for this topic as the old one is pretty old and a lot has changed since then; I figured I would link to it here, though, just in case there's useful information. My wife's laptop woke from sleep this morning briefly and then gave an IRQL_NOT_LESS_OR_EQUAL BSoD. For about an hour, the computer wouldn't start; it just showed a Lenovo splash screen, and Windows wouldn't boot. After powering off and on multiple times (which is the only thing that got the system going, previously) it eventually started. 

 

The difference between the old thread and this one is that since the old one we eventually just buckled down and factory-reset the thing. And since then, it's worked great! This is the first time we've had this issue since the reset. It could just be a one-off, but who knows with this machine, anymore. 

 

Here are the laptop's specs from Speccy. 

 

Here's the dump from the BSoD:

 

 

Microsoft ® Windows Debugger Version 6.3.9600.17298 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Only kernel address space is available

 

 

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols

Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols

Executable search path is: 

Windows 8 Kernel Version 9600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 9600.17476.amd64fre.winblue_r5.141029-1500

Machine Name:

Kernel base = 0xfffff800`8e019000 PsLoadedModuleList = 0xfffff800`8e2f2250

Debug session time: Mon Feb  9 09:58:17.443 2015 (UTC - 8:00)

System Uptime: 2 days 15:36:27.277

Loading Kernel Symbols

...............................................................

................................................................

.............................

Loading User Symbols

PEB is paged out (Peb.Ldr = 00000000`ff6d5018).  Type ".hh dbgerr001" for details

Loading unloaded module list

....................................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck A, {0, 2, 1, fffff8008e05675f}

 

*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

Probably caused by : iaStorA.sys ( iaStorA+6710a )

 

Followup: MachineOwner

---------

 

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

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: 0000000000000000, 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: fffff8008e05675f, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS: unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

 0000000000000000 

 

CURRENT_IRQL:  2

 

FAULTING_IP: 

nt!KeAcquireInStackQueuedSpinLock+2f

fffff800`8e05675f 488711          xchg    rdx,qword ptr [rcx]

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

BUGCHECK_STR:  AV

 

PROCESS_NAME:  chrome.exe

 

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

 

DPC_STACK_BASE:  FFFFF8008FDD4FB0

 

TRAP_FRAME:  fffff8008fdd4960 -- (.trap 0xfffff8008fdd4960)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000

rdx=fffff8008fdd4b60 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8008e05675f rsp=fffff8008fdd4af8 rbp=fffff8008fdd4ce0

 r8=fffff8008fdd4b60  r9=fffff8008fdd4aa0 r10=fffff8008e7b3501

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!KeAcquireInStackQueuedSpinLock+0x2f:

fffff800`8e05675f 488711          xchg    rdx,qword ptr [rcx] ds:00000000`00000000=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff8008e1755e9 to fffff8008e169aa0

 

STACK_TEXT:  

fffff800`8fdd4818 fffff800`8e1755e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff800`8fdd4820 fffff800`8e173e3a : 00000000`00000001 fffff800`8fdd4b60 ffffe000`178fd000 fffff801`db39a69c : nt!KiBugCheckDispatch+0x69

fffff800`8fdd4960 fffff800`8e05675f : fffff801`db14610a 00000000`00000000 ffffe000`167ad798 ffffe000`17832f02 : nt!KiPageFault+0x23a

fffff800`8fdd4af8 fffff801`db14610a : 00000000`00000000 ffffe000`167ad798 ffffe000`17832f02 ffffe000`167ad618 : nt!KeAcquireInStackQueuedSpinLock+0x2f

fffff800`8fdd4b00 fffff801`db0e545e : ffffe000`178fd0a8 ffffe000`167ad010 ffffe000`1780d008 fffff800`8fdd4e30 : iaStorA+0x6710a

fffff800`8fdd4b30 fffff801`db0e9d81 : ffffe000`167ad010 ffffe000`16397180 00000000`00000004 fffff801`db16f000 : iaStorA+0x645e

fffff800`8fdd4b90 fffff800`8e0c6580 : fffff800`8e31ef00 fffff800`8fdd4e80 ffffe000`17832fa8 fffff801`db150e05 : iaStorA+0xad81

fffff800`8fdd4be0 fffff800`8e0c5837 : 00000000`00000001 fffff800`8fdd4e70 fffff800`8e31c180 00000000`00000001 : nt!KiExecuteAllDpcs+0x1b0

fffff800`8fdd4d30 fffff800`8e16cbd5 : 00000000`00000000 fffff800`8e31c180 fffff800`8e801900 00000000`01eb9150 : nt!KiRetireDpcList+0xd7

fffff800`8fdd4fb0 fffff800`8e16c9d9 : 00000000`00000000 fffff800`00000000 ffffd000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5

ffffd000`2826aac0 fffff800`8e16ec45 : 00000000`00000000 fffff800`8e16b387 ffffe000`1dc66080 00000000`00000000 : nt!KiDispatchInterruptContinue

ffffd000`2826aaf0 fffff800`8e16b387 : ffffe000`1dc66080 00000000`00000000 00000000`00000000 ffffe000`170354c0 : nt!KiDpcInterruptBypass+0x25

ffffd000`2826ab00 00000000`77931506 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x197

00000000`047cf8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77931506

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP: 

iaStorA+6710a

fffff801`db14610a 488b5c2430      mov     rbx,qword ptr [rsp+30h]

 

SYMBOL_STACK_INDEX:  4

 

SYMBOL_NAME:  iaStorA+6710a

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: iaStorA

 

IMAGE_NAME:  iaStorA.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb0de8

 

FAILURE_BUCKET_ID:  AV_iaStorA+6710a

 

BUCKET_ID:  AV_iaStorA+6710a

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:av_iastora+6710a

 

FAILURE_ID_HASH:  {f733faf2-d2a8-1b11-9fa3-afbe5930de67}

 

Followup: MachineOwner

---------

 

Any help would be appreciated; is there something in there that we can nip in the bud right away? 

 

Please and thank you! :-)

[Advertisements]

Hi Brennan

It looks like the BSOD was caused by the iaStorA.sys driver, which is the Intel Rapid Storage Controller Technology. What is your computer/laptop brand and model, and exact version of Windows?

[Aura]

Hi Brennan

It looks like the BSOD was caused by the iaStorA.sys driver, which is the Intel Rapid Storage Controller Technology. What is your computer/laptop brand and model, and exact version of Windows?

[Brennan C.]

Hi there! :-D

 

Laptop is Lenovo G500 running Windows 8.1. Let me know if you need any more information. 

[Aura]

Here, download and install these drivers:

http://support.lenov...nloads/DS037893

Once done, restart your laptop and let me know if you get any more BSODs after that

[Brennan C.]

Hello, 

Because the machine already has the software installed, the installer gave me the options to remove or repair. I chose repair. Will come back here if the issue continues. Thank you! :-)

[Aura]

Alright that's good, thank you for keeping me updated

[Brennan C.]

Hey, there; more IRQL blah blah blah. Here's the crash dump. Thanks for the help. :-)

 

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

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: 0000000000000000, 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: fffff803526bd75f, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS: unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

 0000000000000000 

 

CURRENT_IRQL:  2

 

FAULTING_IP: 

nt!KeAcquireInStackQueuedSpinLock+2f

fffff803`526bd75f 488711          xchg    rdx,qword ptr [rcx]

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

BUGCHECK_STR:  AV

 

PROCESS_NAME:  System

 

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

 

DPC_STACK_BASE:  FFFFF803543D4FB0

 

TRAP_FRAME:  fffff803543cd4f0 -- (.trap 0xfffff803543cd4f0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000

rdx=fffff803543cd6e0 rsi=0000000000000000 rdi=0000000000000000

rip=fffff803526bd75f rsp=fffff803543cd688 rbp=fffff803543cd990

 r8=fffff803543cd6e0  r9=0000000000000000 r10=0000000000000001

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!KeAcquireInStackQueuedSpinLock+0x2f:

fffff803`526bd75f 488711          xchg    rdx,qword ptr [rcx] ds:00000000`00000000=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff803527dc5e9 to fffff803527d0aa0

 

STACK_TEXT:  

fffff803`543cd3a8 fffff803`527dc5e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff803`543cd3b0 fffff803`527dae3a : 00000000`00000001 fffff803`543cd6e0 00000000`00000000 fffff803`5261669a : nt!KiBugCheckDispatch+0x69

fffff803`543cd4f0 fffff803`526bd75f : fffff801`db88a10a 00000000`00000001 ffffe001`1a2bc002 fffff803`543cd902 : nt!KiPageFault+0x23a

fffff803`543cd688 fffff801`db88a10a : 00000000`00000001 ffffe001`1a2bc002 fffff803`543cd902 ffffffff`fffe7960 : nt!KeAcquireInStackQueuedSpinLock+0x2f

fffff803`543cd690 fffff801`db82950e : ffffe001`18da4180 fffff803`543cd990 ffffe001`1a2bc002 ffffe001`1a2bf000 : iaStorA+0x6710a

fffff803`543cd6c0 fffff801`db82a77a : ffffe001`18da4180 ffffe001`1a2bc000 ffffe001`1a2bc000 ffffe001`1a2bc001 : iaStorA+0x650e

fffff803`543cd710 fffff801`db82cf23 : ffffe001`1a2bc000 ffffe001`198f5618 fffff803`543cd880 fffff801`db82e61b : iaStorA+0x777a

fffff803`543cd760 fffff801`db829343 : ffffe001`19987390 fffff801`00000000 fffff803`543cd810 fffff801`db88a134 : iaStorA+0x9f23

fffff803`543cd790 fffff801`db82944d : ffffe001`1a2bc0a8 fffff801`db88a134 ffffe001`1a2bc000 ffffe001`198f5770 : iaStorA+0x6343

fffff803`543cd7e0 fffff801`db82dd81 : ffffe001`198f5010 ffffe001`19987390 0000007f`ffffffff 7fffffff`fffffffc : iaStorA+0x644d

fffff803`543cd840 fffff803`5272d580 : fffff803`52985f00 fffff803`543cdb60 fffff803`5293a520 fffff803`52980f44 : iaStorA+0xad81

fffff803`543cd890 fffff803`5272c837 : ffffe001`1f77b080 fffff803`543cdae0 fffff803`52983180 fffff803`52983180 : nt!KiExecuteAllDpcs+0x1b0

fffff803`543cd9e0 fffff803`527d45ea : fffff803`52983180 fffff803`52983180 fffff803`529dca00 ffffe001`1e683080 : nt!KiRetireDpcList+0xd7

fffff803`543cdc60 00000000`00000000 : fffff803`543ce000 fffff803`543c8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP: 

iaStorA+6710a

fffff801`db88a10a 488b5c2430      mov     rbx,qword ptr [rsp+30h]

 

SYMBOL_STACK_INDEX:  4

 

SYMBOL_NAME:  iaStorA+6710a

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: iaStorA

 

IMAGE_NAME:  iaStorA.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb0de8

 

FAILURE_BUCKET_ID:  AV_iaStorA+6710a

 

BUCKET_ID:  AV_iaStorA+6710a

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:av_iastora+6710a

 

FAILURE_ID_HASH:  {f733faf2-d2a8-1b11-9fa3-afbe5930de67}

 

Followup: MachineOwner

---------

[Aura]

Is that the first BSOD you have since February 10th?

[Brennan C.]

Is that the first BSOD you have since February 10th?

 

No, it's not. Just haven't had the chance to post. 

[Brennan C.]

Use intel driver update utility to update Intel Rapid Storage Technology driver. If updating the Intel Rapid Storage Technology driver wont stop BSOD then uninstall it to replace it with standard Microsoft SATA AHCI Controller driver.

 

"Intel® Driver Update Utility"

https://downloadcenter.intel.com/

 

"Uninstalling the Intel® Rapid Storage Technology driver"

http://answers.micro...50-89843c9d9b22

 

Attempted to update using Intel Driver Update Utility: No drivers found. Moved on to next step.

 

Uninstalled Intel Rapid Storage Technology driver: Opened link and followed directions to uninstall the driver. First set of directions (uninstalling and restarting) resulted in a BSoD loop. Reverted using System Restore, attempted second set of instructions (manually select Standard SATA AHCI Controller). Was able to successfully complete those instructions. Upon installation of DriverView, there were none of the listed Intel drivers; per the instructions, I was then complete. Will update if future IRQL BSoDs occur.