Thank you very much !
The registry switching by MetaForr saves of the BSOD. MetaForr
And the registry modification by skidkid makes keyboard and mouse works. (even if the windows start normaly)
You have kiss from my mother-in-law.
Stephane.
I was able to solve this problem that happened when trying to downgrade my wife's computer.
Ended up being a driver, avgntflt.sys avira. I was able to rename the driver and it booted right up.
Hi
Thanks a lot.
I solved the BSOD loop problem by uninstalling Avira in safe mode.
I hate you BIll Gates... Go to hell!
Jo
hai guys I recently tried downgrading from windows 10 to 7 and well it gave me a bsod on my lenovo u410 laptop and the bsod was a isastor.sys problem. This is how i solved it:
I located a copy of install windows cd for the version of windows i wanted and booted from the cd and then started the install windows process.
Then it said that there was no drivers to install the os on due to the fact that for whatever reason by downgrading my laptop back to windows 7 it decided to delete my storage controller driver along with windows 10. So during the install process I basically reinstalled my storage controller divers and once the list of partitions showed up, I force shut down my laptop and booted the system again. It stopped looping the bsod after selecting starting windows normally as opposed to the startup repair and windows ran with no problems with no files lost at all. All that seemed to be missing was that one driver that caused my bsod. I found this solution here and as opposed to following all of the steps on that said page, i did the first step and then checked out what was going on with my system as a fresh install is my last resort. hopefully this helps
So I had the same problem (except I did rollback immediately by cancelling the upgrade from Win 7 to Win 10 in progress by not accepting the EULA) - BSOD with STOP 0x0000007e error. System repair would not work. I was still able to start the system in the Safe Mode though.
I reviewed the dump file (with BlueScreenView) and found out that the file that was causing the error was klhk.sys. After checking the file online, it was clear that it was Kaspersky's antivirus system file (note: other users had similar problem with klif.sys). I have never had Kaspersky installed on my Win 7 so I guess it must have come with the Win 10 Upgrade and crashed during the startup, as it was not installed on the Win 7 installation.
So to get rid of the problem sys files, I used the official Kaspersky removal tool - kavremvr.exe - which uninstalled whatever was left of the antivirus from the system (it actually did not find any installation automatically, so I just manually picked both version 2015 and 2016...)
After the restart, I was able to start the system normally - problem solved!
Hope that helps.
Do keep in mind that using BlueScreenView is NOT recommended as it often gives incorrect info, it's very little that it actually gives correct and useful info.
I had the same BSOD problem. Came here, saw the post about Avira, uninstalled Avira in Safe Mode and it booted right up as normal. Everything is good now. Thank you very much!
I can't believe 'Laith' would recommend you to 'copy over the files from D: to C: using an setup commandprompt'. WTF man? Lol
That is horrible advice. Odds are if your C drive appears empty and your D looks like your C drive and you are in recovery options then your drives are probably mounted differently than when booting to Windows. A recovery partition, ram disk or removable volume was probably assigned to C (first drive), then your boot drive (D) and so on.. so your E drive is probably your D. This might be confusing to look at but shouldn't effect the recovery options, so it's hardly relevant as to getting closer to a solution and appears to have derailed the conversation.
I know this post is old and you resolved the issue one way or another but please provide more information in the future as well as details.. like I booted to the Windows disk and am in Recovery Mode.. I tried this that and the other. Most likely just a regular boot recovery would have fixed everything and I'm not sure you should have ever been on the command line. And if you can't figure out Windows command line, someone shouldn't recommend a Linux boot disk unless it's a Utility disk like Hirens boot CD with somewhat straight forward options. But again, there should have been little reason for you to go that far.
I had to post only because of pure fear this is how people think they're helping other people. If you don't know what you're talking about, don't say anything or at least keep it more general and not technical that could in turn just screw up someones day or give them the wrong idea on how it works. After all better to be thought a idiot, than to speak and remove all doubt. Right?
Good luck!
Last edited by aliasfoxkde; 23 Jun 2016 at 13:10. Reason: typo
Thanks skidkid, your post got my keyboard and mouse working again in safe mode.
I used the kavremover tool to get rid of Kaspersky Internet Security and then rebooted back to normal mode, and it is working now.
I guess what happened with the W10 rollback to W7 fail is it could not handle the antivirus.
Just FYI, I was getting a reboot loop with BSOD 7e. I could get into safe mode but the keyboard and mouse were not responding.
I was able to get into the regedit.exe even without a bootable USB drive.
However, there I
- can't load the System hive as it is "in use"
- only find ControlSet001 and not 002
- the values of the upperfilters are already as described
My questions are:
- do I need the Bootable USB drive even?
- I am sure I have the Kaspersky issue. Is there anyway to disable it with access to the cmd menu?
Or is a clean wipe my only chance?
Thanks
Quote