Question New build - - - BSOD after fresh install of Windows 11 ?

Apr 30, 2025
2
0
10
PC Specs
Mobo: MSI X870E Carbon Wi-Fi
CPU: Ryzen 9900X3D
RAM: TeamGroup DDR5 96GB
SSD: Samsung 9100 Pro
PSU: 1000W Lian Li Platinum

Machine has BSOD twice after fresh install of Windows 11. I had to reformat recently and previously no issues with no hardware change since then. Temps are good no OC but XP is enabled for RAM. All drivers I believe are up-to-date as well as Windows 11 24H2 wondering if that has anything to do with it. Thank you in advance!

Here are my 2 minidumps in .dmp format. Happened twice today within the hour no issue yesterday.

https://drive.google.com/drive/folders/1RgkoyCwcvOotnNDYLGpsI8d6Kp4zvDku
 
Welcome to the forums, newcomer!

I'm seeing pci.sys being the trigger for your BSoD...you state installing the OS anew, did you recreate the bootable USB installer then install the OS in offline mode? Installing all necessary drivers for your platform in an elevated command, i.e, Right click installer>Run as Administrator?

BIOS version for your motherboard? You don't have a discrete GPU in your build?
 
both bugchecks are the same. qualcomm bluetooth driver did not respond to a power request.

update this driver:
https://www.msi.com/Motherboard/MPG-X870E-CARBON-WIFI/support#driver
look under the LAN drivers for
Qualcomm NCM865 BlueTooth Drivers
release date: 2025-03-14
===========
most current bugchek:
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.

see if you can update this driver:
qcwlan64.sys Tue Jul 4 19:53:46 2023
(wireless driver)
==========
14: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.7, DMIVersion 0, Size=2434]
BiosMajorRelease = 5
BiosMinorRelease = 35
BiosVendor = American Megatrends International, LLC.
BiosVersion = 1.A30
BiosReleaseDate = 03/12/2025
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7E49
SystemFamily = To be filled by O.E.M.
SystemVersion = 1.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MPG X870E CARBON WIFI (MS-7E49)
BaseBoardVersion = 1.0
 
Last edited:
  • Like
Reactions: clotheman
both bugchecks are the same. qualcomm bluetooth driver did not respond to a power request.

update this driver:
https://www.msi.com/Motherboard/MPG-X870E-CARBON-WIFI/support#driver
look under the LAN drivers for
Qualcomm NCM865 BlueTooth Drivers
release date: 2025-03-14
===========
most current bugchek:
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.

see if you can update this driver:
qcwlan64.sys Tue Jul 4 19:53:46 2023
(wireless driver)
==========
14: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.7, DMIVersion 0, Size=2434]
BiosMajorRelease = 5
BiosMinorRelease = 35
BiosVendor = American Megatrends International, LLC.
BiosVersion = 1.A30
BiosReleaseDate = 03/12/2025
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7E49
SystemFamily = To be filled by O.E.M.
SystemVersion = 1.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MPG X870E CARBON WIFI (MS-7E49)
BaseBoardVersion = 1.0
I truly appreciate the help! I feel confident enough to install my new GPU now ASUS TUF 5080 OC.
I feel pretty embarrassed I couldn't zero in on the faulty driver. I used bluescreenview but got distracted. I have been in IT for years but mainly work with INTUNE \AVD these days. I just now used WinDbg and ran !analyze -v to confirm what you're saying and got the same results. Is this a normal method or is there a preferred better way you recommend?
Thanks again!
 
I truly appreciate the help! I feel confident enough to install my new GPU now ASUS TUF 5080 OC.
I feel pretty embarrassed I couldn't zero in on the faulty driver. I used bluescreenview but got distracted. I have been in IT for years but mainly work with INTUNE \AVD these days. I just now used WinDbg and ran !analyze -v to confirm what you're saying and got the same results. Is this a normal method or is there a preferred better way you recommend?
Thanks again!
doing
!irp on the irp number works on a mini dump now. it used to be only on a kernel dump.

lots of people are having problems with a clean install. looks like windows detects the hardware and downloads old drivers that do not work with the new power settings. Results in bugchecks on clean installs.
would have to check the microsoft catalog to see if they have a old driver for your case. just faster/easier to see if your motherboard vendor had a update.

seeing a lot of bugchecks in old wifi/bluetooth drivers from various vendors. At lease with the kernel dump you can look at the logs and see the errors.
 
Last edited: