Hi there: I'm not sure how it all started, but I've been banging my head ever since. The first time problems occurred, Windows was having issues shutting down. Sometimes it would freeze during the shutdown stage and not shut down at all. Next thing I know, when I try to boot up the computer I get a bluescreen UNMOUNTABLE_BOOT_VOLUME error (discovered only after I disabled auto restart after bluescreen error). The netbook I have (A compaq mini) had a recovery partition installed, but none of the recovery options from the partitions worked, and I couldn't figure out how to create a USB repair disk (having no CD drive, of course). So I brought it away, spent 80 bucks (on a netbook!) and I'm not sure how he fixed it, but he removed the recovery partition in the process. Second time, it happened after a shutdown again. This time, some updates were installed just prior to shutdown (from the blue splash screen) then it seemed to shut down normally. Upon boot, though, Windows 7 wouldn't boot. No blue-screen error this time, just a blank screen and no Windows 7 start up, and now no recovery partition either. This time, however, I was able to figure out how to properly create a USB repair disk. Changed the BIOS settings to boot from USB, and ran the repair disk. It ran startup repair automatically, then when that couldn't fix it, gave me the option to do a system restore, which worked peachy keen. Third time (this time), it happened after a seemingly normal shutdown. Same as last, no bluescreen error, just unable to start. I thought "no big deal, I'll just run the repair disk again." This time, however, it was to no avail. Startup repair was unable to fix, and when I tried to run system restore, it said there were no restore points available. Help?

Hi, Thanks for the post! For this issue, we need to analyze the memory dump files to locate the root cause. Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. If the issue appears again, please refer to the following steps to collect memory dump files: 1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. 4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder". 5. Please send the ZIP file to us. You can refer to the following link to upload the information: http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Miya This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.