Frequent and Random BSOD on Windows 11

[KappaDev]

Hey all,

Upgraded to Windows 11 not too far back. I've been getting random blue screens, the kind without an obvious pointer to a specific driver.
System details:

CPU: Intel Core i9 9900K @ 3.60GHz
RAM: 32.0GB Dual-Channel DDR4 @ 1071MHz (15-15-15-36)
Motherboard: ASUS ROG MAXIMUS XI HERO (WI-FI)
Graphics: NVIDIA GeForce RTX 2060 (EVGA)
Operating System: Windows 11 Pro 64-bit
Computer type: Desktop

Speccy: http://speccy.piriform.com/results/hvvXO5dXMdhTio4TxjK4JU8

I've attached my generated file connection below. Note the most recent blue screens have been happening quite frequently, up to 3-4 times per day.
Any help is much appreciated,

Thanks!!!

 

[ubuysa]

My first question would be "how did you upgrade to Windows 11?"

Did you clean install Windows 11 from bootable media?

Did you simply upgrade an existing Windows 10 system? And if so, was the Windows 10 system fully stable? Were there any issues upgrading (were any apps/devices/drivers not compatible with Windows 11 for example)?

Upgrading any Windows version in-place is supposed to work, and it does - provided the existing Windows system contains nothing out of the ordinary - like old software installed in compatibility mode, or old devices using a driver that wasn't designed for Windows 10.

That said there is a common thread running through your dumps, well two common threads really...

• One common thread is memory (RAM); three dumps fail because of an attempt to access an invalid address, and it's the same invalid address in each dump. The other two dumps fail with 0xC0000005 exception codes, this is also due to an invalid memory reference. Most probably this is due to a flaky driver fouling up and then exiting, but we don't discover the failure until some time later when we get the BSOD and dump. There is a tool we can use to find this flaky driver, but I'll park that for now. I don't see any other evidence that suggests this a a faulty RAM problem, so we'll discount that for now.
  
  
• The other common thread is your NVMe system drive. Four of the dumps reference the Windows driver stornvme.sys in the lead-up to the BSOD. This is the high-level Windows driver that manages I/O to NVMe drives.
  
  I have seen M.2 drives cause niggly issues in the recent past because they weren't fully seated, so in the first instance I'd suggest to remove and fully re-seat that NVMe drive.
  
  If that doesn't help then download the Western Digital Dashboard and use that tool to look for a firmware update for the drive. I don't know whether that tool contains any drive diagnostics, but if it does run the maximal diagnostic you can.

Let us know how things are after you've done all that. If it's still BSODing then we'll move on to looking for a flaky driver.

BTW. If it does BSOD again please run the SysnativeBSODCollectionApp and upload the new zip file.

 

[Sefa K]

For example, when there are calls like disk!DiskDeviceControl+0x1ff call, it shows as disk error. Are you sure there were no problems before Windows 11? If there were no problems before the upgrade, you can do a clean windows installation.

3: kd> k
 # Child-SP          RetAddr               Call Site
00 fffff589`6e525408 fffff803`75a2cce9     nt!KeBugCheckEx
01 fffff589`6e525410 fffff803`75a28234     nt!KiBugCheckDispatch+0x69
02 fffff589`6e525550 fffff803`75c06757     nt!KiPageFault+0x474
03 fffff589`6e5256e0 fffff803`75a52113     nt!ExpTrackTableGetMoreLimit+0x17
04 fffff589`6e525710 fffff803`7585b6b2     nt!ExpPoolTrackerChargeEntry+0x9a847
05 fffff589`6e525760 fffff803`7585afdf     nt!ExAllocateHeapPool+0x6a2
06 fffff589`6e525880 fffff803`760ab68d     nt!ExpAllocatePoolWithTagFromNode+0x5f
07 fffff589`6e5258d0 fffff803`78776bc5     nt!ExAllocatePool2+0xdd
08 fffff589`6e525980 fffff803`7878f274     storport!RaidAllocatePool+0x31
09 fffff589`6e5259b0 fffff803`7877bb51     storport!StorpAllocateContiguousMemorySpecifyCacheNodeEx+0xf0
0a fffff589`6e525a10 fffff803`7889b5b8     storport!StorPortExtendedFunction+0x1ab1
0b fffff589`6e525b00 fffff803`788a9511     stornvme!NVMeAllocateDmaBuffer+0x7c
0c fffff589`6e525b70 fffff803`78893fa2     stornvme!ScsiModeSenseRequest+0xcd
0d fffff589`6e525bd0 fffff803`78891093     stornvme!ScsiToNVMe+0x2ee2
0e fffff589`6e525c90 fffff803`78779071     stornvme!NVMeHwBuildIo+0x83
0f fffff589`6e525ce0 fffff803`787782a0     storport!RaidAdapterPostScatterGatherExecute+0x151
10 fffff589`6e525d70 fffff803`78774bdf     storport!RaUnitStartIo+0x310
11 fffff589`6e525e70 fffff803`7877444e     storport!RaidStartIoPacket+0x50f
12 fffff589`6e525fb0 fffff803`787741d8     storport!RaUnitScsiIrp+0x23e
13 fffff589`6e526050 fffff803`75813c05     storport!RaDriverScsiIrp+0x58
14 fffff589`6e526090 fffff803`788d183c     nt!IofCallDriver+0x55
15 fffff589`6e5260d0 fffff803`77f7e7b8     EhStorClass!FilterDeviceEvtWdmIoctlIrpPreprocess+0x82c
16 fffff589`6e526180 fffff803`77f4b964     Wdf01000!PreprocessIrp+0x58
17 (Inline Function) --------`--------     Wdf01000!DispatchWorker+0x3e51
18 (Inline Function) --------`--------     Wdf01000!FxDevice::Dispatch+0x3e60
19 fffff589`6e5261b0 fffff803`75813c05     Wdf01000!FxDevice::DispatchWithLock+0x3ea4
1a fffff589`6e526200 fffff803`797c62e8     nt!IofCallDriver+0x55
1b fffff589`6e526240 fffff803`79813414     CLASSPNP!SubmitTransferPacket+0x2d8
1c fffff589`6e526290 fffff803`79813323     CLASSPNP!ClasspModeSense+0xe4
1d fffff589`6e5263f0 fffff803`7979d20c     CLASSPNP!ClassModeSense+0x13
1e fffff589`6e526430 fffff803`797912bf     disk!DiskIoctlIsWritable+0x88
1f fffff589`6e526470 fffff803`797c1092     disk!DiskDeviceControl+0x1ff
20 fffff589`6e526500 fffff803`797c89a4     CLASSPNP!ClassDeviceControlDispatch+0x82
21 fffff589`6e5265a0 fffff803`75813c05     CLASSPNP!ClassGlobalDispatch+0x24
22 fffff589`6e5265d0 fffff803`759556ae     nt!IofCallDriver+0x55
23 fffff589`6e526610 fffff803`75dcbb11     nt!IoSynchronousCallDriver+0x4e
24 fffff589`6e526670 fffff803`7855d4d7     nt!IoForwardIrpSynchronously+0x41
25 fffff589`6e5266a0 fffff803`78543b06     partmgr!PmIoctlIsWritable+0x77
26 fffff589`6e5266e0 fffff803`78541f20     partmgr!PmFilterDeviceControl+0x236
27 fffff589`6e526730 fffff803`75813c05     partmgr!PmGlobalDispatch+0x20
28 fffff589`6e526760 fffff803`78542afc     nt!IofCallDriver+0x55
29 fffff589`6e5267a0 fffff803`785428c5     partmgr!PartitionSendRequest+0x6c
2a fffff589`6e5267d0 fffff803`78541f20     partmgr!PartitionDeviceControl+0xe5
2b fffff589`6e526800 fffff803`75813c05     partmgr!PmGlobalDispatch+0x20
2c fffff589`6e526830 fffff803`7867d876     nt!IofCallDriver+0x55
2d fffff589`6e526870 fffff803`7867190e     volmgr!VmpDiskIsWritable+0x72
2e fffff589`6e5268b0 fffff803`75813c05     volmgr!VmDeviceControl+0x40e
2f fffff589`6e526920 fffff803`794661ca     nt!IofCallDriver+0x55
30 fffff589`6e526960 fffff803`75813c05     fvevol!FveFilterDeviceControl+0x1ba
31 fffff589`6e526a60 fffff803`79752633     nt!IofCallDriver+0x55
32 fffff589`6e526aa0 fffff803`75813c05     iorate!IoRateDispatchPassthrough+0x23
33 fffff589`6e526ad0 fffff803`79531033     nt!IofCallDriver+0x55
34 fffff589`6e526b10 fffff803`75813c05     volume!VolumePassThrough+0x23
35 fffff589`6e526b40 fffff803`7955c463     nt!IofCallDriver+0x55
36 fffff589`6e526b80 fffff803`75813c05     volsnap!VolSnapDeviceControl+0x173
37 fffff589`6e526c40 fffff803`78a1ad9d     nt!IofCallDriver+0x55
38 fffff589`6e526c80 fffff803`78aea8a9     Ntfs!NtfsCallStorageDriver+0xc5
39 fffff589`6e526d00 fffff803`78ae6ae1     Ntfs!NtfsDeviceIoControl+0xd1
3a fffff589`6e526da0 fffff803`78b7a10d     Ntfs!NtfsGetDiskGeometry+0x4d
3b fffff589`6e526e10 fffff803`78b7a922     Ntfs!NtfsInitializeDevice+0xf1
3c fffff589`6e526ef0 fffff803`78aecd9b     Ntfs!NtfsMountVolume+0x2f6
3d fffff589`6e5276d0 fffff803`78a26492     Ntfs!NtfsCommonFileSystemControl+0xd7
3e fffff589`6e5277b0 fffff803`758d6b35     Ntfs!NtfsFspDispatch+0x3d2
3f fffff589`6e527900 fffff803`758fd577     nt!ExpWorkerThread+0x155
40 fffff589`6e527af0 fffff803`75a1c414     nt!PspSystemThreadStartup+0x57
41 fffff589`6e527b40 00000000`00000000     nt!KiStartSystemThread+0x34

3: kd> !devobj ffffd888`45eed030
Device object (ffffd88845eed030) is for:
 InfoMask field not found for _OBJECT_HEADER at ffffd88845eed000
 \Driver\volsnap DriverObject ffffd888363c9da0
Current Irp 00000000 RefCount 0 Type 00000007 Flags 00000010
SecurityDescriptor ffff91085ebcd3e0 DevExt ffffd88845eed180 DevObjExt ffffd88845eee230
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) ffffd888367cdcd0 Name paged out
Device queue is not busy.

 

[Sefa K]

3: kd> !irp ffff938b`80283a40
Irp is active with 7 stacks 4 is current (= 0xffff938b80283be8)
 No Mdl: System buffer=ffff938b878d7000: Thread ffff938b740f2080:  Irp stack trace. 
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000   


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000   


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000   


            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            7 e0 ffff938b5b7e9050 ffff938b7b926720 00000000-00000000   
           \Driver\stornvme
            Args: 00001030 00001030 0x2d1400 00000000
 [IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            7  1 ffff938b601cdde0 ffff938b7b926720 00000000-00000000    pending
           \Driver\EhStorClass
            Args: 00001030 00001030 0x2d1400 00000000
 [IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            7 e0 ffff938b603350a0 ffff938b7b926720 fffff80219402730-ffff938b743df890 Success Error Cancel
           \Driver\disk    nt!RawCompletionRoutine
            Args: 00001030 00001030 0x2d1400 00000000
 [IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            5  0 ffff938b743df740 ffff938b7b926720 00000000-00000000   
           Name paged out
            Args: 00001030 00001030 0x2d1400 00000000

 

[ubuysa]

@Sefa K, interesting details, but the device object and the irp are from two different (but similar) dumps I think?