[SOLVED] How to fix errors found in the CheckSUR.log

[dantobal]

Hello - I'm seeking assistance correcting a few items found in my CheckSUR.log. I've attached the log. Any assitance would be appreciated. Thank you!

 

[BrianDrab]

Hi and welcome to Sysnative. Please start with the following.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

 

[dantobal]

Hi there - below are the file contents:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-01-04 21:24:49.982
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\DPT\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Winsxs\Manifests


Successfully copied file C:\Users\DPT\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.18097_none_f5cc81f43710cf0c.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.18097_none_f5cc81f43710cf0c.manifest.
Successfully copied file C:\Users\DPT\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-w..ent-internalupgrade_31bf3856ad364e35_7.6.7601.18847_none_2b7e84dc887fb298.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\amd64_microsoft-windows-w..ent-internalupgrade_31bf3856ad364e35_7.6.7601.18847_none_2b7e84dc887fb298.manifest.


Successfully restored ownership for C:\Windows\Temp\CheckSur\Winsxs\Manifests
Successfully restored permissions on C:\Windows\Temp\CheckSur\Winsxs\Manifests
PowerCopy:: directive completed successfully.








Successfully processed all directives.






Failed to generate a complete zip file. Upload aborted.




SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-01-04 21:56:15.431
Script hash: UCQXS9wWGROOHI/Z7Av/UNc6pn3c51HR5WST/IpnVVk=
----------------------EOF-----------------------

 

[BrianDrab]

Please do the following again.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

 

[dantobal]

Just confirming, you want me to run the SUR tool again? I ran it on 1/2 and attached the log to the first message in this thread.

If I do need to run again, do I need to download the file from Microsoft, or can I run the SUR tool I already downloaded?

Thanks!

 

[BrianDrab]

Yes, please run again. You can run from your already downloaded file.

 

[dantobal]

Apologies for what might be a silly question, but do you know what the name of the Check SUR file might be? It's not on my desktop but I assume it's somewhere in my "Downloads" folder. Thanks.

 

[BrianDrab]

Since you attached it to your initial post I incorrectly assumed you knew where it was. Sorry. It's at c:\windows\logs\cbs\checksur.log

 

[dantobal]

Down to 3. See below -

 

[BrianDrab]

This should fix the rest. Please do the following.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
2. Download SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

 

[dantobal]

File contents:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-01-06 19:40:04.465
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\DPT\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7601.17514_none_177a088436382a34
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7600.16385_none_1548f4bc3949a69a
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.22322_none_6a0c785f7ee0ef0f


Successfully copied file C:\Users\DPT\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7601.17514_none_177a088436382a34\unsecapp.exe to C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7601.17514_none_177a088436382a34\unsecapp.exe.
Successfully copied file C:\Users\DPT\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7600.16385_none_1548f4bc3949a69a\unsecapp.exe to C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7600.16385_none_1548f4bc3949a69a\unsecapp.exe.
Successfully copied file C:\Users\DPT\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.22322_none_6a0c785f7ee0ef0f\wmp.dll to C:\Windows\Winsxs\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.22322_none_6a0c785f7ee0ef0f\wmp.dll.


Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7601.17514_none_177a088436382a34
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7601.17514_none_177a088436382a34
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7600.16385_none_1548f4bc3949a69a
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7600.16385_none_1548f4bc3949a69a
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.22322_none_6a0c785f7ee0ef0f
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.22322_none_6a0c785f7ee0ef0f
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2017-01-06 19:40:08.876
Script hash: +/oXPKNASRmqgIWK8wxcD+Efi5HwiV/ffvJq8n2KBJk=
----------------------EOF-----------------------

 

[BrianDrab]

Go ahead and run the SUR tool again and provide log.

 

[dantobal]

Success?

 

[BrianDrab]

Yup. All set. Take care.

 

[dantobal]

Thank you!

 

[dantobal]

Unfortunately BSOD is back. I ran SFC Scan and it looks like there are still some corrupt files. .txt log attached.

 

[BrianDrab]

I didn't know you had a BSOD previously? As a result please do the following.

Step#1 - ChkDsk Scan
1. Click your Start Orb in the lower left of your computer and type cmd in the search box.
2. Once the cmd program is found, right-click on it with your mouse and select Run as administrator as shown below.

3. Answer Yes when asked to allow.
4. You should now have a black window open that you can type in to.
5. Please type chkdsk and then press enter.
6. Chkdsk will start to run. Please allow it to finish. You will know it is running when you see text as follows.

7. Download ListChkdskResult.exe by SleepyDude and save it on your desktop. If it's already downloaded to your desktop, just skip this step.
8. Right-click this file and select Run as administrator (Allow if prompted)and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.

 

[dantobal]

Contents below:

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013


------< Log generate on 1/19/2017 6:32:59 PM >------
Category: 0
Computer Name: DPT-PC
Event Code: 26212
Record Number: 118562
Source Name: Chkdsk
Time Written: 01-19-2017 @ 23:30:59
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.


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


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
349952 file records processed.


File verification completed.
1906 large file records processed.


0 bad file records processed.


4 EA records processed.


47 reparse records processed.


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


Index verification completed.
0 unindexed files scanned.


0 unindexed files recovered.


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


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


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


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


472985397 KB total disk space.
83398080 KB in 288167 files.
192304 KB in 51098 indexes.
0 KB in bad sectors.
468469 KB in use by the system.
65536 KB occupied by the log file.
388926544 KB available on disk.


4096 bytes in each allocation unit.
118246349 total allocation units on disk.
97231636 allocation units available on disk.


-----------------------------------------------------------------------
Category: 0
Computer Name: DPT-PC
Event Code: 1001
Record Number: 112745
Source Name: Microsoft-Windows-Wininit
Time Written: 10-03-2016 @ 23:11:43
Event Type: Information
User:
Message:


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 0x14d166 for possibly 0x12 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x7dff is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 32255.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9227fd for possibly 0x1061 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x89e9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 35305.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d180 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x8ae0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 35552.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14bd55 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa32c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41772.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14bd58 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa32d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41773.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14bd5c for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa32f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41775.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14c121 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa330 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41776.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14c124 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa331 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41777.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14c127 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa332 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41778.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d182 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa333 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41779.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d186 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa337 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 41783.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14bd60 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa6f2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 42738.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x19e464 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa824 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 43044.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x19e466 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa84e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 43086.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x19e468 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa863 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 43107.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x92610c for possibly 0xb92 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xaec2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 44738.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x926c9e for possibly 0x9ae clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xaec3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 44739.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x92764c for possibly 0xebf clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xaec6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 44742.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0xb12154 for possibly 0x1382 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0xc789 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 51081.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x14a8ea for possibly 0x8e8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x12ae9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 76521.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xb16deb for possibly 0x5fd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x13c37 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 80951.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d1e4 for possibly 0xb clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x18bd9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 101337.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1994fa for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1a409 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 107529.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x924320 for possibly 0x10b9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1c628 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 116264.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d178 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1dd00 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 122112.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x91fd49 for possibly 0x5b0 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1eb67 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 125799.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x9202fa for possibly 0x33e clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x20635 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 132661.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0xb10ccc for possibly 0xab0 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x206be is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 132798.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x14d42c for possibly 0x4c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2085d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 133213.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9210c0 for possibly 0x612 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x20ff9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 135161.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d506 for possibly 0xd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x215f1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 136689.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14b832 for possibly 0x55 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x223dc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 140252.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x71bd60 for possibly 0x46 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x25543 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 152899.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9d0dfc for possibly 0x20dd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x25f97 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 155543.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1994f8 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x262a1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 156321.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14dce0 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x287a2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 165794.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x920ad0 for possibly 0x28f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2c81d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 182301.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x920720 for possibly 0x80 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x2cb6c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 183148.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x9d6f78 for possibly 0xcc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x2dd22 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 187682.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14d7bd for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2f55e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 193886.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x923861 for possibly 0x94a clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x30350 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 197456.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x19e469 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x30f31 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 200497.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9d713f for possibly 0x2d9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x335d1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 210385.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb134d8 for possibly 0xa6c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3377b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 210811.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9d6349 for possibly 0x7aa clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x339c7 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 211399.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb173ea for possibly 0xa6c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x33b69 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 211817.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9d026c for possibly 0xa6c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x33b7b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 211835.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x925420 for possibly 0xb40 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34fb0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 217008.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x29aac5 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x3b5e9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 243177.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9d799c for possibly 0x29a clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3bc44 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 244804.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x921ddd for possibly 0x3a0 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3c085 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 245893.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x9216d4 for possibly 0x3a1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x3cefb is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 249595.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0xaa1c20 for possibly 0xc90 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x3d2fd is already in use.
The attribute of type 0x80 and instance tag
-----------------------------------------------------------------------

 

[BrianDrab]

You should have a c:\windows\memory.dmp file. Can you zip this up and upload it to me?

 

[dantobal]

Hi there - it's a 480MB file, and it's not letting me zip it or even access it via Notepad. Any suggestions?