Solved Windows 7 laptop takes 20-25 minutes to shut down, even from Safe Mode

[Duckbill]

I can't uninstall Risen, it's my favourite game and I haven't beaten chapter three yet. I will uninstall TOR though. CCleaner files attached.

 

[karlsnooks]

Now I know that you are not going to believe me, but keep the faith.

WIN | type MSCONFIG | ENTER | STARTUP tab |
Uncheck ALL

REBOOT!

You have just told Win 7 to not run unchecked programs at start up time.

You have not disabled the programs. They will be run when needed.

WIN = key with the Microsoft logo on top

=====================================

Just do it and be amazed at the performance improvement.
After your system is working correctly, then you can go back and check anything that you, right now, think is absolutely essential to run at startup time.

 

[karlsnooks]

Now here is another one you won't believe, but one again just keep the faith.

CCLEANER | TOOLS icon | STARTUP tab | SCHEDULED TASKS tab |
Use DISABLE button to disable ALL

Close CCleaner.


REBOOT!

You have not disabled any programs. You have disabled the scheduled running.
Later, after your system is running smoothly, you may reenable desired programs.

 

[karlsnooks]

Duckbill,

Oh my god! I've just looked at your install list. What a chamber of horrows!

Now I'm going to list some programs to delete as a start.

You could do me afavor by uninstalling everything not dear to your heart.

You would be doing yourself a real big favor by uninstalling everything yo don't need.

Your system will run better, faster, fewer bsods.

Now let's start with:

UNINSTALL

Bonjour    Apple Inc.    
Process Hacker 2.27 (r4957)
Secunia PSI (2.0.0.3003)
Spybot - Search & Destroy    
SUPERAntiSpyware    
µTorrent

REBOOT

I included Secunia because you version is old. Secunia is a great program. You will want to get the latest version.

I know. Once again, you saying no way I'l do that. Once again, Keep the faith.

Now here comes a sermon:

REMOVAL OF P2P PROGRAMS

There are signs of one or more P2P (Peer to Peer) File Sharing Programs on your computer.

As long as you are using any form of P2P networking to download files, you can anticipate malware infestations.

References citing the risk of using P2P programs:
How cyber criminals infect victims via P2P with pirated software on Vimeo
Malware: Help prevent the Infection
Perils of P2P File Sharing
How to Prevent the Online Invasion of Spyware and Adware
The Hidden Security Risks of P2P Traffic


I strongly recommend that you uninstall:
µTorrent
BitTorrent
Vuze

 

[Duckbill]

OK, I disabled all that startup stuff and scheduled tasks, and uninstalled the stuff you recommended, and updated Secunia. Unfortunately my shutdown is still at 23 minutes from pressing the button to powering off.

Edit: I mean my shutdown after doing all that and then rebooting, obviously.

 

[karlsnooks]

are you connected to a home network?

Please post an updated set of CCleaner files.
thanks,
karl

 

[Duckbill]

I'm connected via wifi to a Sky home router. Turning off the wifi before shutting down makes no difference. Updated files attached.

 

[karlsnooks]

can you run the computer standalone, no router, no wifi, no internet?

Please do and let me know what the startup & shutdown times are.
thanks,
karl

 

[NoelDP]

Please run an MGADiag report - it may give us some clues....

We need to see a full copy of the report produced by the MGADiag tool
(download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
Once saved, run the tool.
Click on the Continue button, which will produce the report.
To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.

 

[gregrocker]

Is this Dell Factory OEM which came with Win7? If not how is it activated?

When was the last time you had a Clean Reinstall?

You should do one now and take the time to get it perfect by following the steps in Clean Reinstall - Factory OEM Windows 7.

Afterwards try to limit the program installs to only those you regularly use, run a Clean Boot, and use the tools and methods suggested to keep a perfect install.

 

[F5ing]

Sorry I didn't get back to you, but I found out that my hard drive is failing. No idea if that's what's causing the problem, but it's a bit more important so I'm putting this on hold until I can deal with that.

Did you resolve the hard drive issue?

 

[Duckbill]

The hard drive issue is not resolved yet, I just wish I could be sure that that's what's causing this.

The last time I did a clean reinstall was probably April of last year, the computer got a virus shortly after I bought it and reinstalling Windows was the only way to fix it. I reinstalled from the Dell install disks that I got with it. I guess if I reinstall Windows and the problem persists, then I'll know it's the hard drive.

Here's the MGADiag report, anyway:



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

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-QCPVQ-KHRB8-RMV82
Windows Product Key Hash: +Rj3N34NLM2JqoBO/OzgzTZXgbY=
Windows Product ID: 00359-OEM-8992687-00095
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {CC12C411-C9B9-4CE0-9C68-F8ABAFEAF06C}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
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: B4D0AA8B-604-645_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\Lauren\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-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{CC12C411-C9B9-4CE0-9C68-F8ABAFEAF06C}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-RMV82</PKey><PID>00359-OEM-8992687-00095</PID><PIDType>2</PIDType><SID>S-1-5-21-771184983-408989836-3582927627</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Inspiron N5010</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A12</Version><SMBIOSVersion major="2" minor="6"/><Date>20110125000000.000000+000</Date></BIOS><HWID>B3D73307018400FC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>WN09 </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, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800095-02-1033-7600.0000-0972011
Installation ID: 003853872346851786794691989284581515100873461062839072
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: RMV82
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 17/07/2012 10:37:53

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 7:12:2012 19:02
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: NAAAAAIAAQABAAEAAQACAAAAAwABAAEA6GECnxU/KnyoQq7E2rB39mI96prg3YAWAARcXQ==

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 DELL WN09
FACP DELL WN09
HPET DELL WN09
MCFG DELL WN09
SSDT AMICPU PROC
SLIC DELL WN09
OSFR DELL M08

 

[NoelDP]

First back up your data to external storage!
then....

Please run a full CHKDSK and SFC scan....
type in the Search box
CMD.EXE
right-click on the only file that is found
Select Run as Administrator
- 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, 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) - then run the SFC

SFC -System File Checker - Instructions
Click on the Start button
type in the Search box
CMD.EXE
right-click on the only file that is found
Select Run as Administrator - the Elevated Command Prompt window should pop up
At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.
Post the Event Viewer entry from the Windows Application log - source Wininit - for your CHKDSK results.

 

[F5ing]

After you complete the steps outlined by NoelDP, download and run the following to check your WD hard drive:

WD Support / Downloads / SATA & SAS / WD VelociRaptor

Don't worry that the product on that page doesn't match yours, they recommend use of the same app for the majority of their hard drives. One of these days I might find a direct link, bypassing their product pages...

 

[Duckbill]

Thanks everyone. OK, here is the Event Viewer entry for the chkdsk I ran this morning. The chkdsk did complete successfully but the Event Viewer text seems to cut off in the middle, I don't know why that is. I'm running the SFC scan now, and will run the WD diagnostic after that.


Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 17/07/2012 15:40:49
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Rachel
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 5)...
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x5273a9 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xad3a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 44346.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x21399dc for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x24396 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 148374.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2140ce4 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2490d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 149773.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x25ac2d1 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x27f17 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 163607.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x526e5f for possibly 0x100 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2b851 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 178257.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2747fa0 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2fbbd is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 195517.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2b644b1 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x30e6c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 200300.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x220e454 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x30ea7 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 200359.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x2b64259 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x30f59 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 200537.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2b6396c for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x311e8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 201192.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2b5ab4c for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32e0d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 208397.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2c42620 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x38a1a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 231962.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x2cc9a18 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x38b2b is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 232235.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2c4112c for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x38b32 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 232242.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2c42437 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x38f7c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 233340.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2f08d38 for possibly 0x4d8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3a04c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 237644.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xd6cc40 for possibly 0x1988 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x42ae9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 273129.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x220e457 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x4dc4b is already in use.
Deleted corrupt attribute list entry
with type code 128 in file 318539.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x34000000020193. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 131475.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x285000000038e78. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 233080.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x30c000000039759. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 235353.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2ebc168 for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x4fa08 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 326152.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x2f118db for possibly 0xcf8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x5554e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 349518.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x27374a4 for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x55b64 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 351076.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2b64b70 for possibly 0x2b clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x57b2d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 359213.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2c2c186 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x607ab is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 395179.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2c41134 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x629be is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 403902.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x2c295b7 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x65728 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 415528.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd6eb0e for possibly 0x905 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x66fa8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 421800.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x24fa21c for possibly 0x382 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x6702a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 421930.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2c41130 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7726b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 488043.
2188032 file records processed.

File verification completed.
Deleting orphan file record segment 131475.
Deleting orphan file record segment 233080.
Deleting orphan file record segment 235353.
1336 large file records processed.

0 bad file records processed.

0 EA records processed.

92 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
The object id index entry in file 0x19 points to file 0x4a9cb
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The file reference 0x24b000000038ff4 of index entry FAEFAD~1.ICO of index $I30
with parent 0x17dc is not the same as 0x249000000038ff4.
Deleting index entry FAEFAD~1.ICO in index $I30 of file 6108.
The file reference 0x24b000000038ff4 of index entry faviconCA3IZH8K.ico of index $I30
with parent 0x17dc is not the same as 0x249000000038ff4.
Deleting index entry faviconCA3IZH8K.ico in index $I30 of file 6108.
The file reference 0x2e700000003c53b of index entry FAEA2E~1.ICO of index $I30
with parent 0x17e7 is not the same as 0x2e500000003c53b.
Deleting index entry FAEA2E~1.ICO in index $I30 of file 6119.
The file reference 0x2e700000003c53b of index entry faviconCAS0TLAY.ico of index $I30
with parent 0x17e7 is not the same as 0x2e500000003c53b.
Deleting index entry faviconCAS0TLAY.ico in index $I30 of file 6119.
The index bitmap $I30 in file 0x207d is incorrect.
Correcting error in index $I30 for file 8317.
The multi-sector header signature for VCN 0xa of index $I30
in file 0x6837 is incorrect.
79 dc 1b 61 69 cb 7d 9c 10 81 10 e4 e4 23 4a 2a y..ai.}......#J*
55 6e c5 89 c9 8c 97 fb 01 6f c6 3f ff f1 94 e8 Un.......o.?....
Correcting error in index $I30 for file 26679.
The index bitmap $I30 in file 0x6837 is incorrect.
Correcting error in index $I30 for file 26679.
The down pointer of current index entry with length 0x78 is invalid.
1d a2 08 00 00 00 09 00 78 00 5a 00 01 00 00 00 ........x.Z.....
37 68 00 00 00 00 ac 05 7b 8d bc 5f 63 d7 cc 01 7h......{.._c...
49 13 ab 96 62 d7 cc 01 a6 9f 63 24 63 d7 cc 01 I...b.....c$c...
7b 8d bc 5f 63 d7 cc 01 00 00 00 00 00 00 00 00 {.._c...........
00 00 00 00 00 00 00 00 20 20 00 00 00 00 00 00 ........ ......
0c 02 4d 00 41 00 44 00 39 00 43 00 33 00 7e 00 ..M.A.D.9.C.3.~.
31 00 2e 00 44 00 41 00 54 00 72 00 72 00 6f 00 1...D.A.T.r.r.o.
ff ff ff ff ff ff ff ff cb e6 02 00 00 00 78 05 ..............x.
b8 00 9a 00 01 00 00 00 37 68 00 00 00 00 ac 05 ........7h......
Sorting index $I30 in file 26679.
The file reference 0x61000000053415 of index entry messages.json of index $I30
with parent 0x11847 is not the same as 0x91000000053415.
Deleting index entry messages.json in index $I30 of file 71751.
The file reference 0x61000000053415 of index entry MESSAG~1.JSO of index $I30
with parent 0x11847 is not the same as 0x91000000053415.
Deleting index entry MESSAG~1.JSO in index $I30 of file 71751.
The index bitmap for index $I30 in file 0x30f59 is invalid or missing.
Correcting error in index $I30 for file 200537.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0x30f59.
Correcting error in index $I30 for file 200537.
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 78 10 3e 85 84 c4 01 .........x.>....
00 78 10 3e 85 84 c4 01 4f 65 4d e2 fc f8 cb 01 .x.>....OeM.....
Sorting index $I30 in file 200537.
The index bitmap for index $I30 in file 0x38b2b is invalid or missing.
Correcting error in index $I30 for file 232235.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0x38b2b.
Correcting error in index $I30 for file 232235.
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 f1 c8 6b ef 02 6f cc 01 ..........k..o..
02 f0 6b ef 02 6f cc 01 02 f0 6b ef 02 6f cc 01 ..k..o....k..o..
Sorting index $I30 in file 232235.
Unable to locate the file name attribute of index entry lsasrv.mof
of index $I30 with parent 0x511a2 in file 0x8739.
Deleting index entry lsasrv.mof in index $I30 of file 332194.
Unable to locate the file name attribute of index entry lsasrv.mof
of index $I30 with parent 0x511a9 in file 0x8736.
Deleting index entry lsasrv.mof in index $I30 of file 332201.
Unable to locate the file name attribute of index entry lsasrv.dll
of index $I30 with parent 0x511bd in file 0x4b6b9.
Deleting index entry lsasrv.dll in index $I30 of file 332221.
Unable to locate the file name attribute of index entry lsasrv.mof
of index $I30 with parent 0x511bd in file 0x8739.
Deleting index entry lsasrv.mof in index $I30 of file 332221.
Unable to locate the file name attribute of index entry lsasrv.mof
of index $I30 with parent 0x511df in file 0x8736.
Deleting index entry lsasrv.mof in index $I30 of file 332255.
The index bitmap for index $I30 in file 0x65728 is invalid or missing.
Correcting error in index $I30 for file 415528.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0x65728.
Correcting error in index $I30 for file 415528.
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 01 92 c1 94 73 ce cc 01 ............s...
00 61 43 41 dd 46 c7 01 28 fd 51 04 7b ce cc 01 .aCA.F..(.Q.{...
Sorting index $I30 in file 415528.
2296950 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file MAC352~1.DAT (638) into directory file 26679.
Recovering orphaned file MA9577~1.DAT (3695) into directory file 26679.
Recovering orphaned file MA9E83~1.DAT (6398) into directory file 26679.
Recovering orphaned file MAB68D~1.DAT (6503) into directory file 26679.
Recovering orphaned file MA3661~1.DAT (15525) into directory file 26679.
Recovering orphaned file MA2B1C~1.DAT (16041) into directory file 26679.
Recovering orphaned file MA220B~1.DAT (16147) into directory file 26679.
Recovering orphaned file MA93B2~1.DAT (16202) into directory file 26679.
Recovering orphaned file MA4978~1.DAT (157503) into directory file 26679.
Recovering orphaned file MA4FF2~1.DAT (187228) into directory file 26679.
Recovering orphaned file MAC9A0~1.DAT (190155) into directory file 26679.
Recovering orphaned file MAB7CB~1.DAT (193750) into directory file 26679.
Recovering orphaned file MAB8BD

 

[NoelDP]

Yikes! - What did you do to your poor hard drive to make it that bad??
You should probably run another CHKDSK - but of a lower rating this time

CHKDSK C: /F
(this should complete a lot faster).

Again, please post the new report.

 

[Duckbill]

OK, I ran the SFC scan and got the message:
'Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

The system file repair changes will take effect after the next reboot.'

I looked at that log file but it's over 18MB and I don't know which bits of it are important. I'm going to run the WD diagnostic and the second CHKDSK next.

 

[NoelDP]

Ouch!
Please upload it to your SkyDrive (if you have one) or other favoured fileshare site (you'll need to copy it to the desktop first, as you can't work on the file itself) and post a link - it's too big for the forum (Zipping it may reduced it significantly - it's worth trying).

 

[Duckbill]

Oh, zipping it worked well. Here it is.

 

[NoelDP]

You need to reboot and run SFC /SCANNOW at least twice more - there's unfinished business there, by the look of it.
Once you've done that, post another CBS log.

*please reboot between runs of SFC!*