Blue Screen of Death


(Marjaan) #1

Tak jak w temacie, BSoD mi wyskoczył dziś, i nie wiem co jest tego przyczyną, ściągnełem Debbugera z windows.com

i to wynik:

Microsoft (R) Windows Debugger Version 6.6.0007.5

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820

Debug session time: Sat Aug 18 07:55:48.062 2007 (GMT+2)

System Uptime: 0 days 0:11:06.631

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 2

*** 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, 82d00da0, 82d00f14, 805fa428}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Probably caused by : csrss.exe


Followup: MachineOwner

---------


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: 00000003, Process

Arg2: 82d00da0, Terminating object

Arg3: 82d00f14, Process image file name

Arg4: 805fa428, Explanatory message (ascii)


Debugging Details:

------------------


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


***** Kernel symbols are WRONG. Please fix symbols to do analysis.



MODULE_NAME: csrss


FAULTING_MODULE: 00000000 


DEBUG_FLR_IMAGE_TIMESTAMP: 0


PROCESS_OBJECT: 82d00da0


IMAGE_NAME: csrss.exe


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WRONG_SYMBOLS


BUGCHECK_STR: 0xF4


STACK_TEXT:  

WARNING: Stack unwind information not available. Following frames may be wrong.

f7960520 8062cb19 000000f4 00000003 82d00da0 nt+0x5c736

f7960544 805fa3e6 805fa428 82d00da0 82d00f14 nt+0x155b19

f7960574 804de7ec 82d00fe8 c0000006 f79609b0 nt+0x1233e6

f7960584 804ddae1 badb0d00 f79605fc 001e0178 nt+0x77ec

f79609b0 8050674c f79609d8 00000000 f7960d64 nt+0x6ae1

f7960d34 804e206b 00fef28c 00fef2ac 00000000 nt+0x2f74c

f7960d50 804de7ec 00fef28c 00fef2ac 00000000 nt+0xb06b

f7960d64 7c90eb94 badb0d00 00fef280 00000000 nt+0x77ec

f7960d68 badb0d00 00fef280 00000000 00000000 0x7c90eb94

f7960d6c 00fef280 00000000 00000000 00000000 0xbadb0d00

f7960d70 00000000 00000000 00000000 00000000 0xfef280



STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


BUCKET_ID: WRONG_SYMBOLS


Followup: MachineOwner

---------

czy jest tu jakiś problem ??

bo zbytnio sie na tym nie znam :?

EDIT:

zapomniałem dodać, komp sie strasznie tnie ;/