npu_kmd.sys stuck the screen util wifi close

[Tom31]

17: kd> !thread ffff8c053bf7b040
THREAD ffff8c053bf7b040  Cid 2de4.341c  Teb: 000000bc76797000 Win32Thread: ffff8c051a5c0830 WAIT: (WrLpcReply) KernelMode Alertable
    ffff8c053bf7b558  Semaphore Limit 0x1
Waiting for reply to ALPC Message ffffc08e358e95d0 : queued at port ffff8c05134c11d0 : owned by process ffff8c053b9c00c0Not impersonating
DeviceMap                 ffffc08e24383d70
Owning Process            ffff8c0536112080       Image:         audiodg.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      945141         Ticks: 4159 (0:00:01:04.984)
Context Switch Count      192            IdealProcessor: 16             
UserTime                  00:00:00.359
KernelTime                00:00:00.375
Win32 Start Address ntdll!TppWorkerThread (0x00007ffa23607d60)
Stack Init fffff6095c11abb0 Current fffff6095c119130
Base fffff6095c11b000 Limit fffff6095c114000 Call 0000000000000000
Priority 21  BasePriority 8  Unusual Boost 15  Priority Floor 21  IoPriority 2  PagePriority 5
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\npu.inf_amd64_2a50686f47615b3f\npu_kmd.sys, Win32 error 0n2
Child-SP          RetAddr               : Args to Child                                                           : Call Site
fffff609`5c119170 fffff801`8a811dca     : 00000000`00000000 00000000`00000001 ffffe201`be9c02f0 fffff609`5c119378 : nt!KiSwapContext+0x76
fffff609`5c1192b0 fffff801`8a810ea0     : ffff8c05`00000000 00000000`00000000 fffff609`5c119488 00000000`00000000 : nt!KiSwapThread+0x59a
fffff609`5c119370 fffff801`8a819544     : 00000000`00000000 ffff8c05`3bf7b180 ffff8c05`00000000 ffff8c05`3bf7b1c6 : nt!KiCommitThreadWait+0x370
fffff609`5c119420 fffff801`8a8eabb7     : ffff8c05`3bf7b558 ffffe201`00000011 ffff8c05`3b8f8100 ffffe201`be9b7101 : nt!KeWaitForSingleObject+0x7a4
fffff609`5c119500 fffff801`8ae890f8     : ffffe201`bea00000 ffff8c05`3bf7b558 00000000`00000011 00000000`00000000 : nt!AlpcpSignalAndWait+0x297
fffff609`5c1195b0 fffff801`8ae88c0d     : 00000000`00000000 00000000`00000000 ffff8c05`134e0630 ffffc08e`257fb000 : nt!AlpcpReceiveSynchronousReply+0x58
fffff609`5c119610 fffff801`8ae232ce     : ffff8c05`134e0630 fffff609`00220000 ffffc08e`257fb000 ffffc08e`308e9190 : nt!AlpcpProcessSynchronousRequest+0x34d
fffff609`5c119740 fffff801`8ac85c55     : fffff609`5c119900 ffff8c05`3bf7b040 fffff609`5c119a38 00000000`00020001 : nt!NtAlpcSendWaitReceivePort+0x1fe
fffff609`5c119810 fffff801`8ac74130     : fffff801`1c4302b6 ffffc08e`257fb000 ffffc08e`308e9120 fffff609`5c119b30 : nt!KiSystemServiceCopyEnd+0x25 (TrapFrame @ fffff609`5c119880)
fffff609`5c119a18 fffff801`1c4302b6     : ffffc08e`257fb000 ffffc08e`308e9120 fffff609`5c119b30 fffff801`1c41eb74 : nt!KiServiceLinkage
fffff609`5c119a20 fffff801`1c42fdd2     : 00000000`00001000 ffffc08e`308e9120 fffff609`5c119cc0 fffff609`5c119b30 : msrpc!LRPC_BASE_CCALL::DoSendReceive+0x72
fffff609`5c119a90 fffff801`1c42e74a     : 00000000`00000000 fffff609`5c119b30 fffff609`5c11a2b9 00000000`00000000 : msrpc!LRPC_BASE_CCALL::SendReceive+0x52
fffff609`5c119ac0 fffff801`1c3f21f4     : fffff609`5c119d70 fffff609`5c119d70 fffff609`5c11a2b9 00000000`00000000 : msrpc!NdrSendReceive+0x3a
fffff609`5c119af0 fffff801`1c3f20a3     : 00000000`00000000 fffff801`1c3d1000 00000000`0000000d fffff609`5c119b20 : msrpc!NdrpClientCall3+0x128
fffff609`5c119d30 fffff801`1c3c1e4f     : fffff609`5c11a258 00000000`00000000 00000000`00000000 ffffc08e`31c8fe80 : msrpc!NdrClientCall3+0x93
fffff609`5c11a0d0 fffff801`1c3c12bd     : 00000000`00000800 fffff801`340befae 00000000`00000000 00000000`00000001 : ksecdd!SspipLookupAccountSid+0x19b
fffff609`5c11a1d0 fffff801`340a8196     : 00000000`00000009 fffff609`5c11a2b9 00000000`00000000 ffffc08e`33042500 : ksecdd!SecLookupAccountSid+0x1d
fffff609`5c11a210 fffff801`340a7be8     : ffff8c05`34e6b000 ffff8c05`34e6b000 ffff8c05`3cdc78b0 ffff8c05`3cdc78b0 : npu_kmd+0x28196
fffff609`5c11a320 fffff801`34083bca     : ffff8c05`34e6b000 fffff609`5c11a520 ffff8c05`3b81b410 ffff8c05`3b81b410 : npu_kmd+0x27be8
fffff609`5c11a3c0 fffff801`1ddb7f96     : ffff8c05`3f87d330 fffff609`5c11a520 ffff8c05`3f87d330 ffff8c05`3b81c000 : npu_kmd+0x3bca
fffff609`5c11a3f0 fffff801`1ddb7bad     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`3a8df533 : dxgkrnl!ADAPTER_RENDER::DdiCreateProcess+0xd6
fffff609`5c11a4d0 fffff801`1ddb7709     : ffffc08e`35f83820 00000000`00000000 00000000`00000000 ffffc08e`2b2a9bc0 : dxgkrnl!DXGPROCESS_RENDER_ADAPTER_INFO::Initialize+0x191
fffff609`5c11a5e0 fffff801`1ddb6dc4     : ffffc08e`35f83820 fffff609`5c11a6e9 00000000`00000008 00000000`00000003 : dxgkrnl!DXGPROCESS::OpenAdapter+0x1f5
fffff609`5c11a660 fffff801`1ddb63ab     : ffffc08e`35f83820 00000000`00000000 ffff8c05`3b81b410 ffffffff`ffffffff : dxgkrnl!DXGDEVICE::Initialize+0x24c
fffff609`5c11a750 fffff801`1ddb5a23     : ffff8c05`3b81a000 fffff609`5c11aaa0 00000272`b59ff510 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::CreateDevice+0x253
fffff609`5c11a7d0 fffff801`1ddb5591     : 00000000`00000000 00000272`b59ff558 00000000`00000000 ffff8c05`3bf7b040 : dxgkrnl!DxgkCreateDeviceImpl+0x483
fffff609`5c11a9f0 fffff801`8ac85c55     : 00000022`6251c500 00000000`00000000 ffff8c05`3bf7b040 00000000`00000000 : dxgkrnl!DxgkCreateDevice+0x11
fffff609`5c11aa20 00007ffa`213d4af4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 (TrapFrame @ fffff609`5c11aa20)
000000bc`768f6888 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32u!NtGdiDdDDICreateDevice+0x14

[ArielP_Intel]

Hello Tom31,

Thank you for posting in Intel Communities! I’m truly sorry to hear that you're experiencing an issue with your screen getting stuck.

To help resolve this, could you kindly provide answers to the following questions:

1. Were there any recent changes made to your system?
2. Could you please provide the Intel System Support Utility logs?
3. Could you specify where this log came from?

These details will assist in troubleshooting the issue more effectively. Thank you for your cooperation and looking forward to hearing from you soon!

Best regards,

Ariel P.

Intel Customer Support Technician

[Tom31]

Hello ArielP,

sorry this discussion was treated as spam last two days. I post another discussion on

https://community.intel.com/t5/Processors/Intel-NPU-Driver-Windows-stuck-the-screen/m-p/1671246#M82101

would you like to trace this problem there.

Best regards,

Tom31.

[ArielP_Intel]

Hello Tom31,

Thank you for your response. Since it seems that you already have an ongoing thread, I will go ahead and close this inquiry. Please refer to your original thread for any further assistance. If you need anything else, don't hesitate to reach out.

Best regards,

Ariel P.

Intel Customer Support Technician