topic Re:Microsoft Wireless Display Adapter causes BSOD in Wireless

Microsoft Wireless Display Adapter causes BSOD

Thomas_123 — Tue, 21 Feb 2023 07:44:20 GMT

Hello,

Since 6 months we have an issue that when we are trying to connect via a Microsoft Wireless Display Adapter we get very often blue screens.

After a couple of months investigation from Microsoft they concluded that it is an Intel driver issue.

The driver that is causing the BSOD is the IntcAudioBus driver.

We are running the following devices:

HP Probook 450 G8 G9

Hp Zbook firefly G8 G9

Hp Zbook Fury G8

The windows version are W10 21H2, W10 22H2 and W11 22H2.

All drivers are up to date according HP Support Assistant and Intel DSA.

Dump analysis:

kd> !mex.crash
Dump Info
============================================
Dump Name: MEMORY_20221202_NB0312.dmp
Windows 10 Kernel Version 22621 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff802`4e200000 PsLoadedModuleList = 0xfffff802`4ee12fe0
Debug session time: Fri Dec 2 14:55:38.917 2022 (UTC + 1:00)
System Uptime: 0 days 7:28:50.688
SystemManufacturer = HP
SystemProductName = HP ZBook Firefly 14 inch G8 Mobile Workstation PC
Processor: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
Bugcheck: 9F (3, FFFFA88716E33060, FFFFF98976ED7118, FFFFA887405E08E0)
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

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: ffffa88716e33060, Physical Device Object of the stack
Arg3: fffff98976ed7118, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffa887405e08e0, The blocked IRP

Bugcheck Thread
============================================
Process                 AttachedProcess           Thread           CID       UserTime   KernelTime ContextSwitches Wait Reason Time State
Idle (fffff8024ef48f40) System (ffffa88714756040) ffffa88714779040 0.0             0s 6h:28:42.906        18409075 Executive   31ms Running on CPU 7

Priority:
    Current Base UB FB IO Page
    63      0    0 0 0 0

# Child-SP         Return           Call Site                                                                                 Source
0 fffff98976ed70c8 fffff8024e772426 nt!KeBugCheckEx+0x0                                                                       open start of function
1 fffff98976ed70d0 fffff8024e7722fc nt!PopIrpWatchdogBugcheck+0x122                                                           open start of function
2 fffff98976ed7150 fffff8024e4b793b nt!PopIrpWatchdog+0xc                                                                     open start of function
3 fffff98976ed7180 fffff8024e4b90b6 nt!KiProcessExpiredTimerList+0x1eb                                                        open start of function
4 fffff98976ed72b0 fffff8024e62d6ee nt!KiRetireDpcList+0xed6                                                                  open start of function
5 fffff98976ed7540 0000000000000000 nt!KiIdleLoop+0x9e                                                                        open start of function

This thread is crashing.
Thread Description: Idle Thread

Insights
============================================
Description: Bugcheck 0x9F DRIVER_POWER_STATE_FAILURE triage

Device object (ffffa88716e33060) is for:
NTPNP_PCI0018 \Driver\pci DriverObject ffffa887146cf4e0
Current Irp 00000000 RefCount 0 Type 0000001d Flags 00001040
SecurityDescriptor ffffdf856bbbb2e0 DevExt ffffa88716e331b0 DevObjExt ffffa88716e33970 DevNode ffffa88716dc58a0
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffa88716eccd20 \Driver\ACPI
Device queue is not busy.

Device Stack

!DevObj           !DrvObj            !DevExt           ObjectName
ffffa8873aee0b30 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_b6bb9ecad049db30\IntcAudioBus.sys, Win32 error 0n2
\Driver\IntcAudioBusffffa8873b494a80
ffffa88716eccd20 \Driver\ACPI       ffffa887146ee8b0
> ffffa88716e33060 \Driver\pci        ffffa88716e331b0 NTPNP_PCI0018
!DevNode ffffa88716dc58a0 :
DeviceInst is "PCI\VEN_8086&DEV_A0C8&SUBSYS_880D103C&REV_20\3&11583659&0&FB"
ServiceName is "IntcAudioBus"

nt!TRIAGE_9F_POWER

dt nt!TRIAGE_9F_POWER fffff98976ed7118 () Recursive: [ -r1 -r2 -r ] Verbose Normal dt
==================================================================================
Symbol nt!TRIAGE_9F_POWER not found.

IRP

Irp Details: ffffa887405e08e0 [ verbose | !ddt | !irp ]

    Frame Count
    ===========
              7

Irp Stack Frame(s)

      # Driver               Major            Minor Dispatch Routine Flg Ctrl Status Completion Invoker(s) Device           File   Context                Completion Routine         Args
    === ==================== ===== ================ ================ === ==== ======= ====================== ================ ====== ====================== ========================== ===================================================================
      5 \Driver\pci          POWER IRP_MN_WAIT_WAKE IRP_MJ_POWER       0    0 None    None                   ffffa88716e33060 (null) ffffa88740cdaaf0(FOCX) nt!IopUnloadSafeCompletion 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    ->6 \Driver\IntcAudioBus POWER IRP_MN_SET_POWER IRP_MJ_POWER       0   e1 Pending Cancel, Success, Error ffffa8873aee0b30 (null) ffffa8873c3834c0(PFXM) nt!PopRequestCompletion    0000000000000000 0000000000000001 0000000000000001 0000000000000000
kd> dt nt!_TRIAGE_9F_POWER fffff98976ed7118
   +0x000 Signature        : 0x8000
   +0x002 Revision         : 2
   +0x008 IrpList          : 0xfffff802`4ee3d010 _LIST_ENTRY [ 0xffffa887`413ec440 - 0xffffa887`3c3834c0 ]
   +0x010 ThreadList       : 0xfffff802`4ee3a060 _LIST_ENTRY [ 0xfffff989`76e17498 - 0xfffff989`76e1f498 ]
   +0x018 DelayedWorkQueue : 0xffffa887`14725c60 _TRIAGE_EX_WORK_QUEUE
   +0x020 DelayedIoWorkQueue : 0xffffa887`14729c50 _TRIAGE_EX_WORK_QUEUE
!irp ffffa887405e08e0
Irp is active with 7 stacks 6 is current (= 0xffffa887405e0b18)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
     cmd flg cl Device   File     Completion-Context
[N/A(0), N/A(0)]
            0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0 0 ffffa88716e33060 00000000 00000000-00000000
       \Driver\pci
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffa8873aee0b30 00000000 fffff8024e5a5d10-ffffa8873c3834c0 Success Error Cancel pending
       \Driver\IntcAudioBus        nt!PopRequestCompletion
Args: 00000000 00000001 00000001 00000000
[N/A(0), N/A(0)]
            0 0 00000000 00000000 00000000-ffffa8873c3834c0

Args: 00000000 00000000 00000000 00000000
kd> !devstack ffffa88716e33060
!DevObj           !DrvObj            !DevExt           ObjectName
ffffa8873aee0b30 \Driver\IntcAudioBusffffa8873b494a80
ffffa88716eccd20 \Driver\ACPI       ffffa887146ee8b0
> ffffa88716e33060 \Driver\pci        ffffa88716e331b0 NTPNP_PCI0018
!DevNode ffffa88716dc58a0 :
DeviceInst is "PCI\VEN_8086&DEV_A0C8&SUBSYS_880D103C&REV_20\3&11583659&0&FB"
ServiceName is "IntcAudioBus"
kd> !poaction
PopAction: fffff8024ee3c820
State..........: 0 - Idle
Updates........: 0
Action.........: None
Lightest State.: Unspecified
Flags..........: 10000003 QueryApps|UIAllowed
Irp minor......: ??
System State...: Unspecified
Hiber Context..: 0000000000000000

Allocated power irps (PopIrpList - fffff8024ee3d010)
IRP: ffffa8873aecd7d0 (wait-wake/S4), PDO: ffffa88716ed7360
IRP: ffffa88736633650 (wait-wake/S0), PDO: ffffa88716ead360
IRP: ffffa8873c38edc0 (wait-wake/S0), PDO: ffffa88716eb1360
IRP: ffffa8874d0e52b0 (wait-wake/S0), PDO: ffffa88716ec8360
IRP: ffffa8873f7419e0 (wait-wake/S0), PDO: ffffa88744750870
IRP: ffffa88756db16b0 (wait-wake/S0), PDO: ffffa8873b3d4860
IRP: ffffa8875709f7c0 (wait-wake/S0), PDO: ffffa8874470ed30
IRP: ffffa887412bc010 (wait-wake/S0), PDO: ffffa8873aceb300
IRP: ffffa8873bd9da30 (wait-wake/S3), PDO: ffffa8874470ead0
IRP: ffffa88716e99b60 (wait-wake/S0), PDO: ffffa88716ed3360
IRP: ffffa88740f2e6a0 (wait-wake/S0), PDO: ffffa88716ec6360
IRP: ffffa8873a8cb630 (set/D0,), PDO: ffffa8874470ead0, CURRENT: ffffa8874470ead0
IRP: ffffa8873c56c2b0 (set/D0,), PDO: ffffa887405e0690, CURRENT: ffffa887405e0690
IRP: ffffa887405e08e0 (set/D0,), PDO: ffffa88716e33060, CURRENT: ffffa8873aee0b30

Irp worker threads (PopIrpThreadList - fffff8024ee3a060)
THREAD: ffffa88714729200 (static)
THREAD: ffffa887146b1040 (static)

Broadcast in progress: FALSE
Is Directed DRIPS Transition: FALSE

No Device State present
kd> !kic
Machine & Dump Info
============================================
Dump Name: MEMORY_20221202_NB0312.dmp
Windows 10 Kernel Version 22621 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff802`4e200000 PsLoadedModuleList = 0xfffff802`4ee12fe0
Debug session time: Fri Dec 2 14:55:38.917 2022 (UTC + 1:00)
System Uptime: 0 days 7:28:50.688
SystemManufacturer = HP
SystemProductName = HP ZBook Firefly 14 inch G8 Mobile Workstation PC
Processor: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
Bugcheck: 9F (3, FFFFA88716E33060, FFFFF98976ED7118, FFFFA887405E08E0)
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

Description: Bugcheck 0x9F DRIVER_POWER_STATE_FAILURE triage

Device object (ffffa88716e33060) is for:
NTPNP_PCI0018 \Driver\pci DriverObject ffffa887146cf4e0
Current Irp 00000000 RefCount 0 Type 0000001d Flags 00001040
SecurityDescriptor ffffdf856bbbb2e0 DevExt ffffa88716e331b0 DevObjExt ffffa88716e33970 DevNode ffffa88716dc58a0
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffa88716eccd20 \Driver\ACPI
Device queue is not busy.

Device Stack

!DevObj           !DrvObj            !DevExt           ObjectName
ffffa8873aee0b30 \Driver\IntcAudioBusffffa8873b494a80
ffffa88716eccd20 \Driver\ACPI       ffffa887146ee8b0
> ffffa88716e33060 \Driver\pci        ffffa88716e331b0 NTPNP_PCI0018
!DevNode ffffa88716dc58a0 :
DeviceInst is "PCI\VEN_8086&DEV_A0C8&SUBSYS_880D103C&REV_20\3&11583659&0&FB"
ServiceName is "IntcAudioBus"

nt!TRIAGE_9F_POWER

dt nt!TRIAGE_9F_POWER fffff98976ed7118 () Recursive: [ -r1 -r2 -r ] Verbose Normal dt
==================================================================================
Symbol nt!TRIAGE_9F_POWER not found.

IRP

Irp Details: ffffa887405e08e0 [ verbose | !ddt | !irp ]

    Frame Count
    ===========
              7

Irp Stack Frame(s)

      # Driver               Major            Minor Dispatch Routine Flg Ctrl Status Completion Invoker(s) Device           File   Context                Completion Routine         Args
    === ==================== ===== ================ ================ === ==== ======= ====================== ================ ====== ====================== ========================== ===================================================================
      5 \Driver\pci          POWER IRP_MN_WAIT_WAKE IRP_MJ_POWER       0    0 None    None                   ffffa88716e33060 (null) ffffa88740cdaaf0(FOCX) nt!IopUnloadSafeCompletion 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    ->6 \Driver\IntcAudioBus POWER IRP_MN_SET_POWER IRP_MJ_POWER       0   e1 Pending Cancel, Success, Error ffffa8873aee0b30 (null) ffffa8873c3834c0(PFXM) nt!PopRequestCompletion    0000000000000000 0000000000000001 0000000000000001 0000000000000000

Scan for related threads

Rule 92 brought to you by jasone. Please Follow up with the rule owner if you have any questions or comments.
Stats:
Rules Ran: 38 Success: 26 Failed: 0 Skipped: 1
Number of Issues Found: 1
Number of Fishing Rules Found: 0 [Use -v to see output]
Total Number of Rules: 429
Scan Ended: 12/13/2022 4:34:25 PM (00:00:24.9071428)
kd> !kic -v
RunRules Invoked
Starting Rule 27 (MexTestRule - Fires if any dump type has the name mextestdump.dmp)
Finished Rule 27 after (00:00:00.0074011)
Starting Rule 62 (Issue with page table translation on Intel Xeon Processor E5 v2 Product Family)
Finished Rule 62 after (00:00:00.0003855)
Starting Rule 92 (Bugcheck 0x9F DRIVER_POWER_STATE_FAILURE triage)
Finished Rule 92 after (00:00:22.4531827)
Machine & Dump Info
============================================
Dump Name: MEMORY_20221202_NB0312.dmp
Windows 10 Kernel Version 22621 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff802`4e200000 PsLoadedModuleList = 0xfffff802`4ee12fe0
Debug session time: Fri Dec 2 14:55:38.917 2022 (UTC + 1:00)
System Uptime: 0 days 7:28:50.688
SystemManufacturer = HP
SystemProductName = HP ZBook Firefly 14 inch G8 Mobile Workstation PC
Processor: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
Bugcheck: 9F (3, FFFFA88716E33060, FFFFF98976ED7118, FFFFA887405E08E0)
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

Description: Bugcheck 0x9F DRIVER_POWER_STATE_FAILURE triage

Device object (ffffa88716e33060) is for:
NTPNP_PCI0018 \Driver\pci DriverObject ffffa887146cf4e0
Current Irp 00000000 RefCount 0 Type 0000001d Flags 00001040
SecurityDescriptor ffffdf856bbbb2e0 DevExt ffffa88716e331b0 DevObjExt ffffa88716e33970 DevNode ffffa88716dc58a0
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffa88716eccd20 \Driver\ACPI
Device queue is not busy.

Device Stack

!DevObj           !DrvObj            !DevExt           ObjectName
ffffa8873aee0b30 \Driver\IntcAudioBusffffa8873b494a80
ffffa88716eccd20 \Driver\ACPI       ffffa887146ee8b0
> ffffa88716e33060 \Driver\pci        ffffa88716e331b0 NTPNP_PCI0018
!DevNode ffffa88716dc58a0 :
DeviceInst is "PCI\VEN_8086&DEV_A0C8&SUBSYS_880D103C&REV_20\3&11583659&0&FB"
ServiceName is "IntcAudioBus"

nt!TRIAGE_9F_POWER

dt nt!TRIAGE_9F_POWER fffff98976ed7118 () Recursive: [ -r1 -r2 -r ] Verbose Normal dt
==================================================================================
Symbol nt!TRIAGE_9F_POWER not found.

IRP

Irp Details: ffffa887405e08e0 [ verbose | !ddt | !irp ]

    Frame Count
    ===========
              7

Irp Stack Frame(s)

      # Driver               Major            Minor Dispatch Routine Flg Ctrl Status Completion Invoker(s) Device           File   Context                Completion Routine         Args
    === ==================== ===== ================ ================ === ==== ======= ====================== ================ ====== ====================== ========================== ===================================================================
      5 \Driver\pci          POWER IRP_MN_WAIT_WAKE IRP_MJ_POWER       0    0 None    None                   ffffa88716e33060 (null) ffffa88740cdaaf0(FOCX) nt!IopUnloadSafeCompletion 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    ->6 \Driver\IntcAudioBus POWER IRP_MN_SET_POWER IRP_MJ_POWER       0   e1 Pending Cancel, Success, Error ffffa8873aee0b30 (null) ffffa8873c3834c0(PFXM) nt!PopRequestCompletion    0000000000000000 0000000000000001 0000000000000001 0000000000000000

Scan for related threads

Rule 92 brought to you by jasone. Please Follow up with the rule owner if you have any questions or comments.
Starting Rule 101 (Hotfix available: Hyper-V host crashes and has bug checks when you perform a VM live migration in Windows 8.1 and Windows Server 2012 R2)
Not on Windows 8.1 or Windows Server 2012R2. Bailing out of rule.
Finished Rule 101 after (00:00:00.0211476)
Starting Rule 503 (Surface Pro Bug Check 0x9F_3_SETPOWER_UsbHub3_IMAGE_msux64w10.sys)
SystemProductName = HP ZBook Firefly 14 inch G8 Mobile Workstation PC

Not on a Surface device...quiting rule
Finished Rule 503 after (00:00:00.0174318)
Starting Rule 4968 (Bugcheck 0x133 / 0x9f in HDAudBus.sys (HdaController::Isr / HdaController::CodecDpc))
Finished Rule 4968 after (00:00:00.0090290)
Starting Rule 4984 (Failure in usbhub3 hub driver - doesn't complete IOCTL_INTERNAL_USB_ENDPOINTS_CONFIGURE)
Finished Rule 4984 after (00:00:00.0001427)
Starting Rule 6006 (Bug 11938612: Issue where MSISCSI.sys doesn't decrement in a specific code path leading to leaked threads )
Finished Rule 6006 after (00:00:00.0009226)
Starting Rule 7600 (Atom handle table leak issue)
Finished Rule 7600 after (00:00:00.1099188)
Starting Rule 9208 (Servicing: 4B.18: http.sys bugchecks after installing KB4093119 on WinX 10586++ or WS16)
Finished Rule 9208 after (00:00:00.0117409)
Starting Rule 9302 (IO hang caused by Storport Gateway bug.)
Finished Rule 9302 after (00:00:00.8397612)
Starting Rule 9500 (Kernel pool Leak caused by Surface Laptop Intersil Ambient Light Sensor Drive)
Finished Rule 9500 after (00:00:00.2230841)
Starting Rule 9600 (Long wait in SmbCeWaitForCompletionAndFinalizeExchangeEx)
Finished Rule 9600 after (00:00:00.0098794)
Starting Rule 9700 (OS crashes with EXFAT_FILE_SYSTEM (12c) when user renames file/folder on SD card)
Finished Rule 9700 after (00:00:00.0001232)
Starting Rule 9701 (OS crashes with NO_PAGES_AVAILABLE(4D) due to page file space leak in Mm)
Finished Rule 9701 after (00:00:00.0000933)
Starting Rule 9706 (PspSelectNodeForProcess() may cause system bugcheck if PspProcessNodeAssignment is incremented to 0x80000000)
Finished Rule 9706 after (00:00:00.0003548)
Starting Rule 9708 (Bugcheck 0xd1 in msiscsi.sys when receiving high CommandSeqNum from the iSCSI target)
Finished Rule 9708 after (00:00:00.0003038)
Starting Rule 9710 (0x139 BugCheck in srvnet!SrvNetScavengerCloseConnection when receiving and disconnecting NetBT connection)
Finished Rule 9710 after (00:00:00.0000991)
Starting Rule 9711 (Cldflt double releasing ERESOURCE on hydration restart path bugchecks machine)
Finished Rule 9711 after (00:00:00.0000893)
Starting Rule 9904 (Any crash in win32k)
Finished Rule 9904 after (00:00:00.0003966)
Starting Rule 9911 (Please add a Description)
Finished Rule 9911 after (00:00:00.0000936)
Starting Rule 9999 (Dans Rule)
Finished Rule 9999 after (00:00:00.0018687)
Starting Rule 11008 (NET: VMSwitch bugcheck triage)
Finished Rule 11008 after (00:00:00.0011096)
Starting Rule 11009 (NET: Mlx driver code defect causing various BSOD when freeing VMQ or vPORT)
Finished Rule 11009 after (00:00:00.0009658)
Starting Rule 16017 (Code Integrity causes bugcheck processing non NULL terminated unicode string)
Finished Rule 16017 after (00:00:00.0000990)
Starting Rule 16018 (Bugcheck 0x9F in DpiFdoSetAdapterPowerState when dxgkrnl.sys page faults after storage is powered down)
Finished Rule 16018 after (00:00:00.8620615)
Stats:
Rules Ran: 38 Success: 26 Failed: 0 Skipped: 1
Number of Issues Found: 1
Number of Fishing Rules Found: 0 [Use -v to see output]
Total Number of Rules: 429
Scan Ended: 12/13/2022 4:35:22 PM (00:00:24.8382163)

If in the case Intel need assistance from Microsoft, they can get it via TSANet.

I hope somebody can help us.

Thanks in advance

Re:Microsoft Wireless Display Adapter causes BSOD

Alberto_R_Intel — Wed, 22 Feb 2023 20:33:33 GMT

Thomas_123, Thank you for posting in the Intel® Communities Support.

In order for us to provide the most accurate assistance on this scenario, we just wanted to confirm a few details about your system:

What is the model of the Intel® wireless card?

Was the Microsoft Wireless Display Adapter working fine before with those specific laptops that you mentioned?

Did you make any recent hardware/software changes that might cause this issue?

The wireless card, did you purchase them separately or did they come installed on the laptops?

Does the problem happen at home or in the work environment?

Please attach the SSU report of at least one of the laptops in question so we can verify further details about the components in your platform, check all the options in the report including the one that says "3rd party software logs":

https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-?product=91600

Any questions, please let me know.

Regards,

Albert R.

Intel Customer Support Technician

Re: Re:Microsoft Wireless Display Adapter causes BSOD

Thomas_123 — Tue, 28 Feb 2023 08:47:01 GMT

Hello Alberto,

First of all, sorry for my late reply. The topic was marked as spam and couldn`t subscribe on it.

I will take my own laptop as example because that is the easiest and quickest way to get the required information.

The wireless card that is in my laptop, the standard delivered by HP is the Intel(R) Wi-Fi 6 AX201 160MHz.

Before we had no issues at all with the MS Wireless Display Adapter. Not with an single laptop.

We didn`t make any hardware or software changes what is causing the problem. Only the Windows Updates but Microsoft said to us it is not related to MS software.

The problem does happen in a work environment. We didn`t test it yet in a home environment

Please see attached the SSU

Re:Microsoft Wireless Display Adapter causes BSOD

Alberto_R_Intel — Tue, 28 Feb 2023 16:45:32 GMT

Hello Thomas_123, No problem at all, thank you very much for providing that information and the SSU report.

Based on the details shown in the SSU report, we can confirm, as you mentioned, that the wireless driver version currently installed on your computer is 22.170.0.3, provided by HP and that should be the proper driver for your device customized by them:

https://support.hp.com/us-en/drivers/selfservice/hp-zbook-firefly-14-inch-g8-mobile-workstation-pc/2100000206

Even though the Intel® graphics drivers are generic, for testing purposes, not sure if you already try this, please try a clean installation of our latest wireless driver version 22.190.0.4 following the instructions in the links below:

https://www.intel.com/content/www/us/en/download/19351/windows-10-and-windows-11-wi-fi-drivers-for-intel-wireless-adapters.html?wapkw=AX201

https://www.intel.com/content/www/us/en/support/articles/000022173/wireless.html

Also, please make sure that the latest BIOS version is currently installed on your machine. If necessary, you can always get in contact with HP Support to gather the details on how to update it:

https://support.hp.com/us-en

Once you get the chance, please let us know the results.

Regards,

Albert R.

Intel Customer Support Technician

Re: Re:Microsoft Wireless Display Adapter causes BSOD

Thomas_123 — Wed, 01 Mar 2023 12:43:17 GMT

Hello Alberto,

Thanks for your reply.

Me and my colleague have installed the latest version of the BIOS and performed a clean install of the Intel Wireless Adapter without a good result. Both laptops freezed and blue screened afterwards.

The link is now referring to version 22.200.0.6 instead of the version you mentioned.

Please find attached the screenshot of the driver version and the memory dump analyze.

Best Regards,

Thomas

Re:Microsoft Wireless Display Adapter causes BSOD

Alberto_R_Intel — Wed, 01 Mar 2023 15:32:09 GMT

Hello Thomas_123, You are very welcome, thank you very much for letting us know those results.

We are sorry to hear the issue persists after updating the BIOS and installing wireless driver version 22.200.0.6.

We will now do further research on this matter. As soon as I get any updates, I will post all the details on this thread.

Regards,

Albert R.

Intel Customer Support Technician

Re: Re:Microsoft Wireless Display Adapter causes BSOD

Thomas_123 — Thu, 02 Mar 2023 07:56:36 GMT

Hello Alberto,

Thanks for investigating this issue.

Microsoft told us when you/Intel need assistance from them you can contact get it via TSANet.org

Our TrackingID from MS was 2210070040003602

Kind regards,

Thomas

Re:Microsoft Wireless Display Adapter causes BSOD

Alberto_R_Intel — Thu, 09 Mar 2023 20:57:20 GMT

Hello Thomas_123, I just received an update on this matter.

As you can confirm in the link below, wireless display (WIDI)/Miracast is no longer supported by Intel. In this case, the next thing to do will be to get in contact directly with Microsoft Support for further assistance on this topic:

https://www.intel.com/content/www/us/en/support/articles/000021693/emerging-technologies.html

https://support.microsoft.com/en-us

Regards,

Albert R.

Intel Customer Support Technician