Sign in with
Sign up | Sign in
Your question
Solved

Windows 7 freeze before/after reinstall

Tags:
  • Hardware
  • Windows 7
Last response: in Windows 7
Share
March 19, 2013 8:45:58 PM

Hello everybody. About a month ago 2 days after download music I was playing a PC game for about 7 minutes when it suddenly froze. I attributed it to coincidence so I restarted. The PC froze again two more times. I ran a few boot scans with avast and discovered several infected items. I deleted 20 items except for Win-32 adware gen virus which avast could not delete. My problem with freezing at random 1-20 min intervals persisted after several scans with avast and malwarebytes. About 2 weeks ago I decided to reinstall windows 7 Home x64 by deleting my main and recovery partitions. I reinstalled and the PC function well for about 30 min until it froze again and te problem persists now to this date. Some times it freezes at the welcome screen sometimes after clicking a random icon or button or If I just wait a few minutes. The computer however runs without freeze in safe mode but not in normal or safe+networking.

Could this be a possible hardware problem or could malware have survived te deletion of the windows 7 partitions. Maybe evn BIOS. Please help me. Any assistance is appreciated

More about : windows freeze reinstall

March 19, 2013 10:59:43 PM

scout_03 said:
you could use this to see if you have a rootkit virus http://www.sophos.com/en-us/products/free-tools/sophos-...


Hi, thanks for the help. I would like to add a few more details. When I reinstalled Windows 7 for some reason the network drivers were not installed and I had to find drivers on my sisters laptop and transfer with a USB
m
0
l
Related resources
March 20, 2013 7:34:57 PM

Hello. I have used Sophos Virus Removal Tool and it has turned up zero results
m
0
l
a b $ Windows 7
March 20, 2013 7:49:55 PM

Hi :) 

Run a hard drive test in DOS... HIRENS BOOT CD etc, it sounds like a failing hard drive...

All the best Brett :) 
m
0
l
March 20, 2013 8:53:26 PM

Brett928S2 said:
Hi :) 

Run a hard drive test in DOS... HIRENS BOOT CD etc, it sounds like a failing hard drive...

All the best Brett :) 


Thanks for the help. I will definitely try out Hirens Boot CD. I'm currently running a CHKDSK at about 70% for about 2 hours now.
I will post what I find here, thank you


EDIT: it has been 3 hours and CHKDSK has finished. It found no errors yet immediately on reboot the PC froze when the "starting windows" logo with the lights on black back ground appeared. It has been sitting for nearly 5 minutes o confirm it freezing. Could this be a HDD problem or a malware problem still thank you. Tomorrow I will try out Hirens boot CD though
m
0
l
a b $ Windows 7
March 21, 2013 5:41:18 AM

specter208 said:
Brett928S2 said:
Hi :) 

Run a hard drive test in DOS... HIRENS BOOT CD etc, it sounds like a failing hard drive...

All the best Brett :) 


Thanks for the help. I will definitely try out Hirens Boot CD. I'm currently running a CHKDSK at about 70% for about 2 hours now.
I will post what I find here, thank you


EDIT: it has been 3 hours and CHKDSK has finished. It found no errors yet immediately on reboot the PC froze when the "starting windows" logo with the lights on black back ground appeared. It has been sitting for nearly 5 minutes o confirm it freezing. Could this be a HDD problem or a malware problem still thank you. Tomorrow I will try out Hirens boot CD though


Hi :) 

Run Hirens...

CHKDSKshould take MINUTES not hours :) 

Its your HD Failing... :( 

All the best Brett :) 
m
0
l
a c 204 $ Windows 7
March 21, 2013 7:27:35 AM

you could use the drive maker test tool that wil confirm brett928s2 answer .save all your data.
m
0
l
March 22, 2013 4:03:27 PM

Brett928S2 said:
specter208 said:
Brett928S2 said:
Hi :) 

Run a hard drive test in DOS... HIRENS BOOT CD etc, it sounds like a failing hard drive...

All the best Brett :) 


Thanks for the help. I will definitely try out Hirens Boot CD. I'm currently running a CHKDSK at about 70% for about 2 hours now.
I will post what I find here, thank you


EDIT: it has been 3 hours and CHKDSK has finished. It found no errors yet immediately on reboot the PC froze when the "starting windows" logo with the lights on black back ground appeared. It has been sitting for nearly 5 minutes o confirm it freezing. Could this be a HDD problem or a malware problem still thank you. Tomorrow I will try out Hirens boot CD though


Hi :) 

Run Hirens...

CHKDSKshould take MINUTES not hours :) 

Its your HD Failing... :( 

All the best Brett :) 

Hello again. I have finishe downloading Hirens Boot CD but I'm not sure which program to use. My HDD is a Western Digtal Green Drive 5400RPM 640gb

m
0
l
a c 204 $ Windows 7
March 22, 2013 7:56:28 PM

data lifeguard diagnostic .
m
0
l
March 23, 2013 12:01:02 PM

scout_03 said:
data lifeguard diagnostic .


Im trying to Run WD Data Lifeguard Diagnostic but upon attempting to run a quick test I get unexpected error code 0141.

I managed to get a copy of the CHKDSK log file. The scan took more or less 3 hours. I will post here

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 3/20/2013 6:55:06 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: LIMA-PC
Description:


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 0xa0 and instance tag 0x4 is cross linked
starting at 0x1c5ed2 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x10401 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 66561.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd7c4b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10405 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66565.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x471da4 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10406 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66566.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xa8b1a for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10407 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66567.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4728eb for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10408 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66568.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x406f3f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10409 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66569.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x6770 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1040f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66575.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x45b97 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10413 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66579.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3880ef for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10414 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66580.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x8bc50 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10415 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66581.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x4688ec for possibly 0x2f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10416 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66582.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x32a8b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10419 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66585.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x46760 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1041b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66587.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x387b16 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1041c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66588.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd9787 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1041e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66590.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3d7ff4 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1041f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66591.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x400b08 for possibly 0x1c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10422 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66594.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x10014e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10424 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66596.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x56f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10425 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66597.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb99e for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10427 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66599.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xd56a1 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10428 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66600.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3dfa0e for possibly 0x3f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1042c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66604.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x49f169 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10435 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66613.
68352 file records processed.

File verification completed.
36 large file records processed.

0 bad file records processed.

0 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
The object id in file 0x10426 does not appear in the object
id index in file 0x19.
Inserting an index entry into index $O of file 25.
The file reference 0x2000000010405 of index entry 10e53aef6b5bdde2469c00a66f17f611 of index $I30
with parent 0xe086 is not the same as 0x19000000010405.
Deleting index entry 10e53aef6b5bdde2469c00a66f17f611 in index $I30 of file 57478.
The file reference 0x2000000010405 of index entry 10E53A~1 of index $I30
with parent 0xe086 is not the same as 0x19000000010405.
Deleting index entry 10E53A~1 in index $I30 of file 57478.
The file reference 0x1000000010410 of index entry 4a6d99800fffd24367a0657997582779 of index $I30
with parent 0xe086 is not the same as 0x9000000010410.
Deleting index entry 4a6d99800fffd24367a0657997582779 in index $I30 of file 57478.
The file reference 0x1000000010410 of index entry 4A6D99~1 of index $I30
with parent 0xe086 is not the same as 0x9000000010410.
Deleting index entry 4A6D99~1 in index $I30 of file 57478.
The file reference 0x100000001041c of index entry 4bf9df843471694e34b6c9e4af8cfd8c of index $I30
with parent 0xe086 is not the same as 0x1bc00000001041c.
Deleting index entry 4bf9df843471694e34b6c9e4af8cfd8c in index $I30 of file 57478.
The file reference 0x100000001041c of index entry 4BF9DF~1 of index $I30
with parent 0xe086 is not the same as 0x1bc00000001041c.
Deleting index entry 4BF9DF~1 in index $I30 of file 57478.
The file reference 0x200000001041b of index entry 6a0f44afb333ccc3320fd72d9e20c57c of index $I30
with parent 0xe086 is not the same as 0x24d00000001041b.
Deleting index entry 6a0f44afb333ccc3320fd72d9e20c57c in index $I30 of file 57478.
The file reference 0x200000001041b of index entry 6A0F44~1 of index $I30
with parent 0xe086 is not the same as 0x24d00000001041b.
Deleting index entry 6A0F44~1 in index $I30 of file 57478.
The file reference 0x1000000010428 of index entry 71e79ff014f223d2cda8d22e9aef98f0 of index $I30
with parent 0xe086 is not the same as 0x4c000000010428.
Deleting index entry 71e79ff014f223d2cda8d22e9aef98f0 in index $I30 of file 57478.
The file reference 0x1000000010428 of index entry 71E79F~1 of index $I30
with parent 0xe086 is not the same as 0x4c000000010428.
Deleting index entry 71E79F~1 in index $I30 of file 57478.
The file reference 0x100000001040d of index entry 74f326dda14c60c449dcbffc6addc5d5 of index $I30
with parent 0xe086 is not the same as 0x2b00000001040d.
Deleting index entry 74f326dda14c60c449dcbffc6addc5d5 in index $I30 of file 57478.
The file reference 0x100000001040d of index entry 74F326~1 of index $I30
with parent 0xe086 is not the same as 0x2b00000001040d.
Deleting index entry 74F326~1 in index $I30 of file 57478.
The file reference 0x1000000010406 of index entry 8dff913fc410d6d286e0f56ecd36878b of index $I30
with parent 0xe086 is not the same as 0x20c000000010406.
Deleting index entry 8dff913fc410d6d286e0f56ecd36878b in index $I30 of file 57478.
The file reference 0x1000000010406 of index entry 8DFF91~1 of index $I30
with parent 0xe086 is not the same as 0x20c000000010406.
Deleting index entry 8DFF91~1 in index $I30 of file 57478.
The file reference 0x1000000010424 of index entry c20a9125d57fc9edbd48bd80e0026711 of index $I30
with parent 0xe086 is not the same as 0x99000000010424.
Deleting index entry c20a9125d57fc9edbd48bd80e0026711 in index $I30 of file 57478.
The file reference 0x1000000010424 of index entry C20A91~1 of index $I30
with parent 0xe086 is not the same as 0x99000000010424.
Deleting index entry C20A91~1 in index $I30 of file 57478.
The file reference 0x200000001041d of index entry d6ff317798affe13d00ca44eb93c96d0 of index $I30
with parent 0xe086 is not the same as 0x14700000001041d.
Deleting index entry d6ff317798affe13d00ca44eb93c96d0 in index $I30 of file 57478.
The file reference 0x200000001041d of index entry D6FF31~1 of index $I30
with parent 0xe086 is not the same as 0x14700000001041d.
Deleting index entry D6FF31~1 in index $I30 of file 57478.
Unable to locate the file name attribute of index entry localconfig.vdf
of index $I30 with parent 0xf3ec in file 0x10435.
Deleting index entry localconfig.vdf in index $I30 of file 62444.
Unable to locate the file name attribute of index entry LOCALC~1.VDF
of index $I30 with parent 0xf3ec in file 0x10435.
Deleting index entry LOCALC~1.VDF in index $I30 of file 62444.
The file reference 0x3000000010401 of index entry state of index $I30
with parent 0x103ce is not the same as 0x99000000010401.
Deleting index entry state in index $I30 of file 66510.
The file reference 0x1000000010404 of index entry BITB63D.tmp of index $I30
with parent 0x103d9 is not the same as 0x56000000010404.
Deleting index entry BITB63D.tmp in index $I30 of file 66521.
The file reference 0x1000000010402 of index entry cbshandler of index $I30
with parent 0x103d9 is not the same as 0xd000000010402.
Deleting index entry cbshandler in index $I30 of file 66521.
The file reference 0x1000000010402 of index entry CBSHAN~1 of index $I30
with parent 0x103d9 is not the same as 0xd000000010402.
Deleting index entry CBSHAN~1 in index $I30 of file 66521.
The file reference 0x1000000010423 of index entry BITC68B.tmp of index $I30
with parent 0x103f0 is not the same as 0xe000000010423.
Deleting index entry BITC68B.tmp in index $I30 of file 66544.
The file reference 0x100000001040c of index entry BITB90D.tmp of index $I30
with parent 0x103f6 is not the same as 0x5000000001040c.
Deleting index entry BITB90D.tmp in index $I30 of file 66550.
The file reference 0x100000001040a of index entry cbshandler of index $I30
with parent 0x103f6 is not the same as 0xf100000001040a.
Deleting index entry cbshandler in index $I30 of file 66550.
The file reference 0x100000001040a of index entry CBSHAN~1 of index $I30
with parent 0x103f6 is not the same as 0xf100000001040a.
Deleting index entry CBSHAN~1 in index $I30 of file 66550.
The file reference 0x1000000010418 of index entry state of index $I30
with parent 0x103f9 is not the same as 0xd000000010418.
Deleting index entry state in index $I30 of file 66553.
The file reference 0x1000000010420 of index entry state of index $I30
with parent 0x103fa is not the same as 0x41000000010420.
Deleting index entry state in index $I30 of file 66554.
The file reference 0x2000000010419 of index entry BITC1E7.tmp of index $I30
with parent 0x103fd is not the same as 0x58000000010419.
Deleting index entry BITC1E7.tmp in index $I30 of file 66557.
The file reference 0x1000000010400 of index entry state of index $I30
with parent 0x103ff is not the same as 0x1e000000010400.
Deleting index entry state in index $I30 of file 66559.
The index bitmap for index $I30 in file 0x10401 is invalid or missing.
Correcting error in index $I30 for file 66561.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0x10401.
Correcting error in index $I30 for file 66561.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 02 91 6d 49 c8 cd 01 ...........mI...
00 02 91 6d 49 c8 cd 01 fa 37 d2 df d3 1e ce 01 ...mI....7......
Sorting index $I30 in file 66561.
An index entry of index $I30 in file 0x10426 points to file 0x2c783
which is beyond the MFT.
Deleting index entry 5 001.jpg in index $I30 of file 66598.
An index entry of index $I30 in file 0x10426 points to file 0x2c783
which is beyond the MFT.
Deleting index entry 5001~1.JPG in index $I30 of file 66598.
An index entry of index $I30 in file 0x10426 points to file 0x2c77b
which is beyond the MFT.
Deleting index entry Thumbs.db in index $I30 of file 66598.
97918 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file APPLES~1 (66561) into directory file 273.
Recovering orphaned file Apple Software Update (66561) into directory file 273.
Recovering orphaned file KB2160~1.HTM (66562) into directory file 3562.
Recovering orphaned file KB2160841_20101212_105659612.html (66562) into directory file 3562.
Recovering orphaned file BF2_PA~1.EXE (66574) into directory file 517.
Recovering orphaned file BF2_Patch_1.41.exe (66574) into directory file 517.
Recovering orphaned file Plugins (66578) into directory file 66561.
Recovering orphaned file E269C0~1.CDF (66583) into directory file 10057.
Recovering orphaned file e25e4e4b1716ce0177110000c005cc05.$$_system32_migwiz_dlmanifests_microsoft-windows-wmi-core_0fa6ec0ad029fddb.cdf-ms (66583) i
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="2013-03-21T01:55:06.000000000Z" />
<EventRecordID>509</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>LIMA-PC</Computer>
<Security />
</System>
<EventData>
<Data>

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 0xa0 and instance tag 0x4 is cross linked
starting at 0x1c5ed2 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x10401 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 66561.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd7c4b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10405 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66565.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x471da4 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10406 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66566.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xa8b1a for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10407 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66567.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4728eb for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10408 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66568.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x406f3f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10409 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66569.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x6770 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1040f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66575.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x45b97 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10413 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66579.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3880ef for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10414 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66580.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x8bc50 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10415 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66581.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x4688ec for possibly 0x2f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10416 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66582.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x32a8b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10419 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66585.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x46760 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1041b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66587.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x387b16 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1041c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66588.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd9787 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1041e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66590.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3d7ff4 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1041f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66591.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x400b08 for possibly 0x1c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10422 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66594.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x10014e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10424 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66596.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x56f for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10425 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66597.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb99e for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10427 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66599.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xd56a1 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10428 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66600.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3dfa0e for possibly 0x3f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1042c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66604.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x49f169 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10435 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66613.
68352 file records processed.

File verification completed.
36 large file records processed.

0 bad file records processed.

0 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
The object id in file 0x10426 does not appear in the object
id index in file 0x19.
Inserting an index entry into index $O of file 25.
The file reference 0x2000000010405 of index entry 10e53aef6b5bdde2469c00a66f17f611 of index $I30
with parent 0xe086 is not the same as 0x19000000010405.
Deleting index entry 10e53aef6b5bdde2469c00a66f17f611 in index $I30 of file 57478.
The file reference 0x2000000010405 of index entry 10E53A~1 of index $I30
with parent 0xe086 is not the same as 0x19000000010405.
Deleting index entry 10E53A~1 in index $I30 of file 57478.
The file reference 0x1000000010410 of index entry 4a6d99800fffd24367a0657997582779 of index $I30
with parent 0xe086 is not the same as 0x9000000010410.
Deleting index entry 4a6d99800fffd24367a0657997582779 in index $I30 of file 57478.
The file reference 0x1000000010410 of index entry 4A6D99~1 of index $I30
with parent 0xe086 is not the same as 0x9000000010410.
Deleting index entry 4A6D99~1 in index $I30 of file 57478.
The file reference 0x100000001041c of index entry 4bf9df843471694e34b6c9e4af8cfd8c of index $I30
with parent 0xe086 is not the same as 0x1bc00000001041c.
Deleting index entry 4bf9df843471694e34b6c9e4af8cfd8c in index $I30 of file 57478.
The file reference 0x100000001041c of index entry 4BF9DF~1 of index $I30
with parent 0xe086 is not the same as 0x1bc00000001041c.
Deleting index entry 4BF9DF~1 in index $I30 of file 57478.
The file reference 0x200000001041b of index entry 6a0f44afb333ccc3320fd72d9e20c57c of index $I30
with parent 0xe086 is not the same as 0x24d00000001041b.
Deleting index entry 6a0f44afb333ccc3320fd72d9e20c57c in index $I30 of file 57478.
The file reference 0x200000001041b of index entry 6A0F44~1 of index $I30
with parent 0xe086 is not the same as 0x24d00000001041b.
Deleting index entry 6A0F44~1 in index $I30 of file 57478.
The file reference 0x1000000010428 of index entry 71e79ff014f223d2cda8d22e9aef98f0 of index $I30
with parent 0xe086 is not the same as 0x4c000000010428.
Deleting index entry 71e79ff014f223d2cda8d22e9aef98f0 in index $I30 of file 57478.
The file reference 0x1000000010428 of index entry 71E79F~1 of index $I30
with parent 0xe086 is not the same as 0x4c000000010428.
Deleting index entry 71E79F~1 in index $I30 of file 57478.
The file reference 0x100000001040d of index entry 74f326dda14c60c449dcbffc6addc5d5 of index $I30
with parent 0xe086 is not the same as 0x2b00000001040d.
Deleting index entry 74f326dda14c60c449dcbffc6addc5d5 in index $I30 of file 57478.
The file reference 0x100000001040d of index entry 74F326~1 of index $I30
with parent 0xe086 is not the same as 0x2b00000001040d.
Deleting index entry 74F326~1 in index $I30 of file 57478.
The file reference 0x1000000010406 of index entry 8dff913fc410d6d286e0f56ecd36878b of index $I30
with parent 0xe086 is not the same as 0x20c000000010406.
Deleting index entry 8dff913fc410d6d286e0f56ecd36878b in index $I30 of file 57478.
The file reference 0x1000000010406 of index entry 8DFF91~1 of index $I30
with parent 0xe086 is not the same as 0x20c000000010406.
Deleting index entry 8DFF91~1 in index $I30 of file 57478.
The file reference 0x1000000010424 of index entry c20a9125d57fc9edbd48bd80e0026711 of index $I30
with parent 0xe086 is not the same as 0x99000000010424.
Deleting index entry c20a9125d57fc9edbd48bd80e0026711 in index $I30 of file 57478.
The file reference 0x1000000010424 of index entry C20A91~1 of index $I30
with parent 0xe086 is not the same as 0x99000000010424.
Deleting index entry C20A91~1 in index $I30 of file 57478.
The file reference 0x200000001041d of index entry d6ff317798affe13d00ca44eb93c96d0 of index $I30
with parent 0xe086 is not the same as 0x14700000001041d.
Deleting index entry d6ff317798affe13d00ca44eb93c96d0 in index $I30 of file 57478.
The file reference 0x200000001041d of index entry D6FF31~1 of index $I30
with parent 0xe086 is not the same as 0x14700000001041d.
Deleting index entry D6FF31~1 in index $I30 of file 57478.
Unable to locate the file name attribute of index entry localconfig.vdf
of index $I30 with parent 0xf3ec in file 0x10435.
Deleting index entry localconfig.vdf in index $I30 of file 62444.
Unable to locate the file name attribute of index entry LOCALC~1.VDF
of index $I30 with parent 0xf3ec in file 0x10435.
Deleting index entry LOCALC~1.VDF in index $I30 of file 62444.
The file reference 0x3000000010401 of index entry state of index $I30
with parent 0x103ce is not the same as 0x99000000010401.
Deleting index entry state in index $I30 of file 66510.
The file reference 0x1000000010404 of index entry BITB63D.tmp of index $I30
with parent 0x103d9 is not the same as 0x56000000010404.
Deleting index entry BITB63D.tmp in index $I30 of file 66521.
The file reference 0x1000000010402 of index entry cbshandler of index $I30
with parent 0x103d9 is not the same as 0xd000000010402.
Deleting index entry cbshandler in index $I30 of file 66521.
The file reference 0x1000000010402 of index entry CBSHAN~1 of index $I30
with parent 0x103d9 is not the same as 0xd000000010402.
Deleting index entry CBSHAN~1 in index $I30 of file 66521.
The file reference 0x1000000010423 of index entry BITC68B.tmp of index $I30
with parent 0x103f0 is not the same as 0xe000000010423.
Deleting index entry BITC68B.tmp in index $I30 of file 66544.
The file reference 0x100000001040c of index entry BITB90D.tmp of index $I30
with parent 0x103f6 is not the same as 0x5000000001040c.
Deleting index entry BITB90D.tmp in index $I30 of file 66550.
The file reference 0x100000001040a of index entry cbshandler of index $I30
with parent 0x103f6 is not the same as 0xf100000001040a.
Deleting index entry cbshandler in index $I30 of file 66550.
The file reference 0x100000001040a of index entry CBSHAN~1 of index $I30
with parent 0x103f6 is not the same as 0xf100000001040a.
Deleting index entry CBSHAN~1 in index $I30 of file 66550.
The file reference 0x1000000010418 of index entry state of index $I30
with parent 0x103f9 is not the same as 0xd000000010418.
Deleting index entry state in index $I30 of file 66553.
The file reference 0x1000000010420 of index entry state of index $I30
with parent 0x103fa is not the same as 0x41000000010420.
Deleting index entry state in index $I30 of file 66554.
The file reference 0x2000000010419 of index entry BITC1E7.tmp of index $I30
with parent 0x103fd is not the same as 0x58000000010419.
Deleting index entry BITC1E7.tmp in index $I30 of file 66557.
The file reference 0x1000000010400 of index entry state of index $I30
with parent 0x103ff is not the same as 0x1e000000010400.
Deleting index entry state in index $I30 of file 66559.
The index bitmap for index $I30 in file 0x10401 is invalid or missing.
Correcting error in index $I30 for file 66561.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0x10401.
Correcting error in index $I30 for file 66561.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 02 91 6d 49 c8 cd 01 ...........mI...
00 02 91 6d 49 c8 cd 01 fa 37 d2 df d3 1e ce 01 ...mI....7......
Sorting index $I30 in file 66561.
An index entry of index $I30 in file 0x10426 points to file 0x2c783
which is beyond the MFT.
Deleting index entry 5 001.jpg in index $I30 of file 66598.
An index entry of index $I30 in file 0x10426 points to file 0x2c783
which is beyond the MFT.
Deleting index entry 5001~1.JPG in index $I30 of file 66598.
An index entry of index $I30 in file 0x10426 points to file 0x2c77b
which is beyond the MFT.
Deleting index entry Thumbs.db in index $I30 of file 66598.
97918 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file APPLES~1 (66561) into directory file 273.
Recovering orphaned file Apple Software Update (66561) into directory file 273.
Recovering orphaned file KB2160~1.HTM (66562) into directory file 3562.
Recovering orphaned file KB2160841_20101212_105659612.html (66562) into directory file 3562.
Recovering orphaned file BF2_PA~1.EXE (66574) into directory file 517.
Recovering orphaned file BF2_Patch_1.41.exe (66574) into directory file 517.
Recovering orphaned file Plugins (66578) into directory file 66561.
Recovering orphaned file E269C0~1.CDF (66583) into directory file 10057.
Recovering orphaned file e25e4e4b1716ce0177110000c005cc05.$$_system32_migwiz_dlmanifests_microsoft-windows-wmi-core_0fa6ec0ad029fddb.cdf-ms (66583) i</Data>
</EventData>
</Event>
m
0
l
March 23, 2013 5:48:27 PM

Okay, I have a serious problem now. I bought a new drive and was going through the Intial Installation of windows 7 and was copying windows files and expanding features. This process completed and when doing the first Intial restart to complete installation the PC is now stuck in endless loop of turning on and off. Nothing shows up on the screen and the PC will turn off after 5-15 seconds followed by a beep but will then turn back on. I cannot cannot complete windows installation

EDIT: I removed a stick of 2GB ram and the PC was able to restart and complete windows 7 x64 home installation. So far it runs fine all that is left is to have PC running for a period of time and see if works fine again. I'll update in a while of the status. For now thanks for your help guys!
m
0
l

Best solution

a c 204 $ Windows 7
March 23, 2013 8:11:33 PM

do a memtest with your ram stick one at the time,also for the code 0141 if you goole it that tel you the drive is defective if this wd drive is still under warranrty ask for advance rma .
Share
March 23, 2013 8:30:17 PM

scout_03 said:
do a memtest with your ram stick one at the time,also for the code 0141 if you goole it that tel you the drive is defective if this wd drive is still under warranrty ask for advance rma .


Alright thanks, I think I'm just going to replace my RAM. I have to say I was so nervous when using my PC, every little pause or black screen made me go "oh crap!". After running various programs for 2 hours+ All seems to be well though, Thank God!

Lastly do you have any recommendations for 8GB of RAM DDR3 preferably in 1333mhz. Thank you again
m
0
l
a c 204 $ Windows 7
March 23, 2013 8:32:40 PM

one other thing if this ram came as a dual set you have to replace both of them there could be still under warranty so ask rma for them .
m
0
l
March 23, 2013 9:00:01 PM

scout_03 said:
one other thing if this ram came as a dual set you have to replace both of them there could be still under warranty so ask rma for them .


I bought the RAM second hand on eBay 3 years ago actually. They are Avant Brand
m
0
l
!