• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

[SOLVED] Question about a file that scans hang up on - System.Data.dll

You're going to need a few 4GB dvds to make the image backup.

Do you have an external HDD with some space available?
 
No, I don't.

I will express the need for them to get one.

Tell me tho...Do you feel the issue with that particular file means the end for the current HDD or a hint to a possibility?

Also, I reran the scan that was freezing and it appears to cruise by that file now.
 
Yes... Please do as jc asks...

Usually, when you start getting bad clusters it is a sign the drive is nearing failure... I would like to have you run some Hardware tests on the HDD, but it would be best if you had a recoverable backup of the OS first...

At this point, I cannot say what the true condition of the HDD is.
 
I apologize... but I see many entries in the application log location. WMI, Winlogon. user profile.....etc..

I am searching but I do not see anything indicating CHKdSK
 
I think I found it:

Code:
Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          9/13/2012 7:18:58 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Chris-HP
Description:

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.                         
CHKDSK is verifying files (stage 1 of 5)...
  149760 file records processed.                                         
File verification completed.
  163 large file records processed.                                   
  0 bad file records processed.                                     
  0 EA records processed.                                           
  62 reparse records processed.                                      
CHKDSK is verifying indexes (stage 2 of 5)...
  202326 index entries processed.                                        
Index verification completed.
  0 unindexed files scanned.                                        
  0 unindexed files recovered.                                      
CHKDSK is verifying security descriptors (stage 3 of 5)...
  149760 file SDs/SIDs processed.                                        
Cleaning up 665 unused index entries from index $SII of file 0x9.
Cleaning up 665 unused index entries from index $SDH of file 0x9.
Cleaning up 665 unused security descriptors.
Security descriptor verification completed.
  26284 data files processed.                                           
CHKDSK is verifying Usn Journal...
  35373824 USN bytes processed.                                            
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x23d77cc000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x23d77d6000 for 0x1000 bytes.
Windows replaced bad clusters in file 83014
of name \Windows\MICROS~1.NET\assembly\GAC_64\System.Data\V40_40~1.0__\SYSTEM~1.DLL.
  149744 files processed.                                                
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  60749214 free clusters processed.                                        
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
 292773887 KB total disk space.
  49457048 KB in 94537 files.
     59984 KB in 26285 indexes.
         4 KB in bad sectors.
    259991 KB in use by the system.
     65536 KB occupied by the log file.
 242996860 KB available on disk.
      4096 bytes in each allocation unit.
  73193471 total allocation units on disk.
  60749215 allocation units available on disk.
Internal Info:
00 49 02 00 02 d8 01 00 35 72 03 00 00 00 00 00  .I......5r......
9e 0d 00 00 3e 00 00 00 00 00 00 00 00 00 00 00  ....>...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Windows has finished checking your disk.
Please wait while your computer restarts.
Event Xml:
<Event xmlns="[URL]http://schemas.microsoft.com/win/2004/08/events/event[/URL]">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-14T02:18:58.000000000Z" />
    <EventRecordID>17474</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Chris-HP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.                         
CHKDSK is verifying files (stage 1 of 5)...
  149760 file records processed.                                         
File verification completed.
  163 large file records processed.                                   
  0 bad file records processed.                                     
  0 EA records processed.                                           
  62 reparse records processed.                                      
CHKDSK is verifying indexes (stage 2 of 5)...
  202326 index entries processed.                                        
Index verification completed.
  0 unindexed files scanned.                                        
  0 unindexed files recovered.                                      
CHKDSK is verifying security descriptors (stage 3 of 5)...
  149760 file SDs/SIDs processed.                                        
Cleaning up 665 unused index entries from index $SII of file 0x9.
Cleaning up 665 unused index entries from index $SDH of file 0x9.
Cleaning up 665 unused security descriptors.
Security descriptor verification completed.
  26284 data files processed.                                           
CHKDSK is verifying Usn Journal...
  35373824 USN bytes processed.                                            
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x23d77cc000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x23d77d6000 for 0x1000 bytes.
Windows replaced bad clusters in file 83014
of name \Windows\MICROS~1.NET\assembly\GAC_64\System.Data\V40_40~1.0__\SYSTEM~1.DLL.
  149744 files processed.                                                
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  60749214 free clusters processed.                                        
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
 292773887 KB total disk space.
  49457048 KB in 94537 files.
     59984 KB in 26285 indexes.
         4 KB in bad sectors.
    259991 KB in use by the system.
     65536 KB occupied by the log file.
 242996860 KB available on disk.
      4096 bytes in each allocation unit.
  73193471 total allocation units on disk.
  60749215 allocation units available on disk.
Internal Info:
00 49 02 00 02 d8 01 00 35 72 03 00 00 00 00 00  .I......5r......
9e 0d 00 00 3e 00 00 00 00 00 00 00 00 00 00 00  ....>...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>
I hope that came out right.
 
Last edited by a moderator:
Yes... Please do as jc asks...

Usually, when you start getting bad clusters it is a sign the drive is nearing failure... I would like to have you run some Hardware tests on the HDD, but it would be best if you had a recoverable backup of the OS first...

At this point, I cannot say what the true condition of the HDD is.


Willing to do that for sure and I have been waiting for a reason to get an external HDD:thumbsup2:
 
This is relatively common and nothing serious to worry about...

Code:
Cleaning up 665 unused index entries from index $SII of file 0x9.
Cleaning up 665 unused index entries from index $SDH of file 0x9.
Cleaning up 665 unused security descriptors.

This is the reason your AV programs were hanging up... A bad cluster is normally nothing to worry about, but it did cause issues because part of the .dll was written to it. It seems as though chkdsk was able to recover/repair the file. If there are issue in the future, .net Framework can be reinstalled.

Unfortunately, bad clusters are rarely a singular occurrence... We need to run a HDD diagnostic. More on that later.

Code:
Read failure with status 0xc0000185 at offset 0x23d77cc000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x23d77d6000 for 0x1000 bytes.
Windows replaced bad clusters in file 83014
of name \Windows\MICROS~1.NET\assembly\GAC_64\System.Data\V40_40~1.0__\SYSTEM~1.DLL.

This is another reason the scans may have taken a bit longer than usual. The MFT (partition table) is like a manifest at a parts store... The manifest says there is something there, but when you go look, you can't find it... It is the way software knows where to find the files on the drive... It is good that it is taken care of.

Code:
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Okay... Here is the fun part. Do you have any blank CDs?
 
Read failure with status 0xc0000185 at offset 0x23d77cc000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x23d77d6000 for 0x1000 bytes.

Exception code 0xc0000185 = I/O error


Code:
292773887 KB total disk space.
  49457048 KB in 94537 files.
     59984 KB in 26285 indexes.
         [COLOR=#ff0000]4 KB in bad sectors.[/COLOR]
    259991 KB in use by the system.
     65536 KB occupied by the log file.
 242996860 KB available on disk.
      4096 bytes in each allocation unit.
  73193471 total allocation units on disk.

0xc0000185 + bad sectors = HDD is failing.

Back up vital files. Best to use a USB drive.

Create system manufacturer Windows recovery disc(s) using DVD-R. Most OEMs do not allow DVD+RW; some - can't use DVD+R. You can purchase a set of recovery discs from the manufacturer, if necessary.

https://www.sysnative.com/forums/showthread.php/3716-OEM-Replacement-Media

HDD should be replaced.

Regards. . .

jcgriff2
 
Download UBCD from http://www.ultimatebootcd.com/ (direct link).
Burn it to DVD and label it (you can use it many times over! :smile9:)

Once that is done, boot the computer to the UBCD. You may have to change the boot order in the BIOS settings or access the Boot Menu. If you go into the BIOS, check to see if there is a SATA setting that has an "IDE" or "Compatability Mode" option. Some of the bootable HDD diagnostics will not work with AHCI.

Choose the HDD menu then Diagnosis.
Choose the latest diagnostic for your brand HDD. If you don't know your HDD brand, choose Drive Fitness Test (Hitatchi).
Run the Long or Advanced test.

Post back the results.

GZ is the hardware expert here; however the 0xc0000185 exceptions. . . are troublesome to me.

Getting there JC!!! We will have a full media scan done very soon!!!!
 
HDD should be replaced.

Regards. . .

jcgriff2

This is crazy, this is the third HDD going bad from the same household!

I don't know what to think about it.

But not the same system... correct?

Several HDDs have gone bad here, including one that was just 13 months old.


Run HDD diagnostics - SeaTools (for DOS) --> SeaTools for DOS | Seagate

Burn ISO to CD with ImgBurn --> The Official ImgBurn Website

ImgBurn - Select "Write image file to disk" -

Boot with SeaTools CD.

I know GZ has another HDD test in mind, but I can't recall the name.

Back up your files 1st -- if the HDD is in fact failing, each use can be detrimental.

Regards. . .

jcgriff2

.
 
GZ is the hardware expert here; however the 0xc0000185 exceptions. . . are troublesome to me.

At this point the exceptions are Greek to me. Need to do some research to understand what exactly is going on for future reference.

Click on NTSTATUS Codes - scroll down - http://www.jcgriff2.com/

You'll find in the list from TechNet -
0xC0000185
STATUS_IO_DEVICE_ERROR

The I/O device reported an I/O error.

http://msdn.microsoft.com/en-us/library/cc704588(d=lightweight,l=en-us,v=PROT.10).aspx

Regards. . .

jcgriff2
 
@GZ...Just happend to have a UBCD already burned...tx to AustrAlien..

@jcgriff2...Just happen to have seagate seatools for DOS burned as well..tx to usasma..

I have to get to sleep as I start my regular 4 tomorrow. I will get something done after work tomorrow.

Here I go learning again......:thumbsup2:


Thank you both for your input i will be back tomorrow evening with something for ya.

4
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top