1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

error 0x80070005: access denied

Discussion in 'Windows Vista' started by glowpowered, Oct 27, 2007.

Thread Status:
Not open for further replies.
Advertisement
  1. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    I would like to create a system restore point and backup my system files, but i keep getting this error. I heard that i is probably another program using some files, but how to i solve that? thanks in advance.
     
  2. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    See if this applies first >> http://bertk.mvps.org/html/eerrormsgsv.html#3

    So you are getting that message whenever you try to create a manual restore point?

    Are automatic points being created?

    Does this error appear in the Event Viewer (run eventvwr.msc and copy/paste the details here if found.

    You might try either booting in Safe Mode and testing -- or perhaps better trying clean boot troubleshooting >>

    http://support.microsoft.com/kb/929135
     
  3. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    I tried the first link and unchecked the read-only box: no success, tried safe boot and clean boot: no success. No automatic points have been created. here is the event viewer error in the system restore

    Log Name: Application
    Source: System Restore
    Date: 10/27/2007 7:45:26 PM
    Event ID: 8193
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: LukeStonesif-PC
    Description:
    Failed to create restore point on volume (Process = C:\Windows\system32\rundll32.exe /d srrstr.dll,ExecuteScheduledSPPCreation; Descripton = Scheduled Checkpoint; Hr = 0x80070005).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="System Restore" />
    <EventID Qualifiers="0">8193</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2007-10-27T23:45:26.000Z" />
    <EventRecordID>2963</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LukeStonesif-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>C:\Windows\system32\rundll32.exe /d srrstr.dll,ExecuteScheduledSPPCreation</Data>
    <Data>Scheduled Checkpoint</Data>
    <Data>0x80070005</Data>
    <Binary>0500078002020000D60100000000000032CA19E58CAF4DCB010000000000000000000000</Binary>
    </EventData>
    </Event>

    Thank You for all your help
     
  4. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    If you run sysdm.cpl and select the System Protection tab, what drive(s) are selected there?

    If the c: drive, how much free space remains on this drive?

    And you say no restore points have been created at all? How long have you had the system?

    You might try removing the check from the main drive (should be c: -- normally), disabling system restore per the link below and then re-enabling it after rebooting.

    http://vistasupport.mvps.org/turn_off_system_restore.htm
     
  5. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    I tried each of my four drives and they all have the same problem. The root drive has 13.9 GB free of 37.7 GB. I tried disabling then restarting then re enabling system restore and it doesn't fix the error message. thanks again for all your help
     
  6. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    There's not much to be found for this. In the Event Viewer are you seeing any other errors, perhaps referencing "Volsnap" (system log) or "VSS" (application log)?

    Have you installed a non-Microsoft defrag utility by any chance?

    In services.msc is the Volume Shadow Copy service present and set to "manual"? Same for " Windows Backup and Restore"

    If you go to the Control Panel > Performance Information and Tools > Advanced and run a "system health diagnostic" -- what problems, if any, does it report?

    Finally, if you have installed using a Microsoft Retail CD -- you qualify for free Microsoft support; if this is an out of the box OEM system -- you should contact them for warranty support if the problem cannot be resolved otherwise.

    >> http://support.microsoft.com/contactussupport/?ws=support
     
  7. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    I see nothing from "Volsnap", but in the system log there are some warnings from "volmgr" saying that the system failed to flush data to the transaction log.
    In the application log there were some "VSS" information logs saying that it is shutting down. Also there was one saying that "Volume Shadow Copy Service" attempted to subscribe during setup.

    I have no third-party defragers.

    "Volume Shadow Copy Service" is set to manual. There is a "Windows Backup" and it's set to manual, but I see nothing suggesting the "restore" part.

    In "system health diagnostic" it says I have no anti-spyware or anti-virus, but i think they are just out-of-date. Also, It says that User Access Control is disabled, which i set.

    I have had Vista for only a couple months.

    Thanks again
     
  8. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    UAC can be disabled, and%2
     
  9. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    UAC can be disabled, and "manual" is the default for VSS.

    Do you have a sufficiently large 2nd drive or partition that would allow you to try a Full Drive Backup?

    This is one of the options in Ultimate.

    You should be able to do it on an external drive as well, of course.

    Was this Vista system an upgrade from another or is it an off the shelf OEM system like HP or Dell?

    If an upgrade that might explain having an out of date antivirus. As for "antispyware" -- Windows Defender should have come with it, and that qualifies.

    >> also can you use the 'copy' option to copy the "volsnap" error to the clipboard and paste it here. I need the event id, source and details to look into it further.
     
  10. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    I am not sure what you meant by post 8 and the first line of 9.

    I could do a disk backup if absolute necessary, but i am sure it would take a while.

    It is an OEM version that i installed on my custom pc.

    It didn't see an error from "volsnap".

    Also i have updated and ran AVG Anti-virus and spybot. AVG came up clean. Spybot detected some stuff and fixed it, but problem still remains
     
  11. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    Post 8 was a duplicate that should have been deleted but wasn't entirely. In post 9 I am just saying that UAC would have no effect on the problem. I keep it disabled myself.

    Was this a "clean" install or an upgrade?

    Let's give this a shot: navigate to c:\windows\system32\rstrui.exe

    Right click on rstrui.exe and select "run as administrator".

    Any better luck that way?

    If you look at the Security tab on the properties page, there should be checks for "read & execute" and "read" for "system", "administrators", and "Users"
     
  12. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    It was a clean install

    The only place i can go with that window is to open system protection.

    The properties tab checks out ok.
     
  13. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    What happens when you click "next"?

    And what happens when you open "system protection" and click "create"?

    Do you get the reported error for both immediately?

    In "available disks" what is present, and what is currently checked.

    I'm really in the dark here as much as you are, since there is little else on the web other than what I posted.

    So if you don't have too much to lose, you might want to take the option of doing another clean install.

    By the way, will chkdsk /r run on the drive? (requires a reboot and some patience). The log will be available in the Event Viewer > Applications > Wininit entry after reboot.
     
  14. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    The Next button is not click able. The only thing i can click takes me into system protection.

    Clicking "create" on each of my drives brings up the error. I have tried them individually and all at once with same result. All 4 of my drives show up in "system protection".

    I have so much software and i have tweaked vista so much that it would be a major undertaking to reinstall.

    I will run that chkdsk and post back.
     
  15. glowpowered

    glowpowered Thread Starter

    Joined:
    Feb 9, 2006
    Messages:
    278
    Here is the log:


    Log Name: Application
    Source: Microsoft-Windows-Wininit
    Date: 10/5/2007 12:45:27 PM
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: LukeStonesif-PC
    Description:


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


    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.
    69888 file records processed.

    83 large file records processed.

    0 bad file records processed.

    2 EA records processed.

    44 reparse records processed.

    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x5b9 is incorrect.
    0b aa 00 19 00 0f 1e a5 00 11 00 0b 28 a7 00 09 ............(...
    00 07 31 aa 00 00 00 0c 23 79 3c 00 00 0b 29 53 ..1.....#y<...)S
    Correcting error in index $I30 for file 1465.
    The index bitmap $I30 in file 0x5b9 is incorrect.
    Correcting error in index $I30 for file 1465.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff 80 af 84 33 6a fe c6 01 ...........3j...
    a3 88 c1 05 6a db c6 01 a4 83 55 7c e0 f7 c7 01 ....j.....U|....
    Sorting index $I30 in file 1465.
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x813 is incorrect.
    0a 00 4d 00 53 00 49 00 20 00 28 00 73 00 29 00 ..M.S.I. .(.s.).
    20 00 28 00 34 00 30 00 3a 00 30 00 30 00 29 00 .(.4.0.:.0.0.).
    Correcting error in index $I30 for file 2067.
    The index bitmap $I30 in file 0x813 is incorrect.
    Correcting error in index $I30 for file 2067.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff fa 82 46 4d 5a fe c6 01 ..........FMZ...
    c0 3b 36 b7 63 fe c6 01 08 1a 52 d0 e0 f7 c7 01 .;6.c.....R.....
    Sorting index $I30 in file 2067.
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x107df is incorrect.
    44 42 50 46 01 00 00 00 01 00 00 00 00 00 00 00 DBPF............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    Correcting error in index $I30 for file 67551.
    The index bitmap $I30 in file 0x107df is incorrect.
    Correcting error in index $I30 for file 67551.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff bb 58 dd 73 19 fe c7 01 .........X.s....
    bb 58 dd 73 19 fe c7 01 bb 58 dd 73 19 fe c7 01 .X.s.....X.s....
    Sorting index $I30 in file 67551.
    Index entry l_000120.log of index $I30 in file 0x997d points to unused file 0x9a17.
    Deleting index entry l_000120.log in index $I30 of file 39293.
    262916 index entries processed.

    CHKDSK is recovering lost files.
    Recovering orphaned file channels (2068) into directory file 2067.
    Recovering orphaned file identity (2070) into directory file 2067.
    Recovering orphaned file issuance (2071) into directory file 2067.
    Recovering orphaned file PKEYCO~1 (2072) into directory file 2067.
    Recovering orphaned file pkeyconfig (2072) into directory file 2067.
    Recovering orphaned file ppdlic (2073) into directory file 2067.
    Recovering orphaned file skus (2074) into directory file 2067.
    Recovering orphaned file cmiadapter.dll (15738) into directory file 1465.
    Recovering orphaned file cmitrust.dll (15739) into directory file 1465.
    Recovering orphaned file cmiv2.dll (15740) into directory file 1465.
    Recovering orphaned file CntrtextInstaller.DLL (15742) into directory file 1465.
    Recovering orphaned file helpcins.dll (15743) into directory file 1465.
    Recovering orphaned file locdrv.dll (15744) into directory file 1465.
    Recovering orphaned file OEMHelpIns.dll (15745) into directory file 1465.
    Recovering orphaned file rescinst.dll (15746) into directory file 1465.
    Recovering orphaned file slcinst.dll (56090) into directory file 67551.
    Recovering orphaned file SLsvc.exe (67575) into directory file 67551.
    Recovering orphaned file SECURI~1.XRM (67577) into directory file 67551.
    Recovering orphaned file Security-Licensing-SLC-ppdlic.xrm-ms (67577) into directory file 67551.
    22 unindexed files processed.

    69888 security descriptors processed.

    Cleaning up 171 unused index entries from index $SII of file 0x9.
    Cleaning up 171 unused index entries from index $SDH of file 0x9.
    Cleaning up 171 unused security descriptors.
    11675 data files processed.

    CHKDSK is verifying Usn Journal...
    The remaining of an USN page at offset 0x2a013bc0 in file 0x9295
    should be filled with zeros.
    The USN Journal entry at offset 0x2a014000 and length 0xf3014048 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a015000 and length 0x4f1f00a crosses
    the page boundary.
    The USN Journal entry at offset 0x2a016000 and length 0x457b815d crosses
    the page boundary.
    The USN Journal entry at offset 0x2a017000 and length 0x1e122e1 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a018000 and length 0x3e75a0b crosses
    the page boundary.
    The USN Journal entry at offset 0x2a019000 and length 0xb0220048 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01a000 and length 0xcae7c0c crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01b000 and length 0xf170aa06 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01c000 and length 0xfc0e01f1 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01d000 and length 0x1a516e0 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01e000 and length 0xe05f0206 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01f000 and length 0x1fb0285 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a020000 and length 0xb03701 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a021000 and length 0x17e605e3 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a022000 and length 0x82a91787 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a023000 and length 0xd562f701 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a024000 and length 0x70543d90 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a025000 and length 0x51209a23 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a026000 and length 0x54b78432 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a027000 and length 0xe76c29ec crosses
    the page boundary.
    The USN Journal entry at offset 0x2a028000 and length 0x15fc1eb2 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a029000 and length 0x11e1e025 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02a000 and length 0x43cc6243 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02b000 and length 0x37aa0044 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02c000 and length 0xf103f200 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02d000 and length 0xd6143303 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02e000 and length 0xf15000f7 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02f000 and length 0x10eb5200 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a030000 and length 0x58078150 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a031000 and length 0x4682ad20 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a032000 and length 0x19e29a05 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a033000 and length 0xfc3612f5 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a034000 and length 0x41eb2906 crosses
    the page boundary.
    Repairing Usn Journal file record segment.
    33793504 USN bytes processed.

    Usn Journal verification completed.
    Correcting errors in the master file table's (MFT) BITMAP attribute.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

    39621928 KB total disk space.
    19471992 KB in 54920 files.
    28272 KB in 11676 indexes.
    0 KB in bad sectors.
    170176 KB in use by the system.
    65536 KB occupied by the log file.
    19951488 KB available on disk.

    4096 bytes in each allocation unit.
    9905482 total allocation units on disk.
    4987872 allocation units available on disk.

    Internal Info:
    00 11 01 00 2f 04 01 00 e4 be 01 00 00 00 00 00 ..../...........
    c7 06 00 00 2c 00 00 00 06 02 00 00 00 00 00 00 ....,...........
    52 67 97 04 00 00 00 00 10 a7 de 0f 00 00 00 00 Rg..............
    80 4a 5d 05 00 00 00 00 00 00 00 00 00 00 00 00 .J].............
    00 00 00 00 00 00 00 00 ca b3 cd 22 00 00 00 00 ..........."....
    99 9e 36 00 00 00 00 00 c0 1f e7 00 70 6f 26 00 ..6.........po&.
    60 e6 2b 00 10 00 00 00 34 1d e7 00 b0 70 26 00 `.+.....4....p&.

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2007-10-05T16:45:27.000Z" />
    <EventRecordID>1436</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>LukeStonesif-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>

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


    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.
    69888 file records processed.

    83 large file records processed.

    0 bad file records processed.

    2 EA records processed.

    44 reparse records processed.

    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x5b9 is incorrect.
    0b aa 00 19 00 0f 1e a5 00 11 00 0b 28 a7 00 09 ............(...
    00 07 31 aa 00 00 00 0c 23 79 3c 00 00 0b 29 53 ..1.....#y&lt;...)S
    Correcting error in index $I30 for file 1465.
    The index bitmap $I30 in file 0x5b9 is incorrect.
    Correcting error in index $I30 for file 1465.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff 80 af 84 33 6a fe c6 01 ...........3j...
    a3 88 c1 05 6a db c6 01 a4 83 55 7c e0 f7 c7 01 ....j.....U|....
    Sorting index $I30 in file 1465.
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x813 is incorrect.
    0a 00 4d 00 53 00 49 00 20 00 28 00 73 00 29 00 ..M.S.I. .(.s.).
    20 00 28 00 34 00 30 00 3a 00 30 00 30 00 29 00 .(.4.0.:.0.0.).
    Correcting error in index $I30 for file 2067.
    The index bitmap $I30 in file 0x813 is incorrect.
    Correcting error in index $I30 for file 2067.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff fa 82 46 4d 5a fe c6 01 ..........FMZ...
    c0 3b 36 b7 63 fe c6 01 08 1a 52 d0 e0 f7 c7 01 .;6.c.....R.....
    Sorting index $I30 in file 2067.
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x107df is incorrect.
    44 42 50 46 01 00 00 00 01 00 00 00 00 00 00 00 DBPF............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    Correcting error in index $I30 for file 67551.
    The index bitmap $I30 in file 0x107df is incorrect.
    Correcting error in index $I30 for file 67551.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff bb 58 dd 73 19 fe c7 01 .........X.s....
    bb 58 dd 73 19 fe c7 01 bb 58 dd 73 19 fe c7 01 .X.s.....X.s....
    Sorting index $I30 in file 67551.
    Index entry l_000120.log of index $I30 in file 0x997d points to unused file 0x9a17.
    Deleting index entry l_000120.log in index $I30 of file 39293.
    262916 index entries processed.

    CHKDSK is recovering lost files.
    Recovering orphaned file channels (2068) into directory file 2067.
    Recovering orphaned file identity (2070) into directory file 2067.
    Recovering orphaned file issuance (2071) into directory file 2067.
    Recovering orphaned file PKEYCO~1 (2072) into directory file 2067.
    Recovering orphaned file pkeyconfig (2072) into directory file 2067.
    Recovering orphaned file ppdlic (2073) into directory file 2067.
    Recovering orphaned file skus (2074) into directory file 2067.
    Recovering orphaned file cmiadapter.dll (15738) into directory file 1465.
    Recovering orphaned file cmitrust.dll (15739) into directory file 1465.
    Recovering orphaned file cmiv2.dll (15740) into directory file 1465.
    Recovering orphaned file CntrtextInstaller.DLL (15742) into directory file 1465.
    Recovering orphaned file helpcins.dll (15743) into directory file 1465.
    Recovering orphaned file locdrv.dll (15744) into directory file 1465.
    Recovering orphaned file OEMHelpIns.dll (15745) into directory file 1465.
    Recovering orphaned file rescinst.dll (15746) into directory file 1465.
    Recovering orphaned file slcinst.dll (56090) into directory file 67551.
    Recovering orphaned file SLsvc.exe (67575) into directory file 67551.
    Recovering orphaned file SECURI~1.XRM (67577) into directory file 67551.
    Recovering orphaned file Security-Licensing-SLC-ppdlic.xrm-ms (67577) into directory file 67551.
    22 unindexed files processed.

    69888 security descriptors processed.

    Cleaning up 171 unused index entries from index $SII of file 0x9.
    Cleaning up 171 unused index entries from index $SDH of file 0x9.
    Cleaning up 171 unused security descriptors.
    11675 data files processed.

    CHKDSK is verifying Usn Journal...
    The remaining of an USN page at offset 0x2a013bc0 in file 0x9295
    should be filled with zeros.
    The USN Journal entry at offset 0x2a014000 and length 0xf3014048 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a015000 and length 0x4f1f00a crosses
    the page boundary.
    The USN Journal entry at offset 0x2a016000 and length 0x457b815d crosses
    the page boundary.
    The USN Journal entry at offset 0x2a017000 and length 0x1e122e1 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a018000 and length 0x3e75a0b crosses
    the page boundary.
    The USN Journal entry at offset 0x2a019000 and length 0xb0220048 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01a000 and length 0xcae7c0c crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01b000 and length 0xf170aa06 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01c000 and length 0xfc0e01f1 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01d000 and length 0x1a516e0 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01e000 and length 0xe05f0206 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a01f000 and length 0x1fb0285 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a020000 and length 0xb03701 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a021000 and length 0x17e605e3 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a022000 and length 0x82a91787 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a023000 and length 0xd562f701 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a024000 and length 0x70543d90 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a025000 and length 0x51209a23 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a026000 and length 0x54b78432 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a027000 and length 0xe76c29ec crosses
    the page boundary.
    The USN Journal entry at offset 0x2a028000 and length 0x15fc1eb2 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a029000 and length 0x11e1e025 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02a000 and length 0x43cc6243 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02b000 and length 0x37aa0044 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02c000 and length 0xf103f200 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02d000 and length 0xd6143303 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02e000 and length 0xf15000f7 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a02f000 and length 0x10eb5200 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a030000 and length 0x58078150 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a031000 and length 0x4682ad20 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a032000 and length 0x19e29a05 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a033000 and length 0xfc3612f5 crosses
    the page boundary.
    The USN Journal entry at offset 0x2a034000 and length 0x41eb2906 crosses
    the page boundary.
    Repairing Usn Journal file record segment.
    33793504 USN bytes processed.

    Usn Journal verification completed.
    Correcting errors in the master file table's (MFT) BITMAP attribute.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

    39621928 KB total disk space.
    19471992 KB in 54920 files.
    28272 KB in 11676 indexes.
    0 KB in bad sectors.
    170176 KB in use by the system.
    65536 KB occupied by the log file.
    19951488 KB available on disk.

    4096 bytes in each allocation unit.
    9905482 total allocation units on disk.
    4987872 allocation units available on disk.

    Internal Info:
    00 11 01 00 2f 04 01 00 e4 be 01 00 00 00 00 00 ..../...........
    c7 06 00 00 2c 00 00 00 06 02 00 00 00 00 00 00 ....,...........
    52 67 97 04 00 00 00 00 10 a7 de 0f 00 00 00 00 Rg..............
    80 4a 5d 05 00 00 00 00 00 00 00 00 00 00 00 00 .J].............
    00 00 00 00 00 00 00 00 ca b3 cd 22 00 00 00 00 ..........."....
    99 9e 36 00 00 00 00 00 c0 1f e7 00 70 6f 26 00 ..6.........po&amp;.
    60 e6 2b 00 10 00 00 00 34 1d e7 00 b0 70 26 00 `.+.....4....p&amp;.

    Windows has finished checking your disk.
    Please wait while your computer restarts.
    </Data>
    </EventData>
    </Event>
     
  16. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Similar Threads - error 0x80070005 access
  1. Bubsey
    Replies:
    1
    Views:
    128
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/644253

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice