Boot failure after chkdsk /r No bootable image found

Page 13 of 15 FirstFirst ... 31112131415 LastLast
  1. Caledon Ken's Avatar
    Posts : 15,246
    Windows 10 Pro x64 Build 1809
       #121

    Not sure how you are going to fix a file not found message. You said you ran chkdsk so the allocation table was repaired as best it could. Still think you are experiencing file damage caused by breaking Raid 0.

    Sorry to hear about F:, more news you didn't need

    So assessing where you are. You have F: which is dated and may have been influenced by long names / duplicates.

    You have your original Macrium Image which has all your data up to July 18/18 although data recovery is cumbersome, it appears the restore options are the whole image or manual copies of folders.

    You have a "working" c: drive that has all your data but itself maybe suspect.

    One option that remains is to install the trial Macrium, create boot media and backup user folders Looks like you can skip Administrator. My hope is there is no corruption within users\aaaaaaa

    It is my understanding that aaaaaaa on the 750GB has all your data, correct?

    I don't think I would run incremental as it will try all files that have changed. os, temps and data.

    For future start Macrium. Click on Backup tasks. Click on Backup definitions. Click icon to run backup definition and a menu appears. Click Incremental.

    Click image for larger version. 

Name:	image.png 
Views:	18 
Size:	42.8 KB 
ID:	204253

    In the meantime I've asked names of utilities to batch rename. You are slowly being forced into dealing with this data issue as I see it. I think the dups are caused by recopying folders but that is yet to be proven.

    I'll also look on clearing VSS issue.
      My ComputerSystem Spec

  2.    #122

    Reflect has some good VSS troubleshooting & repair tools (Look under "Other Tools" menu):
    Click image for larger version. 

Name:	image.png 
Views:	17 
Size:	24.2 KB 
ID:	204259
    HTH,
    --Ed--
      My ComputersSystem Spec


  3. Posts : 26,422
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #123

    Ed that appears to be the same image as in post 119 and the tool did not indicate whether it requires a reboot.

    With Macrium finding problems in the log files it was not able to make an automatic incremental backup.
    If a 30 day trial was used for a new version wouldn't the new version fail to make a new backup with the same findings in the logs?

    With the new findings I made an extra copy of the users folder despite the time requirement.
    So now there is a folder on the E: drive: Users after fixed boot 9 15 2018.
    This is all users. There was only one user on the computer and the administrator was from a prior Microsoft remote access attempt by Microsoft to fix a failed Windows upgrade.

    Using this method to find chkdsk reports: Read Chkdsk Log in Event Viewer in Windows 10 | Windows 10 Tutorials the last chkdsk that was recorded in the logs was on 7/26/2018.
    There were a very large number of Informational chkdsk events event ID 26228 reporting problems with Mozilla Firefox: …cache2\entries…..is partially mis-ordered ...no corruption found

    Code:
    Chkdsk was executed in verify mode on a volume snapshot.  
    
    Checking file system on \Device\HarddiskVolume4
    
    
    Examining 1 corruption record ...
    
    
    Record 1 of 1: Index "$I30" of directory "\Users\aaaaaaa\AppData\Local\Mozilla\Firefox\Profiles\fshei91f.default-1528398554804\cache2\entries <0x9c,0x7ff9>" is partially mis-ordered ... no corruption found.
    
    
    1 corruption record processed in 0.1 seconds.
    
    
    Windows has examined the list of previously identified potential issues and found no problems.
    No further action is required.


    There was only one Wininit event ID 1001 displaying corruption and the report was incomplete:

    Code:
    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.                         
    
    
    Stage 1: Examining basic file system structure ...
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x85cd1d for possibly 0x44 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1afaf is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x1AFAF.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x4be78 for possibly 0xb clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3edab is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x3EDAB.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0xf095dd for possibly 0x7e clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3edaf is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x3EDAF.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0xf0d9ea for possibly 0x80 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3edb7 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x3EDB7.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0xfd7ff8 for possibly 0x7e clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3edd3 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x3EDD3.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x18b3a40 for possibly 0x88 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3fa85 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x3FA85.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x780e8d for possibly 0xbd clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x40f18 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x40F18.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x6a4c08b for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x41b97 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x41B97.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x1a7440 for possibly 0x10 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x420c9 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x420C9.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x791684 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x43ebe is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x43EBE.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x47bcf58 for possibly 0x25 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x44caa is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x44CAA.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x8f184 for possibly 0xb clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x56b62 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x56B62.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x90852 for possibly 0xe clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x58259 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x58259.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3184a00 for possibly 0x128 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x5832b is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5832B.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x4b97e for possibly 0x9 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x59c4b is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x59C4B.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x1980aa for possibly 0x7 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x5c129 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5C129.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x1a7453 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x5c2d2 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5C2D2.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x9107cf for possibly 0x48 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x5d5ad is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5D5AD.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x58659d4 for possibly 0x38 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x5d61b is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5D61B.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x768c90 for possibly 0x4c clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x5daab is already in use.
    The attribute of type 0x80 and instance tag 0x0 in file 0x5daab
    has allocated length of 0x11642000 instead of 0xf484000.
    Deleted corrupt attribute list entry
    with type code 80 in file 5DAAB.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x11e000000011bcf.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x11BCF.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x4f00000005d9a1.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5D9A1.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x31935b0 for possibly 0x23 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x5e640 is already in use.
    The attribute of type 0x80 and instance tag 0x0 in file 0x5e640
    has allocated length of 0x19c1000 instead of 0x14a2000.
    Deleted corrupt attribute list entry
    with type code 80 in file 5E640.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x1a000000063e2c.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x63E2C.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x1f000000063e93.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x63E93.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x56a4fb8 for possibly 0x3a clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x5f1f8 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5F1F8.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x54cf424 for possibly 0xc clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x5f201 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5F201.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x5865a0c for possibly 0x15 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x5f208 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5F208.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x5685222 for possibly 0x67 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x5f20b is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5F20B.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x738320 for possibly 0x19 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x60475 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x60475.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x6912262 for possibly 0x17 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x604ad is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x604AD.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x738021 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x6053d is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x6053D.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x738174 for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x60544 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x60544.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x73816f for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x6054b is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x6054B.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x73817f for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x60554 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x60554.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x246b0 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x608fa is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x608FA.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x47bcf53 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x60fd3 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x60FD3.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x384370 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x6109c is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x6109C.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x98230 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x61211 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61211.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x7382b8 for possibly 0x26 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x61311 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61311.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x9b99e3 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x6133e is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x6133E.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x6a4d2db for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x61398 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61398.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x586bfcf for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x613c3 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x613C3.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x747d50 for possibly 0x2c clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x6152a is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x6152A.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x643a for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x61761 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61761.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x643b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x61773 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61773.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x738dd8 for possibly 0xa0 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x6177a is already in use.
    The attribute of type 0x80 and instance tag 0x0 in file 0x6177a
    has allocated length of 0x685c000 instead of 0x65f8000.
    Deleted corrupt attribute list entry
    with type code 80 in file 6177A.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x150000000616c4.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x616C4.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x26000000061785.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61785.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x582ab74 for possibly 0xb0 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x61789 is already in use.
    The attribute of type 0x80 and instance tag 0x0 in file 0x61789
    has allocated length of 0xe115000 instead of 0x5aa4000.
    Deleted corrupt attribute list entry
    with type code 80 in file 61789.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xee00000003f5e0.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x3F5E0.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x2900000005eb0e.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x5EB0E.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x38000000061751.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x61751.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x24f3f4c for possibly 0xd4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x6179a is already in use.
    The attribute of type 0x80 and instance t

    With the chkdsk finding of problems with Firefox I'll uninstall and reinstall the software.
    The Macrium VSS I'll run and report the results.
    If a boot is required and fails the fallback is Kyhi boot rescue.
      My ComputerSystem Spec


  4. Posts : 26,422
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #124

    This is the Macrium VSS log before repair in two parts:

    Code:
    (Gathering writer metadata...)(Waiting for the asynchronous operation to finish...)Initialize writer metadata ...- Get exclude files- Enumerate components- Get file list descriptors- Get database descriptors- Get log descriptors- Get exclude files- Enumerate components- Get file list descriptors- Get database descriptors- Get log descriptors- Get exclude files- Enumerate components- Get file list descriptors- Get database descriptors- Get log descriptors- Get exclude files- Enumerate components- Get file list descriptors- Get database descriptors- Get log descriptors- Get exclude files- Enumerate components- Get file list descriptors- Get database descriptors- Get log descriptors- Get exclude files- Enumerate components- Get file list descriptors- Get database descriptors- Get log descriptors- Get exclude files- Enumerate componentsDiscover directly excluded components ...- Excluding writer '' since it has no selected components for restore.- Excluding writer '' since it has no selected components for restore.- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.Discover components that reside outside the shadow set ...Discover all excluded components ...Discover excluded writers ...Discover explicitly included components ...Verifying explicitly specified writers/components ...Select explicitly included components ... * Writer 'Task Scheduler Writer':   - Add component \TasksStore * Writer 'VSS Metadata Store Writer':   - Add component \WriterMetadataStore * Writer 'Performance Counters Writer':   - Add component \PerformanceCounters * Writer 'Registry Writer':   - Add component \Registry * Writer 'WMI Writer':   - Add component \WMI * Writer 'COM+ REGDB Writer':   - Add component \COM+ REGDBCreating shadow set {ae62e44c-4b7b-48b6-b931-bba006f29a58} ...- Adding volume \\?\Volume{00704c0d-3860-4dbf-9d6b-adcef9ed2178}\ [C:\] to the shadow set...Preparing for backup ... (Waiting for the asynchronous operation to finish...)(Waiting for the asynchronous operation to finish...)Creating the shadow (DoSnapshotSet) ... (Waiting for the asynchronous operation to finish...)(Waiting for the asynchronous operation to finish...)Shadow copy set succesfully created.Saving the backup components document ... List of created shadow copies: Querying all shadow copies with the SnapshotSetID {ae62e44c-4b7b-48b6-b931-bba006f29a58} ...* SNAPSHOT ID = {702250a4-8c89-49c1-8991-bb41bae7da73} ...   - Shadow copy Set: {ae62e44c-4b7b-48b6-b931-bba006f29a58}   - Original count of shadow copies = 1   - Original Volume name: \\?\Volume{00704c0d-3860-4dbf-9d6b-adcef9ed2178}\ [C:\]   - Creation Time: 9/14/2018 5:41:37 PM   - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1   - Originating machine: DESKTOP-BH9NBPV   - Service machine: DESKTOP-BH9NBPV   - Not Exposed   - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}   - Attributes:  Auto_Release DifferentialWindows Events*****************************Date      9/14/2018 5:51:06 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 28463104 (0x0000000001b25000) (database page 6948 (0x1B24)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 6948 (0x1B24) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:51:00 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9965568 (0x0000000000981000) (database page 2432 (0x980)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2432 (0x980) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:59 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 19062784 (0x000000000122e000) (database page 4653 (0x122D)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4653 (0x122D) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:57 PM  Type      Error Event     447  Source    ESENTCatalog Database (3424) Catalog Database: A bad page link (error -338) has been detected in a B-Tree (ObjectId: 8, PgnoRoot: 35) of database C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb (1497 => 8055, 8).*****************************Date      9/14/2018 5:50:57 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 32997376 (0x0000000001f78000) (database page 8055 (0x1F77)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 8055 (0x1F77) was 1 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:55 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9994240 (0x0000000000988000) (database page 2439 (0x987)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2439 (0x987) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:52 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 19034112 (0x0000000001227000) (database page 4646 (0x1226)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4646 (0x1226) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:50 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9904128 (0x0000000000972000) (database page 2417 (0x971)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2417 (0x971) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:45 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 6696960 (0x0000000000663000) (database page 1634 (0x662)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1634 (0x662) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:42 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 10575872 (0x0000000000a16000) (database page 2581 (0xA15)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2581 (0xA15) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:38 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 5181440 (0x00000000004f1000) (database page 1264 (0x4F0)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1264 (0x4F0) was 1 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:35 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 13508608 (0x0000000000ce2000) (database page 3297 (0xCE1)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3297 (0xCE1) was 3 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:32 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 11911168 (0x0000000000b5c000) (database page 2907 (0xB5B)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2907 (0xB5B) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:32 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 19546112 (0x00000000012a4000) (database page 4771 (0x12A3)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4771 (0x12A3) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:30 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 12345344 (0x0000000000bc6000) (database page 3013 (0xBC5)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3013 (0xBC5) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:29 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 13701120 (0x0000000000d11000) (database page 3344 (0xD10)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3344 (0xD10) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:21 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 10657792 (0x0000000000a2a000) (database page 2601 (0xA29)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2601 (0xA29) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:21 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 21790720 (0x00000000014c8000) (database page 5319 (0x14C7)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 5319 (0x14C7) was 3 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:19 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 24354816 (0x000000000173a000) (database page 5945 (0x1739)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 5945 (0x1739) was 1 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:18 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 13385728 (0x0000000000cc4000) (database page 3267 (0xCC3)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3267 (0xCC3) was 1 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:16 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 5496832 (0x000000000053e000) (database page 1341 (0x53D)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1341 (0x53D) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:05 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 1982464 (0x00000000001e4000) (database page 483 (0x1E3)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 483 (0x1E3) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:50:03 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 28356608 (0x0000000001b0b000) (database page 6922 (0x1B0A)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 6922 (0x1B0A) was 3 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:58 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 31911936 (0x0000000001e6f000) (database page 7790 (0x1E6E)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 7790 (0x1E6E) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:55 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 2162688 (0x0000000000210000) (database page 527 (0x20F)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 527 (0x20F) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************

    Code:
    Date      9/14/2018 5:49:52 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 19034112 (0x0000000001227000) (database page 4646 (0x1226)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4646 (0x1226) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:49 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 28909568 (0x0000000001b92000) (database page 7057 (0x1B91)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 7057 (0x1B91) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:47 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 29622272 (0x0000000001c40000) (database page 7231 (0x1C3F)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 7231 (0x1C3F) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:44 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 4632576 (0x000000000046b000) (database page 1130 (0x46A)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1130 (0x46A) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:43 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9904128 (0x0000000000972000) (database page 2417 (0x971)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2417 (0x971) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:42 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 11882496 (0x0000000000b55000) (database page 2900 (0xB54)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2900 (0xB54) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:37 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9965568 (0x0000000000981000) (database page 2432 (0x980)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2432 (0x980) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:32 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 1044480 (0x00000000000ff000) (database page 254 (0xFE)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 254 (0xFE) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:27 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 3330048 (0x000000000032d000) (database page 812 (0x32C)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 812 (0x32C) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:27 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 25681920 (0x000000000187e000) (database page 6269 (0x187D)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 6269 (0x187D) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:24 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 18845696 (0x00000000011f9000) (database page 4600 (0x11F8)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4600 (0x11F8) was 3 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:23 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 7847936 (0x000000000077c000) (database page 1915 (0x77B)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1915 (0x77B) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:22 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 14733312 (0x0000000000e0d000) (database page 3596 (0xE0C)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3596 (0xE0C) was 3 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:16 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 5455872 (0x0000000000534000) (database page 1331 (0x533)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1331 (0x533) was 1 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:16 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 19546112 (0x00000000012a4000) (database page 4771 (0x12A3)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4771 (0x12A3) was 2 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:15 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 12988416 (0x0000000000c63000) (database page 3170 (0xC62)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3170 (0xC62) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:14 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 14721024 (0x0000000000e0a000) (database page 3593 (0xE09)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 3593 (0xE09) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:11 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 5341184 (0x0000000000518000) (database page 1303 (0x517)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 1303 (0x517) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:09 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 26894336 (0x00000000019a6000) (database page 6565 (0x19A5)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 6565 (0x19A5) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:05 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 16543744 (0x0000000000fc7000) (database page 4038 (0xFC6)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4038 (0xFC6) was 1 while the flush state on flush map page 0 (0x0) was 3. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:49:00 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9039872 (0x000000000089f000) (database page 2206 (0x89E)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2206 (0x89E) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:59 PM  Type      Warning Event     508  Source    ESENTSearchIndexer (3560) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (20 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:51 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 19034112 (0x0000000001227000) (database page 4646 (0x1226)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4646 (0x1226) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:44 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 32669696 (0x0000000001f28000) (database page 7975 (0x1F27)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 7975 (0x1F27) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:41 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 18833408 (0x00000000011f6000) (database page 4597 (0x11F5)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4597 (0x11F5) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:40 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 29040640 (0x0000000001bb2000) (database page 7089 (0x1BB1)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 7089 (0x1BB1) was 3 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:40 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9965568 (0x0000000000981000) (database page 2432 (0x980)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2432 (0x980) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:38 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 30433280 (0x0000000001d06000) (database page 7429 (0x1D05)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 7429 (0x1D05) was 3 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:35 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 11055104 (0x0000000000a8b000) (database page 2698 (0xA8A)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2698 (0xA8A) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:30 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 16420864 (0x0000000000fa9000) (database page 4008 (0xFA8)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 4008 (0xFA8) was 2 while the flush state on flush map page 0 (0x0) was 1. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:48:27 PM  Type      Error Event     544  Source    ESENTCatalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 9904128 (0x0000000000972000) (database page 2417 (0x971)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). The flush state on database page 2417 (0x971) was 1 while the flush state on flush map page 0 (0x0) was 2. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.*****************************Date      9/14/2018 5:45:37 PM  Type      Warning Event     3  Source    NVWMIInstance and Method provider registration failed - Invalid namespace hr=0x8004100E (-2147217394)*****************************Date      9/14/2018 5:45:26 PM  Type      Error Event     8229  Source    Microsoft-Windows-Security-SPPThe rules engine failed to perform one or more scheduled actions.Error Code:0x80070005Path:SERIALIZE_INTERNALArguments:<none>*****************************Date      9/14/2018 5:45:16 PM  Type      Error Event     1000  Source    Application ErrorFaulting application name: IAStorDataMgrSvc.exe, version: 14.8.1.1043, time stamp: 0x564b505aFaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x04664c35Faulting process id: 0x145cFaulting application start time: 0x01d44c7c565b38edFaulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exeFaulting module path: unknownReport Id: 4942b68c-1faa-4e0b-a566-e90e96adc95dFaulting package full name: Faulting package-relative application ID: *****************************Date      9/14/2018 5:45:15 PM  Type      Error Event     1026  Source    .NET RuntimeApplication: IAStorDataMgrSvc.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.NullReferenceException   at IAStorUtil.SystemDataModelListener.ProcessSystemDataModelChanges()   at IAStorUtil.SystemDataModelListener.LoadSavedSystemState()   at IAStorDataMgr.EventRelay.<Start>b__0(System.Object)   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()   at System.Threading.ThreadPoolWorkQueue.Dispatch()   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()*****************************Date      9/14/2018 5:42:37 PM  Type      Error Event     8229  Source    Microsoft-Windows-Security-SPPThe rules engine failed to perform one or more scheduled actions.Error Code:0x80070005Path:SERIALIZE_INTERNALArguments:<none>*****************************Date      9/14/2018 5:42:36 PM  Type      Error Event     8229  Source    Microsoft-Windows-Security-SPPThe rules engine failed to perform one or more scheduled actions.Error Code:0x80070005Path:SERIALIZE_INTERNALArguments:<none>
      My ComputerSystem Spec

  5. Caledon Ken's Avatar
    Posts : 15,246
    Windows 10 Pro x64 Build 1809
       #125

    I'm hoping by installing the trial version of Macrium you will be able to target your Users folders and use the back up technology to get around files names to long and data duplicates.

    With the ability to target folders my assumption is you can avoid data errors as I'm assuming the caching feature would not have picked up on data files. More it would be used for system files / regularly used files, paging etc. The example of the FF cache is the type of file I would expect, a file in high demand.

    Yes I'm making assumptions but until you try we don't know. If backing up users\aaaaaaa produces file errors you can refine and do individual copies of documents, pictures etc.

    This all may be moot now.

    How confident are you that F: has all your data files? This is an important decision point. If you are confident then you can push onward to next next step. If you are not confident then it would be worth tinkering with Macrium and folder backups.

    Myself, being something of a freak about my data, I would try the Macrium trial to get one last copy of data.

    It is important that you keep that original Macrium Full Image backup. If has a very good collection of your data up to July 18/18.


    Ken
      My ComputerSystem Spec


  6. Posts : 26,422
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #126

    The Macrium backup image is on the 1 TB internal storage drive.
    The old users from March 2018 is also on the 1 TB internal storage drive.
    The 4 TB external drive now has two copies of the Users folder:
    One made using Kyhi boot rescue.
    And One made using copy and paste directly from C: > E:

    The Macrium VSS was ran

    Click image for larger version. 

Name:	macrium vss  press ok to re-register microsoft vss componets and update the microsoft shadow sof.PNG 
Views:	14 
Size:	4.5 KB 
ID:	204299

    There was no prompt or message after running the tool.
    Macrium was closed and reopened.
    It seemed to have the identical display as before running VSS:

    Click image for larger version. 

Name:	Macrium after running vss repair.PNG 
Views:	1 
Size:	108.2 KB 
ID:	204298




    What is the next step?
    Reboot to see if the Intel software/drive can fix the problem related to Macrium?
    Reboot to see whether Intel RAID acceleration can be turned off?

    It is unclear whether the Users has everything but there does not seem to be a better method than using the Users as a proxy for everything. There is the Macrium image if that can be used.

    The Microsoft database corruption may prevent Windows updates. But that may be one option to fix the ESENT error messages displayed in Macrium.

    There may be too much corruption and then it may end of requiring a disk sanitization and restoring the Users folder?
      My ComputerSystem Spec


  7. Caledon Ken's Avatar
    Posts : 15,246
    Windows 10 Pro x64 Build 1809
       #127

    I think you have to run a backup in some form to see if VSS is fixed. These appear to be logs from the 14th and earlier.

    So simple question with a more difficult answer...

    Do you have all you data? You said 4TB has two copies. I assume you know the names of those critical files created between July 18/18 and July 25/18. Are they whole, can you open the file(s)?
      My ComputerSystem Spec


  8. Posts : 26,422
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #128

    Windows updates were not able to be performed.
    This was after running the Windows update troubleshooter.
    It displayed:
    0x8007042c

    The dependency service or group failed to start.

    How to fix?

    I cannot tell whether all the data is in the Users folder and that appears to be the best that can be done?
      My ComputerSystem Spec

  9. Caledon Ken's Avatar
    Posts : 15,246
    Windows 10 Pro x64 Build 1809
       #129

    Okay.

    Myself I would not put anymore effort into saving this copy of Windows. It is broke and in some form has been for some time if I recall your description properly.

    So you think you have all your data. You didn't answer if you tested one of those critical files.

    So decision point, try installing Macrium trail and backup folders

    or

    Clean Install

    Do you see another option?? ... maybe in place repair but you would need 1709 bootable media.... which can be downloaded.
      My ComputerSystem Spec


  10. Posts : 26,422
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #130

    What do you mean by testing a critical file?
    Does that mean opening the backup users folder and launching any file?

    There is an identical Windows 10 iso 1703 that failed to perform the in place upgrade repair.

    With ESENT database corruption one of the steps that may fail is Windows updates?
      My ComputerSystem Spec


 
Page 13 of 15 FirstFirst ... 31112131415 LastLast

Related Threads
how do I extract a boot image file from a WIndows 10 install USB to create a bootable ISO ? John
Hi all Here's the story... I had 2x 3TB HDD's in my NAS drive that was reporting that one of them had bad sectors, this was confirmed by Western Digital's HDD Utility tool, so I replaced it. I've reformatted it and hooked it up via a USB caddy...
Windows 10 Pro, Toshiba Satellite upgraded from OEM Win 8. Created system image w/ Macrium and restored it to a new second HD(HD2). Both drives had a lot of partitions due to Win 8 upgraded to Win 8.1 and back to Win 8 prior to upgrade to Win 10....
chkdsk /f /r failure to fix errors in Performance & Maintenance
How do you troubleshoot chkdsk /f /r failure to fix errors? Several days earlier chkdsk produced no errors. And several days earlier chkdsk /f /r was ran. I did not know how to find and view the log in the eventvwr. How do you find this...
I have a slightly annoying problem. I got myself a new 120GB SSD for the jump to Windows 10. I install the OS without problems from a DVD disk, boot up and begin to install stuff as steam, spotify and GeForce experience. I remove the...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:03.
Find Us