Apex: Werde ich gleich machen.
@Hitoyoshi: Nein habe ich nicht
habe auch in viele Seiten gelesen, das auch ne SSD der Fehler sein kann.
//Edit
Apex: Habe sie mal geöffnet, dort steht drinne ....
Inhalt anzeigen
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Inhalt anzeigen
Inhalt anzeigen
Inhalt anzeigen
Loading Dump File [C:\Users\Eddy\Desktop\071514-18875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Inhalt anzeigen
Inhalt anzeigen
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff803`86c05000 PsLoadedModuleList = 0xfffff803`86ecf2d0
Debug session time: Tue Jul 15 13:37:42.534 2014 (UTC + 2:00)
System Uptime: 0 days 22:52:12.413
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.................
Inhalt anzeigen
Inhalt anzeigen
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
Inhalt anzeigen
Inhalt anzeigen
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.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Inhalt anzeigen
Inhalt anzeigen
Use !analyze -v to get detailed debugging information.
Inhalt anzeigen
Inhalt anzeigen
BugCheck 133, {0, 501, 500, 0}
Inhalt anzeigen
Inhalt anzeigen
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Inhalt anzeigen
Inhalt anzeigen
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+153fa0 )
Inhalt anzeigen
Inhalt anzeigen
Followup: MachineOwner
---------
Inhalt anzeigen
Inhalt anzeigen
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Inhalt anzeigen
Inhalt anzeigen
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: 0000000000000000
Inhalt anzeigen
Inhalt anzeigen
Debugging Details:
------------------
Inhalt anzeigen
Inhalt anzeigen
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Inhalt anzeigen
Inhalt anzeigen
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Inhalt anzeigen
Inhalt anzeigen
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
Inhalt anzeigen
Inhalt anzeigen
MODULE_NAME: nt
Inhalt anzeigen
Inhalt anzeigen
FAULTING_MODULE: fffff80386c05000 nt
Inhalt anzeigen
Inhalt anzeigen
DEBUG_FLR_IMAGE_TIMESTAMP: 53388e13
Inhalt anzeigen
Inhalt anzeigen
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
Inhalt anzeigen
Inhalt anzeigen
CUSTOMER_CRASH_COUNT: 1
Inhalt anzeigen
Inhalt anzeigen
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
Inhalt anzeigen
Inhalt anzeigen
BUGCHECK_STR: 0x133
Inhalt anzeigen
Inhalt anzeigen
CURRENT_IRQL: 0
Inhalt anzeigen
Inhalt anzeigen
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
Inhalt anzeigen
Inhalt anzeigen
LAST_CONTROL_TRANSFER: from fffff80386d98ad6 to fffff80386d58fa0
Inhalt anzeigen
Inhalt anzeigen
STACK_TEXT:
fffff803`885cbc98 fffff803`86d98ad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt+0x153fa0
fffff803`885cbca0 00000000`00000133 : 00000000`00000000 00000000`00000501 00000000`00000500 00000000`00000000 : nt+0x193ad6
fffff803`885cbca8 00000000`00000000 : 00000000`00000501 00000000`00000500 00000000`00000000 00000000`00000000 : 0x133
Inhalt anzeigen
Inhalt anzeigen
Inhalt anzeigen
STACK_COMMAND: kb
Inhalt anzeigen
Inhalt anzeigen
FOLLOWUP_IP:
nt+153fa0
fffff803`86d58fa0 48894c2408 mov qword ptr [rsp+8],rcx
Inhalt anzeigen
Inhalt anzeigen
SYMBOL_STACK_INDEX: 0
Inhalt anzeigen
Inhalt anzeigen
SYMBOL_NAME: nt+153fa0
Inhalt anzeigen
Inhalt anzeigen
FOLLOWUP_NAME: MachineOwner
Inhalt anzeigen
Inhalt anzeigen
IMAGE_NAME: ntoskrnl.exe
Inhalt anzeigen
Inhalt anzeigen
BUCKET_ID: WRONG_SYMBOLS
Inhalt anzeigen
Inhalt anzeigen
FAILURE_BUCKET_ID: WRONG_SYMBOLS
Inhalt anzeigen
Inhalt anzeigen
ANALYSIS_SOURCE: KM
Inhalt anzeigen
Inhalt anzeigen
FAILURE_ID_HASH_STRING: km:wrong_symbols
Inhalt anzeigen
Inhalt anzeigen
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Inhalt anzeigen
Inhalt anzeigen
Followup: MachineOwner
---------
Inhalt anzeigen
Inhalt anzeigen