Question Constant BSOD's all linked to ntoskrnl.exe. What should I do?

[janton]

Hello everyone, and thanks for showing interest in my situation!
I'm getting crazy with a lot of BSOD's from the windows kernel: ntoskrnl.exe+4b8680

This new MiniPC that I am not able to use normally because of BSOD blue screens.
The computer in question has no brand because it was bought by Aliexpress but it is similar to the one sold by GENMACHINE, TOPTON, FIREBAT....
AMD 7535HS (ZEN3+) 35W TDP (RADEON 660M) 32GB DDR5 4800Mhz
https://aliexpress.com/item/1005006594113138.html

Mini-PC-Gehäuse - AliExpress 7

Smarter Shopping, Better Living! Aliexpress.com

aliexpress.com

https://aliexpress.com/item/1005007171097893.html

I updated the BIOS with the one provided by FIREBAT MN56:
https://drive.google.com/drive/folders/164DlHHP-sMX-VeZtwOH01thjww5dBwfm?usp=sharing

I can try with this BIOS of Genmachine for Rembrant 6000:
https://onedrive.live.com/?redeem=a...e2744c31b8960ef8ea19c35e&cid=568C64C2F06246D0

I have configured it by setting both the RAM speed and timings and the CPU/GPU TDP limited to 35W. Now at least it is more stable and does not fail neither in memtest tests nor in CPU stress tests like OCCT.

I was still suffering a lot of BSOD despite being stable until I disabled directly in the BIOS the two PCIe network cards (I was seeing strange things between Intel drivers of the 1Gb board and Realtek drivers of the 2.5Gb Ethernet connection). Disabling it has reduced the BSODs but they are still present.
I think everything was more stable before installing the AMD/Radeon drivers (Chipset included) but I can't be 100% sure.

Attached MiniDump so you can evaluate them, thank you very much:
https://drive.google.com/drive/folders/1RSC6UyEDVBlHa-yvUNAKYhctKdwCIBEF?usp=sharing

Kind regards, thanks.
Jaime.

 

[Lutfij]

Welcome to the forums, newcomer!

Using WinDBG on your two .dmp files, HDAudBus.sys apart from ntkrnlmp.exe was found to be the culprit, I'm curious, did you install the OS onto the mini system or did it come that way?

I would start fresh, after recreating your bootable USB installer for your OS, then install the OS in offline mode, then install the latest drivers relevant to your platform in an elevated command, i.e, Right click installer>Run as Administrator(yes you will need to download the drivers beforehand from AMD's support site and your mini PC's support portal).

I updated the BIOS with the one provided by FIREBAT MN56
Were you instructed by the seller to use that BIOS file from another brand?

 

[janton]

Welcome to the forums, newcomer!

Using WinDBG on your two .dmp files, HDAudBus.sys apart from ntkrnlmp.exe was found to be the culprit, I'm curious, did you install the OS onto the mini system or did it come that way?

I would start fresh, after recreating your bootable USB installer for your OS, then install the OS in offline mode, then install the latest drivers relevant to your platform in an elevated command, i.e, Right click installer>Run as Administrator(yes you will need to download the drivers beforehand from AMD's support site and your mini PC's support portal).

I updated the BIOS with the one provided by FIREBAT MN56
Were you instructed by the seller to use that BIOS file from another brand?

Thank you @Lutfij!! It's the first time I cannot resolve this things for myself with your knowledge but I've been around for years just watching you

It came with an OS version installed but I did a fresh install from USB (Microsoft Media Creator) fresh just in case malware, OEM, etcetera. I have backedup the drivers with this commom powershell prompt.

My seller is gone, is not selling nor answering anymore. So..., I'm [vulgarity redacted]

My WIN11 is almost fresh now, but the AMD Chipset and RADEON drivers, I haven't installed anything else.
If it is pointing to HDAudBus.sys is anything else would you do ?

 

[johnbl]

one bugcheck was
HYPERVISOR_ERROR (20001)
normally you would"
update bios, install the chipset drivers for the CPU, install motherboard drivers. confirm your memory timings are correct for your ram, then run memtest86 to check them.
after that I would run a CPU diagnostic test for your CPU

 

[janton]

one bugcheck was
HYPERVISOR_ERROR (20001)
normally you would"
update bios, install the chipset drivers for the CPU, install motherboard drivers. confirm your memory timings are correct for your ram, then run memtest86 to check them.
after that I would run a CPU diagnostic test for your CPU

I have deactivated from Windows features anything related to HyperV and Virtualization.

I did that:
· BIOS is updated
· Windows fresh installation formatting the SSD (windows stock drivers)
· AMD Chipset
· Radeon drivers
.. (haven't installed anything more yet,, in "manufacturer" there are RLTK Audio / RLTK WLAN / RLTK BT / RLTK LAN)