Hello,
I have problems with this error, seems to appear when I mess around properties of the hardisk/volumes.
Both C, D volumes are healthy/no bad sectors.
There is a 2 MB unallocated space at the end of the drive though that people around the net seem to agree it's natural - it is seen only in Acronis True Image and in the hardrive properties.
Thank you for your help.
hello,
i have the same error on a w7 x64 os, any ideas what might be causing it? google directed me here... :)
Hi,
All I found out is that it appears when I check disk/volume properties. Posted in other places too, but didn't find anyone knowing the system well enough to troubleshoot it.
Maybe you should fill other details about your system, they usually help a lot.
Gigabyte EX58-UD5, Core i7 920, Windows 7 x64 7600 RTM, 4HDDs: Velociraptor 300GB, WD6400AAKS, Seagate 640GB, Samsung 250GB.
I also have an assortment of partitions and even assigned letter B: to one of them (the DVD-RW is letter A:). I also have a dedicated SWAP partition placed before the system partition and I have assigned letter Z: to it.
Disk Management showed a gap of a couple of unallocated megs between two logical drives on a logical partition, but I have removed that by deleting the closest partition and then recreating it, including the previously unallocated space.
I will check if it appears when I check the properties of a partition or HDD, however it is very annoying the message does not include more details.
I'm not sure the unallocated space should cause any errors. I read on the net (I'll try getting back with some Google search results when I get back home) that the space is normal, as it is needed if you later decide to convert your drive from Basic to a Dynamic Disk. As I never had more than one HDD in my system, I'm surely not the one to explain these things, they seem to be related to RAID and multi-hdd configs.
The unallocated space should be positioned at the end of the drive (I remember I read that somewhere). As Windows sees that as a natural condition, it doesn't appear in normal Disk Management as you can see in the picture.
Are you also getting Volsnap (in the second picture) event?
OK, I have managed to replicate (not repair) the VDS Basic Provider error (code: 490@01010004). It starts to appear exactly when you install Alcohol 120% virtual drive. I'll attach the look of a Alcohol 120% installation below. The VSS error is Alcohol's too.
I am using Alcohol 1.9.8.7612, last version ATM.
Same error appears in the Event log by using Virtual CloneDrive 5.4.3.2 software (is this using sptd, too?). There is something with Windows 7 and image mounting software, maybe that infamous sptd driver, maybe not, maybe someone has qualified opinions on the subject?
The 1.60 version available on their site is not having Windows 7 compatibility.SPTD=SCSI Pass Through Direct (usually abbreviated as SPTD, filename "sptd.sys") is a device driver developed by Duplex Secure Ltd. that provides a new method of access to storage devices. The SPTD API is not open to the public.
Maybe someone can dig more on this.
OK I have the same problem too. Some parallels with other posters: I too run Win7 X64 Ultimate (it seems to be affecting X64) and I too have Virtual Clonedrive installed. In my case, there are two versions of the same error, one says 490@01010004 and the other D@01010004. My disk configuration is 500GB Seagate 7200RPM C: and 500GB 5400RPM Western Digital D: on Acer Aspire 6930G laptop (one of the few 16" laptops that take two physical drives). Machine newly formatted and built about 10 days ago.
I get another error as well, as follows: Unexpected provider failure. Restarting the service may fix the problem. Error code: 8007001F@0200014.
Just adding this info as it may help establish a pattern.
I don't have the Alcohol 120 software that toyo describes - never used it.
The culprit is the sptd driver, now at version 1.62 - some of the virtual disk apps like Alcohol 120% and Virtual Clonedrive install it. It is described on their forums too, feel free to check out their site, maybe download the last version, for x64 (I did just that, updated the driver correctly - they have some special procedure, but the errors keep on being logged).
However, the system seem to work just fine, it's just the damn logs... and who knows what other unseen failures, due to sptd. I'm waiting for version 1.63, but I don't have high hopes...
Quote