[Windows 11 x64] BSOD upon computer boot

[eepycurry]

• A brief description of your problem (but you can also include the steps you tried)
  • PC Built in December BSOD's upon system boot from time to time (no specific reproduction steps could be found).
  • I just turn on the computer, and upon reaching the desktop, BSOD, computer restarts and boots without issues.
    • I have Windows configured to boot directly to desktop, not asking password (this PC was conceived to be used as a "console-pc" for playing videogames.
• System Manufacturer?
  • None, mix of newly purchased parts (will describe below).
• Laptop or Desktop?
  • Desktop, tower.
• Exact model number (if laptop, check label on bottom)
  • N/A
• OS ? (Windows 11, 10, 8.1, 8, 7, Vista)
  • Windows 11
• x86 (32bit) or x64 (64bit)?
  • x64
• (Only for Vista, Windows 7) Service pack?
  • N/A
• What was original installed OS on system?
  • N/A
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
  • Full retail version
• Age of system? (hardware)
  • 2 months
• Age of OS installation?
  • 2 months
• Have you re-installed the OS?
  • First install of the OS on this hardware configuration
• CPU
  • AMD Ryzen 5 5600X 3.7GHz
• RAM (brand, EXACT model, what slots are you using?)
  • Kingston HyperX Fury Black DDR4 3200Mhz PC-25600 16GB 2x8GB CL16
  • Slots B2/A2
• Video Card
  • SAPPHIRE VGA Pulse Radeon RX 7800 XT Gaming,AMD,RX7800XT,16GB,GDDR6,256BIT,2HDMI+2DP
• MotherBoard - (if NOT a laptop)
  • ASUS ROG Strix B550-F Gaming
• Power Supply - brand & wattage (if laptop, skip this one)
  • Corsair RM850 2021, RM Series, 850 Watts 80 Plus Gold
• Is driver verifierenabled or disabled?
  • Never heard of it, so I understand that it is disabled.
• What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
  • Microsoft Defender, as default.
• Are you using proxy, vpn, ipfilters or similar software?
  • No I'm not.
• Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
  • No I'm not.
• Are you currently under/overclocking? Are there overclocking software installed on your system?
  • I am not, but does Adrenaline (AMD drivers) count as overclocking software?

 

[ubuysa]

Hello, and welcome for the forum!

All your dumps are pretty much identical and all of them feature only one third-party driver on the call stack leading to the BSOD; AtihdWT6.sys, your AMD HD Audio driver. The bugcheck itself happens during a Windows function call...

CONTEXT:  fffff2820b7c67b0 -- (.cxr 0xfffff2820b7c67b0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000006
rdx=ffff9382ef0f6930 rsi=000000000000000a rdi=00000000000000b8
rip=fffff8003f0a64ea rsp=fffff2820b7c71d0 rbp=ffff9382f86c9a90
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000001 r13=ffff9382fc6f7460
r14=ffff9382ef0f6910 r15=0000000000000008
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
ks!KspPinPropertyHandler+0x192:
fffff800`3f0a64ea 458b5104        mov     r10d,dword ptr [r9+4] ds:002b:00000000`00000004=????????
Resetting default scope

Here you can see the Windows ks!KspPinPropertyHandler (a kernel streaming function) executing a MOV instruction using register R9 (plus 4 bytes) as a memory pointer. The resulting memory reference shows that R9 must have contained zeroes and so the resulting memory reference is invalid. The question of course is 'why was R9 all zeros' and we can't really answer that question. The best we can say is that any failure is going to be down to a third-party driver (because Windows drivers don't make these kinds of errors) and since AtihdWT6.sys is the only third-party driver referenced then that's the most likely cause.

The version of AtihdWT6.sys that you have installed is fairly recent, dating from August 2023...

3: kd> lmvm AtihdWT6
Browse full module list
start             end                 module name
fffff807`99510000 fffff807`9954e000   AtihdWT6 T (no symbols)     
    Loaded symbol image file: AtihdWT6.sys
    Image path: AtihdWT6.sys
    Image name: AtihdWT6.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug 22 07:42:10 2023 (64E43CA2)
    CheckSum:         0004B3E7
    ImageSize:        0003E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would suggest checking under Windows Update in the 'View optional updates' section. Expand Driver Updates and see whether there is an AMD HD Audio driver ready to be installed in there. If not, then you could right-click on the AMD High Definition Audio Device in Device Manager and select 'Update Driver' from there. If neither of those help then it's worth checking with the AMD Driver & Support Tool for an updated driver.

AFIK, based on some web searches I've just done, the AtihdWT6.sys driver is only required if you send audio over an HDMI connection. If you're not doing that then you could try locating the AtihdWT6.sys driver in the C:\Windows\System32\Drivers folder and rename it to AtihdWT6.old so that it's not recognised as a driver and not loaded at boot time. Now do a cold boot and see what happens.

With all that said, that these BSODs happen only on a cold boot and reboots just fine might suggest that this has a hardware cause. It's possible the some component of the audio hardware doesn't respond fast enough when cold (or the monitor/TV on the end of the HDMI cable?) and this causes the AtihdWT6.sys driver to fail, causing the BSOD. On rebooting the audio hardware component (or monitor/TV?) may have warmed up enough so that it responds correctly and AtihdWT6.sys responds as expected.

One other thing, if you have a monitor/TV HDMI connected then ensure that the monitor/TV is on and not sleeping before you boot the PC. I have seen other motherboards fail to POST properly if the monitor is in its sleep mode...

In summary, I would try renaming the driver to .old and see a) whether the cold boot BSODs cease, and b) whether you actually need it at all.

 

[eepycurry]

This PC is connected to an LG OLED TV, so I'm using HDMI and as such, It would not be advisable to be let without audio.
I have checked if there are any new version of "AMD High Definition Audio Device" driver and had no luck. I used "AMD Driver & Support Tool", and a new version of Adrenaline was downloaded and installed. Just in case, I checked if the version of "AMD High Definition Audio Device" was updated in the process, but no, I remain in "10.0.1.30".
From what I was able to gather from you, there is a possibility that the problem might lie in the GPU itself and not on the driver?
I was thinking on maybe unplugging and pluggin the GPU again to see if I get this issue in the near future (but again, not being able to reproduce this at will, it will be hard to say if this somehow fixed the issue, or not).

Thanks for your time!

 

[ubuysa]

In that case, go into device manager, right-click on the AMD High Definition Audio Device and select 'uninstall'. If asked to uninstall the driver as well click Yes. Then reboot. WIndows should find and install the right driver. See whether that helps.

It could be the card, but it's essential to eliminate everything else first.