Windows 8 and 8.1 Forums

User profile Failed to load.

  1. #1


    Posts : 10
    Windows 8.1 64-bit

    User profile Failed to load.


    I'm having a unique problem and I cant figure out if its my hardware or software failing.
    Short Version:
    Every time I install windows 8.1 on a formatted SSD it eventually somehow corrupts and after restarting or turning it off for a bit, the next time I log in I get the error, " User profile could not be loaded " Now i know this is because the profile is corrupt and I've tried to fix this via cmd prompt but it just isn't working. After reinstalling windows 8.1 multiple times this just keeps happening I've come to the conclusion it has to be something to do with a registry error and or a driver malfunction or complication. At first the OS works fine, right now i'm running the base 8.1 with all updates but only the base drivers that come with my cards.

    Specs:
    OS-
    Windows 8.1 64-bit
    CPU-
    AMD FX-6300 Six-Core Processor 3.5 GHz
    Motherboard-
    ASASUSTeK COMPUTER INC. M5A99FX PRO R2.0
    Memory-
    RAM 16.0GB Dual-Channel DDR3 @ 802MHzGraphics
    Card(s)-
    Two 3072MB ATI AMD Radeon R9 200 Series
    Monitor(s) Displays-
    42 TV (1920x1080@60Hz), HP 2310 (1920x1080@60Hz)
    Hard Drives-
    111GB OCZ-ARC100 SSD
    931GB Western Digital WDC SATA

    Not really sure what to do at this point as it seems like every time I install any kind of new driver at all everything starts to fail and I become locked out of my computer. I've tried doing chkdsk and running scans in the command prompt, looking into the Diskpart and checking for read-only flags and trying to make the windows section of my SSD set as Active, but nothing seems to work. Even tried Bootrec.exe. I just cant figure out what I'm doing, or not doing to ensure that this doesn't keep happening. And I'd like to go back to 10, I used it for a while and kinda like it. I will gladly settle for a stable 8.1 though. So if you have any suggestions or information you need from me, just tell me what and I will do my best to gather it.

    Long Version:

    I was using Windows 10 for almost a year and although it had some issues it was running alright. One day I messed things up while trying to get Nexus mod manager to open properly and took the advice from their forum, which led me to use a program called Ccleaner.exe to clean my registry files to make NMM work correctly. It didn't work and shortly after my computer had fatal errors and they just got worse over time. At first it was just sluggishness and then very long boot times with black screens, The windows menu wouldn't open and the action center wouldn't load. I also couldn't open most menus or windows for various systems or programs. System restore and image didn't work nor did the recovery media usb I had for Windows 10. Finally It began saying my user profile was corrupted, "User profile failed to load "

    My computer at that point was done for and I just reinstalled 8.1 and went straight to the windows 10 update. Began to re download my programs and update my drivers for my AMD cards and everything was working fine. I was able to load and play Crusaders Kings 2, but when i tried to load Skyrim, it wouldn't load. The next time I shut down my pc was the time it failed in this new and now repeating way. It now says it cant refresh or restart my pc because the drive that contains windows is locked and must be unlocked. I followed several online help tutorials but nothing really worked. I'm back at windows 8.1 but afraid to move forward with any installation of drivers for any devices including my amd cards.

    I'm afraid to restart it or anything because it may happen again. What I need is a list of things to prevent this error from happening again. Is there certain programs i can get or steps i can take to make sure this doesn't happen once again. I'm really getting tired of having to re install windows 8 or 10 at this point.
    Last edited by Right0usMan; 21 Jul 2016 at 00:09. Reason: Cleaning up

      My System SpecsSystem Spec

  2. #2


    Posts : 22,031
    64-bit Windows 10


    Hello RightOusMan, and welcome to Eight Forums.

    Depending on the exact error message you are currently getting, you might see if one of the tutorials below may be able to help with it.

    User Profile Service failed the sign-in - Fix in Windows 8

    https://www.eightforums.com/tutorials...ofile-fix.html
      My System SpecsSystem Spec

  3. #3


    Posts : 10
    Windows 8.1 64-bit


    Quote Originally Posted by Brink View Post
    Hello RightOusMan, and welcome to Eight Forums.

    Depending on the exact error message you are currently getting, you might see if one of the tutorials below may be able to help with it.

    User Profile Service failed the sign-in - Fix in Windows 8

    https://www.eightforums.com/tutorials...ofile-fix.html

    I've actually used both of those guides before and while they provide help after the error has occurred. I'm looking for ways to Prevent it from occurring at all. What steps can I take to make sure this error doesn't happen again?

    Edit: Let me be more specific, I've got windows 8.1 fully updated but I've not installed any graphic drivers, because once i do so, the computer will install them fine but the next time I log out it will inevitably give me that error again about being unable to load into my profile and then if i investigate further from the recovery screen I will also inevitably find that the drive is locked and must be unlocked. This has happened not once, not twice but three times in a row. There must be some way to for sure prevent these two specific errors from happening again.
      My System SpecsSystem Spec

  4. #4


    Posts : 22,031
    64-bit Windows 10


    What are you using or doing to lock the drive? BitLocker?
      My System SpecsSystem Spec

  5. #5


    Posts : 10
    Windows 8.1 64-bit


    Quote Originally Posted by Brink View Post
    What are you using or doing to lock the drive? BitLocker?
    As far as I know, i'm not using any program that specifically locks any of my drives. Bitlocker is not something that is or has been previously installed on my computer. After failing to log in ( profile corrupted ) I go into advanced options and try to reset, only to be told the drive is locked where windows is located.

    Programs I do use regularly that may be causing this issue as this issue seems to happen sometime after I install these three.. Spy Bot Search and Destroy, Malware Bytes, AMD install manager for my AMD cards. Currently just using the ones that came with the computer for fear of causing this error again if I update or do anything with the drivers. After many tutorials i'm sure it has to be something causing a registry error or a driver error with how I install them or something.
      My System SpecsSystem Spec

  6. #6


    Posts : 22,031
    64-bit Windows 10


    I must admit that I'm not sure what could be causing this either.

    For now, I would recommend to create a restore point before doing anything that affect the system to hopefully be able to do a system restore to undo it if needed.
      My System SpecsSystem Spec

  7. #7


    Posts : 10
    Windows 8.1 64-bit


    Quote Originally Posted by Brink View Post
    I must admit that I'm not sure what could be causing this either.

    For now, I would recommend to create a restore point before doing anything that affect the system to hopefully be able to do a system restore to undo it if needed.
    Is it possible my hardware is bad? Maybe I have bad sectors on my SSD where windows is installed or something? One time before, I used a program called DDU to fully remove any and all amd driver software, restarted and then installed a downloaded new driver. The computer ran fine, there was absolutely no problems.. but after I tried to restart the computer several hours later, the error occurred again. I just cant figure this out. I made a usb recovery drive which has allowed me a easier time of access the repair functions, but even if I run those, they cant fix the problem. I'm going to restart the pc and see if the issue comes up without having installed any updates or new drivers now.

    Also I should mention that although I have all recommended updates, I haven't installed the windows update for mico machine amd driver support. Its listed as being recommended, So after I do my restart and creating a new recovery point I'll see about installing that one.

    Edit: Also, I have a secondary hard drive that is a normal hard drive, not SSD. I'm attaching a picture that shows their status, keep in mind I've not yet added the 2nd hard drive to this new windows installation. One thing I'm curious about is though, previous times when i had them both registered on the installation the 2nd drive would still register as no protected.

    Click image for larger version
      My System SpecsSystem Spec

  8. #8


    Posts : 10
    Windows 8.1 64-bit


    Also, obviously the computer does see and recognize the 2nd drive there. I didn't register it myself though, usually I have to. I didn't format that drive like i did the SSD because i was tired of reinstalling my games. But before, when i had reinstalled 8.1, all three times I did format it. So I guess the problem isn't on that drive for sure.

    Edit: So I've installed and restarted several times with the windows driver for amd micro machines. So far so good. I'd like to install the new drivers for my cards next. I know that improperly doing this can be a cause of the issues i was having.. so. Currently I'm using the windows drivers.. should i remove them and then install new ones or just install over them? I'm actually not sure how to uninstall the window drivers for amd.
    Last edited by Right0usMan; 21 Jul 2016 at 15:13.
      My System SpecsSystem Spec

  9. #9


    Posts : 22,031
    64-bit Windows 10


    You could install the drivers over your existing ones, but I'd create a restore point first just to be safe.
      My System SpecsSystem Spec

  10. #10


    Posts : 10
    Windows 8.1 64-bit


    Quote Originally Posted by Brink View Post
    You could install the drivers over your existing ones, but I'd create a restore point first just to be safe.
    Alright So each time I install a new program there are errors on my c drive. When I installed and then uninstalled winrar 32 i restarted, scanned C and had errors, auto repair fixed them. Then I installed WinRar 64, scanned had errors and restarted. Scanned and found No errors. Installed Malwarebytes, same thing after it told me to restart, scanned and found errors. Restarted again and then scanned again after auto repair. Scan was unable to complete and restarted with auto fix again, this time detecting no errors. I have no idea who all that happened though.

    I'll make a restore point again now and see what happens when i try to install amds newest drivers for these cards.

    Edit: Just scanned again after waiting for about an hour from the last time i scanned. Haven't done anything, the pc was just sitting there. here is the event loggs from the detailed view of the scan for drive c.

    Chkdsk was executed in scan mode on a volume snapshot.


    Code:
    Checking file system on C:
    
    
    Stage 1: Examining basic file system structure ...
        Found 0x1 clusters allocated to file "...\amdkmafd.msi <0x2,0x3ae>" at offset "0x7" marked as free
            ... repaired online.
        Found 0x3 clusters allocated to file "...\amdkmafd.sys <0x2,0x3af>" at offset "0" marked as free
            ... repaired online.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x204c9 for possibly 0x1c3 clusters.
        Found corrupt basic file structure for "\Users\Ryan\AppData\Local\Google\Chrome\User Data\Default\Cache\f_000620 <0x4,0x60e4>"
            ... repaired online.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x7a9636 for possibly 0x7bda clusters.
        Found corrupt basic file structure for "\ProgramData\Microsoft\Windows Defender\Scans\mpcache-D4573AE0326AABE1EB2D865C233311CC93F3E471.bin.67 <0x3,0x67f5>"
            ... repaired online.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x30334 for possibly 0xc8 clusters.
        Found corrupt basic file structure for "\Windows\WinSxS\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.9600.17416_none_a6be6b1cc529b8b5\iexplore.exe <0x1,0x7f7d>"
            ... repaired online.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x71122b for possibly 0x4 clusters.
        Found corrupt basic file structure for "\Windows\Logs\CBS\CbsPersist_20160721042215.log <0x3,0x8f87>"
            ... queued for offline repair.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x70ee63 for possibly 0x16c9 clusters.
        Found corrupt basic file structure for "\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\1a6edd7a36968b7566b93cdc1cdb673f\PresentationFramework.ni.dll <0x6,0x1fd41>"
            ... repaired online.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x7111d2 for possibly 0x59 clusters.
        Found corrupt basic file structure for "\Program Files\WindowsApps\Microsoft.BingFinance_3.0.4.344_x64__8wekyb3d8bbwe\shared\js\FinanceUtils.js <0x3,0x21867>"
            ... repaired online.
        File "...\amdkmafd.cat <0x2,0x3ac>" and file "\Users\Ryan\AppData\Local\Google\Chrome\User Data\Default\Cache\f_000620 <0x4,0x60e4>" both own logical clusters [0x20518, 0x2051b)
            ... queued for offline repair.
        File "...\amdkmafd.inf <0x2,0x3ad>" and file "\Windows\WinSxS\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.9600.17416_none_a6be6b1cc529b8b5\iexplore.exe <0x1,0x7f7d>" both own logical cluster 0x303ac
            ... queued for offline repair.
        File "...\amdkmafd.msi <0x2,0x3ae>" and file "\Program Files\WindowsApps\Microsoft.BingFinance_3.0.4.344_x64__8wekyb3d8bbwe\shared\js\FinanceUtils.js <0x3,0x21867>" both own logical clusters [0x711228, 0x71122b)
            ... queued for offline repair.
        File "...\amdkmafd.msi <0x2,0x3ae>" and file "\Windows\Logs\CBS\CbsPersist_20160721042215.log <0x3,0x8f87>" both own logical clusters [0x71122b, 0x71122f)
            ... queued for offline repair.
        File "...\amdkmafd.msi <0x2,0x3ae>" and file "\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\1a6edd7a36968b7566b93cdc1cdb673f\PresentationFramework.ni.dll <0x6,0x1fd41>" both own logical clusters [0x70f760, 0x70f762)
            ... queued for offline repair.
        File "...\amdkmafd.msi <0x2,0x3ae>" and file "\ProgramData\Microsoft\Windows Defender\Scans\mpcache-D4573AE0326AABE1EB2D865C233311CC93F3E471.bin.67 <0x3,0x67f5>" both own logical clusters [0x7b0451, 0x7b045b)
            ... queued for offline repair.
                                                                                           
      155392 file records processed.                                                         File verification completed.
                                                                                           
      2358 large file records processed.                                                                                                                           
      0 bad file records processed.                                      
    Stage 2: Examining file name linkage ...
        Found an unneeded link ($FILE_NAME: "{1C4E74AC-149D-39AE-B74A-B53F4CC32D79}") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\Entries <0x2,0xb14>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "{1C4E7~1") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\Entries <0x2,0xb14>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "30") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\ResourceData <0x2,0xb15>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "68") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\Resources <0x2,0xb16>"
            ... repaired online.
                                                                                           
      204422 index entries processed.                                                        Index verification completed.
                                                                                                                                                                                        Found missing Index entry for file "...\301638BE4F53941F737B470E48DFD0DE0842AE9B <0x3,0x3b0>" from index "\??\C:\found.005" of directory "$I30"
            ... repaired online.
        Found 4 lost files (...\amdkmafd.cat <0x2,0x3ac>, ...\amdkmafd.inf <0x2,0x3ad>, ...); requesting reconnection to index "$I30" of directory "\??\C:\found.006"
            ... repaired online.
    
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
                                                                                           
      24522 data files processed.                                            CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    Windows has found problems and some were fixed online;
    the remaining problems must be fixed offline.
    Please run chkdsk /spotfix to fix the issues.
    
    
     116859903 KB total disk space.
      33211776 KB in 128410 files.
        101676 KB in 24519 indexes.
        226063 KB in use by the system.
         65536 KB occupied by the log file.
      83320388 KB available on disk.
    
    
          4096 bytes in each allocation unit.
      29214975 total allocation units on disk.
      20830097 allocation units available on disk.
    
    
    ----------------------------------------------------------------------
    
    
    
    
    Stage 1: Examining basic file system structure ...
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x60e4 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 24804.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x67f5 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 26613.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x7f7d is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 32637.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x8f87 is already in use.
    The attribute of type 0x80 and instance tag 0x0 in file 0x8f87
    has allocated length of 0xa040000 instead of 0x9740000.
    Deleted corrupt attribute list entry
    with type code 128 in file 36743.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xa000000019afe.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 105214.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x4000000019b24.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 105252.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x400000001ad10.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 109840.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x800000001e31d.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 123677.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x1700000001e320.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 123680.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x800000001e48f.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 124047.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xb00000001e4be.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 124094.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x500000001f105.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 127237.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x800000001ff8b.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 130955.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x2f000000020290.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 131728.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x700000002057d.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 132477.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x7000000020594.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 132500.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xa00000002059b.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 132507.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x70000000205c4.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 132548.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x70000000205c8.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 132552.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xb000000020a4a.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 133706.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xb000000020b7f.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 134015.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x6000000020d86.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 134534.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x6000000020d87.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 134535.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x7000000020d8e.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 134542.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x8000000020d91.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 134545.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x7000000020ef5.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 134901.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x500000002167a.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 136826.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x500000002168f.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 136847.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x40000000216cf.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 136911.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x400000002175d.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 137053.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x30000000218ab.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 137387.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1fd41 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 130369.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x21867 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 137319.
    
    
    Stage 2: Examining file name linkage ...
    The file reference 0x30000000003ae of index entry {1C4E74AC-149D-39AE-B74A-B53F4CC32D79} of index $I30
    with parent 0xb14 is not the same as 0x20000000003ae.
    Deleting index entry {1C4E74AC-149D-39AE-B74A-B53F4CC32D79} in index $I30 of file 2836.
    The file reference 0x30000000003ae of index entry {1C4E7~1 of index $I30
    with parent 0xb14 is not the same as 0x20000000003ae.
    Deleting index entry {1C4E7~1 in index $I30 of file 2836.
    The file reference 0x30000000003af of index entry 30 of index $I30
    with parent 0xb15 is not the same as 0x20000000003af.
    Deleting index entry 30 in index $I30 of file 2837.
    The file reference 0x30000000003ac of index entry 68 of index $I30
    with parent 0xb16 is not the same as 0x20000000003ac.
    Deleting index entry 68 in index $I30 of file 2838.
    CHKDSK is scanning unindexed files for reconnect to their original directory.
    CHKDSK is recovering remaining unindexed files.
    
    
    Stage 3: Examining security descriptors ...
    Inserting data attribute into file 24804.
    Inserting data attribute into file 26613.
    Inserting data attribute into file 32637.
    Inserting data attribute into file 36743.
    Inserting data attribute into file 130369.
    Inserting data attribute into file 137319.
    
    
    
    
    Checking file system on C: Stage 1: Examining basic file system structure ... Found 0x1 clusters allocated to file "...\amdkmafd.msi <0x2,0x3ae>" at offset "0x7" marked as free ... repaired online. Found 0x3 clusters allocated to file "...\amdkmafd.sys <0x2,0x3af>" at offset "0" marked as free ... repaired online. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x204c9 for possibly 0x1c3 clusters. Found corrupt basic file structure for "\Users\Ryan\AppData\Local\Google\Chrome\User Data\Default\Cache\f_000620 <0x4,0x60e4>" ... repaired online. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x7a9636 for possibly 0x7bda clusters. Found corrupt basic file structure for "\ProgramData\Microsoft\Windows Defender\Scans\mpcache-D4573AE0326AABE1EB2D865C233311CC93F3E471.bin.67 <0x3,0x67f5>" ... repaired online. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x30334 for possibly 0xc8 clusters. Found corrupt basic file structure for "\Windows\WinSxS\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.9600.17416_none_a6be6b1cc529b8b5\iexplore.exe <0x1,0x7f7d>" ... repaired online. Attribute record of type 0x80 and instance tag 0x0 is cross linked starting at 0x71122b for possibly 0x4 clusters. Found corrupt basic file structure for "\Windows\Logs\CBS\CbsPersist_20160721042215.log <0x3,0x8f87>" ... queued for offline repair. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x70ee63 for possibly 0x16c9 clusters. Found corrupt basic file structure for "\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\1a6edd7a36968b7566b93cdc1cdb673f\PresentationFramework.ni.dll <0x6,0x1fd41>" ... repaired online. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x7111d2 for possibly 0x59 clusters. Found corrupt basic file structure for "\Program Files\WindowsApps\Microsoft.BingFinance_3.0.4.344_x64__8wekyb3d8bbwe\shared\js\FinanceUtils.js <0x3,0x21867>" ... repaired online. File "...\amdkmafd.cat <0x2,0x3ac>" and file "\Users\Ryan\AppData\Local\Google\Chrome\User Data\Default\Cache\f_000620 <0x4,0x60e4>" both own logical clusters [0x20518, 0x2051b) ... queued for offline repair. File "...\amdkmafd.inf <0x2,0x3ad>" and file "\Windows\WinSxS\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.9600.17416_none_a6be6b1cc529b8b5\iexplore.exe <0x1,0x7f7d>" both own logical cluster 0x303ac ... queued for offline repair. File "...\amdkmafd.msi <0x2,0x3ae>" and file "\Program Files\WindowsApps\Microsoft.BingFinance_3.0.4.344_x64__8wekyb3d8bbwe\shared\js\FinanceUtils.js <0x3,0x21867>" both own logical clusters [0x711228, 0x71122b) ... queued for offline repair. File "...\amdkmafd.msi <0x2,0x3ae>" and file "\Windows\Logs\CBS\CbsPersist_20160721042215.log <0x3,0x8f87>" both own logical clusters [0x71122b, 0x71122f) ... queued for offline repair. File "...\amdkmafd.msi <0x2,0x3ae>" and file "\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\1a6edd7a36968b7566b93cdc1cdb673f\PresentationFramework.ni.dll <0x6,0x1fd41>" both own logical clusters [0x70f760, 0x70f762) ... queued for offline repair. File "...\amdkmafd.msi <0x2,0x3ae>" and file "\ProgramData\Microsoft\Windows Defender\Scans\mpcache-D4573AE0326AABE1EB2D865C233311CC93F3E471.bin.67 <0x3,0x67f5>" both own logical clusters [0x7b0451, 0x7b045b) ... queued for offline repair. 155392 file records processed. File verification completed. 2358 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... Found an unneeded link ($FILE_NAME: "{1C4E74AC-149D-39AE-B74A-B53F4CC32D79}") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\Entries <0x2,0xb14>" ... repaired online. Found an unneeded link ($FILE_NAME: "{1C4E7~1") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\Entries <0x2,0xb14>" ... repaired online. Found an unneeded link ($FILE_NAME: "30") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\ResourceData <0x2,0xb15>" ... repaired online. Found an unneeded link ($FILE_NAME: "68") in index "$I30" of directory "\ProgramData\Microsoft\Windows Defender\Scans\CleanStore\Resources <0x2,0xb16>" ... repaired online. 204422 index entries processed. Index verification completed. Found missing Index entry for file "...\301638BE4F53941F737B470E48DFD0DE0842AE9B <0x3,0x3b0>" from index "\??\C:\found.005" of directory "$I30" ... repaired online. Found 4 lost files (...\amdkmafd.cat <0x2,0x3ac>, ...\amdkmafd.inf <0x2,0x3ad>, ...); requesting reconnection to index "$I30" of directory "\??\C:\found.006" ... repaired online. Stage 3: Examining security descriptors ... Security descriptor verification completed. 24522 data files processed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Windows has found problems and some were fixed online; the remaining problems must be fixed offline. Please run chkdsk /spotfix to fix the issues. 116859903 KB total disk space. 33211776 KB in 128410 files. 101676 KB in 24519 indexes. 226063 KB in use by the system. 65536 KB occupied by the log file. 83320388 KB available on disk. 4096 bytes in each allocation unit. 29214975 total allocation units on disk. 20830097 allocation units available on disk. ---------------------------------------------------------------------- Stage 1: Examining basic file system structure ... Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x60e4 is already in use. Deleting corrupt attribute record (128, "") from file record segment 24804. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x67f5 is already in use. Deleting corrupt attribute record (128, "") from file record segment 26613. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x7f7d is already in use. Deleting corrupt attribute record (128, "") from file record segment 32637. Some clusters occupied by attribute of type 0x80 and instance tag 0x0 in file 0x8f87 is already in use. The attribute of type 0x80 and instance tag 0x0 in file 0x8f87 has allocated length of 0xa040000 instead of 0x9740000. Deleted corrupt attribute list entry with type code 128 in file 36743. Unable to locate attribute with instance tag 0x0 and segment reference 0xa000000019afe. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 105214. Unable to locate attribute with instance tag 0x0 and segment reference 0x4000000019b24. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 105252. Unable to locate attribute with instance tag 0x0 and segment reference 0x400000001ad10. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 109840. Unable to locate attribute with instance tag 0x0 and segment reference 0x800000001e31d. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 123677. Unable to locate attribute with instance tag 0x0 and segment reference 0x1700000001e320. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 123680. Unable to locate attribute with instance tag 0x0 and segment reference 0x800000001e48f. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 124047. Unable to locate attribute with instance tag 0x0 and segment reference 0xb00000001e4be. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 124094. Unable to locate attribute with instance tag 0x0 and segment reference 0x500000001f105. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 127237. Unable to locate attribute with instance tag 0x0 and segment reference 0x800000001ff8b. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 130955. Unable to locate attribute with instance tag 0x0 and segment reference 0x2f000000020290. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 131728. Unable to locate attribute with instance tag 0x0 and segment reference 0x700000002057d. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 132477. Unable to locate attribute with instance tag 0x0 and segment reference 0x7000000020594. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 132500. Unable to locate attribute with instance tag 0x0 and segment reference 0xa00000002059b. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 132507. Unable to locate attribute with instance tag 0x0 and segment reference 0x70000000205c4. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 132548. Unable to locate attribute with instance tag 0x0 and segment reference 0x70000000205c8. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 132552. Unable to locate attribute with instance tag 0x0 and segment reference 0xb000000020a4a. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 133706. Unable to locate attribute with instance tag 0x0 and segment reference 0xb000000020b7f. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 134015. Unable to locate attribute with instance tag 0x0 and segment reference 0x6000000020d86. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 134534. Unable to locate attribute with instance tag 0x0 and segment reference 0x6000000020d87. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 134535. Unable to locate attribute with instance tag 0x0 and segment reference 0x7000000020d8e. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 134542. Unable to locate attribute with instance tag 0x0 and segment reference 0x8000000020d91. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 134545. Unable to locate attribute with instance tag 0x0 and segment reference 0x7000000020ef5. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 134901. Unable to locate attribute with instance tag 0x0 and segment reference 0x500000002167a. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 136826. Unable to locate attribute with instance tag 0x0 and segment reference 0x500000002168f. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 136847. Unable to locate attribute with instance tag 0x0 and segment reference 0x40000000216cf. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 136911. Unable to locate attribute with instance tag 0x0 and segment reference 0x400000002175d. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 137053. Unable to locate attribute with instance tag 0x0 and segment reference 0x30000000218ab. The expected attribute type is 0x80. Deleting corrupt attribute record (128, "") from file record segment 137387. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x1fd41 is already in use. Deleting corrupt attribute record (128, "") from file record segment 130369. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x21867 is already in use. Deleting corrupt attribute record (128, "") from file record segment 137319. Stage 2: Examining file name linkage ... The file reference 0x30000000003ae of index entry {1C4E74AC-149D-39AE-B74A-B53F4CC32D79} of index $I30 with parent 0xb14 is not the same as 0x20000000003ae. Deleting index entry {1C4E74AC-149D-39AE-B74A-B53F4CC32D79} in index $I30 of file 2836. The file reference 0x30000000003ae of index entry {1C4E7~1 of index $I30 with parent 0xb14 is not the same as 0x20000000003ae. Deleting index entry {1C4E7~1 in index $I30 of file 2836. The file reference 0x30000000003af of index entry 30 of index $I30 with parent 0xb15 is not the same as 0x20000000003af. Deleting index entry 30 in index $I30 of file 2837. The file reference 0x30000000003ac of index entry 68 of index $I30 with parent 0xb16 is not the same as 0x20000000003ac. Deleting index entry 68 in index $I30 of file 2838. CHKDSK is scanning unindexed files for reconnect to their original directory. CHKDSK is recovering remaining unindexed files. Stage 3: Examining security descriptors ... Inserting data attribute into file 24804. Inserting data attribute into file 26613. Inserting data attribute into file 32637. Inserting data attribute into file 36743. Inserting data attribute into file 130369. Inserting data attribute into file 137319.
    005F020039550200E8CE04000000000064000000E50000000000000000000000

    Binary data: In Words 0000: 00025F00 00025539 0004CEE8 00000000 0010: 00000064 000000E5 00000000 00000000 In Bytes 0000: 00 5F 02 00 39 55 02 00 ._..9U.. 0008: E8 CE 04 00 00 00 00 00 ...... 0010: 64 00 00 00 E5 00 00 00 d...... 0018: 00 00 00 00 00 00 00 00 ........




    Just restarted, and it gave me this error. Rescanned C drive, found errors again.
    Click image for larger version
    Last edited by Brink; 21 Jul 2016 at 19:54. Reason: code box
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
User profile Failed to load.

Similar Threads
Thread Forum
User Profile Service failed the sign-in - Fix in Windows 8
How to Fix "User Profile Service service failed the sign-in. User Profile cannot be loaded." Error in Windows 8 and 8.1 This is for when you try to sign in to a user account using a temporary profile, you get the error message below instead of your user account starting. When you click/tap on...
Tutorials
New user cannot login (user profile service failed)
I am trying to add a second account to my machine and whether I try a Local or Microsoft account, I get the same "User Profile Service failed the sign-in. User profile cannot be loaded" error every time I try to sign in for the first time. I've Googled this a bit and it seems everything I've found...
User Accounts and Family Safety
The User profile service failed the sign in, please help
Hello everybody I have a lenovo y410p , each time I try to log in it gives me "The user profile Service service failed the sign-in. User profile cannot be loaded". I cant get into safemode because my computer doesn't fully shutdown, I tried some methods to get into safe mode but it still takes me...
General Support
User profile login failed and temporary profile created
Hi. I'm having this problem where when I tried to log into my computer it gave me this thing that my user login has failed and a temporary profile had been created. I was looking at other form posts with this problem and going through the steps. But while I'm in safe mode at the moment I still...
General Support
The User Profile Service failed to logon. No SID key.
I created a new account on Windows 8.1. The login attempt resulted in a "The User Profile Service failed the logon" error. Attempted the standard registry fix (linked below). However, a SID key does not exist for the new account. I've tried deleting the account, recreating, recreating in safe...
User Accounts and Family Safety
webroot and User profile failed the log on
So hello there forums. I'm in a crisis mode becuase my main computer is down and out. I have the error of the user profile failed the log on and as such I cannot log on to my windows 8.1 computer. I've tried following all of the advice online and have come only upon a list of things I am unable to...
System Security
The User Profile Service failed the sign-in.
Whenever I make a new user account I get: "The Profile Service service failed the sign-in User profile cannot be loaded." I've tried going into regedit and altering the user account, however there is not an S-1-5 entry associated with it. This happens every time I create a new user. My...
User Accounts and Family Safety
Eight Forums Android App Eight Forums IOS App Follow us on Facebook