hiho
ich hab seit längeren immer mal wieder Bluescreens. diese tauchen bei zocken programmieren oder einfach bei surfen auf.
Mein System:
phenom 2 x4 965 Be
geforce gtx 468
4 GB DDR2 RAM 800 MHz
GA-MA790X-DS4 (Motherboard)
500 Watt Netzteil
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012411-14960-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03092e50
Debug session time: Mon Jan 24 18:09:08.164 2011 (UTC + 1:00)
System Uptime: 0 days 0:10:52.005
*********************************************************************
* 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, fffffa800562eb30, fffffa800562ee10, fffff800031cf240}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : csrss.exe
Followup: MachineOwner
---------
1: 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: fffffa800562eb30, Terminating object
Arg3: fffffa800562ee10, Process image file name
Arg4: fffff800031cf240, 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 ***
*** ***
*************************************************************************
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: fffffa800562eb30
IMAGE_NAME: csrss.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`038de0e8 fffff800`03252142 : 00000000`000000f4 00000000`00000003 fffffa80`0562eb30 fffffa80`0562ee10 : nt+0x71f00
fffff880`038de0f0 00000000`000000f4 : 00000000`00000003 fffffa80`0562eb30 fffffa80`0562ee10 fffff800`031cf240 : nt+0x3fd142
fffff880`038de0f8 00000000`00000003 : fffffa80`0562eb30 fffffa80`0562ee10 fffff800`031cf240 00000000`024b1900 : 0xf4
fffff880`038de100 fffffa80`0562eb30 : fffffa80`0562ee10 fffff800`031cf240 00000000`024b1900 fffffa80`0562eb30 : 0x3
fffff880`038de108 fffffa80`0562ee10 : fffff800`031cf240 00000000`024b1900 fffffa80`0562eb30 fffff800`031fe269 : 0xfffffa80`0562eb30
fffff880`038de110 fffff800`031cf240 : 00000000`024b1900 fffffa80`0562eb30 fffff800`031fe269 ffffffff`ffffffff : 0xfffffa80`0562ee10
fffff880`038de118 00000000`024b1900 : fffffa80`0562eb30 fffff800`031fe269 ffffffff`ffffffff fffffa80`06338610 : nt+0x37a240
fffff880`038de120 fffffa80`0562eb30 : fffff800`031fe269 ffffffff`ffffffff fffffa80`06338610 fffffa80`0562eb30 : 0x24b1900
fffff880`038de128 fffff800`031fe269 : ffffffff`ffffffff fffffa80`06338610 fffffa80`0562eb30 fffffa80`0562eb30 : 0xfffffa80`0562eb30
fffff880`038de130 ffffffff`ffffffff : fffffa80`06338610 fffffa80`0562eb30 fffffa80`0562eb30 ffffffff`ffffffff : nt+0x3a9269
fffff880`038de138 fffffa80`06338610 : fffffa80`0562eb30 fffffa80`0562eb30 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
fffff880`038de140 fffffa80`0562eb30 : fffffa80`0562eb30 ffffffff`ffffffff 00000000`00000008 fffffa80`0562eb30 : 0xfffffa80`06338610
fffff880`038de148 fffffa80`0562eb30 : ffffffff`ffffffff 00000000`00000008 fffffa80`0562eb30 00000000`c0000006 : 0xfffffa80`0562eb30
fffff880`038de150 ffffffff`ffffffff : 00000000`00000008 fffffa80`0562eb30 00000000`c0000006 fffffa80`06338610 : 0xfffffa80`0562eb30
fffff880`038de158 00000000`00000008 : fffffa80`0562eb30 00000000`c0000006 fffffa80`06338610 fffff800`03182c74 : 0xffffffff`ffffffff
fffff880`038de160 fffffa80`0562eb30 : 00000000`c0000006 fffffa80`06338610 fffff800`03182c74 ffffffff`ffffffff : 0x8
fffff880`038de168 00000000`c0000006 : fffffa80`06338610 fffff800`03182c74 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`0562eb30
fffff880`038de170 fffffa80`06338610 : fffff800`03182c74 ffffffff`ffffffff 00000000`00000001 fffffa80`0562eb30 : 0xc0000006
fffff880`038de178 fffff800`03182c74 : ffffffff`ffffffff 00000000`00000001 fffffa80`0562eb30 fffff6fb`00000008 : 0xfffffa80`06338610
fffff880`038de180 ffffffff`ffffffff : 00000000`00000001 fffffa80`0562eb30 fffff6fb`00000008 00000000`746c6644 : nt+0x32dc74
fffff880`038de188 00000000`00000001 : fffffa80`0562eb30 fffff6fb`00000008 00000000`746c6644 fffff880`038de200 : 0xffffffff`ffffffff
fffff880`038de190 fffffa80`0562eb30 : fffff6fb`00000008 00000000`746c6644 fffff880`038de200 00000000`00000000 : 0x1
fffff880`038de198 fffff6fb`00000008 : 00000000`746c6644 fffff880`038de200 00000000`00000000 00000000`00000000 : 0xfffffa80`0562eb30
fffff880`038de1a0 00000000`746c6644 : fffff880`038de200 00000000`00000000 00000000`00000000 00000000`024b0dd0 : 0xfffff6fb`00000008
fffff880`038de1a8 fffff880`038de200 : 00000000`00000000 00000000`00000000 00000000`024b0dd0 00000000`024b1390 : 0x746c6644
fffff880`038de1b0 00000000`00000000 : 00000000`00000000 00000000`024b0dd0 00000000`024b1390 00000000`0010001f : 0xfffff880`038de200
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner