Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041422-8234-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* Windows 10 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff801`19200000 PsLoadedModuleList = 0xfffff801`19e2a230 Debug session time: Thu Apr 14 19:33:17.909 2022 (UTC + 8:00) System Uptime: 0 days 0:14:44.044 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ................................................................ ........... Loading User Symbols Loading unloaded module list ........ ************* Symbol Loading Error Summary ************** Module name Error ntoskrnl The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. For analysis of this file, run !analyze -v nt+0x3f78a0: fffff801`195f78a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`1f691c90=0000000000000133 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff80119efb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KINTERRUPT *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KINTERRUPT *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 77 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 160346 Key : Analysis.Init.CPU.mSec Value: 546 Key : Analysis.Init.Elapsed.mSec Value: 595383 Key : Analysis.Memory.CommitPeak.Mb Value: 50 FILE_IN_CAB: 041422-8234-01.dmp ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. WRONG_SYMBOLS_TIMESTAMP: 6e35293 WRONG_SYMBOLS_SIZE: 1046000 FAULTING_MODULE: fffff80119200000 nt DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80119efb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: fffff801`1f691c88 fffff801`1961fbfa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt+0x3f78a0 fffff801`1f691c90 00000000`00000133 : 00000000`00000000 00000000`00000501 00000000`00000500 fffff801`19efb320 : nt+0x41fbfa fffff801`1f691c98 00000000`00000000 : 00000000`00000501 00000000`00000500 fffff801`19efb320 00000000`00000000 : 0x133 STACK_COMMAND: .cxr; .ecxr ; kb EXCEPTION_CODE_STR: 06E35293 EXCEPTION_STR: WRONG_SYMBOLS PROCESS_NAME: ntoskrnl.wrong.symbols.exe IMAGE_NAME: ntoskrnl.wrong.symbols.exe MODULE_NAME: nt_wrong_symbols SYMBOL_NAME: nt_wrong_symbols!06E352931046000 FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_06E35293_nt_wrong_symbols!06E352931046000 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fdcde62f-4a06-e334-8571-b07043a8b440} Followup: MachineOwner --------- 您好，A&K，前来提供帮助。您提供的信息显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。
我进行驱动更换后还会有蓝屏但不是那么频繁了然后接着上面分析我又进行了分析日志一直在这样循环我也看不懂到底是哪里出了问题0:kd>lmvmnt_wrong_symbolsBrowsefullmoduleliststartendmodulename0:kd>lmDvstartendmodulenameffff8342`2ce00000ffff8342`2d0d3000win32kbase(exportsymbols)win32kbase.sysLoadedsymbolimagefile:win32kbase.sysMappedmemoryimagefile:C:\WINDOWS\system32\win32kbase.sysImagepath:win32kbase.sysImagename:win32kbase.sysBrowseallglobalsymbolsfunctionsdataImagewasbuiltwith/Breproflag.Timestamp:1154BD18(Thisisareproduciblebuildfilehash,notatimestamp)CheckSum:002CC81FImageSize:002D3000Fileversion:10.0.19041.1645Productversion:10.0.19041.1645Fileflags:0(Mask3F)FileOS:40004NTWin32Filetype:3.7DriverFiledate:00000000.00000000Translations:0409.04b0Informationfromresourcetables:CompanyName:MicrosoftCorporationProductName:Microsoft?Windows?OperatingSystemInternalName:win32kbase.sysOriginalFilename:win32kbase.sysProductVersion:10.0.19041.1645FileVersion:10.0.19041.1645(WinBuild.160101.0800)FileDescription:BaseWin32kKernelDriverLegalCopyright:?MicrosoftCorporation.Allrightsreserved.ffff8342`2d0e0000ffff8342`2d496000win32kfull(deferred)Mappedmemoryimagefile:C:\WINDOWS\system32\win32kfull.sysImagepath:win32kfull.sysImagename:win32kfull.sysBrowseallglobalsymbolsfunctionsdataImagewasbuiltwith/Breproflag.Timestamp:E0208948(Thisisareproduciblebuildfilehash,notatimestamp)CheckSum:003B20DEImageSize:003B6000Fileversion:10.0.19041.1645Productversion:10.0.19041.1645Fileflags:0(Mask3F)FileOS:40004NTWin32Filetype:3.7DriverFiledate:00000000.00000000Translations:0409.04b0Informationfromresourcetables:CompanyName:MicrosoftCorporationProductName:Microsoft?Windows?OperatingSystemInternalName:win32kfull.sysOriginalFilename:win32kfull.sysProductVersion:10.0.19041.1645FileVersion:10.0.19041.1645(WinBuild.160101.0800)FileDescription:Full/DesktopWin32kKernelDriverLegalCopyright:?MicrosoftCorporation.Allrightsreserved.ffff8342`2d4f0000ffff8342`2d539000cdd(deferred)Mappedmemoryimagefile:C:\WINDOWS\system32\cdd.dllImagepath:cdd.dllImagename:cdd.dllBrowseallglobalsymbolsfunctionsdataImagewasbuiltwith/Breproflag.Timestamp:679D198D(Thisisareproduciblebuildfilehash,notatimestamp)CheckSum:00048406ImageSize:00049000Fileversion:10.0.19041.1620Productversion:10.0.19041.1620Fileflags:0(Mask3F)FileOS:40004NTWin32Filetype:3.4DriverFiledate:00000000.00000000Translations:0000.04b0Informationfromresourcetables:CompanyName:MicrosoftCorporationProductName:Microsoft?Windows?OperatingSystemInternalName:cdd.dllOriginalFilename:cdd.dllProductVersion:10.0.19041.1620FileVersion:10.0.19041.1620(WinBuild.160101.0800)FileDescription:CanonicalDisplayDriverLegalCopyright:?MicrosoftCorporation.Allrightsreserved.ffff8342`2d680000ffff8342`2d71a000win32k(deferred)Mappedmemoryimagefile:C:\WINDOWS\system32\win32k.sysImagepath:win32k.sysImagename:win32k.sysBrowseallglobalsymbolsfunctionsdataImagewasbuiltwith/Breproflag.Timestamp:0014322E(Thisisareproduciblebuildfilehash,notatimestamp)CheckSum:00095F6AImageSize:0009A000Fileversion:10.0.19041.1645Productversion:10.0.19041.1645Fileflags:0(Mask3F)FileOS:40004NTWin32Filetype:3.7DriverFiledate:00000000.00000000Translations:0409.04b0Informationfromresourcetables:CompanyName:MicrosoftCorporationProductName:Microsoft?Windows?OperatingSystemInternalName:win32k.sysOriginalFilename:win32k.sysProductVersion:10.0.19041.1645FileVersion:10.0.19041.1645(WinBuild.160101.0800)FileDescription:Multi-UserWin32DriverLegalCopyright:?MicrosoftCorporation.Allrightsreserved.fffff800`4a200000fffff800`4a48f000mcupdate(deferred)Imagepath:mcupdate.dllImagename:mcupdate.dllBrowseallglobalsymbolsfunctionsdataTimestamp:*****Invalid(9FB1DE46)CheckSum:0028C60BImageSize:0028F000Translations:0000.04b00000.04e40409.04b00409.04e4Informationfromresourcetables:fffff800`4a490000fffff800`4a496000hal(deferred)Mappedmemoryimagefile:C:\WINDOWS\system32\hal.dllImagepath:hal.dllImagename:hal.dllBrowseallglobalsymbolsfunctionsdataImagewasbuiltwith/Breproflag.Timestamp:1A7BE8E9(Thisisareproduciblebuildfilehash,notatimestamp)CheckSum:0000B5D8ImageSize:00006000Fileversion:10.0.19041.1566Productversion:10.0.19041.1566Fileflags:0(Mask3F)FileOS:40004NTWin32Filetype:2.0DllFiledate:00000000.00000000Translations:0409.04b0Informationfromresourcetables:CompanyName:MicrosoftCorporationProductName:Microsoft?Windows?OperatingSystemInternalName:hal.dllOriginalFilename:hal.dllProductVersion:10.0.19041.1566FileVersion:10.0.19041.1566(WinBuild.160101.0800)FileDescription:HardwareAbstractionLayerDLLLegalCopyright:?MicrosoftCorporation.Allrightsreserved.此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
请您把dump文件用网盘分享给我，我再帮您看一下。
hi，这是我用百度网盘分享的文件~复制这段内容打开「百度网盘」APP即可获取。链接：https://pan.baidu.com/s/1VsxUFyXb7cb798k1DBlm2Q提取码：Y2b3此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您的dump文件显示网络相关的驱动程序出现了问题，导致系统崩溃。建议先卸载网卡驱动程序，然后前往设备制造商官网下载最新版本并重新安装看看。
微信小程序
微信扫一扫体验
投稿
微信公众账号
微信扫一扫加关注
评论 返回
顶部