CrashPlan, Windows Event Viewer, Frozen Device Manager, and SD Card readers

Hey all,

This is just a little dump of info that I found useful in diagnosing what CrashPlan was doing, and why it was constantly refreshing (and freezing) the Device Manager.  Hopefully this helps someone else down the line.

During my investigation of what was happening, I found a few hints as to what was happening in the Event Viewer.  First was a flood of VSS Errors ID 12294 with the text

Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine returned E_INVALIDARG. Routine details GetSnapshot({00000000-0000-0000-0000-000000000000},000001B6CE471A00).

Get Shadow Copy Properties

Execution Context: Coordinator

This error indicates that an application called for a VSS Snapshot, but the system was unable to fulfill the request.  This particular problem was caused by my SD Card reader not having media in it.  CrashPlan sees a drive, makes a VSS request and it fails.

I unplugged the Card Reader, but the errors continued… so I kept looking.

Under Applications and Services\Microsoft\DeviceSetupManager I found a few useful logs,

Source: DeviceSetupManager EventID : 130
Metadata package 356c6219-23c4-46f4-a7aa-61fa0ed1c928 has been staged for container {c0a56d36-7c5e-5045-9d6a-6da82d3564ab}, time was 123 milliseconds

Source: DeviceSetupManager EventID : 112
Device 'My Passport' ({c0a56d36-7c5e-5045-9d6a-6da82d3564ab}) has been serviced, processed 4 tasks, wrote 93 properties, active worktime was 1500 milliseconds.

Source: DeviceSetupManager EventID : 112
Device 'Samsung SSD 850 EVO 500GB' ({feb3b9a7-8493-11e8-b930-806e6f6e6963}) has been serviced, processed 4 tasks, wrote 34 properties, active worktime was 2330 milliseconds.

These three appear to indicate that data was pulled from my SSD into a VSS Container, then dropped into my local backup drive (a WD Passport)

After changing the backup interval from 15 minutes to 2 hours, and restarting CrashPlan, I haven’t seen the errors since, and the Device Manger is working well.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.