[Win 11 x64] BSOD Crash 0x7f (8)

[tacokiller]

• A brief description of your problem (but you can also include the steps you tried)
  • I'm getting BSOD crashes on a brand-new PC build. All components are brand-new and have not migrated from a previous build.
  • I have updated BIOS and installed all the drivers after assembling the PC. Now I'm occasionally getting BSOD crash on system shutdown.
  • I couldn't get Sysnative app to work (antivirus disabled, app saved to Desktop as instructed) so I have manually copied minidump files. Hope this is enough.
• System Manufacturer?
  • Custom Built
• Laptop or Desktop?
  • Desktop
• OS
  • Windows 11 build 22631.3155
• x86 (32bit) or x64 (64bit)?
  • x64
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
  • Retail
• Age of system? (hardware)
  • Less than 3 months.
• Have you re-installed the OS?
  • No
• CPU
  • i5-12600k
• RAM (brand, EXACT model, what slots are you using?)
  • Kingston Fury DDR4-3600 32768MB PC4-28800 (KF436C18BBK2/32)
• Video Card
  • None
• Motherboard - (if NOT a laptop)
  • MSI PRO Z690-A WiFi
• Power Supply - brand & wattage (if laptop, skip this one)
  • Be Quite 1000w.
• Is driver verifier enabled or disabled?
  • Enabled
• What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
  • Windows Defender, BitDefender
• Are you using proxy, vpn, ipfilters or similar software?
  • VPN
• Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
  • No
• Are you currently under/overclocking? Are there overclocking software installed on your system?
  • No

Thanks for your help in advance!

 

[tacokiller]

Turns out Sysnative app was quarantined by Bitdefender. I was able to generate a report this time around.

 

[ubuysa]

Hello, and welcome to the forum!

The BSODs were all identical, they all happen because of a series of (apparently graphical) system calls that eventually exhausted the call stack memory allocation. I'm thinking these are graphics related system calls because there is a PDEV components referenced in these calls. A PDEV is a physical device structure used by the WIndows graphics device interface (GDI). These are the repeating (possibly recursive) calls that we see over and over again until the stack space is exhausted...

fffbe00`d155eaa0 fffff897`03b56e01     win32kbase!PDEVOBJ::vUnreferencePdev+0x136
ffffbe00`d155eaf0 fffff897`03acbdb7     win32kbase!MulDisablePDEV+0x31
ffffbe00`d155eb20 fffff897`03a25496     win32kbase!vUnreferencePdevWorker+0x3b7

In addition, the process in control in every BSOD is MSI True Color, a graphics process.

The first thing of note is that your Intel graphics driver is not up to date...

1: kd> lmDvmigdkmdn64
Browse full module list
start             end                 module name
fffff801`4ce00000 fffff801`4fab4000   igdkmdn64   (deferred)             
    Image path: igdkmdn64.sys
    Image name: igdkmdn64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Sep  2 21:53:17 2022 (6312511D)
    CheckSum:         02CBE57E
    ImageSize:        02CB4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The MSI website for your motherboard has a more recent graphics driver dated 21st July 2023, it would be wise to install that version. I would check all of your drivers and upgrade any where the MSI website has a more recent version. There is also a more recent BIOS update, dated 24th Jan 2024 available there too, though I wouldn't suggest flashing that until you have explored all other possibilities.

You also have MSI Afterburner installed and back in 2014 there were many BSODs probably caused by one of the drivers that Afterburner installs; NTIOLib_X64.sys. The version of this driver that you have installed dates from 2017 which might make it suspect...

1: kd> lmvm NTIOLib_X64
Browse full module list
start             end                 module name
fffff801`3cb80000 fffff801`3cb87000   NTIOLib_X64   (deferred)             
    Image path: NTIOLib_X64.sys
    Image name: NTIOLib_X64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 10 05:11:47 2017 (5962E263)
    CheckSum:         0000A452
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would suggest that you completely uninstall Afterburner, and any other MSI tools, since this driver is used by other MSI products as well, just to see whether that stops the BSODs. Unless you really need MSI True Color I would consider uninstalling that too, just to see whether the BSODs stop. Once you've done that then you can slowly reinstall those MSI tools you absolutely need, one at a time, until/if you get BSODs again.

 

[tacokiller]

Thanks for taking your time to help me resolve this issue.

I removed the MSI Afterburner (as well as TrueColor) and restarted the PC. With MSI tools gone I proceeded to download Intel VGA driver from MSI website. However, Windows update decided to force upon me the dated version of the driver. I tried to disable automatic update by selecting "2 — Notify for download and auto install" option in gpedit.msc — but that didn't work. So, I decided to try to install the latest driver again manually and immediately after Intel installer finished working, I got BSOD again (MSI tools are gone by this point).

This was the first time I got BSOD without me trying to shut the PC down. So, the Intel installer finished working and prompted me to restart but I didn't click "reboot" and got BSOD anyway. Now I'm confused if this was caused by the new driver from MSI website (build 4255), the old driver Windows installed automatically (build 3616) or did I attempt reinstalling the driver too many times and it got corrupted by different versions installed on top of each other?

 

[ubuysa]

Hmmm. This BSOD appears to have been caused by the audio driver, in the call stack leading up to the BSOD we see several calls to the Windows driver HDAudBus.sys. Although we don't see the third-party audio device driver called specifically in the dump, it will have been called (by HDAudBus.sys). Your audio driver is RTKVHD64.sys, a Realtek audio driver and it's dated August 2021...

0: kd> lmDvmRTKVHD64
Browse full module list
start             end                 module name
fffff803`b1bd0000 fffff803`b2204000   RTKVHD64   (deferred)          
    Image path: RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug 24 13:21:22 2021 (6124C822)
    CheckSum:         0063F58A
    ImageSize:        00634000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

There were no indications of an audio problem in the earlier dumps at all, however the MSI website for your motherboard also has an updated driver for your audio card.

It's never wise to try and interrupt Windows Update when it's trying to install drivers. The drivers that Windows Update installs are provided by the specific hardware vendors, so this will have been a genuine Intel driver that Windows Update was trying to install and it wasn't wise to try and stop it. If you have often attempted to defeat Windows Update when installing device drivers then this might account for your BSODs.

You do have some fairly old third-party drivers installed...
e2f68.sys - Intel LAN adapter driver - Feb 2021
gna.sys - Intel Gaussian Neural Accelerator driver (a coprocessor component in Intel CPUs, probably part of chipset driver) - Nov 2021
ICCWDT.sys - part of the Intel Watchdog Timer - Aug 2022 (Note that this tool has been superseded by the Intel Pro Software Suite)
iqvsw64e.sys - Intel Network Adapter Diagnostic Driver - Sept 2020
RTKVHD64.sys - Realtek audio driver - Aug 2021
tap0901.sys - OpenVPN (or ComodoVPN) driver - Oct 2019
TeeDriverW10x64.sys - part of the Intel Management Engine Interface - Oct 2021
wtd.sys - Intel Watchdog Timer Driver - Nov 1998 (Note that this tool has been superseded by the Intel Pro Software Suite)

I would now suggest that you run Windows Update repeatedly (and across any auto-reboots) until no more updates are found. Then click on 'view optional updates' and expand the Driver Updates section. If there are device drivers listed in there I would install them. If you are in any doubt then post a screenshot of that optional driver updates page.

FYI: device manufacturers tests new drivers for their devices using the Windows Hardware Quality Labs (WHQL) testing tools to validate their drivers and they then submit them to Microsoft for inclusion in the next round of Windows updates. When the device manufacturer submits a driver to Microsoft they indicate whether it is 'automatic' or 'manual'. Automatic drivers are installed when Windows Update runs with no other input from the user. These will be drivers that the device manufacturer knows are applicable to every system using this device and which are required to fix some bug or provide some additional universal functionality. Manual drivers are not installed by Windows Update, instead they are stored in the 'optional updates' section for the end user to choose to install or not. These will be drivers that may not be universally applicable to all users using this device, they may introduce extra functionality that not all users need for example. Manual drivers are there so that, if the user has a problem or needs the extra functionality, the driver is there and ready to be installed.