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: Computer needs to be checked for consistancy... is the drive failing?

09 Jul 2012   #1
KelvinW4

Windows 7 Professional x86
 
 
Computer needs to be checked for consistancy... is the drive failing?

I have never had such a big problem when I check my disk. Should I be worried?
Here is the log:
Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x440d16 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x188b2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 100530.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4492d6 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x188b3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 100531.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415e62 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195eb is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103915.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b47 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195ec is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103916.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415e59 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195ed is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103917.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b46 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195ee is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103918.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415e32 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195ef is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103919.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b45 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103920.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415e29 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103921.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b44 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103922.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415e09 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103923.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b43 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f4 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103924.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415df2 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f5 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103925.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b42 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103926.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415de9 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f7 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103927.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b41 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103928.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415dd0 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195f9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103929.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b40 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195fa is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103930.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415d53 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195fb is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103931.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b3f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195fc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103932.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415b82 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195fd is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103933.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b3e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195fe is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103934.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415b79 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x195ff is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103935.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b3d for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19600 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103936.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415b6d for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19601 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103937.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b3c for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19602 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103938.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415909 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19603 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103939.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b3b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19604 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103940.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4158f9 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19605 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103941.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b3a for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19606 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103942.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4158e8 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19607 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103943.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b39 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19608 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103944.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4158df for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19609 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103945.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b38 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1960a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103946.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4158d6 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1960b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103947.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b37 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1960c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103948.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b36 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1960e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103950.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415549 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1960f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103951.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b35 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19610 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103952.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415534 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19611 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103953.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b34 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19612 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103954.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x44085b for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19613 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103955.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b33 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19614 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103956.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x41552b for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19615 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103957.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b32 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19616 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103958.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415522 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19617 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103959.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b31 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19618 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103960.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x415519 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x19619 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103961.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b30 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1961a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103962.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4154fe for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1961b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103963.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b2f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1961c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103964.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x4154f5 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1961d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103965.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x448b2e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1961e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 103966.

there seems to be some more earlier but it did not fit :l


My System SpecsSystem Spec
.

10 Jul 2012   #2
usasma
Microsoft MVP

 
 

Wow! That log file looks pretty bad!
The first thing to do is to ensure that you have everything backed up. If you don't, do it now! There's no telling where this will go/end up - so you don't want to lose your data!

CHKDSK checks the NTFS file system on the hard drive. If it finds errors, it'll fix them if you use the proper commands (and will automatically fix problems at times).

In most cases this doesn't cause any problems. But with the amount of stuff going on in your NTFS file system it's likely to cause some issues (programs not working correctly, odd behaviors, etc)

If it's only a problem with the NTFS file system, then the problems shouldn't be there the next time that you run CHKDSK.

But if they do return, then you have to wonder what's causing them. The first thing to do in that case is to run one of these free hard drive diagnostics: Hard Drive Diagnostic Procedure This will tell you if the hard drive is dead/dying.

Please post back with the results of what you've done and we'll see about moving on from there.
My System SpecsSystem Spec
10 Jul 2012   #3
KelvinW4

Windows 7 Professional x86
 
 

It happened only one time. I checked this disk again there was no problems and the computer is running smoothly. No program freezes, no crashes, no BSODs, but I am concerned about what may cause that large of a corruption. Never had I shut down improperly and I took good care of the drive.
My System SpecsSystem Spec
.


10 Jul 2012   #4
usasma
Microsoft MVP

 
 

Still run the hard drive diagnostic program listed here (it's free): Hard Drive Diagnostic Procedure
You never know until you've seen the results of the test (and it's also the start for trying to figure out why this happened).
My System SpecsSystem Spec
Reply

 Computer needs to be checked for consistancy... is the drive failing?




Thread Tools





Similar help and support threads
Thread Forum
Computer keep failing to go to sleep...
Hello, i have this issue : when the computer is put to sleep, it'll fail, resulting in me having to force shutdown & restart... RAM & disk space = plenty avalaible, always. Checked windows event log : i can see traces when computer go to sleep, but not error... So i'm stuck! Reinstall Windows?...
Performance & Maintenance
Jacks picked up by computer but still no sound, checked control panel
Hi guys, my friend is having trouble with his headset. He has the jacks plugged in on the rear ports and they come up in the control panel but they dont seem to be transmitting his voice at all while the he can hear sounds. We have checked the control panel sound menu and the realtek drivers, and...
Sound & Audio
disk consistancy check
My MSI laptop has been crashing today.. gettting errors and blue screen of death. it says i have to run the disk consistancy check at start up but it automatically cancels it and i cant figure out how to make it run...
BSOD Help and Support
computer failing
So im at point I think a clean install is only chance I have. My computer keeps hanging when I try to update. It installs update restarts fails to log in. Safe mode won't work nothing I end up restoring to previous verision then it works.. Why would windows update cause compter to fail could...
Windows Updates & Activation
Hard drive failing
I built a Sandy Bridge and foolishly used a Samsung 103J Spinpoint 1TB drive. NOw being a first timer I just put it altogether and swircted on > loaded the OS -7 Home and began computing. However the Samsung has made quite loud clicking / scratching noises form the start as it reads /...
Hardware & Devices
BD-ROM Drive not being checked at boot-up!
When I powered the computer on it would first search for the BD-ROM Drive, display "no medium" (no boot disk inserted) and carry on booting from my internal drive. It no longer checks with the ROM drive before actually booting up. Would anyone know the reason for this and how to fix it? Thanks...
Hardware & Devices

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 18:43.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App