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

蓝屏代码thread stuck in device driver

elitebook 845G7
Microsoft Windows 10 (64-bit)

应该是小问题蓝屏,只是反馈给工程师而已,可能是驱动问题,我没有使用过任何第三方的驱动工具,确保驱动都是原版官方的,而且没有运行什么大型程序,就是正常谷歌浏览器上网突然报错。不过恢复也很快,从蓝屏创建日志到重启再进入系统没超过1分钟,还好我及时记下了代码thread stuck in device driver

 

日志如下

——————————————————————

日志名称: System
来源: EventLog
日期: 2020/9/13 11:40:39
事件 ID: 6008
任务类别: 无
级别: 错误
关键字: 经典
用户: 暂缺
计算机: DESKTOP-HB2SUEJ
描述:
上一次系统的 19:24:11 在 ‎2020/‎9/‎12 上的关闭是意外的。
事件 Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-09-13T03:40:39.3557506Z" />
<EventRecordID>12089</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DESKTOP-HB2SUEJ</Computer>
<Security />
</System>
<EventData>
<Data>19:24:11</Data>
<Data>‎2020/‎9/‎12</Data>
<Data>
</Data>
<Data>
</Data>
<Data>10</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E407090006000C00130018000B00D203E407090006000C000B0018000B00D2033C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>


DLOGFILE00010000DUMP?
Dump stack initialized at UTC: 2020/09/13 03:39:58, local time: 2020/09/13 11:39:58.
Starting get secondary dump callbacks size.
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 1188292372, Secondary Dump Size: 2225940.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Dumping physical memory to disk: 0%
Dumping physical memory to disk: 5%
Dumping physical memory to disk: 10%
Dumping physical memory to disk: 15%
Dumping physical memory to disk: 20%
Dumping physical memory to disk: 25%
Dumping physical memory to disk: 30%
Dumping physical memory to disk: 35%
Dumping physical memory to disk: 40%
Dumping physical memory to disk: 45%
Dumping physical memory to disk: 50%
Dumping physical memory to disk: 55%
Dumping physical memory to disk: 60%
Dumping physical memory to disk: 65%
Dumping physical memory to disk: 70%
Dumping physical memory to disk: 75%
Dumping physical memory to disk: 80%
Dumping physical memory to disk: 85%
Dumping physical memory to disk: 90%
Dumping physical memory to disk: 95%
Dumping physical memory to disk: 100%
Finish write of bitmap dump data. Total pages:289435 Pages written:289435
Starting invoking secondary dump callbacks.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling TRIAGEDUMPDATA secondary callback.
Return from TRIAGEDUMPDATA secondary callback.
Writing TRIAGEDUMPDATA secondary callback data.
Writing TRIAGEDUMPDATA secondary callback data done.
Calling CRASHDUMP secondary callback.
Return from CRASHDUMP secondary callback.
Writing CRASHDUMP secondary callback data.
Writing CRASHDUMP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling ibtusb secondary callback.
Return from ibtusb secondary callback.
Writing ibtusb secondary callback data.
Writing ibtusb 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 amdacpbus secondary callback.
Return from amdacpbus secondary callback.
Writing amdacpbus secondary callback data.
Writing amdacpbus 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 \Device\DxgKrnl secondary callback.
Return from \Device\DxgKrnl secondary callback.
Writing \Device\DxgKrnl secondary callback data.
Writing \Device\DxgKrnl 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 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 secondary multi-part dump callbacks.
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.
Finish invoking secondary dump callbacks.
Starting invoking dump complete callbacks.
Finish invoking dump complete callbacks.
Dump completed successfully.

2 条回复2
教务长 教务长
教务长
31,671 27,312 2,264 3,071
2个帖子(共 3 条)
标记帖子

蓝屏代码thread stuck in device driver

做硬件诊断,开机F2进入-系统测试-全面测试-循环运行直到出现错误

HP 电脑 - 硬件故障测试

https://support.hp.com/cn-zh/document/c03561731


欢迎来到社区,我是一名志愿者,私人信息不会被回复。
如果我的回复对您有帮助, 请点击按钮。如果我的回复帮助您解决了问题,别忘了点击,可以帮到其他遇到同样问题的用户。


我长期使用过的机型
DC7600 USDT
Pavilion dv4000
ProBook 6510b
xw4600
z800
z820
EliteBook 2740p
ProBook 6460b
Pavilion DV4
Envy 15
SlateBook x2
ProDesk 600 G3 SFF
t5740 Thin Client
t620 Thin Client
EliteBook 840 G3
ZBook 15 G3
ProBook 440 G8
Omen 25L GT12 AMD
这条回复对您有帮助吗? 没有
学生
学生
1 1 0 0
3个帖子(共 3 条)
标记帖子

蓝屏代码thread stuck in device driver

那可以删除这个日志文件吗

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