Unexpected reboot due to unhandled exception in iaStorAC.sys

TedLyngmo · ‎07-29-2024

Since about 3 weeks, my Windows 11 machine reboots if I leave it alone for some time (10-15 minutes seems to be enough). If I keep active, everything seems to be working fine and I can work for hours and hours.

I've tried to disable putting the monitor to sleep and it's set to _never_ put the system to sleep. My WinDbg interpretation of the minidump is below. Note that it mentions Windows 10 a lot, but that's probably because this is a W10 system that's been upgraded to W11. I'm afraid it could be a sign of a failing SSD or something else so I'd like to find the root cause but I don't know where to look.

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

   EnableRedirectToV8JsProvider : 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.203 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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


Loading Dump File [C:\Users\Ted\Documents\072924-11078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`70c00000 PsLoadedModuleList = 0xfffff807`71813510
Debug session time: Mon Jul 29 18:11:04.962 2024 (UTC + 2:00)
System Uptime: 0 days 0:39:28.668
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols

Loading unloaded module list
..................
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify timestamp for iaStorAC.sys
iaStorAC+0x819cc:
fffff807`75d919cc 488b5068        mov     rdx,qword ptr [rax+68h] ds:002b:0000270f`00000068=????????????????
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80775d919cc, The address that the exception occurred at
Arg3: fffffe05a200f148, Exception Record Address
Arg4: fffffe05a200e960, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 6015

    Key  : Analysis.Elapsed.mSec
    Value: 20847

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000007e

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_iaStorAC!unknown_function

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

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80775d919cc

BUGCHECK_P3: fffffe05a200f148

BUGCHECK_P4: fffffe05a200e960

FILE_IN_CAB:  072924-11078-01.dmp

DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

EXCEPTION_RECORD:  fffffe05a200f148 -- (.exr 0xfffffe05a200f148)
ExceptionAddress: fffff80775d919cc (iaStorAC+0x00000000000819cc)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000270f00000068
Attempt to read from address 0000270f00000068

CONTEXT:  fffffe05a200e960 -- (.cxr 0xfffffe05a200e960)
rax=0000270f00000000 rbx=ffffa888e092ec30 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffa888dfd00fe8 rdi=0000000000000000
rip=fffff80775d919cc rsp=fffffe05a200f380 rbp=0000000000000000
 r8=ffffa888dfc939b0  r9=ffffa888dfd00fe8 r10=ffffa888d51fc420
r11=0000000000000001 r12=0000000000000006 r13=0000000000000000
r14=000000000000ea60 r15=000000000000001e
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
iaStorAC+0x819cc:
fffff807`75d919cc 488b5068        mov     rdx,qword ptr [rax+68h] ds:002b:0000270f`00000068=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8077191c4a8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000270f00000068 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000270f00000068

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
fffffe05`a200f380 fffff807`75def760     : ffffa888`dfc92fb8 fffff807`75de57f0 ffffa888`e15785a0 ffffa888`e092edf0 : iaStorAC+0x819cc
fffffe05`a200f388 ffffa888`dfc92fb8     : fffff807`75de57f0 ffffa888`e15785a0 ffffa888`e092edf0 fffff807`75d524f6 : iaStorAC+0xdf760
fffffe05`a200f390 fffff807`75de57f0     : ffffa888`e15785a0 ffffa888`e092edf0 fffff807`75d524f6 ffffa888`e00dfd10 : 0xffffa888`dfc92fb8
fffffe05`a200f398 ffffa888`e15785a0     : ffffa888`e092edf0 fffff807`75d524f6 ffffa888`e00dfd10 00000000`00000000 : iaStorAC+0xd57f0
fffffe05`a200f3a0 ffffa888`e092edf0     : fffff807`75d524f6 ffffa888`e00dfd10 00000000`00000000 ffffa888`dfd00fe8 : 0xffffa888`e15785a0
fffffe05`a200f3a8 fffff807`75d524f6     : ffffa888`e00dfd10 00000000`00000000 ffffa888`dfd00fe8 00000000`00000000 : 0xffffa888`e092edf0
fffffe05`a200f3b0 ffffa888`e00dfd10     : 00000000`00000000 ffffa888`dfd00fe8 00000000`00000000 00000000`00000001 : iaStorAC+0x424f6
fffffe05`a200f3b8 00000000`00000000     : ffffa888`dfd00fe8 00000000`00000000 00000000`00000001 00000000`00002000 : 0xffffa888`e00dfd10


SYMBOL_NAME:  iaStorAC+819cc

MODULE_NAME: iaStorAC

IMAGE_NAME:  iaStorAC.sys

STACK_COMMAND:  .cxr 0xfffffe05a200e960 ; kb

BUCKET_ID_FUNC_OFFSET:  819cc

FAILURE_BUCKET_ID:  AV_iaStorAC!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

JedG_Intel · ‎08-21-2024

Hello TedLyngmo,

Thank you for posting at Intel Community Forum

For me to properly address this concern, please share the following details:

1. Are you using a RAID? If yes, please specify

2. What is the version of RST?

3. What kinds of systems are impacted?

Additionally, to have a better understanding of your system components please generate System Support Utility (SSU) report. Please follow instructions here and send the report - How to get the Intel® System Support Utility Logs on Windows*

I hope to hear from you soon.

Best regards,

Jed G.

Intel Customer Support Technician

TedLyngmo · ‎08-25-2024

Hi Jed!

No RAID.

I used the RST version that came with the system and I don't think it's getting automatically updated via Windows Update for some reason. A few days after I wrote this report, I found that there was a newer version so I manually upgraded to use that instead - and suddenly the problem was gone.

I have no idea _why_ the problem with your iaStorAC

(
ExceptionAddress: fffff80775d919cc (iaStorAC+0x00000000000819cc)

ExceptionCode: c0000005 (Access violation)

FAILURE_BUCKET_ID: AV_iaStorAC!unknown_function

)
started appearing since it's been working like a charm for so many years though.

Br,

Ted

JedG_Intel · ‎08-28-2024

Hello TedLyngmo,

Thank you for responding.

We appreciate your effort in keeping us posted and I am glad to hear that updating the RST version fixed the issue.

Since the issue is now resolved, we will proceed with closing the case. If you need further assistance, please submit a new question, as this thread will no longer be monitored.

Thank you for choosing Intel and stay safe.

Best regards,

Jed G.

Intel Customer Support Technician