dmcmillen

Extraordinary Member
Joined
Jan 12, 2012
Messages
43
Win 7, Home Premium, 64
Every time I reboot my machine I get a volsnap Event 25 error: "The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied." and all restore points are deleted. I can successfully create restore points. C: drive has over 60gb free and protection for C: has 3.35gb max usage. I have tried turning system protection off and on and gotten the following errors for both off and on. It did turn off and back on.




Not sure whether System Volume Information is corrupted or what but would appreciate some help here.

This started when I had a data drive (not same drive as C) begin to fail and cause problems with windows booting. Once I replaced the data drive Windows booted ok, but with some odd problems including this. I am also experiencing a Kernel-Event Tracing Event 3: "Session "UBPM" stopped due to the following error: 0xC0000022" and a companion "Session "Eventlog-Security" stopped due to the following error: 0xC0000022" which I was going to start another thread on.

Everything else seems to be working ok, knock on wood. Thanks for your help!
 
Solution
It seems like you are encountering some issues with volsnap Event 25 error on your Windows 7 Home Premium system. This error indicates that the shadow copies stored on volume C were deleted due to the shadow copy storage not being able to grow in time. This can lead to the deletion of all restore points on your system. Here are some steps you can take to address this issue:
  1. Check System Protection Settings:
    • Ensure that the System Protection settings for drive C are configured correctly.
    • Verify that there is sufficient space allocated for shadow copies to grow.
    []Check Shadow Copy Storage:
    • Check if the shadow copy storage volume is experiencing any issues.
    • Consider choosing a different volume...
It seems like you are encountering some issues with volsnap Event 25 error on your Windows 7 Home Premium system. This error indicates that the shadow copies stored on volume C were deleted due to the shadow copy storage not being able to grow in time. This can lead to the deletion of all restore points on your system. Here are some steps you can take to address this issue:
  1. Check System Protection Settings:
    • Ensure that the System Protection settings for drive C are configured correctly.
    • Verify that there is sufficient space allocated for shadow copies to grow.
    []Check Shadow Copy Storage:
    • Check if the shadow copy storage volume is experiencing any issues.
    • Consider choosing a different volume for shadow copy storage if possible.
    [
    ]Check Data Drive Replacement Correlation:
    • As you mentioned that this issue started after replacing a data drive, there might be a correlation between the two.
    • Confirm that the replacement of the data drive did not inadvertently affect the shadow copy storage or System Volume Information.
    []System File Corruption:
    • It's possible that the System Volume Information folder or related system files are corrupted.
    • Running system file checker (sfc /scannow) can help identify and repair any corrupted system files.
    [
    ]Kernel-Event Tracing Event 3:
    • The Kernel-Event Tracing Event 3 errors you mentioned may also be related to system file corruption or permission issues.
    • Further investigation might be needed to resolve these errors. To address the volsnap Event 25 error, you can try the following steps:
      • Run a disk check on both the C drive and the data drive to ensure there are no underlying disk issues causing the problem.
      • Check the permissions on the System Volume Information folder to ensure they are set correctly.
      • Monitor the system for any recurring errors or warnings that could provide more insight into the issue.
      If the issue persists, you may need to dig deeper into system logs and perform more advanced troubleshooting steps. Feel free to provide more details or logs for further assistance.
 
Solution