07-07-2014 03:14 PM
Has anyone encountered this error shown in the subject line?
My computer will start running very slowly and so I do a normal shutdown and then try a reboot of the machine. During reboot I get some kind of "Lenovo Automatic Repair" message going on. It ends up with the ubiquitous blue screen of death with the "missing or corrupt winload.efi, error code 0xc0000185" error.
This has happened numermous times in the last two months.
Here's how I've managed to get it running: I disconnect all cables and the laptop battery and let the laptop sit for an hour or so. I then reboot with ethernet cable only plugged in. While rebooting, I'll press the F8 key a few times. One of two things happens 1) the "Lenovo Automatic Repair" message comes on again, then the same error code. 2) I'll get a screen that allows me to access the safe mode. At that point I just do a normal shutdown. I start the computer up again and it starts up normally and the problem is fixed........................ until the next time this happens which is usually weeks later.
All thoughts suggestions are appreciated!
Solved! Go to Solution.
07-08-2014 08:21 AM
Thanks for Posting!
This error seems to show on some users booting up normally and ended up booting into safemode to boot to normal mode again.
I suggest running an msconfig command an perform a clean boot.
than enabling the background files ny one's or by twos to check which is causing it.
On some cases this could be a UEFI hardware check with the ODD causing it to fail.
07-08-2014 12:05 PM
Hi Solid Cruver,
Thanks for your reply. I'm reading the link http://support.microsoft.com/kb/929135
When you go into msconfig and disable all the boot up items, does this become the new default, or does it apply to just that one reboot?
Also, it's kind of a chicken and the egg. When the error happens, you can't boot, so you can never get to msconfig, you just get the "blue screen of death" error message again. When I can coax it into safe mode and exit, it will then reboot correctly. So when the problem went away, how do you trace it?
07-08-2014 12:35 PM - edited 07-08-2014 12:35 PM
Thanks for Getting back.
If the issue will go away by going into safemode.
It is definitely one of the background or start up items or services
Msconfig will give you option to disable Start up items and Services.
This will remain Disabled until you change it back.
So to isolate the issue
Using MSconfig clean boot.
Since all non Microsoft Services and Startup items will be disabled you should not get the BSOD.
So i suggest after disabling all non Microsoft Services and Start up items Check the computer if it will show the same concern. If not then able two things under Services and start up then try to observe the system again.
07-18-2014 06:20 PM
I think I have found a solution and felt I should post it in the hope it might help others.
This microsoft tech's suggestion to use the command prompt "bootrec" command 3 times fixed my computer, I believe.
The only problem is in this age who has the "distribution media" for windows 8.1. Give me a break!
If you can get your windows 8.1 computer to reboot (as I could), I learned from another microsoft forum this essential fact:
when you're ready to shut down the computer and the "power" menu has "restart" in the options, press the "shift" key while pressing "restart" with your mouse. You will be able to access a command line prompt from which follow the url above.
hope this helps.............. isn't windows a pain?
07-02-2017 05:24 PM
I've had my Y510P for almost four years now and I'm just now encountering this problem. I don't have the Microsoft Installation Media, so I don't know how to reboot it so I can fix the problem. Everytime that I press F8 it does the same thing and goes back to the BSOD. I tried using methods above, like the battery unplug and use ethernet but it doesn't help. I've tried everything and nothing is helping, if I could get some help that would be wonderful. Thanks