Frustrating BSOD - CRITICAL_OBJECT_TERMINATION - A non close operation has been requested of a file object with a delete pending.
OK, I've had this BSOD happen to me on the most coincidental times, it is always the same BSOD too.
First on 7/8/12 at 3:05 AM, then 7/18/12 at 1:21 PM, then 9/1/12 at 12:02 AM, then 9/18/12 at 3:16 PM... It's always the same thing, Bug Check 0x000000f4, CRITICAL_OBJECT_TERMINATION.
Here's the complete dump from the debugger, any ideas? The system is running Windows 7 Ultimate 32-bit. It is running on an Intel 530 120 GB SSD and two 1 TB hard drives. The Paging file is set to use the 1 TB hard drives instead of the SSD. I am using a
Gigabyte GA-965P-DQ6 mainboard running 4 GB of RAM. What other information do you need?
I know the hardware is good because I've run disk diagnostics and the system runs for days at a time without any issues. I've reseated the hard drive cables and the SSD is only about six months old. I've already swapped out the power supply (It was noisy
anyway) and an Intel 320 120 GB SSD which I initially thought was defective.
At least I can say that this BSOD is consistent and always the same. I have run a sfc /scannow online and it has reported no problems. I have run Memtest on the machine for 12 hours straight with no issues. I ran a chkdsk on both the hard drives and the
SSD, no issues reported. What else could it be?
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: 87db1030, Terminating object
Arg3: 87db119c, Process image file name
Arg4: 82e2ddf0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: 87db1030
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAULTING_MODULE: 00000000
PROCESS_NAME: wininit.exe
EXCEPTION_RECORD: 8ed5bc7c -- (.exr 0xffffffff8ed5bc7c)
ExceptionAddress: 00e10083
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 00e10083
Parameter[2]: c0000056
Inpage operation failed at 00e10083, due to I/O error c0000056
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1: 00000008
EXCEPTION_PARAMETER2: 00e10083
EXCEPTION_PARAMETER3: c0000056
IO_ERROR: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.
EXCEPTION_STR: 0xc0000006_c0000056
FAULTING_IP:
+12a
00e10083 ?? ???
BUGCHECK_STR: 0xF4_IOERR_C0000056
STACK_TEXT:
8ed5b448 82ef32ad 000000f4 00000003 87db1030 nt!KeBugCheckEx+0x1e
8ed5b46c 82e70e2c 82e2ddf0 87db119c 87db12a0 nt!PspCatchCriticalBreak+0x71
8ed5b49c 82e70d6f 87db1030 87e14d48 c0000006 nt!PspTerminateAllThreads+0x2d
8ed5b4d0 82c5327a ffffffff c0000006 8ed5b964 nt!NtTerminateProcess+0x1a2
8ed5b4d0 82c524cd ffffffff c0000006 8ed5b964 nt!KiFastCallEntry+0x12a
8ed5b550 82cca309 ffffffff c0000006 0001003f nt!ZwTerminateProcess+0x11
8ed5b964 82c42017 8ed5bc7c 00000000 8ed5bd34 nt!KiDispatchException+0x497
8ed5bd04 82c56e17 8ed5bc7c 00d3eea8 00000000 nt!KiRaiseException+0x18a
8ed5bd20 82c5327a 00d3ee88 00d3eea8 00000000 nt!NtRaiseException+0x33
8ed5bd20 00e10083 00d3ee88 00d3eea8 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00d3f210 00000000 00000000 00000000 00000000 0xe10083
STACK_COMMAND: kb
FOLLOWUP_IP:
+12a
00e10083 ?? ???
SYMBOL_STACK_INDEX: a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
SYMBOL_NAME: +12a
FAILURE_BUCKET_ID: 0xF4_IOERR_C0000056_+12a
BUCKET_ID: 0xF4_IOERR_C0000056_+12a
Followup: MachineOwner
---------
0: kd> !process ffffffff87db1030 3
GetPointerFromAddress: unable to read from 82d7e84c
PROCESS 87db1030 SessionId: none Cid: 02ec Peb: 7ffd6000 ParentCid: 0294
DirBase: de1110a0 ObjectTable: 8278b428 HandleCount: <Data Not Accessible>
Image: wininit.exe
VadRoot 88ab0910 Vads 66 Clone 0 Private 217. Modified 12. Locked 2.
DeviceMap 8de08860
Token 8275a360
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
ffdf0000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (1807, 50, 345) (7228KB, 200KB, 1380KB)
PeakWorkingSetSize 2440
VirtualSize 34 Mb
PeakVirtualSize 48 Mb
PageFaultCount 2702
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 267
THREAD 87db1468 Cid 02ec.02f0 Teb: 7ffdf000 Win32Thread: ffb6edd8 WAIT: (UserRequest) UserMode Non-Alertable
87dc2400 NotificationEvent
*** Error in reading nt!_ETHREAD @ 87dd46d8
0: kd> .exr 0xffffffff8ed5bc7c
ExceptionAddress: 00e10083
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 00e10083
Parameter[2]: c0000056
Inpage operation failed at 00e10083, due to I/O error c0000056
0: kd> !object 87db1030
GetUlongFromAddress: unable to read from 82d7e844
Could not read ObjectType address
0: kd> dc 87db119c
87db119c 696e6977 2e74696e 00657865 03000000 wininit.exe.....
87db11ac 00000000 00000000 00000000 87db16d0 ................
87db11bc 88cc67b8 00000000 87b110a0 00000005 .g..............
87db11cc 00000000 00008000 00000000 7ffd6000 .............`..
87db11dc 00000000 0000000d 00000000 00000000 ................
87db11ec 00000000 00000703 00000000 0014a891 ................
87db11fc 00000000 00000000 00000000 000026be .............&..
87db120c 00000000 00000000 0000011d 00000000 ................
0: kd> dc 82e2ddf0
82e2ddf0 6d726554 74616e69 20676e69 74697263 Terminating crit
82e2de00 6c616369 6f727020 73736563 25783020 ical process 0x%
82e2de10 25282070 000a2973 cccccccc cccccccc p (%s)..........
82e2de20 61657242 6f202c6b 67492072 65726f6e Break, or Ignore
82e2de30 69622820 00203f29 cccccccc cccccccc (bi)? .........
82e2de40 74697243 6c616369 72687420 20646165 Critical thread
82e2de50 70257830 6e692820 29732520 69786520 0x%p (in %s) exi
82e2de60 0a646574 cccccc00 cccccccc cccccccc ted.............
0: kd> !error c0000056
Error code: (NTSTATUS) 0xc0000056 (3221225558) - A non close operation has been requested of a file object with a delete pending.
0: kd> .formats 0x400
Evaluate expression:
Hex: 00000400
Decimal: 1024
Octal: 00000002000
Binary: 00000000 00000000 00000100 00000000
Chars: ....
Time: Wed Dec 31 17:17:04 1969
Float: low 1.43493e-042 high 0
Double: 5.05923e-321
0: kd> !vm2
No export vm2 found
0: kd> !vm 2
*** Virtual Memory Usage ***
GetUlongFromAddress: unable to read from 82d7e840
Physical Memory: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from 82d5da24
************ NO PAGING FILE *********************
82d7e174: Unable to get paged pool info
GetUlongPtrFromAddress: unable to read from 82d7e6e0
GetUlongPtrFromAddress: unable to read from 82d7e208
GetUlongPtrFromAddress: unable to read from 82d5e538
GetUlongPtrFromAddress: unable to read from 82d5d034
GetUlongPtrFromAddress: unable to read from 82d5d018
GetUlongPtrFromAddress: unable to read from 82d5d060
GetUlongPtrFromAddress: unable to read from 82d7f240
GetUlongPtrFromAddress: unable to read from 82d3e94c
GetUlongPtrFromAddress: unable to read from 82d43480
GetUlongPtrFromAddress: unable to read from 82d43500
unable to get nt!MmTotalFreeSystemPtes
GetUlongFromAddress: unable to read from 82d5dd5c
Available Pages: 0 ( 0 Kb)
ResAvail Pages: 0 ( 0 Kb)
********** Running out of physical memory **********
Locked IO Pages: 0 ( 0 Kb)
Free System PTEs: 0 ( 0 Kb)
********** Running out of system PTEs **************
GetUlongFromAddress: unable to read from 82d5ff00
Modified Pages: 0 ( 0 Kb)
Modified PF Pages: 2885 ( 11540 Kb)
82d4b6c0: Unable to get pool descriptor
GetUlongFromAddress: unable to read from 82d7e060
NonPagedPool Usage: 0 ( 0 Kb)
NonPagedPoolNx Usage: 0 ( 0 Kb)
NonPagedPool Max: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from 82d7e014
PagedPool Usage: 0 ( 0 Kb)
PagedPool Maximum: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from 82d508c8
Unable to read _LIST_ENTRY @ 82d5d0a8
Session Commit: 0 ( 0 Kb)
Shared Commit: 61218 ( 244872 Kb)
Special Pool: 0 ( 0 Kb)
Shared Process: 0 ( 0 Kb)
PagedPool Commit: 0 ( 0 Kb)
Driver Commit: 0 ( 0 Kb)
Committed pages: 438840 ( 1755360 Kb)
Commit limit: 0 ( 0 Kb)
********** Number of committed pages is near limit ********
GetUlongFromAddress: unable to read from 82d5d020
GetUlongFromAddress: unable to read from 82d5d024
GetUlongFromAddress: unable to read from 82d5d028
GetUlongFromAddress: unable to read from 82d5d02c
Unable to read/NULL value _LIST_ENTRY @ 82d56b98
ProcessCommitUsage could not be calculated
Memory Management Thread Stacks:
Unable to read nt!_LIST_ENTRY @ 82d56b98
0: kd> !poolused
GetPointerFromAddress: unable to read from 82d7e848
Unable to read MiSystemVaType memory at 82d5de20
September 18th, 2012 11:28pm
Run the Windows 7 Memory diagnostic Tool
http://www.sevenforums.com/performance-maintenance/104698-memory-diagnostic-tool.html
Select Start, Run, type cmd and press ENTER. Type "chkdsk c: /f /r" without the quotes and hit ENTER. Make sure you include the spaces indicated. Enter Y when
asked whether you wish to run chkdsk on restarting the computer. Exit and restart the computer.
Marking off bad sectors on a hard drive takes time so be patient. Marking off does not repair a bad sector. It places pointers on the drive telling the system not
to read or write to those sectors which have been damaged.
If the number of bad sectors continues to increase after you have run the procedure above several times then you should replace the drive. If an important system
file is written to a bad sector you can corrupt registry hives and lose the whole contents of the drive.
On the other hand if having run chkdsk you see no more new bad sectors then the drive can work for you for years.Hope this helps, Gerry
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2012 1:57am
Hi,
According to the BUGCHECK_STR: 0xF4_IOERR_C0000056, please refers to
http://msdn.microsoft.com/en-us/library/ff560177(v=vs.85).aspx
Also i suspect there may something wrong with your Memory, please try Gerry's suggestion.
Finally,Enable
Driver Verifier. Enabling this should hopefully crash your system and then point to the faulty
driver that is causing problems. However before you do, it is advised that you
create a system restore point and
backup first.
Driver Verifier - Enable and DisableSpencer
TechNet Community Support
September 20th, 2012 1:23am