The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x00000003, 0x85faea20, 0x85faeb94, 0x80604498). A dump was saved in: C:\WINDOWS\Minidump\Mini020706-11.dmp. Now this is my first time using WinDbg 6.6 - and I think I have done everything right up till now... when I open the dump file this is what WinDbg comes up with.... Maybe someone here can give me some more info? I'm not sure why it comes up Unable to verify timestamp, nor why it says "Probably caused by : csrss.exe" The good thing is, is that I can reproduce the error that causes the system crash, it happens every time I open a .mov (quicktime) file that I have saved on my computer. So I'm thinking that if I save a more detailed dump file that will give me more info on exactly what is causing it? Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini020706-11.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 2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Tue Feb 7 21:24:11.984 2006 (GMT-5) System Uptime: 0 days 1:26:14.944 Unable to load image ntoskrnl.exe, Win32 error 2 *** 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, 85faea20, 85faeb94, 80604498} 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: 00000003, Process Arg2: 85faea20, Terminating object Arg3: 85faeb94, Process image file name Arg4: 80604498, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: 85faea20 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 00000000 CUSTOMER_CRASH_COUNT: 11 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT BUGCHECK_STR: 0xF4 PROCESS_NAME: csrss.exe STACK_TEXT: f7931520 80633f32 000000f4 00000003 85faea20 nt!MiRemoveUnusedSegments+0x637 f7931544 80604456 80604498 85faea20 85faeb94 nt!RtlDescribeChunkNS+0x3 f7931544 80604456 80604498 85faea20 85faeb94 nt!WmiTraceThread+0x70 f7931574 804dd98f 85faec68 c0000006 f79319b0 nt!WmiTraceThread+0x70 f7931584 804e4697 badb0d00 f79315fc 000c0000 nt!ZwQueryEvent+0x4 f7931584 804e4697 badb0d00 f79315fc 000c0000 nt!KiInsertQueue+0x57 f79319b0 80517e25 f79319d8 00000000 f7931d64 nt!KiInsertQueue+0x57 f7931d34 804e1298 0052fbe8 0052fc08 00000000 nt!PopPromoteFromIdle0+0x49 f7931d50 804dd98f 0052fbe8 0052fc08 00000000 nt!Dr_kitb_a+0x7f f7931d54 0052fbe8 0052fc08 00000000 0052fff4 nt!ZwQueryEvent+0x4 WARNING: Frame IP not in any known module. Following frames may be wrong. f7931d64 7c90eb94 badb0d00 0052fbdc ffffffff 0x52fbe8 f7931d68 badb0d00 0052fbdc ffffffff 00000001 0x7c90eb94 f7931d6c 0052fbdc ffffffff 00000001 00000000 0xbadb0d00 f7931d70 ffffffff 00000001 00000000 00000000 0x52fbdc f7931d74 00000000 00000000 00000000 00000000 0xffffffff STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0xF4_IMAGE_csrss.exe BUCKET_ID: 0xF4_IMAGE_csrss.exe Followup: MachineOwner --------- Title Edited - Please follow new forum rules from now on -- Martin L