tb582 Posted February 8, 2006 Share Posted February 8, 2006 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.5Copyright (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 availableSymbol search path is: C:\WINDOWS\SymbolsExecutable search path is: Unable to load image ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0Debug session time: Tue Feb 7 21:24:11.984 2006 (GMT-5)System Uptime: 0 days 1:26:14.944Unable to load image ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exeLoading Kernel Symbols............................................................................................................................................................Loading User SymbolsLoading unloaded module list...................................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck F4, {3, 85faea20, 85faeb94, 80604498}Probably caused by : csrss.exeFollowup: MachineOwner---------0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CRITICAL_OBJECT_TERMINATION (f4)A process or thread crucial to system operation has unexpectedly exited or beenterminated.Several processes and threads are necessary for the operation of thesystem; when they are terminated (for any reason), the system can nolonger function.Arguments:Arg1: 00000003, ProcessArg2: 85faea20, Terminating objectArg3: 85faeb94, Process image file nameArg4: 80604498, Explanatory message (ascii)Debugging Details:------------------PROCESS_OBJECT: 85faea20IMAGE_NAME: csrss.exeDEBUG_FLR_IMAGE_TIMESTAMP: 0MODULE_NAME: csrssFAULTING_MODULE: 00000000 CUSTOMER_CRASH_COUNT: 11DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULTBUGCHECK_STR: 0xF4PROCESS_NAME: csrss.exeSTACK_TEXT: f7931520 80633f32 000000f4 00000003 85faea20 nt!MiRemoveUnusedSegments+0x637f7931544 80604456 80604498 85faea20 85faeb94 nt!RtlDescribeChunkNS+0x3f7931544 80604456 80604498 85faea20 85faeb94 nt!WmiTraceThread+0x70f7931574 804dd98f 85faec68 c0000006 f79319b0 nt!WmiTraceThread+0x70f7931584 804e4697 badb0d00 f79315fc 000c0000 nt!ZwQueryEvent+0x4f7931584 804e4697 badb0d00 f79315fc 000c0000 nt!KiInsertQueue+0x57f79319b0 80517e25 f79319d8 00000000 f7931d64 nt!KiInsertQueue+0x57f7931d34 804e1298 0052fbe8 0052fc08 00000000 nt!PopPromoteFromIdle0+0x49f7931d50 804dd98f 0052fbe8 0052fc08 00000000 nt!Dr_kitb_a+0x7ff7931d54 0052fbe8 0052fc08 00000000 0052fff4 nt!ZwQueryEvent+0x4WARNING: Frame IP not in any known module. Following frames may be wrong.f7931d64 7c90eb94 badb0d00 0052fbdc ffffffff 0x52fbe8f7931d68 badb0d00 0052fbdc ffffffff 00000001 0x7c90eb94f7931d6c 0052fbdc ffffffff 00000001 00000000 0xbadb0d00f7931d70 ffffffff 00000001 00000000 00000000 0x52fbdcf7931d74 00000000 00000000 00000000 00000000 0xffffffffSTACK_COMMAND: kbFOLLOWUP_NAME: MachineOwnerFAILURE_BUCKET_ID: 0xF4_IMAGE_csrss.exeBUCKET_ID: 0xF4_IMAGE_csrss.exeFollowup: MachineOwner---------Title Edited - Please follow new forum rules from now on-- Martin L Link to comment Share on other sites More sharing options...
cluberti Posted February 8, 2006 Share Posted February 8, 2006 The error you're getting is:0x000000F4: CRITICAL_OBJECT_TERMINATIONIf any system object (file, process, thread, etc.) critical to system operation terminates with any unexpected error code (and csrss.exe is a very critical system object), Windows bugchecks with this (and possibly a few other) bugcheck messages.Is there any way you can post the dump file here, or at least the minidump file from the %windir%\minidump\ folder? I'd like to track the callstack back and see what kind of locks or traps I can find...Csrss.exe is likely the victim here, not the culprit, and so I need to see more than just an analyze -v statement to determine what's going on. Let me know if posting that dump from your XP box is a problem, and perhaps you can email or PM me. Link to comment Share on other sites More sharing options...
tb582 Posted February 8, 2006 Author Share Posted February 8, 2006 (edited) Is there any way you can post the dump file here, or at least the minidump file from the %windir%\minidump\ folder? I'd like to track the callstack back and see what kind of locks or traps I can find...Csrss.exe is likely the victim here, not the culprit, and so I need to see more than just an analyze -v statement to determine what's going on. Let me know if posting that dump from your XP box is a problem, and perhaps you can email or PM me.Here is the dump file...Mini020706_11.rar Edited February 8, 2006 by tb582 Link to comment Share on other sites More sharing options...
tb582 Posted February 8, 2006 Author Share Posted February 8, 2006 Here are all the miniDump's there are 11 total including the one posted above, It only happens when I open a quicktime file...www.silverscreencreations.com/images/Minidump.rar Link to comment Share on other sites More sharing options...
WolfX2 Posted February 9, 2006 Share Posted February 9, 2006 (edited) 12. Very often we see meaningless subjects in topic title. They give no clue of what the posts are all about. For example: - Oh no! - Help - I'm mad - Please help - Question - I need your help - Hmmmm .... This should be avoided. Users should enter something more specific in topic title so that it is easier for others to help.A few good examples: - Strange problem with DirectX9b redist- RunOnceEx install problem (double installation)- Change Internet Explorer's Icon back to default Be sure to read the forum rules Edited February 9, 2006 by wolf74481 Link to comment Share on other sites More sharing options...
cluberti Posted February 9, 2006 Share Posted February 9, 2006 I PM'ed, but I thought it'd be wise to post here as well. I was able to trace csrss.exe to what appears to be a driver, but the minidump doesn't contain any information about said driver. Do you perchance have a memory.dmp file in your \Windows directory that I can look at? That, assuming it's a kernel memory dump, should have at least the kernel information about the driver that belongs to the thread that dumped csrss.exe. Link to comment Share on other sites More sharing options...
tb582 Posted February 9, 2006 Author Share Posted February 9, 2006 Thanks, I also sent you a PM back but I'm not sure that it went through so I will just post here also...I don't think there is a kernel or full dump, but like I said before I can recreate the crash so if you could tell me how to setup windows to create a full dump upon crashing then I can recreate the crash and upload the file. Link to comment Share on other sites More sharing options...
cluberti Posted February 9, 2006 Share Posted February 9, 2006 Well, this is why I never make assumptions from minidumps - they can be wrong .I didn't have to go any further than analyze -v to see what's wrong on your box. You've got a hard disk issue:1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_STACK_INPAGE_ERROR (77)The requested page of kernel data could not be read in. Caused bybad block in paging file or disk controller error.In the case when the first arguments is 0 or 1, the stack signaturein the kernel stack was not found. Again, bad hardware.An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) orC000016AL (STATUS_DISK_OPERATION_FAILED) normally indicatesthe data could not be read from the disk due to a badblock. Upon reboot autocheck will run and attempt to map out the badsector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the pagingfile is on a SCSI disk device, then the cabling and termination should bechecked. See the knowledge base article on SCSI termination.Arguments:Arg1: c000009d, status codeArg2: c000009d, i/o status codeArg3: 00000000, page file numberArg4: 049a8000, offset into page fileDebugging Details:------------------ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTEDDISK_HARDWARE_ERROR: There was error with disk hardwareBUGCHECK_STR: 0x77_c000009dDEFAULT_BUCKET_ID: DRIVER_FAULTFOLLOWUP_NAME: ntmsdMODULE_NAME: hardware_diskIMAGE_NAME: hardware_diskDEBUG_FLR_IMAGE_TIMESTAMP: 0STACK_COMMAND: kbFAILURE_BUCKET_ID: 0x77_c000009dBUCKET_ID: 0x77_c000009dINTERNAL_BUCKET_URL: http://deviceweb/Bucket/Bucket.aspx?BucketID=1543OCA_CRASHES: 3077 (in last 90 days)Followup: ntmsd--------- Link to comment Share on other sites More sharing options...
tb582 Posted February 9, 2006 Author Share Posted February 9, 2006 What kind of hard disk issue? Why does this problem only happen with quicktime movies? Link to comment Share on other sites More sharing options...
cluberti Posted February 9, 2006 Share Posted February 9, 2006 I can't tell you exactly what, short of what the dump says - the status code c000009d translates to "STATUS_DEVICE_NOT_CONNECTED". That's all I can tell you - perhaps it's a chipset or disk controller driver issue, but when your machine is crashing, the OS is stating that the device being written to or read from has become disconnected, which almost always signifies a hardware error.Sorry I can't give you more, but the dump is pretty specific that I PM'ed you. Link to comment Share on other sites More sharing options...
cluberti Posted February 9, 2006 Share Posted February 9, 2006 OK, looked at your second dump uploaded - similar dump, same error, reported differently:3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CRITICAL_OBJECT_TERMINATION (f4)A process or thread crucial to system operation has unexpectedly exited or beenterminated.Several processes and threads are necessary for the operation of thesystem; when they are terminated (for any reason), the system can nolonger function.Arguments:Arg1: 00000003, ProcessArg2: 8646e020, Terminating objectArg3: 8646e194, Process image file nameArg4: 80604498, Explanatory message (ascii)Debugging Details:------------------PROCESS_OBJECT: 8646e020IMAGE_NAME: csrss.exeDEBUG_FLR_IMAGE_TIMESTAMP: 41107c1fMODULE_NAME: csrssFAULTING_MODULE: 4a680000 csrssEXCEPTION_RECORD: f63c89d8 -- (.exr fffffffff63c89d8)ExceptionAddress: 75b7b1c1 (winsrv!UserHardError) ExceptionCode: c0000006 (In-page I/O error) ExceptionFlags: 00000000NumberParameters: 3 Parameter[0]: 00000000 Parameter[1]: 75b7b1c1 Parameter[2]: c000009dInpage operation failed at 75b7b1c1, due to I/O error c000009dEXCEPTION_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTEDDEFAULT_BUCKET_ID: DRIVER_FAULTPROCESS_NAME: csrss.exeERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".IO_ERROR: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTEDEXCEPTION_STR: 0xc0000006_c000009dFAULTING_IP: winsrv!UserHardError+075b7b1c1 ?? ???BUGCHECK_STR: 0xF4_IOERR_C000009DSTACK_TEXT: f63c8520 80633f32 000000f4 00000003 8646e020 nt!KeBugCheckEx+0x1bf63c8544 80604456 80604498 8646e020 8646e194 nt!PspCatchCriticalBreak+0x75f63c8574 804dd98f 8646e268 c0000006 f63c89b0 nt!NtTerminateProcess+0x7df63c8574 804e4697 8646e268 c0000006 f63c89b0 nt!KiFastCallEntry+0xfcf63c85f4 80522106 ffffffff c0000006 f63c89f8 nt!ZwTerminateProcess+0x11f63c89b0 80517e25 f63c89d8 00000000 f63c8d64 nt!KiDispatchException+0x3a0f63c8d34 804e1298 0069fbe8 0069fc08 00000000 nt!KiRaiseException+0x175f63c8d50 804dd98f 0069fbe8 0069fc08 00000000 nt!NtRaiseException+0x33f63c8d50 75b7b1c1 0069fbe8 0069fc08 00000000 nt!KiFastCallEntry+0xfc0069fed0 75b447a0 00000000 0069feec 00000005 winsrv!UserHardError0069fff4 00000000 00000000 00000000 00000000 CSRSRV!CsrApiRequestThread+0x18aSTACK_COMMAND: kbFOLLOWUP_IP: csrss!_imp__CsrServerInitialization <PERF> (csrss+0x0)+04a680000 4d dec ebpFOLLOWUP_NAME: NtConFAILURE_BUCKET_ID: 0xF4_IOERR_C000009D_IMAGE_csrss.exe_DATE_8_4_2004BUCKET_ID: 0xF4_IOERR_C000009D_IMAGE_csrss.exe_DATE_8_4_2004Followup: NtCon---------Unless I'm in the twilight zone, this is a hardware error. Link to comment Share on other sites More sharing options...
cluberti Posted February 9, 2006 Share Posted February 9, 2006 Well, thought I'd do some further digging for no apparent reason, and I came up with this - this may be why quicktime is causing your box to crash with a hardware error:3: kd> !process 0 0**** NT ACTIVE PROCESS DUMP ****<snipt>PROCESS 85732020 SessionId: 0 Cid: 09dc Peb: 7ffde000 ParentCid: 02dc DirBase: 17a65000 ObjectTable: e1931f10 HandleCount: 629. Image: QuickTimePlayer.exe3: kd> .process 85732020Implicit process is now 857320203: kd> .reloadLoading Kernel Symbols...........................................................................................................................................................Loading User Symbols................................................................Loading unloaded module list..........................................3: kd> kpChildEBP RetAddr f63c8520 80633f32 nt!KeBugCheckEx(unsigned long BugCheckCode = 0xf4, unsigned long P1 = 3, unsigned long P2 = 0x8646e020, unsigned long P3 = 0x8646e194, unsigned long P4 = 0x80604498)+0x1bf63c8544 80604456 nt!PspCatchCriticalBreak(char * Msg = 0x80604498 "Terminating critical process 0x%p (%s).", void * Object = 0x8646e020, unsigned char * ImageFileName = 0x8646e194 "csrss.exe")+0x75f63c8574 804dd98f nt!NtTerminateProcess(void * ProcessHandle = 0x8646e268, long ExitStatus = -1073741818)+0x7df63c8574 804e4697 nt!KiFastCallEntry(<HRESULT 0x80004005>)+0xfcf63c85f4 80522106 nt!ZwTerminateProcess(void)+0x11f63c89b0 80517e25 nt!KiDispatchException(struct _EXCEPTION_RECORD * ExceptionRecord = 0xf63c89d8, struct _KTRAP_FRAME * ExceptionFrame = 0x00000000, struct _KTRAP_FRAME * TrapFrame = 0xf63c8d64, char PreviousMode = 1 '', unsigned char FirstChance = 0x00 '')+0x3a0f63c8d34 804e1298 nt!KiRaiseException(struct _EXCEPTION_RECORD * ExceptionRecord = 0x0069fbe8, struct _CONTEXT * ContextRecord = 0x0069fc08, struct _KTRAP_FRAME * ExceptionFrame = 0x00000000, struct _KTRAP_FRAME * TrapFrame = 0xf63c8d64, unsigned char FirstChance = 0x00 '')+0x175f63c8d50 804dd98f nt!NtRaiseException(void)+0x33f63c8d50 75b7b1c1 nt!KiFastCallEntry(<HRESULT 0x80004005>)+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0069fff4 00000000 0x75b7b1c13: kd> !threadTHREAD 85fddab0 Cid 0324.0350 Teb: 7ffdd000 Win32Thread: e12cf340 RUNNING on processor 3Not impersonatingDeviceMap e1000148Owning Process 8646e020 Image: csrss.exeWait Start TickCount 2249603 Ticks: 0Context Switch Count 2914 LargeStackUserTime 00:00:00.0578KernelTime 00:00:00.0265Start Address 0x75b44616LPC Server thread working on message Id 218e4Stack Init f63c9000 Current f63c8c34 Base f63c9000 Limit f63c6000 Call 0Priority 14 BasePriority 13 PriorityDecrement 0 DecrementCount 16ChildEBP RetAddr Args to Child f63c8520 80633f32 000000f4 00000003 8646e020 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo]) (CONV: stdcall)f63c8544 80604456 80604498 8646e020 8646e194 nt!PspCatchCriticalBreak+0x75 (FPO: [Non-Fpo]) (CONV: stdcall)f63c8574 804dd98f 8646e268 c0000006 f63c89b0 nt!NtTerminateProcess+0x7d (FPO: [Non-Fpo]) (CONV: stdcall)f63c8574 804e4697 8646e268 c0000006 f63c89b0 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ f63c8584)f63c85f4 80522106 ffffffff c0000006 f63c89f8 nt!ZwTerminateProcess+0x11 (FPO: [2,0,0])f63c89b0 80517e25 f63c89d8 00000000 f63c8d64 nt!KiDispatchException+0x3a0 (FPO: [Non-Fpo]) (CONV: stdcall)f63c8d34 804e1298 0069fbe8 0069fc08 00000000 nt!KiRaiseException+0x175 (FPO: [Non-Fpo]) (CONV: stdcall)f63c8d50 804dd98f 0069fbe8 0069fc08 00000000 nt!NtRaiseException+0x33f63c8d50 75b7b1c1 0069fbe8 0069fc08 00000000 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ f63c8d64)WARNING: Frame IP not in any known module. Following frames may be wrong.0069fff4 00000000 00000000 00000000 00000000 0x75b7b1c1Note that csrss.exe owns the quicktime.exe process. This could be an issue with quicktime making a call to an invalid hardware address, an invalid pagedpool or nonpaged pool memory address, or a request to a portion of the disk that is corrupt - since csrss.exe owns the process, it's likely that quicktime is bringing down csrss.exe when it crashes, causing the bugcheck.A reinstall of quicktime.exe to see if it still happens, perhaps?You can see that csrss.exe owns the quicktime process in the line"Owning Process 8646e020 Image: csrss.exe"in the dump information pasted in above. Link to comment Share on other sites More sharing options...
tb582 Posted February 9, 2006 Author Share Posted February 9, 2006 A reinstall of quicktime.exe to see if it still happens, perhaps?You can see that csrss.exe owns the quicktime process in the line"Owning Process 8646e020 Image: csrss.exe"in the dump information pasted in above.Reinstalling Quicktime does not solve the problem... any other ideas? Link to comment Share on other sites More sharing options...
LLXX Posted February 10, 2006 Share Posted February 10, 2006 Have you Scandisk'd the drive? The analyses posted so far indicate a problem with the disk subsystem hardware. Link to comment Share on other sites More sharing options...
cluberti Posted February 10, 2006 Share Posted February 10, 2006 TB has an external disk - is it possible the video or your pagefile is on the external hard disk? That's the only logical conclusion I can come to for the "device" in question being listed as disconnected... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now