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: Windows 7 giving WAT not running genuine windows message

17 Jan 2013   #11
jaycul2k

Windows 7 Ultimate x64
 
 

Sure, here you go


My System SpecsSystem Spec
.
18 Jan 2013   #12
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

There's significant problems in there .....
Code:
 Line 68605: 2013-01-17 10:04:53, Info                  CSI    000003fa [SR] Repairing 6 components
 Line 68606: 2013-01-17 10:04:53, Info                  CSI    000003fb [SR] Beginning Verify and Repair transaction
 Line 68609: 2013-01-17 10:04:53, Info                  CSI    000003fd [SR] Cannot repair member file [l:24{12}]"dciman32.dll" of Microsoft-Windows-GDI, Version = 6.1.7601.18032, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68612: 2013-01-17 10:04:53, Info                  CSI    000003ff [SR] Cannot repair member file [l:22{11}]"iscsium.dll" of Microsoft-Windows-iSCSI_Initiator_Service, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68615: 2013-01-17 10:04:53, Info                  CSI    00000401 [SR] Cannot repair member file [l:24{12}]"splwow64.exe" of Microsoft-Windows-Printing-Spooler-Splwow64, Version = 6.1.7601.17777, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68618: 2013-01-17 10:04:53, Info                  CSI    00000403 [SR] Cannot repair member file [l:20{10}]"vdsldr.exe" of Microsoft-Windows-VirtualDiskService, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68621: 2013-01-17 10:04:53, Info                  CSI    00000405 [SR] Cannot repair member file [l:16{8}]"Sens.dll" of Microsoft-Windows-Sens-Service, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68624: 2013-01-17 10:04:53, Info                  CSI    00000407 [SR] Cannot repair member file [l:16{8}]"d2d1.dll" of Microsoft-Windows-D2D, Version = 6.1.7601.17563, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68625: 2013-01-17 10:04:53, Info                  CSI    00000408 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:24{12}]"dciman32.dll" by copying from backup
 Line 68626: 2013-01-17 10:04:53, Info                  CSI    00000409 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:24{12}]"dciman32.dll" from store
 Line 68627: 2013-01-17 10:04:53, Info                  CSI    0000040a [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[ml:24{12},l:22{11}]"iscsium.dll" by copying from backup
 Line 68630: 2013-01-17 10:04:53, Info                  CSI    0000040c [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:22{11}]"iscsium.dll" from store
 Line 68631: 2013-01-17 10:04:53, Info                  CSI    0000040d [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:20{10}]"vdsldr.exe" by copying from backup
 Line 68634: 2013-01-17 10:04:53, Info                  CSI    0000040f [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:20{10}]"vdsldr.exe" from store
 Line 68635: 2013-01-17 10:04:53, Info                  CSI    00000410 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:16{8}]"Sens.dll" by copying from backup
 Line 68638: 2013-01-17 10:04:53, Info                  CSI    00000412 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\windows\SysWOW64"\[l:16{8}]"Sens.dll" from store
 Line 68639: 2013-01-17 10:04:54, Info                  CSI    00000413 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:24{12}]"splwow64.exe" by copying from backup
 Line 68642: 2013-01-17 10:04:54, Info                  CSI    00000415 [SR] Repairing corrupted file [ml:520{260},l:28{14}]"\??\C:\windows"\[l:24{12}]"splwow64.exe" from store
 Line 68643: 2013-01-17 10:04:54, Info                  CSI    00000416 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:16{8}]"d2d1.dll" by copying from backup
 Line 68646: 2013-01-17 10:04:54, Info                  CSI    00000418 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\windows\SysWOW64"\[l:16{8}]"d2d1.dll" from store
 Line 68675: 2013-01-17 10:04:54, Info                  CSI    0000041a [SR] Repair complete
 Line 68676: 2013-01-17 10:04:54, Info                  CSI    0000041b [SR] Committing transaction
 Line 68681: 2013-01-17 10:04:54, Info                  CSI    0000041f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
All these problems appear to have been solved.

Please run a new SFC scan and post the new CBS log - this should confirm it.
Then reboot, and create a manual Restore Point
Please also run a new CheckSUR scan (after backups!) and see if you get a better result this time.
My System SpecsSystem Spec
18 Jan 2013   #13
jaycul2k

Windows 7 Ultimate x64
 
 

Ran SFC again, rebooted, and attached the log.

Ran a new CheckSUR scan with no problems.

Ran another MGA Diagnostic, and copied results

Code:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0x8004FE21
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-X92GV-V7DCV-P4K27
Windows Product Key Hash: aU2z1/fnhnLHmhBm699qYZT2E6s=
Windows Product ID: 00426-OEM-8992662-00400
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {DDC101A9-B226-4689-A1D7-515C8BCDB556}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE; Win32)
Default Browser: C:\Users\Jason\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:\windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100
File Mismatch: C:\windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:\windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:\windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100
File Mismatch: C:\windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80092003
File Mismatch: C:\windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100
File Mismatch: C:\windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{DDC101A9-B226-4689-A1D7-515C8BCDB556}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-P4K27</PKey><PID>00426-OEM-8992662-00400</PID><PIDType>2</PIDType><SID>S-1-5-21-2048840114-538357040-3838390185</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>XPS L701X   </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A07</Version><SMBIOSVersion major="2" minor="6"/><Date>20101224000000.000000+000</Date></BIOS><HWID>C36D3E07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>QA09   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00178-926-600400-02-1033-7600.0000-0352011
Installation ID: 012602492244325031717991980271866560623823727730241592
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: P4K27
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 1/18/2013 7:51:05 AM

Windows Activation Technologies-->
HrOffline: 0x8004FE21
HrOnline: N/A
HealthStatus: 0x000000000000A8B0
Event Time Stamp: 1:17:2013 21:04
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
Tampered File: %systemroot%\system32\sppobjs.dll
Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
Tampered File: %systemroot%\system32\sppwinob.dll
Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui


HWID Data-->
HWID Hash Current: MAAAAAEAAQABAAEAAAACAAAAAwABAAEAHKIESaCzKn5OCpRhzp9a67CHPoQKcHZW

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			PTLTD 			 APIC  
  FACP			INTEL 		CALPELLA
  HPET			INTEL 		CALPELLA
  BOOT			PTLTD 		$SBFTBL$
  MCFG			INTEL 		CALPELLA
  SLIC			DELL  		QA09   
  OSFR			DELL  		DELL    
  ASF!			  CETP		    CETP
  SSDT			PmRef		CpuPm
My System SpecsSystem Spec
.

18 Jan 2013   #14
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

The CBS log is interesting - it's a shame I don't understand the ramifications
The SFC scan didn't find any problems.... but the section after it ran is the interesting bit
KB2726535 seems to be stuck in staging - but Windows isn't worried about it

I suspect that there's either a dll file unregistered somewhere, or registry corruption - or possibly a broken certificate (although I would have expected that to impact more files).
Have you been using any form or registry cleaner or optimizer??
My System SpecsSystem Spec
18 Jan 2013   #15
jaycul2k

Windows 7 Ultimate x64
 
 

No, I've used programs such as Combofix, Spybot, and Malwarebytes for dealing with the occasional virus and whatnot, but certainly not any specific Registry cleaners or optimizers.

I can tell you that before this all started I had been having some issues with the DC power jack before this started, and there were times when the battery drained completely, and the power would cut midboot. Soon after this was fixed, the computer flagged itself to run scandisk at which time it found literally a few hundred errors as it went through, and I started receiving some .dll messages when I would login to windows.

So it is quite possible that the registry also got messed up during that time.
My System SpecsSystem Spec
18 Jan 2013   #16
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Ah.
Please open the Event Viewer
Navigate in the left pane to the Windows logs/Application
look in the error list (or filter it) for Wininit events - doubleclick on the latest to open it, and click on the Copy button.
Past the result in your reply.
My System SpecsSystem Spec
18 Jan 2013   #17
jaycul2k

Windows 7 Ultimate x64
 
 

Code:
Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          1/1/2013 8:03:58 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Jason-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


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 0x4 is cross linked
starting at 0x1f for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xc05 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3077.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x285 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x1051 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 4177.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x2f5 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x1936 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 6454.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x166c for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x4e9a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 20122.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x490d for possibly 0x70 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x5b93 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 23443.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xe395 for possibly 0x2c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7ccf is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 31951.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xe8fb for possibly 0x29 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x847d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 33917.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x17c9 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xc3ca is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 50122.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2d73 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xc42d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 50221.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x6f88 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0xc7c0 is already in use.
Deleted corrupt attribute list entry
with type code 128 in file 51136.
Unable to locate attribute with instance tag 0x5 and segment
reference 0x1b00000000c7c1.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 51137.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x45f3 for possibly 0xa clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xccb8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 52408.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x69a for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xd40c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54284.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x970 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xd416 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54294.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x237d for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xd5c3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54723.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x27e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xf313 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 62227.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb2f for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xf837 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 63543.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x559 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xf8a0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 63648.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x53dc for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10675 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 67189.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x28e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x11136 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 69942.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x4f03 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x1116a is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 69994.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xaa21 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x11a71 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 72305.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x81de4 for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x15615 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 87573.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1854 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x156ba is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 87738.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x6eba for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x15922 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 88354.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2fbc for possibly 0x40 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x15c1a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 89114.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x14c7 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x15e97 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 89751.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2a5 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x160da is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90330.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x46d8 for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x160e6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90342.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4ee7 for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16100 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90368.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4efe for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16107 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90375.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4eef for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1610d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90381.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4ef7 for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16110 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90384.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6e96 for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16118 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90392.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6ea3 for possibly 0xc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1619a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90522.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xc56 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x161d6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90582.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6a74 for possibly 0x18 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1620a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90634.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xc84 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16260 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90720.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1fb for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x162da is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90842.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x103f for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x162de is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90846.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6eaf for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x162fc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90876.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x371 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16441 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91201.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xad40 for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1647c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91260.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe94c for possibly 0xe clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1647f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91263.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6b1e for possibly 0x15 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1678b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 92043.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x12 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1679b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 92059.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x456c for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1770b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 96011.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xbb93 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x178ca is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 96458.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xe9ac for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x17a3b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 96827.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6eb1 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x17b46 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 97094.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x644 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x17d6f is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 97647.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x704 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x17f0d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 98061.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x7558 for possibly 0xa clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x180a3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 98467.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xf71e for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x18512 is already in use.
Deleting corrupt attribute record (128, ""
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-01-02T01:03:58.000000000Z" />
    <EventRecordID>6931</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Jason-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


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 0x4 is cross linked
starting at 0x1f for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xc05 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3077.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x285 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x1051 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 4177.
My System SpecsSystem Spec
18 Jan 2013   #18
jaycul2k

Windows 7 Ultimate x64
 
 

Here is part 2...

Code:
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x2f5 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x1936 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 6454.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x166c for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x4e9a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 20122.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x490d for possibly 0x70 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x5b93 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 23443.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xe395 for possibly 0x2c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7ccf is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 31951.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xe8fb for possibly 0x29 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x847d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 33917.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x17c9 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xc3ca is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 50122.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2d73 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xc42d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 50221.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x6f88 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0xc7c0 is already in use.
Deleted corrupt attribute list entry
with type code 128 in file 51136.
Unable to locate attribute with instance tag 0x5 and segment
reference 0x1b00000000c7c1.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 51137.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x45f3 for possibly 0xa clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xccb8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 52408.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x69a for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xd40c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54284.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x970 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xd416 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54294.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x237d for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xd5c3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54723.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x27e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xf313 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 62227.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb2f for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xf837 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 63543.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x559 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xf8a0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 63648.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x53dc for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10675 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 67189.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x28e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x11136 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 69942.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x4f03 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x1116a is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 69994.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xaa21 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x11a71 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 72305.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x81de4 for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x15615 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 87573.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1854 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x156ba is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 87738.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x6eba for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x15922 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 88354.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2fbc for possibly 0x40 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x15c1a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 89114.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x14c7 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x15e97 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 89751.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2a5 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x160da is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90330.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x46d8 for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x160e6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90342.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4ee7 for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16100 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90368.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4efe for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16107 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90375.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4eef for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1610d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90381.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4ef7 for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16110 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90384.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6e96 for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16118 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90392.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6ea3 for possibly 0xc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1619a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90522.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xc56 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x161d6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90582.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6a74 for possibly 0x18 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1620a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90634.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xc84 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x16260 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90720.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1fb for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x162da is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90842.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x103f for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x162de is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90846.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6eaf for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x162fc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 90876.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x371 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16441 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91201.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xad40 for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1647c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91260.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe94c for possibly 0xe clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1647f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91263.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6b1e for possibly 0x15 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1678b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 92043.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x12 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1679b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 92059.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x456c for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1770b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 96011.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xbb93 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x178ca is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 96458.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xe9ac for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x17a3b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 96827.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6eb1 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x17b46 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 97094.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x644 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x17d6f is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 97647.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x704 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x17f0d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 98061.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x7558 for possibly 0xa clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x180a3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 98467.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xf71e for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x18512 is already in use.
Deleting corrupt attribute record (128, ""</Data>
  </EventData>
</Event>
My System SpecsSystem Spec
18 Jan 2013   #19
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

OUCH!
Please run a full CHKDSK, then post the new event report - this one might contain more useful data (that one overflowed the buffer in the Event)


Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -
My System SpecsSystem Spec
18 Jan 2013   #20
jaycul2k

Windows 7 Ultimate x64
 
 

In the meantime while I'm waiting for the 2-3 hours that will take... that was the event with all the errors. I ran a full chkdsk /r since then. Here is the log of that.

Code:
Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          1/14/2013 3:47:32 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Jason-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


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)...
  293120 file records processed.                                         

File verification completed.
  988 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  60 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 3)...
  359824 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 3)...
  293120 file SDs/SIDs processed.                                        

Cleaning up 29 unused index entries from index $SII of file 0x9.
Cleaning up 29 unused index entries from index $SDH of file 0x9.
Cleaning up 29 unused security descriptors.
Security descriptor verification completed.
  33353 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36230800 USN bytes processed.                                            

Usn Journal verification completed.
Windows has checked the file system and found no problems.

 717173397 KB total disk space.
 254839912 KB in 166085 files.
     99436 KB in 33354 indexes.
         0 KB in bad sectors.
    419249 KB in use by the system.
     65536 KB occupied by the log file.
 461814800 KB available on disk.

      4096 bytes in each allocation unit.
 179293349 total allocation units on disk.
 115453700 allocation units available on disk.

Internal Info:
00 79 04 00 1a 0b 03 00 64 76 05 00 00 00 00 00  .y......dv......
89 02 00 00 3c 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="2013-01-14T20:47:32.000000000Z" />
    <EventRecordID>7480</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Jason-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


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)...
  293120 file records processed.                                         

File verification completed.
  988 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  60 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 3)...
  359824 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 3)...
  293120 file SDs/SIDs processed.                                        

Cleaning up 29 unused index entries from index $SII of file 0x9.
Cleaning up 29 unused index entries from index $SDH of file 0x9.
Cleaning up 29 unused security descriptors.
Security descriptor verification completed.
  33353 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36230800 USN bytes processed.                                            

Usn Journal verification completed.
Windows has checked the file system and found no problems.

 717173397 KB total disk space.
 254839912 KB in 166085 files.
     99436 KB in 33354 indexes.
         0 KB in bad sectors.
    419249 KB in use by the system.
     65536 KB occupied by the log file.
 461814800 KB available on disk.

      4096 bytes in each allocation unit.
 179293349 total allocation units on disk.
 115453700 allocation units available on disk.

Internal Info:
00 79 04 00 1a 0b 03 00 64 76 05 00 00 00 00 00  .y......dv......
89 02 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....&lt;...........
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
Reply

 Windows 7 giving WAT not running genuine windows message




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
"This computer is not running Genuine Windows" message - still / again
When I got this message earlier this month, I searched around, read the posts here etc. After reading about the problem I let windows install KB3024777 to fix the KB3004394(?) problem. Everything appeared to work. January updates were installed. This was three days ago. But today I got the...
Windows Updates & Activation
Windows 7: Not running genuine Windows message error
So, I get this Windows 7: Not running genuine Windows error out of the blue. Weird. I hate it... I have tried doing sfc /scannow to chkdsk and the works. Nada. Help. Windows 7 64-Bit... Thank you. Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows...
Windows Updates & Activation
Not running genuine Windows Error message
HI My computer has been getting a popup saying that this computer is not running genuine windows. Can anyone help fix this? Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0x8004FE21 Cached Online Validation Code: N/A,...
Windows Updates & Activation
"This computer is not running Genuine Windows" message
Hi, all! I just got this computer four months ago and I am getting a "This computer is not running Genuine Windows" message every so often. I no longer have the Windows install disc that came with the computer. The computer is a Sony Vaio. Here is the diagnostic report: Diagnostic Report...
Windows Updates & Activation
This computer is not running genuine windows message
Hi, My laptop is running Windows 7 64bit home premium ed., I installed new larger HDD and cloned partitions from the old one, then I'm getting from time to time the message: This computer is not running genuine windows Here is MGADIAG report. Diagnostic Report (1.9.0027.0):...
Windows Updates & Activation
This computer is not running genuine windows message
Hi, I recently bought this used laptop, it came with Windows 7 64 bit installed, but no discs. I do have the original disc and activation code for Windows Vista 32 bit. I would like to keep this version of windows, actually I dont care but I dont want to have to reinstall all of my software. Is...
Windows Updates & Activation


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 09:27.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App