Hibernate Requires Hard-Restart (power supply reset)

I just got bitten by something similar, related to the Intel Management Engine's power management setting. See this blog post: Driver Setting Explains Venue Pro Restart Fail - Windows Enterprise Desktop. Might be related...
--Ed--

compupix said:

I appreciate all of your efforts Ken!
Report Number 2:
Summary Attachment 222434
Full report as pdf. https://1drv.ms/b/s!Ag3kMlvkg9qhjDakhgPfNzsF-Die

You still have all these errors.



I started chasing down threads with this error. Nothing finite. One mentioned replacing the PSU to resolve.

Let see what comes of bro67 and zbook's ideas.

compupix said:

Which Speccy section do you want to see? I don’t see a way of expanding all.

In Speccy, Click on File then save the output as a text file. Then you can attach in your onedrive, as an attachment on here or inline text in a post.

Caledon Ken said:

You still have all these errors.



I started chasing down threads with this error. Nothing finite. One mentioned replacing the PSU to resolve.

Let see what comes of bro67 and zbook's ideas.

That ACPI is not normal. This should be the latest bios ver that they should have. "Dell Studio XPS 435T System BIOS, A16" Sad thing is that it is from 2010 and that model EOL'd around 2014 after the last push of fixes.

Consolidated Responses

Repeat Questions are answered with the first instance of that question.

zbook said:

Please run the BETA log collector and post a zip into this thread:

Beta Log Collector results: https://1drv.ms/u/s!Ag3kMlvkg9qhjDgSnDRRwNcF1eSY

zbook said:

2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow

C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.”

zbook said:

4) dism /online /cleanup-image /restorehealth

‘C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.292
[===========================86.5%================== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.

The DISM log file: https://1drv.ms/u/s!Ag3kMlvkg9qhjDnytj7dIvsnm8ad

The source files could not be found; their location must be specified using the /source option to restore the feature.

I couldn’t figure out how to resolve the source files location problem.

zbook said:

5) chkdsk /scan

CHKDSK results:

https://1drv.ms/t/s!Ag3kMlvkg9qhjDohvE6pNv5PhqPQ

Hint: I didn’t see anything interesting in the results.

zbook said:

Run the Dell diagnostics: Full tests

Dell Diagnostics Full Test Results:
{deleted}
{Another try to post the results was posted after zbook's post below.}

I didn't see anything significant.

zbook said:

Support for Studio XPS 435T / 9000 | Drivers & downloads | Dell US

“No driver updates found. Your system has the most recent updates”

EdTittel said:

I just got bitten by something similar, related to the Intel Management Engine's power management setting. See this blog post: Driver Setting Explains Venue Pro Restart Fail - Windows Enterprise Desktop. Might be related.

I don’t recognize “Intel Management Engine Interface.”
What would the IME Driver be attached to?
Note: Your second graphic doesn’t load:
The requested URL /ITKE/uploads/blogs.dir/79/files/2019/01/kari-imefix.png was not found on this server.
Running the two Intel discovery tools both generate the line…
“…either the Intel(R) MEI/TXEI driver is not installed … or the system manufacturer does not permit access to the ME/TXE from the host driver.”

Caledon Ken said:

I started chasing down threads with this error. Nothing finite. One mentioned replacing the PSU to resolve.

Brief System History:
January 15, 2019

The power supply unit was replaced because of a noisy fan.

January 15 - 23, 2019

The system was shut down and subsequently restarted without incident on January 15, 16, & 23
Hibernate was used at least twice a day, without issue, between January 16 and 23.

January 23, 2019

Cumulative Update for Version 1809 was installed KB4476976.
Cumulative Update for .NET Framework 3.5 and 4.7.2 for 1809 installed; KB4481031

January 25, 2019

System Restore used to back out the latest updates.
The problem continued, so…

January 26, 2019

Updates re-installed

Could my issue be caused by an improperly connected power supply and was triggered with the latest Windows update?

bro67 said:

In Speccy, Click on File then save the output as a text file. Then you can attach in your onedrive, as an attachment on here or inline text in a post.

See: https://1drv.ms/t/s!Ag3kMlvkg9qhjDeu0A_h44BJSkne

This file will be removed in about a week.

If I missed someone's question or test, please let me know.

There is flexibility in the steps below and they can be performed in any order.

1) The results from the Dell diagnostics were not able to be opened or viewed.
Please find an alternative method to post the results into the thread.
Consider using a camera or smartphone camera to take a picture and post an image into the thread.

2) The last BSOD was on 10/10/2018 with bugcheck 12B.
Bugcheck 12 B is typically a hardware problem.
There were no recent BSOD.

3) There was corruption of the drive file system.


4) There was some discrepancy in the Memory reports. Msinfo32 and dxdiag displayed installed 14 GB, the "My Computer" section displayed 12 GB, and the RAM text displayed 3 modules with 2 GB each with a total of 6 GB RAM.

5) Open task manager with control + alt + del > click performance tab > click memory > post an image into the thread

6) Open administrative command prompt and copy and paste:

a) wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
b) wmic memorychip list full
c) systeminfo | findstr /C:”Total Physical Memory”
d) systeminfo |find “Available Physical Memory”

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


7) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

8) Open administrative command prompt and type or copy and paste: chkdsk /r /v C:
This command may take many hours so plan to run overnight.
Run this command on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive
chkdsk /r /v C:
chkdsk /r /v J:

C:\WINDOWS\system32>chkdsk /r /v C:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

9) Use the text and images in this thread to find the chkdsk reports in the event viewer > copy and paste > notepad > post share links into the thread using one drive, drop box, or google drive
Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials

10) Uninstall Iobit using the applicable uninstall tool:
http://forums.iobit.com/forum/advanc...y-remove-iobit

11) Uninstall and reinstall: ctaud2k.sys

Updating a driver. - Microsoft Community
Install from the Dell website > then perform windows updates

Support for Studio XPS 435T / 9000 | Drivers & downloads | Dell US


ctaud2k.sys
Creative Audio Driver (WDM)
http://support.creative.com/

12) Run HD Tune: (free or trial edition) (test all drives)
https://www.hdtune.com/
Post images into the thread for results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

13) Run Sea Tools for Windows: (test all drives)
long generic test > post an image into the thread
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows | Seagate Support

14) Find a flash drive that you can format ( > or = 8 GB)

15) Create a bootable Windows 10 iso:
Download Windows 10 ISO File | Tutorials
Download Windows 10

16) Run Memtest86+ version 5.01 for 8 or more passes.
Memtest86+ - Advanced Memory Diagnostic Tool
Memtest86+ - Advanced Memory Diagnostic Tool

This may take hours so plan to run it overnight.

a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool

The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.

b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.

Memory problems. - Microsoft Community

MemTest86+ - Test RAM | Tutorials


17) Open Speecy:
a) click RAM > expand each row > post images into the thread
b) click storage > expand each row > post images into the thread

Code:

10/10/2018 4:15 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 12b
P2: ffffffffc00002c4
P3: 5f4
P4: 13c82b1be20
P5: ffffcf015bdb6000
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100918-12218-01.dmp
\\?\C:\WINDOWS\TEMP\WER-19265-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D9E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DBE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DCD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DED.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_12b_fb2438d834a0edba2cface91fcb7fa2ebfa74e5_00000000_cab_1540733c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 920bec7c-f0ef-489a-92f0-8b283e48db5b
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
10/10/2018 4:15 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 12b
P2: ffffffffc00002c4
P3: 5f4
P4: 13c82b1be20
P5: ffffcf015bdb6000
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100918-12218-01.dmp
\\?\C:\WINDOWS\TEMP\WER-19265-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D9E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DBE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DCD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DED.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_12b_fb2438d834a0edba2cface91fcb7fa2ebfa74e5_00000000_03306dec

Analysis symbol: 
Rechecking for solution: 0
Report Id: 920bec7c-f0ef-489a-92f0-8b283e48db5b
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

Event[3837]:
  Log Name: System
  Source: Ntfs
  Date: 2019-01-26T06:56:38.910
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-FECR0D5
  Description: 
A corruption was discovered in the file system structure on volume C:.

A corruption was found in a file system index structure.  The file reference number is 0x14000000038916.  The name of the file is "\Users\Drew\AppData\Local\Google\Chrome\User Data\Default\Extensions\hdokiejnpimakedhajhdlcegeplioahd\4.23.0.3_0\_locales".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Code:

Event[3855]:
  Log Name: System
  Source: Ntfs
  Date: 2019-01-26T07:04:14.181
  Event ID: 133
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-FECR0D5
  Description: 
Skipped posting of 10 repair events.  Repair event posting will now be resumed.
 Here are the skipped posting repair events count by repair verbs:
 BadFRS:            0
 OrphanChildFRS:    0
 BadClusters:       0
 BadFreeClusters:   0
 CrossLink:         0
 SDEntry:           0
 InvalidSecurityId: 0
 IndexAttribute:    0
 IndexSubtree:      0
 IndexOffset:       0
 IndexEntry:        0
 IndexOrder:        0
 Connect:           0
 BreakCycle:        0
 FRSAllocate:       10
 Others:            0

Code:

Installed Physical Memory (RAM)	14.0 GB
Total Physical Memory	14.0 GB
Available Physical Memory	6.64 GB
Total Virtual Memory	28.0 GB
Available Virtual Memory	18.1 GB
Page File Space	14.0 GB
Page File	C:\pagefile.sys

Code:

Location     : DIMM0
BankLabel    : BANK0
Manufacturer : Samsung       
MemoryType   : Other
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 1066
Serial       : EF8B9C86
PartNumber   : M378B5673EH1-CF8  
ECC          : False
TypeDetail   : {0}

Location     : DIMM2
BankLabel    : BANK2
Manufacturer : Samsung       
MemoryType   : Other
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 1066
Serial       : 058C9C86
PartNumber   : M378B5673EH1-CF8  
ECC          : False
TypeDetail   : {0}

Location     : DIMM4
BankLabel    : BANK4
Manufacturer : Samsung       
MemoryType   : Other
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 1066
Serial       : 048C9C86
PartNumber   : M378B5673EH1-CF8  
ECC          : False
TypeDetail   : {0}

Code:

                   Memory: 14326MB RAM
      Available OS Memory: 14326MB RAM
                Page File: 10156MB used, 18506MB available

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 313.1 GB
Total Space: 456.3 GB
File System: NTFS
      Model: Micron_M500_MTFDDAK480MAV

      Drive: E:
 Free Space: 0.4 GB
Total Space: 0.4 GB
File System: NTFS
      Model: Micron_M500_MTFDDAK480MAV

      Drive: J:
 Free Space: 966.5 GB
Total Space: 1216.4 GB
File System: NTFS
      Model: Microsoft Storage Space Device

Code:

Event[3416]:
  Log Name: Application
  Source: Microsoft-Windows-Wininit
  Date: 2019-01-26T07:07:01.230
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-FECR0D5
  Description: 


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


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.                         

Stage 1: Examining basic file system structure ...
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0xee1804 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x6386 is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x6386
has allocated length of 0x84b000 instead of 0x701000.
Deleted corrupt attribute list entry
with type code 80 in file 6386.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xab00000000143a.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x143A.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x2600000000160b.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x160B.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0xee17e7 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x7daa is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x7daa
has allocated length of 0x1750000 instead of 0x443000.
The total allocated size 0x495000 of attribute of type 0x80 and instance
tag 0x0 in file 0x7daa is incorrect.  The expected value is 5a000.
Correcting total allocated size in attribute record (80, "")
of file A000000007DAA.
Deleted corrupt attribute list entry
with type code 80 in file 7DAA.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x9700000000005a.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5A.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x53000000000935.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x935.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1680000000009eb.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x9EB.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x4500000000a664.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0xA664.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x4700000000a776.  The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0xA776.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17cb for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x805b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x805B.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17ea for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x18416 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x18416.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17f7 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1841b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x1841B.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee1809 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x224fd is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x224FD.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17e2 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2f636 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x2F636.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17f1 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2f646 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x2F646.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee180a for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2f64f is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x2F64F.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee180e for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2f652 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x2F652.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17f2 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2f71d is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x2F71D.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17bc for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3047b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x3047B.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17be for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x30554 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x30554.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17b0 for possibly 0x9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x314c3 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x314C3.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17c0 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31bc5 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x31BC5.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17c4 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31bc6 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x31BC6.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17c7 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31bc7 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x31BC7.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17d7 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31bc9 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x31BC9.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17de for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31bcb is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x31BCB.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0xee17dc for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x38916 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x38916.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17cd for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x502a7 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x502A7.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17ce for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x502a8 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x502A8.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee17cf for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x502aa is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x502AA.
  624896 file records processed.                                                        


File verification completed.
Deleting orphan file record segment 5A.
Deleting orphan file record segment 935.
Deleting orphan file record segment 9EB.
Deleting orphan file record segment 143A.
Deleting orphan file record segment 160B.
  4977 large file records processed.                                   


  0 bad file records processed.                                     



Stage 2: Examining file name linkage ...
  1492 reparse records processed.                                      


A downpointer (VCN 0x0) was found in index $I30 in file 0x38916 but the index has no index allocation attribute.
Removing corrupt index $I30 in file 38916.
Recreating deleted index $I30 in file 38916.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x502a9 is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ??  ................
Correcting error in index $I30 for file 502A9.
The index bitmap $I30 in file 0x502a9 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 502A9.
The down pointer of current index entry with length 0xf0 is invalid.
af 02 05 00 00 00 03 00 f0 00 d8 00 01 00 00 00  ................
a9 02 05 00 00 00 03 00 06 41 ee c3 d4 4c d4 01  .........A...L..
06 41 ee c3 d4 4c d4 01 e4 ae b8 7b 80 af d4 01  .A...L.....{....
06 41 ee c3 d4 4c d4 01 00 10 00 00 00 00 00 00  .A...L..........
e1 01 00 00 00 00 00 00 20 00 00 00 00 00 00 00  ........ .......
4b 01 4d 00 69 00 78 00 65 00 64 00 52 00 65 00  K.M.i.x.e.d.R.e.
61 00 6c 00 69 00 74 00 79 00 50 00 6f 00 72 00  a.l.i.t.y.P.o.r.
74 00 61 00 6c 00 41 00 70 00 70 00 4c 00 69 00  t.a.l.A.p.p.L.i.
73 00 74 00 2e 00 74 00 61 00 72 00 67 00 65 00  s.t...t.a.r.g.e.
74 00 73 00 69 00 7a 00 65 00 2d 00 33 00 30 00  t.s.i.z.e.-.3.0.
5f 00 61 00 6c 00 74 00 66 00 6f 00 72 00 6d 00  _.a.l.t.f.o.r.m.
2d 00 75 00 6e 00 70 00 6c 00 61 00 74 00 65 00  -.u.n.p.l.a.t.e.
64 00 5f 00 63 00 6f 00 6e 00 74 00 72 00 61 00  d._.c.o.n.t.r.a.
73 00 74 00 2d 00 77 00 68 00 69 00 74 00 65 00  s.t.-.w.h.i.t.e.
2e 00 70 00 6e 00 67 00 ff ff ff ff ff ff ff ff  ..p.n.g.........
Sorting index $I30 in file 502A9.
  779422 index entries processed.                                                       


Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file ar (38F4A) into directory file 38916.
Recovering orphaned file bg (38F4D) into directory file 38916.
Recovering orphaned file bn (38F4E) into directory file 38916.
Recovering orphaned file ca (38F4F) into directory file 38916.
Recovering orphaned file cs (38F50) into directory file 38916.
Recovering orphaned file da (38F51) into directory file 38916.
Recovering orphaned file de (38F52) into directory file 38916.
Recovering orphaned file el (38F53) into directory file 38916.
Recovering orphaned file en_GB (38F54) into directory file 38916.
Recovering orphaned file en_US (38F55) into directory file 38916.
Skipping further messages about recovering orphans.
  69 unindexed files scanned.                                        


  69 unindexed files recovered to original directory.
  0 unindexed files recovered to lost and found.                    


  1492 reparse records processed.                                      



Stage 3: Examining security descriptors ...
Cleaning up 2691 unused index entries from index $SII of file 0x9.
Cleaning up 2691 unused index entries from index $SDH of file 0x9.
Cleaning up 2691 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 6386.
Inserting data attribute into file 7DAA.
Inserting data attribute into file 805B.
Inserting data attribute into file 18416.
Inserting data attribute into file 1841B.
Inserting data attribute into file 224FD.
Inserting data attribute into file 2F636.
Inserting data attribute into file 2F646.
Inserting data attribute into file 2F64F.
Inserting data attribute into file 2F652.
Inserting data attribute into file 2F71D.
Inserting data attribute into file 3047B.
Inserting data attribute into file 30554.
Inserting data attribute into file 314C3.
Inserting data attribute into file 31BC5.
Inserting data attribute into file 31BC6.
Inserting data attribute into file 31BC7.
Inserting data attribute into file 31BC9.
Inserting data attribute into file 31BCB.
Inserting data attribute into file 502A7.
Inserting data attribute into file 502A8.
Inserting data attribute into file 502AA.
  77286 data files processed.                                           


CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.