Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\082414-24008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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
*** 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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`032576d0
Debug session time: Sun Aug 24 13:55:20.927 2014 (GMT+2)
System Uptime: 0 days 0:57:30.082
*********************************************************************
* 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
*** 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 F4, {3, fffffa8005fb2b30, fffffa8005fb2e10, fffff8000338e7b0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : csrss.exe
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005fb2b30, Terminating object
Arg3: fffffa8005fb2e10, Process image file name
Arg4: fffff8000338e7b0, Explanatory message (ascii)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
DEBUG_FLR_IMAGE_TIMESTAMP: 0
PROCESS_OBJECT: fffffa8005fb2b30
IMAGE_NAME: csrss.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02ba00a8 fffff800`03417ab2 : 00000000`000000f4 00000000`00000003 fffffa80`05fb2b30 fffffa80`05fb2e10 : nt+0x75bc0
fffff880`02ba00b0 00000000`000000f4 : 00000000`00000003 fffffa80`05fb2b30 fffffa80`05fb2e10 fffff800`0338e7b0 : nt+0x403ab2
fffff880`02ba00b8 00000000`00000003 : fffffa80`05fb2b30 fffffa80`05fb2e10 fffff800`0338e7b0 00000000`00000086 : 0xf4
fffff880`02ba00c0 fffffa80`05fb2b30 : fffffa80`05fb2e10 fffff800`0338e7b0 00000000`00000086 fffffa80`05fb2b30 : 0x3
fffff880`02ba00c8 fffffa80`05fb2e10 : fffff800`0338e7b0 00000000`00000086 fffffa80`05fb2b30 fffff800`033c2abb : 0xfffffa80`05fb2b30
fffff880`02ba00d0 fffff800`0338e7b0 : 00000000`00000086 fffffa80`05fb2b30 fffff800`033c2abb ffffffff`ffffffff : 0xfffffa80`05fb2e10
fffff880`02ba00d8 00000000`00000086 : fffffa80`05fb2b30 fffff800`033c2abb ffffffff`ffffffff fffffa80`0603a8e0 : nt+0x37a7b0
fffff880`02ba00e0 fffffa80`05fb2b30 : fffff800`033c2abb ffffffff`ffffffff fffffa80`0603a8e0 fffffa80`05fb2b30 : 0x86
fffff880`02ba00e8 fffff800`033c2abb : ffffffff`ffffffff fffffa80`0603a8e0 fffffa80`05fb2b30 fffffa80`05fb2b30 : 0xfffffa80`05fb2b30
fffff880`02ba00f0 ffffffff`ffffffff : fffffa80`0603a8e0 fffffa80`05fb2b30 fffffa80`05fb2b30 ffffffff`ffffffff : nt+0x3aeabb
fffff880`02ba00f8 fffffa80`0603a8e0 : fffffa80`05fb2b30 fffffa80`05fb2b30 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
fffff880`02ba0100 fffffa80`05fb2b30 : fffffa80`05fb2b30 ffffffff`ffffffff 00000000`00000008 fffffa80`05fb2b30 : 0xfffffa80`0603a8e0
fffff880`02ba0108 fffffa80`05fb2b30 : ffffffff`ffffffff 00000000`00000008 fffffa80`05fb2b30 00000000`c0000005 : 0xfffffa80`05fb2b30
fffff880`02ba0110 ffffffff`ffffffff : 00000000`00000008 fffffa80`05fb2b30 00000000`c0000005 fffffa80`0603a8e0 : 0xfffffa80`05fb2b30
fffff880`02ba0118 00000000`00000008 : fffffa80`05fb2b30 00000000`c0000005 fffffa80`0603a8e0 fffff800`03342674 : 0xffffffff`ffffffff
fffff880`02ba0120 fffffa80`05fb2b30 : 00000000`c0000005 fffffa80`0603a8e0 fffff800`03342674 ffffffff`ffffffff : 0x8
fffff880`02ba0128 00000000`c0000005 : fffffa80`0603a8e0 fffff800`03342674 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`05fb2b30
fffff880`02ba0130 fffffa80`0603a8e0 : fffff800`03342674 ffffffff`ffffffff 00000000`00000001 fffffa80`05fb2b30 : 0xc0000005
fffff880`02ba0138 fffff800`03342674 : ffffffff`ffffffff 00000000`00000001 fffffa80`05fb2b30 00000000`00000008 : 0xfffffa80`0603a8e0
fffff880`02ba0140 ffffffff`ffffffff : 00000000`00000001 fffffa80`05fb2b30 00000000`00000008 ffffffff`746c6644 : nt+0x32e674
fffff880`02ba0148 00000000`00000001 : fffffa80`05fb2b30 00000000`00000008 ffffffff`746c6644 fffff880`02ba01c0 : 0xffffffff`ffffffff
fffff880`02ba0150 fffffa80`05fb2b30 : 00000000`00000008 ffffffff`746c6644 fffff880`02ba01c0 00000000`00000000 : 0x1
fffff880`02ba0158 00000000`00000008 : ffffffff`746c6644 fffff880`02ba01c0 00000000`00000000 00000000`00000000 : 0xfffffa80`05fb2b30
fffff880`02ba0160 ffffffff`746c6644 : fffff880`02ba01c0 00000000`00000000 00000000`00000000 00000000`00fc1000 : 0x8
fffff880`02ba0168 fffff880`02ba01c0 : 00000000`00000000 00000000`00000000 00000000`00fc1000 00000000`00fc0a40 : 0xffffffff`746c6644
fffff880`02ba0170 00000000`00000000 : 00000000`00000000 00000000`00fc1000 00000000`00fc0a40 00000000`0010001f : 0xfffff880`02ba01c0
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> !process fffffa8005fb2b30 3
GetPointerFromAddress: unable to read from fffff800032c1000
NT symbols are incorrect, please fix symbols
0: kd> lmvm csrss
start end module name
-- 24 sie 2014, 14:44 --
[quote="DanielGG"]Witam panowie pomóżcie. Dzisiaj rano po włączeniu komputera zauważyłem pewne problemy mianowicie podczas korzystania nagle usłyszałem w komputerze jakieś dziwne dźwięki po których komputer stawał i wywaliło blue screen. Próbowałem odczytać co leży w komputerze, ale nie mogę sobie sam z tym poradzić. Tylko nie wiem jak tu mogę wrzucić notatnik z odczytem
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\082414-24008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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
*** 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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`032576d0
Debug session time: Sun Aug 24 13:55:20.927 2014 (GMT+2)
System Uptime: 0 days 0:57:30.082
*********************************************************************
* 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
*** 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 F4, {3, fffffa8005fb2b30, fffffa8005fb2e10, fffff8000338e7b0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : csrss.exe
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005fb2b30, Terminating object
Arg3: fffffa8005fb2e10, Process image file name
Arg4: fffff8000338e7b0, Explanatory message (ascii)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
DEBUG_FLR_IMAGE_TIMESTAMP: 0
PROCESS_OBJECT: fffffa8005fb2b30
IMAGE_NAME: csrss.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02ba00a8 fffff800`03417ab2 : 00000000`000000f4 00000000`00000003 fffffa80`05fb2b30 fffffa80`05fb2e10 : nt+0x75bc0
fffff880`02ba00b0 00000000`000000f4 : 00000000`00000003 fffffa80`05fb2b30 fffffa80`05fb2e10 fffff800`0338e7b0 : nt+0x403ab2
fffff880`02ba00b8 00000000`00000003 : fffffa80`05fb2b30 fffffa80`05fb2e10 fffff800`0338e7b0 00000000`00000086 : 0xf4
fffff880`02ba00c0 fffffa80`05fb2b30 : fffffa80`05fb2e10 fffff800`0338e7b0 00000000`00000086 fffffa80`05fb2b30 : 0x3
fffff880`02ba00c8 fffffa80`05fb2e10 : fffff800`0338e7b0 00000000`00000086 fffffa80`05fb2b30 fffff800`033c2abb : 0xfffffa80`05fb2b30
fffff880`02ba00d0 fffff800`0338e7b0 : 00000000`00000086 fffffa80`05fb2b30 fffff800`033c2abb ffffffff`ffffffff : 0xfffffa80`05fb2e10
fffff880`02ba00d8 00000000`00000086 : fffffa80`05fb2b30 fffff800`033c2abb ffffffff`ffffffff fffffa80`0603a8e0 : nt+0x37a7b0
fffff880`02ba00e0 fffffa80`05fb2b30 : fffff800`033c2abb ffffffff`ffffffff fffffa80`0603a8e0 fffffa80`05fb2b30 : 0x86
fffff880`02ba00e8 fffff800`033c2abb : ffffffff`ffffffff fffffa80`0603a8e0 fffffa80`05fb2b30 fffffa80`05fb2b30 : 0xfffffa80`05fb2b30
fffff880`02ba00f0 ffffffff`ffffffff : fffffa80`0603a8e0 fffffa80`05fb2b30 fffffa80`05fb2b30 ffffffff`ffffffff : nt+0x3aeabb
fffff880`02ba00f8 fffffa80`0603a8e0 : fffffa80`05fb2b30 fffffa80`05fb2b30 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
fffff880`02ba0100 fffffa80`05fb2b30 : fffffa80`05fb2b30 ffffffff`ffffffff 00000000`00000008 fffffa80`05fb2b30 : 0xfffffa80`0603a8e0
fffff880`02ba0108 fffffa80`05fb2b30 : ffffffff`ffffffff 00000000`00000008 fffffa80`05fb2b30 00000000`c0000005 : 0xfffffa80`05fb2b30
fffff880`02ba0110 ffffffff`ffffffff : 00000000`00000008 fffffa80`05fb2b30 00000000`c0000005 fffffa80`0603a8e0 : 0xfffffa80`05fb2b30
fffff880`02ba0118 00000000`00000008 : fffffa80`05fb2b30 00000000`c0000005 fffffa80`0603a8e0 fffff800`03342674 : 0xffffffff`ffffffff
fffff880`02ba0120 fffffa80`05fb2b30 : 00000000`c0000005 fffffa80`0603a8e0 fffff800`03342674 ffffffff`ffffffff : 0x8
fffff880`02ba0128 00000000`c0000005 : fffffa80`0603a8e0 fffff800`03342674 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`05fb2b30
fffff880`02ba0130 fffffa80`0603a8e0 : fffff800`03342674 ffffffff`ffffffff 00000000`00000001 fffffa80`05fb2b30 : 0xc0000005
fffff880`02ba0138 fffff800`03342674 : ffffffff`ffffffff 00000000`00000001 fffffa80`05fb2b30 00000000`00000008 : 0xfffffa80`0603a8e0
fffff880`02ba0140 ffffffff`ffffffff : 00000000`00000001 fffffa80`05fb2b30 00000000`00000008 ffffffff`746c6644 : nt+0x32e674
fffff880`02ba0148 00000000`00000001 : fffffa80`05fb2b30 00000000`00000008 ffffffff`746c6644 fffff880`02ba01c0 : 0xffffffff`ffffffff
fffff880`02ba0150 fffffa80`05fb2b30 : 00000000`00000008 ffffffff`746c6644 fffff880`02ba01c0 00000000`00000000 : 0x1
fffff880`02ba0158 00000000`00000008 : ffffffff`746c6644 fffff880`02ba01c0 00000000`00000000 00000000`00000000 : 0xfffffa80`05fb2b30
fffff880`02ba0160 ffffffff`746c6644 : fffff880`02ba01c0 00000000`00000000 00000000`00000000 00000000`00fc1000 : 0x8
fffff880`02ba0168 fffff880`02ba01c0 : 00000000`00000000 00000000`00000000 00000000`00fc1000 00000000`00fc0a40 : 0xffffffff`746c6644
fffff880`02ba0170 00000000`00000000 : 00000000`00000000 00000000`00fc1000 00000000`00fc0a40 00000000`0010001f : 0xfffff880`02ba01c0
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> !process fffffa8005fb2b30 3
GetPointerFromAddress: unable to read from fffff800032c1000
NT symbols are incorrect, please fix symbols
0: kd> lmvm csrss
start end module name
-- 24 sie 2014, 14:45 --
