取消
显示结果 
搜索替代 
您的意思是: 
高才生
高才生
4 1 0 0
1个帖子(共 4 条)
72 次查看
标记帖子

暗影精灵 Max 2025 这类带有混合显卡关机时出现长时间等待并最后出现异常关机的情况

OMEN MAX 16 inch Gaming Laptop PC 16-ah0000 (A4NP1AV)
Microsoft Windows 11
机型:HP [OMEN MAX 16 inch Gaming Laptop PC 16-ah0000 (A4NP1AV)]Intel 集显 + NVIDIA 独显)
Windows 版本:[Windows 11 25H2]
驱动:NVIDIA 驱动 [版本号](已更新至最新),Intel GPU 驱动 [版本号]HP OEM
问题复现步骤:
1. 使用 WSL(即使不在 WSL 中实际用 GPU,wsl 中能运行 nvidia-smi)
2. 在 Windows 上运行 Ollama,默认使用独显进行模型推理
3. 退出 Ollama,随后执行关机(或直接关机)
现象:关机耗时极长(系统生成 dump),有时出现 DRIVER_POWER_STATE_FAILURE (0x9F)
已尝试过的措施:
- 更新 Intel / NVIDIA 驱动(均为最新)
- 关闭 Fast Startup
- 从开机到关机整个使用电脑过程中如果使用过 WSL 环境或者 Ollama 做了基本 GPU 的模型推理加速该问题必现
我希望 HP 能协助:
- 是否有 HP 官方针对混显 + WSL GPU 的已知兼容性补丁或 BIOS/EC 版本?
- 是否有推荐的 Intel OEM 驱动版本或与 NVIDIA 的配对建议?
- 是否能协助分析我的 minidump(以下内容为关机前的日志)



DLOGFILE00010000DUMP

"          

Dump stack initialized at UTC: 2025/11/23 15:40:41, local time: 2025/11/23 23:40:41.

#BugCheckCode 0x000000000000009F

#BugCheckP1 0x0000000000000003

#BugCheckP2 0xFFFFBD0C5E569360

#BugCheckP3 0xFFFFB78505D8F5C0

#BugCheckP4 0xFFFFBD0C6C7A0A20

Progress 0x00000042

Elapsed BugCheck duration 00001519ms

Starting get secondary dump callbacks size.

Progress 0x00000052

Finish get secondary dump callbacks size.

Dump Type: 4, Total Dump Size: 9760038, Secondary Dump Size: 9510182.

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 00003201ms

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 npu_kmd secondary callback.

Return from npu_kmd secondary callback.

Writing npu_kmd secondary callback data.

Writing npu_kmd secondary callback data done.

Calling igdkmdn64.sys secondary callback.

Return from igdkmdn64.sys secondary callback.

Writing igdkmdn64.sys secondary callback data.

Writing igdkmdn64.sys 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 Usb4DeviceRouter secondary callback.

Return from Usb4DeviceRouter secondary callback.

Writing Usb4DeviceRouter secondary callback data.

Writing Usb4DeviceRouter secondary callback data done.

Calling Usb4DeviceRouter secondary callback.

Return from Usb4DeviceRouter secondary callback.

Writing Usb4DeviceRouter secondary callback data.

Writing Usb4DeviceRouter secondary callback data done.

Calling Usb4DeviceRouter secondary callback.

Return from Usb4DeviceRouter secondary callback.

Writing Usb4DeviceRouter secondary callback data.

Writing Usb4DeviceRouter secondary callback data done.

Calling Usb4DeviceRouter secondary callback.

Return from Usb4DeviceRouter secondary callback.

Writing Usb4DeviceRouter secondary callback data.

Writing Usb4DeviceRouter secondary callback data done.

Calling Usb4DeviceRouter secondary callback.

Return from Usb4DeviceRouter secondary callback.

Writing Usb4DeviceRouter secondary callback data.

Writing Usb4DeviceRouter secondary callback data done.

Calling Usb4DeviceRouter secondary callback.

Return from Usb4DeviceRouter secondary callback.

Writing Usb4DeviceRouter secondary callback data.

Writing Usb4DeviceRouter 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 Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Usb4HostRouter secondary callback.

Return from Usb4HostRouter secondary callback.

Writing Usb4HostRouter secondary callback data.

Writing Usb4HostRouter secondary callback data done.

Calling Netwaw18 secondary callback.

Return from Netwaw18 secondary callback.

Writing Netwaw18 secondary callback data.

Writing Netwaw18 secondary callback data done.

Calling nvlddmkm.sys secondary callback.

Return from nvlddmkm.sys secondary callback.

Writing nvlddmkm.sys secondary callback data.

Writing nvlddmkm.sys 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 - UsoCommit secondary callback.

Return from blackbox - UsoCommit secondary callback.

Writing blackbox - UsoCommit secondary callback data.

Writing blackbox - UsoCommit secondary callback data done.

Calling blackbox - CrashedProcess secondary callback.

Return from blackbox - CrashedProcess secondary callback.

Writing blackbox - CrashedProcess secondary callback data.

Writing blackbox - CrashedProcess 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 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/11/23 15:40:41, local time: 2025/11/23 23:40:41.

Elapsed BugCheck duration 00003722ms

Progress 0x00000053

Dump completed successfully.
3 条回复3
杰出教授 杰出教授
杰出教授
2,934 2,922 247 304
2个帖子(共 4 条)
标记帖子

暗影精灵 Max 2025 这类带有混合显卡关机时出现长时间等待并最后出现异常关机的情况

没听说过这种情况

在纯独显直连(非手动指定显卡运行程序)状态下运行Ollama工具可立即复现的话

是否有搜索过其他软件用户有遇到过类似情况?

 

退出软件后建议观察任务管理器,确认与之对应的程序完全退出

也可以尝试下退出软件后用Mem Reduct清理,捎带进程占用恢复平缓再关机

 

社区沟通有限,复杂问题包含日志分析请联系售后工程师对话反馈

微信人工

 

 



-------------------------------------------------------------------------------
我是一名社区志愿者,帮助大家解惑答疑。
回帖仅为我个人言论,不代表惠普官方。
惠普人工 I自助服务 I重置系统 I查询服务中心 I
硬件诊断 I商用驱动(HPIA) I更新电脑BIOS I商用系统恢复 I
重装OGH软件 I重装显卡驱动 I下载官方驱动 I重装系统 I
温度过高 I 显卡高性能I 分析蓝屏 I无畏契约/三角洲虚拟化未开启


如果我的回复对您有帮助, 请点击按钮。如果我的回复帮助您解决了问题,别忘了点击,可以帮到其他遇到同样问题的用户。

这条回复对您有帮助吗? 没有
高才生
作者
高才生
4 1 0 0
3个帖子(共 4 条)
标记帖子

暗影精灵 Max 2025 这类带有混合显卡关机时出现长时间等待并最后出现异常关机的情况

感谢您的回复,这个问题从今年 618 买这款电脑到现在一直存在,最开始关机慢以为是某个进程一直卡住所以导致关机慢,但后来发现在重新开机后会在 C 盘根目录生成一个 log 文件,内容就是我贴出来的,我把 log 内容给到 GPT 做解读,GPT 高度怀疑是显卡驱动导致,由于我日常使用雷电 4 的视频线接 type-c 来使用外接显示器,桌面环境默认使用核显,只有在玩游戏时会自动切到独显,玩游戏并不会触发这个问题,也是很偶然的情况我发现了和使用 WSL环境或 Ollama做基于 GPU 的模型推理加速会导致该问题。

还有一个线索,当我在 bios 中或者在 omen 的应用中禁用其中一个 GPU(不论是禁用核显还是独显),似乎这个问题就没有了,这个也印证了 GPT 的解读,问题的原因可能和 Nvidia 的 Optimus技术有关。但玩游戏的时候其实也是借助该技术做的 GPU 切换但并没有这个问题。

这条回复对您有帮助吗? 没有
杰出教授 杰出教授
杰出教授
2,934 2,922 247 304
4个帖子(共 4 条)
标记帖子

暗影精灵 Max 2025 这类带有混合显卡关机时出现长时间等待并最后出现异常关机的情况

BIOS中显卡切换,相较于系统软切换,理论上稳定性会高一些

既然独显直连可以使用,那么可以保持直连状态/也建议使用HDMI线尝试

 

第三方软件我建议到软件客服处咨询是否有类似的问题反馈

收集完善信息后,联系官方技术客服反馈



-------------------------------------------------------------------------------
我是一名社区志愿者,帮助大家解惑答疑。
回帖仅为我个人言论,不代表惠普官方。
惠普人工 I自助服务 I重置系统 I查询服务中心 I
硬件诊断 I商用驱动(HPIA) I更新电脑BIOS I商用系统恢复 I
重装OGH软件 I重装显卡驱动 I下载官方驱动 I重装系统 I
温度过高 I 显卡高性能I 分析蓝屏 I无畏契约/三角洲虚拟化未开启


如果我的回复对您有帮助, 请点击按钮。如果我的回复帮助您解决了问题,别忘了点击,可以帮到其他遇到同样问题的用户。

这条回复对您有帮助吗? 没有
† 惠普支持社区是一个客户交流平台,便于客户找到有效的解决方法,快速解决问题,充分利用惠普产品。请在发帖之前,阅读社区的使用条款注册须知。