- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using the latest WiFi driver 23.20 and after booting up, the adapter wasn't detecting any WiFi hotspots at work and when I clicked to enter the Windows networking UI that's when the crash happened.
I can't investigate any further without driver symbols. If you'd like a copy of the 2GB DMP file then let me know and I can post a Dropbox link.
I've attached the windbg crash analysis and my system details. I was using a AX211 card and just recently upgraded to the BE200. The BE200 card is working fine for the most part. This was an odd timing issue, me thinks.
-Nick
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffcc81fccea060, Physical Device Object of the stack
Arg3: ffffc9851c537738, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffcc81f921c290, The blocked IRP
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello cnick6,
Thank you for posting on the Intel® communities.
Please be advised that since this is an OEM (Branded Laptop) original equipment manufacturer device, please take into consideration that our support may be limited since we are not familiar with the technology, settings, customizations, custom drivers, and features that the OEM has designed and installed your system.
We are unable to confirm whether the Intel® Wi-Fi 7 BE200 is 100% compatible with your system. There is a possibility that the physical Wi-Fi antenna is not calibrated for the Wi-Fi 7 card causing your system not able to detect any hotspot/wireless networks. You might also consider making sure that the physical Wi-Fi antenna is properly connected to its designated terminals. However, we would like to conduct further investigation regarding the Intel® Wi-Fi 7 BE200.
After reviewing the submitted system scan(SSU), it appears that the BE200 is not detected as installed. When the BE200 is installed in your system, is it being detected inside Device Manager?
In addition, please collect the logs from Windows system event and share it with us here so we could look into your case further for a solution:
- In Windows search, search for "event" and select "Event Viewer"
- In the left pane, expand "Windows logs"
- Right click on "System" and select "Clear Log..."
- Expand “Applications and Service Logs” -> “Microsoft” -> “Windows” -> “WLANAutoConfig”
- Right click on “Operational” and select “Clear Log…”
- Reproduce issue.
- Reference above steps (instead of Clear Log… choose Save All Events as…) to save the system event and WLAN-AutoConfig logs in .evtx format.
Best regards,
Jay B.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jay,
Okay a couple of key points you missed. The crash occurred within a few minutes after logging into the laptop. I had no time to do much of anything. I noticed I wasn't connected to wireless and then clicked on the systray icon. The hotspot picker was empty and that's when it crashed.
I noticed the Intel SSU didn't pick up the BE200 as well. I didn't mention it specifically but figured you'd know better than I do about that application.
The device works 100% fine with Win11. Yes, the antennas are 6E-rated only, but I'm not using any Wi-Fi 7 hotspots nor do I plan to any time soon. Device Manager loads the 23.20 driver just fine -- obviously -- or it wouldn't have crashed. The BE200 has been working 100% since the crash occurred. I haven't been able to reproduce it. There could be some minor BIOS incompatibility but I don't think that's the case here. I purchased the BE200 card from Amazon. Is it possible the card is not genuine? Is there a way to tell?
I don't have the laptop with me so I'll run a couple of other utilities to see if the BE200 card is detected. HWInfo is my favorite for specs such as that.
Let me know if you want a copy of the crashdump.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jay, the Intel SSU application is at fault. For some reason, it doesn't detect the Alder Lake chipset and thus your application cannot see the Wi-Fi NIC. I guess you haven't tested the SSU with this particular laptop.
I've attached the HWINFO log and as you can see it's definitely supported and working as intended:
Intel Wi-Fi 7 BE200 320MHz ------------------------------------------------
[General Information]
Device Name: Intel Wi-Fi 7 BE200 320MHz
Original Device Name: Intel Wi-Fi 6/6E/7 AX221/AX230 160MHz/320MHz (Garfield Peak)
Device Class: Other Network Adapter
Revision ID: 1A
PCI Address (Bus:Device:Function) Number: 45:0:0
PCI Latency Timer: 0
Hardware ID: PCI\VEN_8086&DEV_272B&SUBSYS_00F48086&REV_1A
[PCI Express]
Version: 4.0
Maximum Link Width: x1
Current Link Width: x1
Maximum Link Speed: 16.0 GT/s
Current Link Speed: 8.0 GT/s
Device/Port Type: PCI Express Endpoint
Slot Implemented: No
Emergency Power Reduction: Not Supported
Active State Power Management (ASPM) Support: L1
Active State Power Management (ASPM) Status: L1 Entry
L0s Exit Latency: 2 - 4 us
L1 Exit Latency: 32 - 64 us
Maximum Payload Size Supported: 128 bytes
Maximum Payload Size: 128 bytes
Resizable BAR Support: Not Supported
[System Resources]
Interrupt Line: N/A
Interrupt Pin: INTA#
Memory Base Address 0 AE2FC000
[Features]
Bus Mastering: Enabled
Running At 66 MHz: Not Capable
Fast Back-to-Back Transactions: Not Capable
[Driver Information]
Driver Manufacturer: Intel Corporation
Driver Description: Intel(R) Wi-Fi 7 BE200 320MHz
Driver Provider: Intel
Driver Version: 23.20.0.4
Driver Date: 28-Nov-2023
DeviceInstanceId PCI\VEN_8086&DEV_272B&SUBSYS_00F48086&REV_1A\4&3261BCA&0&00E5
Location Paths PCIROOT(0)#PCI(1C05)#PCI(0000)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm curious about this tbh, SSU is just like system information/msinfo32 so it should gather everything unless you have a modified BIOS. This is out my curiosity but could you send the SSU and the System Information?
I'd like to actually see how that looks like since HWinfo Normally gathers everything despite a modified BIOS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello cnick6,
Thank you for clarifying. At this rate, we would like to request for the crashdump as we will proceed with analyzing and investigating what happened after the integration of the BE200 into your system. We will also look into why SSU is not picking up the BE200, while HWInfo does.
Also, may we request for photos(all angles) of the box/packaging when you bought the Wi-Fi 7 BE200? This is for us to check the genuity of the product.
Best regards,
Jay B.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sure Jay, I'll send a link later tonight to the crashdump file. No can do on the box -- it was recycled. It wasn't much of anything except a small generic cardboard box. It didn't look like anything 'official' Intel. Here's a link to the exact purchase on Amazon:
You'll note the pictures are obscured in a couple of places -- one being the Intel logo. I did confirm the Intel logo was present on the back of the BE200 I received -- but no way to tell if it's genuine.
PS. Regarding the SSU, one thing that's confusing: if I go into the 'about' page on the utility it shows version 2.5.0 from 2016 -- but download link says 3.0.0.2 or something like that. I reinstalled it from the download page again and the version installed still shows 2.5.0 -- which seems strange. Could there be a version mismatch on your download page?
Cheers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello cnick6,
Thank you for the response. No worries, kindly update this thread with the requested dump files so that we can proceed with our investigation of your case. We appreciate you sharing with us the purchase link from Amazon. We will see if we can do something about validating its genuity. Regarding the Intel SSU, please be advise that version 2.5.0.0 shown in "About Intel® SSU" is a known issue as per its release notes here: https://downloadmirror.intel.com/25293/releasenotes_3.0.0.2.txt. This will addressed in later release.
Best regards,
Jay B.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jay, here's the crashdump download link. It's 434MB zipped and just over 2GB uncompressed:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was reading the dump file you provided to them, for some actual reason the wireless card is the one causing it.
0x9F_3_Netwaw14_IMAGE_pci.sys
Since you are using a laptop by any chance did you consult Lenovo first about the installation prior the integration? I know laptop mobos have a whitelist for wireless cards and has to be listed for it to fully function. Another side of the coin I can see here is that the IEEE 802.11be wireless protocol/standard may not be accepted by the motherboard since it could that the mobo only knows the 802.11ax wireless protocol/standard so there could be that part too since the BE200 has the 802.11be( Yes I know the BE200 has all protocols but again this could be a small factor)
In terms of system compatibility, I have no doubt this could be used by most systems since this does not have a CNVIo so there's no limitation in terms of socket and support.
Also, how did the dump file get so big omg, but eh don't it mind haha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes the card can function but not at full power and the mobo of the laptop maybe realized it late then suddenly rejected it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mayu, sorry, you're on the wrong track here. Yes -- the driver at fault is \Driver\Netwaw14 which is the Intel BE200 driver that's currently loaded. This is a fairly common driver problem that is likely a timing issue in the driver code; but it's very difficult to guess without valid driver symbols. As you can see from the last command, the IRP is trying to Set D0 power state (and for some reason) it didn't complete in time and thus the 9F occurred. It is possible (albeit rare) that another driver could be indirectly interfering with the BE200 driver and causing the issue. It's highly unlikely this is an incompatibility problem with the hardware.
The crashdump is this large because I have 40GB of RAM in my laptop and the OS (Win11 Enterprise) performs a partial kernel dump if there's a BSOD.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More debug info:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hmm if that is the case probably re updating the IME and Chipset drivers are update just to make sure the the mobo recognizes the card fully and as for the driver, probably try doing a full clean reinstallation of the driver since the Lenovo wireless driver could be still present in the system which can cause the delay.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FWIW, I am still seeing this Bugcheck x9F with the latest Win11 updates and the latest WiFi driver (23.30) -- but it is possibly due to the fact that WiFi-7 support isn't fully implemented in the released Win11 builds.
Oddly, this crash happens only upon first power on just prior to the logon screen. After the initial crash however, the system seems perfectly stable.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page