tobes2003

Hello MSFN I am quite new to working with mini dump files so would really appreciate some help in decifering the following Microsoft ® Windows Debugger Version 6.8.0004.0 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\Tobes\Desktop\Truro Dental\Mini112809-04.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINDOWS\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Sat Nov 28 03:13:43.250 2009 (GMT+0) System Uptime: 0 days 0:02:12.921 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp 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, 8972a860, 8972a9d4, 805d1206} *** WARNING: Unable to verify timestamp for mssmbios.sys 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: 00000003, Process Arg2: 8972a860, Terminating object Arg3: 8972a9d4, Process image file name Arg4: 805d1206, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: 8972a860 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 00000000 PROCESS_NAME: csrss.exe CUSTOMER_CRASH_COUNT: 4 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT BUGCHECK_STR: 0xF4 STACK_TEXT: 9ef03d00 805d03ad 000000f4 00000003 8972a860 nt!_woutput+0x12c 9ef03d24 805d12b1 805d1206 8972a860 8972a9d4 nt!IopAllocateResources+0x276 9ef03d54 8054088c 8972aaa8 c0000005 0069ebcc nt!PopDefaultProcessorPolicy+0x14 9ef03d64 7c90e514 badb0d00 0069eb94 00000000 nt!RtlIpv6StringToAddressA+0x19f WARNING: Frame IP not in any known module. Following frames may be wrong. 9ef03d74 00000000 00000000 00000000 00000000 0x7c90e514 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0xF4_IMAGE_csrss.exe BUCKET_ID: 0xF4_IMAGE_csrss.exe Followup: MachineOwner --------- 1: kd> lmvm csrss start end module name This is happening on a XP SP3 PC 1 year old , will run in safe mode fine. Kind regards Toby