Thursday, February 16, 2017
STOP c0000135 the program cant start because hs is missing Try reinstalling the program Blue Screen error
STOP c0000135 the program cant start because hs is missing Try reinstalling the program Blue Screen error
This BSOD error occurs due to corrupted registry files and it is caused by some hijackers, viruses, malwares etc. More recently my PC crashes frequently and restarts every time. Then I decide to boot my PC with the function "Disable Automatic Restart on system failure" during start up and it stops at this blue screen of death.
After spending several time in fixing this issue with offline registry editors, again PC crashes with another BSOD error soon after fixing the previous one. It was a fatal system error report and now it was really a bad time for me.
STOP: c000021a {Fatal System Error} - This was the error faced by me. Very soon, (by luck) Ive have found another solution which saves my whole work and no longer the bad time continues. I think this was the entire solution for both the BSOD errors mentioned above.
Solution: (for Vista/7 Users)
[Last Updated on July 8, 2012]
[Last Updated on July 8, 2012]
By luck, if you found to have RegBack folder in C:WindowsSystem32Config then this was perfect fix. Simply copy all those files which is inside this folder and paste it outside the folder and replace all with same name. Hurray, you have won!
- Also check if there was any *.LOG1, *.LOG2 files in config folder and dont forgot to delete these since they are the virus programs which infects the registry files and make us unable to logon by crashing.
- These virus LOG files can be easily identified since it does not have any file type. In actual, all log files have file type as text document. To verify you can see their file properties.
If you are clueless on how to access this folder without encountering this BSOD error, I suggest some methods here.
Method1
Launching Recovery Console by pressing F8 key before Start-up screen appears to bring up eight functions menu > select Repair your computer option > Select your language for keyboard layout > Type the password for user account > Select command prompt from System Recovery options.
Method2
Using windows setup dvd (or) recovery disc. Boot the PC from dvd drive > press any key to boot from cd (if it asks) > select your language > click Repair your computer below the Install button.
click "Use Recovery tools that can help fix problems starting windows" radio button and select the operating system and click Next > and then select command prompt from System Recovery options.
Method3
If you have installed two OS on same PC, then it is easy to access this folder by logging into the other operating system whether it is XP/Vista/7/RedHat linux/Ubuntu/Fedora.
Method3
Using other third-party bootable dvds like Ophcrack LiveCD, Ubuntu LiveCD, Hirens BootCD.
Method4
Connecting your internal hard disk to another PC or laptop via IDE/SATA to USB adapter. For more to know read my post on How to use internal Hard disk as an external USB device.
Using Command prompt
1. Type cd<space>C:WindowsSystem32Config and hit Enter key.
2. Now type dir and hit Enter key.
3. Type the following commands as follows and press Enter key after each.
- cd RegBack
- copy *.* c:WindowsSystem32config
4. If it ask for overwrite any existing files (y/n) > type Y and press Enter.
5. If all files were successfully copied message is displayed, type exit to leave the command prompt and restart Windows.
Finally, if you couldnt find RegBack folder; thinking that I was wasting your time.
GO AHEAD! - FORMAT YOUR PC! - INSTALL NEW OS!
But this is not the end for XP users. Read this Microsoft article on How to recover from a corrupted registry that prevents Windows XP from starting.
Overall, the above choice is my best advice rather than editing registry files directly.
Note: If you are still interested in editing those registry files, read my post on STOP: c0000135 error - Solved using Registry Editor.
But this is not the end for XP users. Read this Microsoft article on How to recover from a corrupted registry that prevents Windows XP from starting.
Overall, the above choice is my best advice rather than editing registry files directly.
Note: If you are still interested in editing those registry files, read my post on STOP: c0000135 error - Solved using Registry Editor.
Available link for download
