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...
Code:
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...
Code:
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.
