The upload isn't complete. Please re-run the procedure again and let it run to completion (it may appear like it's frozen/not working - but it's still doing stuff!).
I did get one memory dump and the dxdiag report, so here's what I suggest so far:
Get all available Windows Updates. I don't know if any are missing, but many problems are solved by getting updates. Do this after updating/replacing the storage and chipset drivers.
Uninstall Daemon Tools/Alcohol 120% (only 1 indication that this is installed) - the sptd.sys driver that they use is known to cause BSOD's in Windows 7 systems. Once it's uninstalled, please use this free tool to ensure that the offending sptd.sys driver has been completely removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys
Interestingly, I've never seen this error before. Here's a link to what little info I have on it: BSOD Index
This seems to relate to a boot volume without enough free space to handle a Virtual Hard Drive
Yet you have more than enough free space on all 3 of your drives (according to the dxdiag report) - the boot volume has 61 gB free. But the NTStatus message c000007f means that the system has returned the message that the disk is full.
Were you trying to mount a Virtual Hard Drive? If so, what size was it supposed to be once it was mounted?
The memory dump shows at a VHD Miniport Driver (vhdmp.sys) is loaded when the crash occurred.
I wonder if the system is trying to store the VHD in the pagefile (wild speculation on my part) and it's too large for that (although the pagefile isn't a drive).
Is the BSOD/freeze/lockup on shutdown nearly 100% predictable? If so, we may want to use Process Monitor to see what's happening at shutdown.
EDIT: I haven't found much on using Process Monitor for this, but have found this: http://www.windowsitpro.com/article/...-with-xbootmgr
As above, update chipset and storage drivers (remove them first, if possible). This includes any disk protection devices containing an accelerometer (Disk Class Filter Driver for Accelerometer by ST MicroElectronics). I'm pretty much convinced that this is a disk sub-system issue - but am uncertain as to exactly what component is causing problems. The remainder of the report(s) requested above may help us to find the offending component.
Finally, I'd test with different Virtual Machines to see if it's just one that does it - or if it's all of them.
I'd also suggest removing the Virtual Machine program and then reinstalling a fresh copy (and then testing it again). OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT
mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT
use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers: BSOD BUGCHECK SUMMARY
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-17830-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Aug 2 06:38:46.903 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:12.778
Probably caused by : FSDEPENDS.SYS ( FSDEPENDS!DepFSAutochkWaitWorker+3d2 )
Bugcheck code 00000136
Arguments 00000000`00000000 ffffffff`c000007f 00000000`00000000 00000000`00000000
CPUID: "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"