Driver irql not less or equal iastorAC. Sys failed

theoneabhi0307 · ‎09-14-2024

My laptop was crashed several times actually from last 4 months I tried windbg it seems caused by iastorAC. Sys I will be thankful if anyone help me I'm providing following screen shot of mini dump

Again one thing from last 4 month I was trying to fix this problem in storage cntroller like if I change intel RST to sata it shows iastorAVC. Sys BSOD and when I restore to RST it shows iastorAC. Sys please look into it Thanks
Note it's happening after I replace my hdd to ssd in my old laptop

Mini dump file

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`18000000 PsLoadedModuleList = 0xfffff807`18c2a820
Debug session time: Fri Sep 13 20:29:32.469 2024 (UTC + 5:30)
System Uptime: 0 days 0:06:09.222
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols

Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`183fe350 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff807`1c8152c0=000000000000000a
0: kd>
0: kd> analize -v
Couldn't resolve error at 'nalize -v'
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8071ab2f8de, address which referenced memory

Debugging Details:
------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6514

Key : Analysis.Elapsed.mSec
Value: 6586

Key : Analysis.IO.Other.Mb
Value: 5

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 6

Key : Analysis.Init.CPU.mSec
Value: 2156

Key : Analysis.Init.Elapsed.mSec
Value: 98202

Key : Analysis.Memory.CommitPeak.Mb
Value: 95

Key : Bugcheck.Code.KiBugCheckData
Value: 0xd1

Key : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key : Bugcheck.Code.TargetModel
Value: 0xd1

Key : Failure.Bucket
Value: AV_iaStorAC!unknown_function

Key : Failure.Hash
Value: {2c48c538-0bdc-1937-76bb-851b68345fca}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 131072

Key : Hypervisor.Flags.ValueHex
Value: 20000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: d1

BUGCHECK_P1: c8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8071ab2f8de

FILE_IN_CAB: MEMORY.DMP

FAULTING_THREAD: fffff80718d27a00

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
00000000000000c8

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: fffff8071c815400 -- (.trap 0xfffff8071c815400)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffff9e8fcd313c28
rdx=ffff9e8fcd313d70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8071ab2f8de rsp=fffff8071c815590 rbp=ffff9e8fcd313c28
r8=ffff9e8fcd314518 r9=0000000000000000 r10=ffff9e8fcd313d70
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
iaStorAC+0xbf8de:
fffff807`1ab2f8de 4883bfc800000000 cmp qword ptr [rdi+0C8h],0 ds:00000000`000000c8=????????????????
Resetting default scope

STACK_TEXT:
fffff807`1c8152b8 fffff807`18412ba9 : 00000000`0000000a 00000000`000000c8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff807`1c8152c0 fffff807`1840e578 : fffff807`18cf3d50 fffff807`182eb5bf 000000c9`c5677590 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff807`1c815400 fffff807`1ab2f8de : fffff807`1ab54658 00000000`00000000 ffff9e8f`cc210000 ffff9e8f`cb3a5168 : nt!KiPageFault+0x478
fffff807`1c815590 fffff807`1ab316be : ffff9e8f`cd313d70 fffff807`1ab54600 ffffd800`80786d00 ffff9e8f`cd315200 : iaStorAC+0xbf8de
fffff807`1c8155d0 fffff807`1ab23340 : ffff9e8f`cd314518 00000000`00000000 fffff807`1ab54600 00000000`0007cb00 : iaStorAC+0xc16be
fffff807`1c815620 fffff807`1ab23252 : ffff9e8f`cd313c28 fffff807`1ab54600 fffff807`1c8156c8 00000000`00000004 : iaStorAC+0xb3340
fffff807`1c815670 fffff807`1ab26e8a : 00000000`00000001 00000000`00000001 00000000`00000000 ffff9e8f`00000001 : iaStorAC+0xb3252
fffff807`1c8156b0 fffff807`1821f4de : fffff807`13640240 fffff807`1c815860 fffff807`1c815a20 fffff807`1363d180 : iaStorAC+0xb6e8a
fffff807`1c815760 fffff807`1821e7c4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff807`1c8158d0 fffff807`18402e4e : 00000000`00000000 fffff807`1363d180 fffff807`18d27a00 ffff9e8f`ea6e9080 : nt!KiRetireDpcList+0x1f4
fffff807`1c815b60 00000000`00000000 : fffff807`1c816000 fffff807`1c80f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: iaStorAC+bf8de

MODULE_NAME: iaStorAC

IMAGE_NAME: iaStorAC.sys

STACK_COMMAND: .process /r /p 0xfffff80718d24a00; .thread 0xfffff80718d27a00 ; kb

BUCKET_ID_FUNC_OFFSET: bf8de

FAILURE_BUCKET_ID: AV_iaStorAC!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2c48c538-0bdc-1937-76bb-851b68345fca}

Followup: MachineOwner
---------

AlfredoS_Intel · ‎09-23-2024

Hi theoneabhi0307,

Thank you for posting in Intel Communities.

I appreciate the logs that you have shared. I need your cooperation to provide the following information, that we can use to provide you viable suggestions:

1. Does the crash happen on a specific application that you run, or is it random?

2. Do you have RAID set up on your drives?

3. Are you still able to boot up to Windows? If yes, it would really help us if we can get more information about your system. Please download and run our Intel® System Support Utility from this page, https://www.intel.com/content/www/us/en/download/18377/intel-system-support-utility-for-windows.html. To run it, please press "Scan". After the scan is finished, click next and there will be a save button, giving you an option to save the logs to a text file, please do so and attach the file on your reply. You can refer to How to get the Intel® System Support Utility Logs on Windows* https://www.intel.com/content/www/us/en/support/articles/000057926/memory-and-storage.html for instructions.

Looking forward to your response.

Best Regards,

Alfred S

Intel Customer Support Technician

theoneabhi0307 · ‎09-23-2024

Yes sir it crashes random after using few minutes

i dont understand about RAID i have intel rst in my laptop

here are few images of device manager and bios and also text of INTEL SYSTEM SUPPORT UTILITY named as ashish RST

THANKS KINDLY RESOLVE MY ISSUE SIR