hmmmm I'll check out my new hitachi 2 tb hdd it had 1 pending sector count before but then vanished.
got new bsod screenshot. http://i54.tinypic.com/ivj1j6.jpg
this one did't get dump file tough cant see to locate it latest is from 3-6-2011 and not 4-6-2011
i also run nod32 smart security 5.0
anyway i did a full format write 0 to the hd back then which fixed it.
think the pending sector gotten re written as a ultra dma crc error which usualy caused by bad sata cable.
here's a full list off dump files i got atm. http://www.**************/?2j51vodns9gk854
ziped into 1 archive
Quote: Originally Posted by cluberti
The error code the BSOD calls out in param 2 is the reason the filesystem driver (ntfs.sys) told the system to crash, although withtout a dump we don't know what the I/O request was to or to what file:
# for hex 0xc0000056 / decimal -1073741738 :
# A non close operation has been requested of a file object
# with a delete pending.
I'd say you have a filesystem filter driver (antivirus, antimalware) causing it, or the filesystems on each hard disk in the machine may need to have chkdsk /r /f run against it to make sure they are clean of errors (or, perhaps, both). Otherwise, some driver on the system is closing a file object and marking it for deletion, and then making a request for it immediately after while the deletion is still pending. That doesn't seem as likely as the former, though.
i let chdsk run for now on my hitachi drive will probaly downgrade my nod32 to 4.0 to see if that fixes problems asswell if so i guess i have to mail them and report it
hmmmmm chdsk runs quite fast so far 4-5 did't find any problems so far i think
edit: now i think about it my laptop i put in sleep and resume from sleep all the time it also has the nod32 5.0 beta.
no errors on my hitachi hdd checking my samsung drive after if checked my ssd for errors.
Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is shit.
CHKDSK is verifying files (stage 1 of 5)...
26880 file records processed.
File verification completed.
6 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
27474 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
26880 file SDs/SIDs processed.
Security descriptor verification completed.
298 data files processed.
CHKDSK is verifying Usn Journal...
37413304 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
26864 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
171511891 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
1953512447 KB total disk space.
1267263704 KB in 8791 files.
11776 KB in 299 indexes.
0 KB in bad sectors.
189399 KB in use by the system.
65536 KB occupied by the log file.
686047568 KB available on disk.
4096 bytes in each allocation unit.
488378111 total allocation units on disk.
171511892 allocation units available on disk.