WIN7 藍屏!提示netmsvc.sys。請問怎樣解決!
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\onedrive\瀝盟\藍屏\leicheng雷\Minidump-leicheng雷\070417-5241-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`04065000 PsLoadedModuleList = 0xfffff800`042a7750
Debug session time: Tue Jul 4 09:59:53.890 2017 (UTC + 8:00)
System Uptime: 0 days 0:09:07.264
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {d1afb0c, 2, 0, fffff880042fb831}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\drivers\netmsvc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netmsvc.sys
*** ERROR: Module load completed but symbols could not be loaded for netmsvc.sys
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Probably caused by : netmsvc.sys ( netmsvc+7831 )
Followup: MachineOwner
---------
最後更新:2017-07-04 11:01:38
上一篇:
win 10 16232 藍屏
下一篇:
windows 係統服務都顯示未安裝,不知到怎麼搞的
你的設備已過期,並缺少重要的安全和質量更新,因此存在風險。讓我們帶你重回正軌,這樣
Microsoft store 無法聯網,顯示Microsoft Store需要聯網,你似乎沒有聯網
設備以遷移 由於僅部分匹配或匹配不明確,因此無法遷移設備
由於在創建轉儲期間出錯,創建轉儲文件失敗。
發生臨時 DNS 錯誤
應用商店,在我們這邊發生問題,無法使你登陸,錯誤代碼: 0xD000000D
照相機不可用,錯誤代碼:0xA00F4244(0xC00DABE0)
應用商店打開異常提示“清單中指定了未知的布局”
自定義掃描Windows defender裏麵的設備性能和運行狀況 黃色感歎號問題
windows預口體驗成員內口版本遇到問題需要重啟
熱門內容
windows10 點開此電腦後,有兩個顯示硬盤盤符的目錄是怎麼回事?
windows 10 專業版無法下載中文語言包
KB4056892
win10不能共享文件夾
在Surfacebook上用Windows to go 1703版本,更新後重啟藍屏,無法進入係統
windows10 1709版本更新失敗,錯誤0x8007001f
microdoft visual c++ 2015 redistributable
WIN10 Insider Preview 17025更新失敗,錯誤代碼0x80096004
計算機管理服務 出現一個內部錯誤(INVALID
關於控製麵板中的安全和維護內提示Windows defender 防病毒已關閉的問題