Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: i have included the chkdsk log, has it went bad already ???


28 Oct 2012   #1

windows 7 home premium
 
 
i have included the chkdsk log, has it went bad already ???

i bought a 128gb ocz vertex plus ssd 1 month ago

i have included the chkdsk log, has ssd went bad already ???

Code:
 
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 28/10/2012 11:25:24
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: IJWIA-PC
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)...
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59728 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59729 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59730 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59731 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59736 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59737 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59738 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59739 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59740 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59741 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59742 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59743 is unreadable.
116224 file records processed. 
 
File verification completed.
107 large file records processed. 
 
Read failure with status 0xc0000185 at offset 0xc3a54400 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc3a56c00 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc3a57400 for 0x400 bytes.
12 bad file records processed. 
 
0 EA records processed. 
 
92 reparse records processed. 
 
CHKDSK is verifying indexes (stage 2 of 5)...
The object id index entry in file 0x19 points to file 0xe95d
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe95c
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe95b
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe95a
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe958
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe953
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe959
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
Index entry NTUSER.DAT{016888bd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf of index $I30 in file 0x37 points to unused file 0xe951.
Deleting index entry NTUSER.DAT{016888bd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf in index $I30 of file 55.
Index entry NTUSER~1.BLF of index $I30 in file 0x37 points to unused file 0xe951.
Deleting index entry NTUSER~1.BLF in index $I30 of file 55.
Index entry Ease of Access.lnk of index $I30 in file 0xe93c points to unused file 0xe95d.
Deleting index entry Ease of Access.lnk in index $I30 of file 59708.
Index entry EASEOF~1.LNK of index $I30 in file 0xe93c points to unused file 0xe95d.
Deleting index entry EASEOF~1.LNK in index $I30 of file 59708.
Index entry Narrator.lnk of index $I30 in file 0xe93c points to unused file 0xe95b.
Deleting index entry Narrator.lnk in index $I30 of file 59708.
155550 index entries processed. 
 
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
9 unindexed files scanned. 
 
0 unindexed files recovered. 
 
CHKDSK is verifying security descriptors (stage 3 of 5)...
116224 file SDs/SIDs processed. 
 
Cleaning up 301 unused index entries from index $SII of file 0x9.
Cleaning up 301 unused index entries from index $SDH of file 0x9.
Cleaning up 301 unused security descriptors.
Security descriptor verification completed.
19664 data files processed. 
 
CHKDSK is verifying Usn Journal...
36187232 USN bytes processed. 
 
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
116208 files processed. 
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
19309080 free clusters processed. 
 
Free space verification is complete.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
 
117218303 KB total disk space.
39709240 KB in 78524 files.
51176 KB in 19665 indexes.
12 KB in bad sectors.
221551 KB in use by the system.
65536 KB occupied by the log file.
77236324 KB available on disk.
 
4096 bytes in each allocation unit.
29304575 total allocation units on disk.
19309081 allocation units available on disk.
 
Internal Info:
00 c6 01 00 99 7f 01 00 ca da 02 00 00 00 00 00 ................
e7 00 00 00 5c 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="http://schemas.microsoft.com/win/2004/08/events/event">
<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-10-28T11:25:24.000000000Z" />
<EventRecordID>2214</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>IJWIA-PC</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)...
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59728 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59729 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59730 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a54000 for 0x1000 bytes.
File record segment 59731 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59736 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59737 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59738 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a56000 for 0x1000 bytes.
File record segment 59739 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59740 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59741 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59742 is unreadable.
Read failure with status 0xc0000185 at offset 0xc3a57000 for 0x1000 bytes.
File record segment 59743 is unreadable.
116224 file records processed. 
 
File verification completed.
107 large file records processed. 
 
Read failure with status 0xc0000185 at offset 0xc3a54400 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc3a56c00 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc3a57400 for 0x400 bytes.
12 bad file records processed. 
 
0 EA records processed. 
 
92 reparse records processed. 
 
CHKDSK is verifying indexes (stage 2 of 5)...
The object id index entry in file 0x19 points to file 0xe95d
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe95c
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe95b
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe95a
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe958
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe953
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xe959
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
Index entry NTUSER.DAT{016888bd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf of index $I30 in file 0x37 points to unused file 0xe951.
Deleting index entry NTUSER.DAT{016888bd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf in index $I30 of file 55.
Index entry NTUSER~1.BLF of index $I30 in file 0x37 points to unused file 0xe951.
Deleting index entry NTUSER~1.BLF in index $I30 of file 55.
Index entry Ease of Access.lnk of index $I30 in file 0xe93c points to unused file 0xe95d.
Deleting index entry Ease of Access.lnk in index $I30 of file 59708.
Index entry EASEOF~1.LNK of index $I30 in file 0xe93c points to unused file 0xe95d.
Deleting index entry EASEOF~1.LNK in index $I30 of file 59708.
Index entry Narrator.lnk of index $I30 in file 0xe93c points to unused file 0xe95b.
Deleting index entry Narrator.lnk in index $I30 of file 59708.
155550 index entries processed. 
 
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
9 unindexed files scanned. 
 
0 unindexed files recovered. 
 
CHKDSK is verifying security descriptors (stage 3 of 5)...
116224 file SDs/SIDs processed. 
 
Cleaning up 301 unused index entries from index $SII of file 0x9.
Cleaning up 301 unused index entries from index $SDH of file 0x9.
Cleaning up 301 unused security descriptors.
Security descriptor verification completed.
19664 data files processed. 
 
CHKDSK is verifying Usn Journal...
36187232 USN bytes processed. 
 
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
116208 files processed. 
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
19309080 free clusters processed. 
 
Free space verification is complete.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
 
117218303 KB total disk space.
39709240 KB in 78524 files.
51176 KB in 19665 indexes.
12 KB in bad sectors.
221551 KB in use by the system.
65536 KB occupied by the log file.
77236324 KB available on disk.
 
4096 bytes in each allocation unit.
29304575 total allocation units on disk.
19309081 allocation units available on disk.
 
Internal Info:
00 c6 01 00 99 7f 01 00 ca da 02 00 00 00 00 00 ................
e7 00 00 00 5c 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>


My System SpecsSystem Spec
.

28 Oct 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

Hi,

As a start, I would check the alignment of the SSD using this tutorial:

SSD Alignment

Regards,
Golden
My System SpecsSystem Spec
28 Oct 2012   #3

windows 7 home premium
 
 

alignment seems fine

Partition 1 Primary 111 GB 1024 KB
My System SpecsSystem Spec
.


28 Oct 2012   #4

Desk1 8 Pro / Desk2 7 Home Prem / Laptop 8.1 Pro all 64bit
 
 

Hum Golden do you think that a Seatools check might be in order?

Just as matter of interest ijwiall why did you need to do a chkdsk?
My System SpecsSystem Spec
29 Oct 2012   #5

windows 7 home premium
 
 

Quote   Quote: Originally Posted by ICit2lol View Post
Hum Golden do you think that a Seatools check might be in order?

Just as matter of interest ijwiall why did you need to do a chkdsk?
windows kept throwing me into a temporary profile

it was suggested that i try a chkdsk, which i done! which identified errors and corrected my temporary profile problem letting me back into my ijwia profile
My System SpecsSystem Spec
29 Oct 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

Hi,

Lets check the installation:

1. Click Start
2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type sfc /scannow and hit enter.

Report the output once it finishes.

Regards,
Golden
My System SpecsSystem Spec
29 Oct 2012   #7

windows 7 home premium
 
 

Quote   Quote: Originally Posted by Golden View Post
Hi,

Lets check the installation:

1. Click Start
2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type sfc /scannow and hit enter.

Report the output once it finishes.

Regards,
Golden

Windows Resource Protection did not find any integrity violations.
My System SpecsSystem Spec
31 Oct 2012   #8

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

Hi,

I'm not sure what else to try. Has the firmware been updated recently?

OCZ Technology

Regards,
Golden
My System SpecsSystem Spec
31 Oct 2012   #9

windows 7 home premium
 
 

yeah i updated it straight away when i got it with 3.55 fw

so theres not any bad blocks on my hard drive then ?

that is all i was wondering about ? i should say aswell as what caused the disk disruption ? and the corruption of my profile ?
as the computer had not crashed or anything, just one day i booted computer and a temporary profile loaded up, it was suggested on the internet to do a chkdsk and errors on harddrive appeared
My System SpecsSystem Spec
02 Nov 2012   #10

windows 7 home premium
 
 

new problem probably related

the computer failed to start today

i have 2 windows seven installations

one one on the vertex plus that ive been having problems with

and this one on a traditional sata hard drive

the vertex plus is now refusing to start tells me to run windows 7 dvd installation disk after trying the fix on the disk it says that my boot config is damaged and although it shows that their are 2 Windows 7 installations the 1st one has 0 under disk capacity and usage where as my original hard disk shows the capacity of installation and whats been used

this new problem with my previous problems does this sounds as if the disk is broken ? or can i fix the boot config somehow ? or am i better formating the vertex and starting again with it regarding a new installation ?

this vertex is only about a month old so any advice is welcome

thanks for reading
My System SpecsSystem Spec
Reply

 i have included the chkdsk log, has it went bad already ???




Thread Tools



Similar help and support threads for2: i have included the chkdsk log, has it went bad already ???
Thread Forum
Solved Tools Chkdsk with no /f /r says errors, bootup chkdsk says none Hardware & Devices
Kernel Data inpage error BSOD. Audio glitches. chkdsk included BSOD Help and Support
Is KB971033 ( WAT ) included in SP1 ? Windows Updates & Activation
Want MKV to be included in WMP 12 Software
drivers included?? Installation & Setup
Win 7 Pro Included Games - where? Gaming
Is Diskclean up included in 7 General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:01 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33