Question BSOD Crashes after Upgrading from Mediatek Wifi to Intel AX210

[NightHawkRMX]

I am asking for some help and guidance with resolving a BSOD crashing issue which have started after installing an Intel AX210NGW Wifi card into a HP Pavilion Aero 13 2023 13z-be200 laptop (specs in signature)

Laptop:
HP Pavilion Aero 13: Ryzen 7 7735U, 16GB DDR5, Radeon 680M, 1TB UD90 PCIe 4, 1600p IPS, Win 11


Some backstory: This HP was optioned with Mediatek MT7922A22M over the base Realtek option. In the years since, it has had some infrequent issues such as not seeing any networks, or refusing to connect to my network, displaying "No Internet". My Pixel 8 and other devices never have issues with the same network. This is far from my first experience dealing with WiFi issues on Realtek/Mediatek chipsets. In fact, my desktop in the past has also had a few non Intel Wifi (mostly realtek tplink or rosewill pcie) adapters which all got swapped at some point for giving me issues. Awhile ago I installed a very basic Intel AC m.2 card I had lying around, and the wifi works perfectly on any network since. Seeing that an Intel card solved my issues on my desktop, I purchased an Intel AX210 Wifi 6e M.2 card and installed it into my laptop.

After swapping the card and booting, Windows 11 instantly detected the card and I was able to connect to my network. Initially all was well. Wifi connects and works as it should, but then when just doing some work in Office 365, the machine bluescreened to a garbled screen where the stopcode was not readable. It proceeded to do this again a few hours later when taking notes in class.

At this point, I looked in event viewer which only had "Kernal Power 41" messages under critical. I downloaded "Whocrashed" which told me that the one of the BSODs had a stopcode of "Kernal Mode Heap Corruption", and the other one was "System Thread Exception Not Handled". Ive seen the latter with failed overclocks on desktops, but this laptop has never given me any stability issues like that. I went into Device manager and "Uninstalled" the Intel Bluetooth and AX210 wifi devices, telling it to uninstall the software/drivers. I then reinstalled the latest Wifi/Bluetooth driver for the AX210 off of Intels site. Again, got 2 more bluescreens within an hour while just trying to do work in office 365. One apparently didnt dump a log, the other one was again stopcode "Kernal Mode Heap Corruption" according to Whocrashed. I enabled full memory crash dumps, but it has not crashed again yet for me to get a more detailed report. I can provide what I do have upon request.

I am assuming this is a driver conflict, but am unsure. What would you reccomend doing to resolve this and proceed? If i can resolve this issue ASAP it would be ideal.

 

[Lutfij]

HP Pavilion Aero 13 2023 laptop (specs in signature)
Sig space specs can and will change. When that happens, this thread and any relevant suggestion will be rendered moot to the end user in the same boat as you're in now. It's for this reason we ask users to include their specs in their thread's body. I've shoehorned that relevant info into your thread. Though an SKU would've helped more when it comes to alaptop/prebuilt.

I purchased an Intel AX210 Wifi 6e M.2 card and installed it into my laptop.
Got a link to the card you'd purchased and installed?

Speaking of which, did you make sure you were on the latest BIOS version prior to swapping in the WiFi card?

After swapping the card and booting, Windows 11 instantly detected the card and I was able to connect to my network.
Did you uninstall the prior adapter's drivers? Did you let the OS download and install drivers for your latter adapter?

BSoD's are caused due to an incompatibility, either hardware or software. When Windows 10 first came out, for a year or so, the OS kept nuking Killer/Atheros/Qualcomm/Broadcom based wireless adapters. The same might be going on here. You might want to pass on the *.dmp file for us to take a look at.

 

[NightHawkRMX]

Sku added to original post.

Got a link to the card you'd purchased and installed?

Card came from Wavlink, but through eBay since the price was slightly lower than the listing on Newegg:

AX5400M WiFi 6E PCIe Network Card Intel AX210 Tri-Band Network Adapter BT5.3 | eBay

WiFi 6E M.2 module. Wavlink Upgraded Wi-Fi 6E AX5400 Tri-band Wi-Fi Module with Bluetooth 5.3--Ascending to Greater Heights! Wavlink Wi-Fi 6E Tri-band M.2 module(WL-WN675X3M) is an AX5400 wireless adapter for.

www.ebay.com

I do have 2 of these, was going to install the other in the desktop for faster wifi but haven't yet.

Speaking of which, did you make sure you were on the latest BIOS version prior to swapping in the WiFi card?

No. Current Bios version is F20, looks like it's from April 2024. I suspect Windows update installed this at some point, because I never tend to update the BIOS unless I have issues. Looks like version F21 from September 2024 is available. Should I update to that?

After swapping the card and booting, Windows 11 instantly detected the card and I was able to connect to my network.
Did you uninstall the prior adapter's drivers? Did you let the OS download and install drivers for your latter adapter?

No, and in retrospect I'm not sure how I overlooked that. I guess I'm used to windows handling that automatically anymore when it detects a hardware change, but perhaps it didn't do so well here. When I booted with the new card it was detected by Windows instantly. Considering the device was offline, Windows couldn't have downloaded the drivers for the AX210, perhaps it already had them in a built in collection?

I've got no clue how to remove those drivers now. Unsure if there's a utility like DDU that can just nuke all Network drivers or not?

/Qualcomm/Broadcom based wireless adapters. The same might be going on here. You might want to pass on the *.dmp file for us to take a look at.

Will get that here soon. Where would you recommend I upload that, or is just posting the text in a spoiler fine?

 

[NightHawkRMX]

Oh, another note, when I booted it for the first time with the new card, windows decided to install an update to 24H2 without promoting me. Unsure if related to causing this issue.

 

[NightHawkRMX]

Here are my dumps.

Spoiler: Dump log file

DLOGFILE00010000DUMP*
Dump stack initialized at UTC: 2025/02/18 19:56:20, local time: 2025/02/18 14:56:20.
#BugCheckCode 0x000000000000013A
#BugCheckP1 0x0000000000000017
#BugCheckP2 0xFFFFA90A1E100380
#BugCheckP3 0xFFFFA90A2F4FB310
#BugCheckP4 0x0000000000000000
Progress 0x00000042
Elapsed BugCheck duration 00008639ms
Starting get secondary dump callbacks size.
Progress 0x00000052
Finish get secondary dump callbacks size.
Dump Type: 4, Total Dump Size: 2947624, Secondary Dump Size: 2730536.
Starting write of dump header.
Finish write of dump header.
Starting write of minidump data.
Finish write of minidump data.
Progress 0x00000044
Elapsed BugCheck duration 00009773ms
Starting invoking secondary dump callbacks.
Calling ibtdrv secondary callback.
Return from ibtdrv secondary callback.
Writing ibtdrv secondary callback data.
Writing ibtdrv secondary callback data done.
Calling Intel Wireless WiFi Link Adapter secondary callback.
Return from Intel Wireless WiFi Link Adapter secondary callback.
Writing Intel Wireless WiFi Link Adapter secondary callback data.
Writing Intel Wireless WiFi Link Adapter secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling HbEvtpSystemDiagLogCrashdump secondary callback.
Return from HbEvtpSystemDiagLogCrashdump secondary callback.
Writing HbEvtpSystemDiagLogCrashdump secondary callback data.
Writing HbEvtpSystemDiagLogCrashdump secondary callback data done.
Calling ETD secondary callback.
Return from ETD secondary callback.
Writing ETD secondary callback data.
Writing ETD secondary callback data done.
Calling secondary callback.
Return from secondary callback.
Writing secondary callback data.
Writing secondary callback data done.
Calling secondary callback.
Return from secondary callback.
Writing secondary callback data.
Writing secondary callback data done.
Calling PortDriverStandard secondary callback.
Return from PortDriverStandard secondary callback.
Writing PortDriverStandard secondary callback data.
Writing PortDriverStandard secondary callback data done.
Calling \Device\DxgKrnl secondary callback.
Return from \Device\DxgKrnl secondary callback.
Writing \Device\DxgKrnl secondary callback data.
Writing \Device\DxgKrnl secondary callback data done.
Calling Wdf01000 secondary callback.
Return from Wdf01000 secondary callback.
Writing Wdf01000 secondary callback data.
Writing Wdf01000 secondary callback data done.
Calling blackbox - CI secondary callback.
Return from blackbox - CI secondary callback.
Writing blackbox - CI secondary callback data.
Writing blackbox - CI secondary callback data done.
Calling blackbox - Winlogon secondary callback.
Return from blackbox - Winlogon secondary callback.
Writing blackbox - Winlogon secondary callback data.
Writing blackbox - Winlogon secondary callback data done.
Calling blackbox - NTFS secondary callback.
Return from blackbox - NTFS secondary callback.
Writing blackbox - NTFS secondary callback data.
Writing blackbox - NTFS secondary callback data done.
Calling blackbox - PNP secondary callback.
Return from blackbox - PNP secondary callback.
Writing blackbox - PNP secondary callback data.
Writing blackbox - PNP secondary callback data done.
Calling blackbox - BSD secondary callback.
Return from blackbox - BSD secondary callback.
Writing blackbox - BSD secondary callback data.
Writing blackbox - BSD secondary callback data done.
Calling SecureKernelFailureLog secondary callback.
Return from SecureKernelFailureLog secondary callback.
Writing SecureKernelFailureLog secondary callback data.
Writing SecureKernelFailureLog secondary callback data done.
Calling SecureKernelCrashdumpArea secondary callback.
Return from SecureKernelCrashdumpArea secondary callback.
Writing SecureKernelCrashdumpArea secondary callback data.
Writing SecureKernelCrashdumpArea secondary callback data done.
Calling secondary multi-part dump callbacks.
Starting TRIAGEDUMPDATA multi-part secondary callback.
Finish TRIAGEDUMPDATA multi-part secondary callback.
Starting SMBiosData multi-part secondary callback.
Finish SMBiosData multi-part secondary callback.
Starting SMBiosRegistry multi-part secondary callback.
Finish SMBiosRegistry multi-part secondary callback.
Starting SMBiosRegisters multi-part secondary callback.
Finish SMBiosRegisters multi-part secondary callback.
Starting SMBiosDataACPI multi-part secondary callback.
Finish SMBiosDataACPI multi-part secondary callback.
Starting PCI multi-part secondary callback.
Finish PCI multi-part secondary callback.
Starting Etw multi-part secondary callback.
Finish Etw multi-part secondary callback.
Finish calling secondary multi-part dump callbacks.
Progress 0x00000045
Finish invoking secondary dump callbacks.
Starting invoking dump complete callbacks; Type: 0x04.
Finished invoking dump complete callbacks; Type: 0x04.
Progress 0x00000046
Dump ended at UTC: 2025/02/18 19:56:20, local time: 2025/02/18 14:56:20.
Elapsed BugCheck duration 00010539ms
Progress 0x00000053
Dump completed successfully.

Link to mini dumps (3)
https://limewire.com/d/f3f9bb4e-dad...0#CwXGqIGoi81M59wAW1qnE2paYh-cGr6BOHl8iTprXvE