EventID 8 and BSOD related to volsnap

dlrubin · 25 Jul 2013

I get BSOD seemingly at random times, about once per week, during times when I'm not in front of the computer (though I leave it on). I tried just starting over with a new install of windows, and reinstalled my apps, but that hasn't resolved. I also notice in the eventvwr an EventID 8 related to volsnap at least once per day (The flush and hold writes operation on volume C: timed out while waiting for a release writes command)
I also occasionally see EventID 25 for volsnap: 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.

What I've done so far:
1) chkdsk with fixing errors and repairing bad sectors (no errors were found)
2) sfc /scannow (no errors found)

Thanks

Arc · 25 Jul 2013

This computer is a virtual one?

Code:

System Manufacturer :   Parallels Software International Inc.
System Model :   Parallels Virtual Platform
BIOS Version/Date :   Parallels Software International Inc. 8.0.18608.898384, 10/26/2007

It is crashing at its own virtue.

Code:

BugCheck D1, {64, 2, 1, 8a3bf9b8}

*** WARNING: Unable to verify timestamp for prl_strg.sys
*** ERROR: Module load completed but symbols could not be loaded for prl_strg.sys
Probably caused by : volsnap.sys ( volsnap!VspReuseTableUpdateIrp+e )

Followup: MachineOwner
---------

A cyclical reasoning. The base of the computer is making it crash. Really dont think there is anything more to troubleshoot. You should start afresh.

Or, some troubleshooting may be done based on the host OS. Mac I guess?

dlrubin · 25 Jul 2013

Yes, you are correct, this is a windows 7 vm running on a MacPro (mountain lion) host os
The vm is on a HD that I've checked for integrity using diskutil and there are no errors.
Is there any other sort of debugging to be done, or are you saying I need to start afresh with a new windows 7 vm again?
Appreciate all the help (and hope can avoid starting afresh yet again..)

Arc · 25 Jul 2013

Mate I really think that it is something beyond windows' scope. As the failing program is Parallels, which is installed in Mac. Parallels made the windows environment, so windows is failing.

Earnestly sorry that it is the fact. Hope you can understand?

And as it is a windows forum, you will not get any Mac expert here (specially on the topic like environment virtualization) who can help you through the issue....

dlrubin · 25 Jul 2013

I appreciate your insights. Is there any generic approaches to troubleshooting on the Mac side you might suggest, or is there any particular info you can suggest from what you see that I can pass back to parallels tech support to help start getting at the heart of the matter?
Thanks!

Arc · 26 Jul 2013

If you contract the Parallels tech support, let them see the Bugcheck D1 part of my first post. They will get the idea.

Mate I have no idea about Macs. But as you are asking, I will ask our other members, if anybody have an idea.

bobafetthotmail · 26 Jul 2013

I suggest to ditch Parallels and use Virtualbox. It has a Mac version and all windows VMs I have run fine in it on both other windows and linux hosts. And there is a vastly larger literature on its use, tweaks and troubleshooting on all possible hosts and guests, as it is free and thus much more widespread than Parallels.

This tutorial will help you set up Virtualbox on your Mac to run a Windows 7 VM.

And if you need help in troubleshooting a mac, need to head for mac support forums.
Although I doubt that it's a OSX problem. With their approach to making computers (that's basically an appliance running a proprietary OS) it's hard for the mac to be unstable unless the hardware itself is failing or you are hacking it on purpose.