BSOD Error C0000135; No reboot after Command Prompt to get DMP files

Hi everyone,


After closing our Asus laptop 2 nights ago (but not shutting it down), BSOD appeared with the following message:
STOP: C0000135 The program cannot start because %hs is missing from your computer. Trying reinstalling the program.
I've tried many different recovery/repair attempts after looking through the forum for answers, but nothing seems to have worked. My last attempt was to retrieve the DMP files, but the computer won't reboot to accept the command (currently, default setting of "No DMP" is selected, unfortunately).

Here is the process when I start up the laptop:
- (F8 accesses the safe boot menu, otherwise, the following process is what usually occurs when I start up the laptop)
- "Starting Windows" message with icon
- BSOD with error message
- ASUS logo page
- Windows Error Recovery message (asks to Launch Startup Repair Tool or Launch Normally)
- "Windows is loading files page"
- "Windows Corp" page
- Startup Repair checks for problems and fails; sends info to Microsoft Corp about problem
- Startup Repair main window offers option of "View diagnostic and repair details" or "View advanced options for system recovery and support", or Shutdown, Finish, and Cancel
- I click on Advanced options and I input keyboard language and admin password, then its takes me to System Recovery Options, which includes Startup Repair Tool, System Restore, System Image Recovery, Windows Memory Diagnostics, and Command Prompt
-

Any suggestions for a fix/recovery/repair would be greatly appreciated. See below for details of my attempts thus far.

GOAL:
I would like to learn what our laptop's problem is and how to fix it. But, as a last ditch effort, I would like to at least recover our files before reinstalling Win 7 (it came pre-installed, but I have my laptop's Win 7 product key).



---------------------------------------------------------------------
#1 FAILED REPAIR ATTEMPT: Remove Periphery Devices
I removed all periphery devices from my laptop (e.g., mouse, usb drives, CD/DVDs, printer, etc.). After removing all devices, I restarted my laptop with no change to BSOD.

#2 FAILED REPAIR ATTEMPT: System Restore to Previous Point
When I tried to restore the OS to a previous point, the restore failed and deleted that restore point. I have tried this 3 times, and each time it has failed and deleted the restore point. I now have about 5 restore points left, but I don't want to continue trying to restore the computer (and fail) and then be left with zero restore points.

The last restore attempt resulted in the following notice "System failed to restore the file (C:\ProgramData\Microsoft\Windows\StartMenu\Programs\Microsoft Silverlight) from the restore point. The restore point was damaged or was deleted during the restore."

Each time I've tried to restore it, I believe I received a different reason for the system restore fail, but I didn't record the first 2 comments.

Attachment 290797

#3 FAILED REPAIR ATTEMPT: Startup Repair
When I attempted to use Windows Startup Repair Tool, it stated "Startup Repair cannot repair this computer automatically," and provided the details below. When I looked at the Diagnostic and Repair Details Box, all tests had a result of "completed successfully" and noted an error code of "0x0".

Problem Signature:
Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200682
Problem Signature 05: AutoFailover
Problem Signature 06: 10
Problem Signature 07: BadPatch
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Diagnostic & Repair Details {Basics}:
Startup Repair diagnosis and repair log
------------------------------
Last successful boot time: 10/12/2013 1:46:03 PM (GMT)
Number of repair attempts: 10

Session Details
------------------------------
System Disk = \Device/Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of Root Causes = 1

Root cause found
------------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.

#4 FAILED REPAIR ATTEMPT: Safe Mode (& Clean Boot)
When I tried to restart the computer in safe mode, the computer stopping loading programs at "Loaded: \Windows\system32\DRIVERS\CLASSPNP.SYS

Then I was sent back to the Windows Error Recover (WER) Page which asks you to Launch Startup Repair (which fails) or to Start Windows Normally (which also fails and sends me back to the WER page).

#5 FAILED REPAIR ATTEMPT: Memory Diagnostics Tool
When Windows ran a memory test, no issues were found during the 2 phase test process. However, I was not actually able to see the results log because the results are displayed when you reboot and get to the Windows user login page (per the Diagnostic Tool instructions) and I cannot get to the login page since the BSOD appears and sends me to WER page.

#6 FAILED REPAIR ATTEMPT: LKGC (Last Known Good Configuration)
I used the F8 key when starting up my computer to get to the advanced boot options page and Safe Mode page and selected the Last Known Good Configuration option and hit enter. Upon restarting, the blue screen appeared as it does after every other attempt with the same error message.

#7 FAILED REPAIR ATTEMPT: Image Backup
I do not have a system image so this option is not available to me. (You live and you learn. I'll learn to do this next time.)

#8 FAILED REPAIR ATTEMPT: System File Check Scan
After opening the black command prompt box from the System Recovery Options page (opens after Startup Repair fails), I entered the command prompt "sfc /scannow" and got the following message: "Beginning system scan. This process will take some time. There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

So, I restarted the computer, which showed a blue screen error message upon boot up, then it went to the Windows Error Recovery page to ask if I wanted to "Launch Startup Repair" or "Start Windows Normally". I went to the Startup Repair screen, as I do in all my above attempts, and since no problem could be found by Microsoft, I was then sent to the Recovery Tools page. I clicked on Command Prompt, and again entered "sfc /scannow" and got the SAME message as befoew: "Beginning system scan. This process will take some time. There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

#9 REPAIR ATTEMPT: Disk Check
Upon attempting to do a scan disk check (using Command Prompt and typing chkdsk /f, ENTER, then typing chkdsk /r), the computer responded to both commands with "Windows cannot run disk checking on this volume because it is write protected".

Could someone kindly interpret the disk check information for me?

Attachment 290798
Attachment 290799

#10 FAILED REPAIR ATTEMPT: Mini Dump File
I followed the forum's guide to manually configure Windows to create a mini dump file, but after restarting (per the instructions) the changes were not applied because the computer will not reboot.

Attachment 290805



We have never had any issues with our computer and at the moment I am out of ideas, but happy to try new ones! Any suggestions?

Here is the scan you requested:

Attachment 290819

We did not install any new software, nor did any cleaning or virus removal. You guessed it, I just shut the lid to my laptop the night before the BSOD. I think the computer hibernates because I have to hit the power button and it takes some time to power up before I'm sent back to the login page.

I'm hopeful that your comment about it being "just a badpatch" means that it's got a possible fix?

Thanks again for your help.

Also, the most recent restore point available is 10/15/2013 and this was a "critical update" from Windows. I had an even more recent restore date that was a "System" Automatic restore, but it was deleted when my first restore attempt failed.

Here is another scan using "dskchk /f c:" command. I wasn't sure if this would help or not, but wanted to add it just in case.

I see... I didn't add double spaces between the prompts.

Well, after inputting the command correctly, I received the message below: