Constant BSODs from envirtahci.sys aka the AHCI Virtual Storage Miniport Driver

Question

I keep getting SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and sometimes NO_MORE_IRP_STACK_LOCATIONS error every time I try to normally use my PC for anything now. This has been happening for 3 days now, and I have no idea why or how it happened. I have tried reinstalling my Nvidia drivers, and updating my AMD Chipset drivers (haven't clean installed the chipset drivers yet). I have a USB with Windows 10 installed on it ready since at this point I'm just gonna completely reinstall Windows 10 on my machine.

I have collected a couple of dump files, but the most recent ones are from 11/10/2021 at around 11:50pm -> https://drive.google.com/file/d/1tmIT2VtxjyIaa35T0iyMoQ--tRPCuQIw/view?usp=sharing

Answer 1

This time it showed that there was a problem with AMD's storage driver.

Now it is definitely the AMD software problem.

Answer 2

Wow, I literally just went to install DiskGenius, and when I went to go run the program, my PC blue screened AGAIN! I'm REALLY tempted to just clean install Windows 10 and start from scratch.

Dump file:

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

Loading Dump File [C:\Users\thesq\Desktop\BSOD_AfterDG.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`53a00000 PsLoadedModuleList = 0xfffff806`5462a2d0
Debug session time: Thu Nov 11 01:46:17.926 2021 (UTC - 5:00)
System Uptime: 0 days 1:02:14.592
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`53df72a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa304`b0604650=000000000000007e
4: 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: fffff80653c8f6e8, The address that the exception occurred at
Arg3: ffffa304b0605648, Exception Record Address
Arg4: ffffa304b0604e80, Context Record Address

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 4249

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5736

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  BSOD_AfterDG.DMP

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80653c8f6e8

BUGCHECK_P3: ffffa304b0605648

BUGCHECK_P4: ffffa304b0604e80

EXCEPTION_RECORD:  ffffa304b0605648 -- (.exr 0xffffa304b0605648)
ExceptionAddress: fffff80653c8f6e8 (nt!IofCallDriver+0x0000000000000048)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000e8
Attempt to read from address 00000000000000e8

CONTEXT:  ffffa304b0604e80 -- (.cxr 0xffffa304b0604e80)
rax=ffffaa0f5278f610 rbx=ffffaa0f50427580 rcx=0000000000000000
rdx=ffffaa0f5278f4b0 rsi=0000000000001000 rdi=ffffaa0f5278f4b0
rip=fffff80653c8f6e8 rsp=ffffa304b0605880 rbp=ffffaa0f4654e2c0
 r8=000000000000000f  r9=ffffaa0f52046050 r10=0000000000000000
r11=fffff780000003b0 r12=ffffaa0f504275c8 r13=0000000000000000
r14=ffffaa0f52046050 r15=ffffaa0f4654e2d2
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050287
nt!IofCallDriver+0x48:
fffff806`53c8f6e8 4a8b44c170      mov     rax,qword ptr [rcx+r8*8+70h] ds:002b:00000000`000000e8=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

READ_ADDRESS:  00000000000000e8 

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:  00000000000000e8

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
ffffa304`b0605880 fffff806`55b96d1c     : fffff806`55c3ac10 8a000004`00000000 00000000`00000000 ffff89d5`07a17700 : nt!IofCallDriver+0x48
ffffa304`b06058c0 fffff806`55b96f1b     : 00000000`00000000 00000000`00000000 ffffaa0f`42eea6c0 ffffaa0f`442101d4 : envirtahci+0x16d1c
ffffa304`b0605940 fffff806`55b9308f     : ffffaa0f`42eea0d0 ffffa304`b06059f8 ffffa304`b0605a10 00000000`00001000 : envirtahci+0x16f1b
ffffa304`b06059b0 fffff806`55b954e5     : 00000000`00000000 00000000`00000001 00000000`0000007d ffffaa0f`42ee70a8 : envirtahci+0x1308f
ffffa304`b0605a40 fffff806`55b919eb     : ffffaa0f`50426b00 ffffaa0f`442101d4 ffffaa0f`4ad2f080 ffffaa0f`42ef8190 : envirtahci+0x154e5
ffffa304`b0605a70 fffff806`55b9399b     : ffffaa0f`42ef8190 ffffaa0f`4ad2f080 ffffaa0f`50ee6700 ffff5431`eb945900 : envirtahci+0x119eb
ffffa304`b0605aa0 fffff806`53c74825     : 00000000`00000000 ffffaa0f`42ee25a0 ffffaa0f`42ecf060 fffff806`558e3f60 : envirtahci+0x1399b
ffffa304`b0605b00 fffff806`53cb8515     : ffffaa0f`50ee6640 ffffaa0f`50ee6640 fffff806`53c746f0 ffffaa0f`00000000 : nt!IopProcessWorkItem+0x135
ffffa304`b0605b70 fffff806`53d55855     : ffffaa0f`50ee6640 00000000`00000080 ffffaa0f`3f073040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffa304`b0605c10 fffff806`53dfe8f8     : ffffce80`9c300180 ffffaa0f`50ee6640 fffff806`53d55800 00000000`00000400 : nt!PspSystemThreadStartup+0x55
ffffa304`b0605c60 00000000`00000000     : ffffa304`b0606000 ffffa304`b0600000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  envirtahci+16d1c

MODULE_NAME: envirtahci

IMAGE_NAME:  envirtahci.sys

STACK_COMMAND:  .cxr 0xffffa304b0604e80 ; kb

BUCKET_ID_FUNC_OFFSET:  16d1c

FAILURE_BUCKET_ID:  AV_envirtahci!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d3183d6b-1db0-cb3d-1096-dc95872ddd66}

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

Answer 3

I use DiskGenius, which is a professional hard disk tool software.

Cleaning up the dust may not help much, but the AMD StoreMi you mentioned is probably the reason, because some of the components I saw in the dump file are from AMD.

Answer 4

Hello, I'm A&K. I'm glad to be able to help you.

Your dump file shows multiple hard disk-related errors.
This may be caused by damage to the hard disk. I suggest you use professional disk management software to perform a health check on the hard disk, or ask a maintenance person to check the hard disk.

What software would you recommend on using to check my hard disk?

Also, would cleaning out my PC (using conpressed air cans) help by any chance?

I also should add that my PC came installed with AMD StoreMi so my SSD and HDD are merged into a single Tier Drive or something.

Answer 5

Hello, I'm A&K. I'm glad to be able to help you.

Your dump file shows multiple hard disk-related errors.

This may be caused by damage to the hard disk. I suggest you use professional disk management software to perform a health check on the hard disk, or ask a maintenance person to check the hard disk.