Windows 10: Multiple boot problems with Windows.

Hi,

So I decided to upgrade my PC's CPU and motherboard a few weeks back. Ever since I've been having problems with my PC. I don't know if it's the new hardware or not but every test I do seems to say it's not about the hardware and that they're fine. I can't see any performance dips either.

So, my problems include:

• When I boot my PC, it goes on to give me a BSOD saying "ntoskrnl not found". It becomes a loop no matter if I press enter or F8. They both send me back to the same message after it flashes for a split second. The only way to get into my PC is by pressing the power off button for 5 seconds and when it closes, hoping for not seeing the same message after powering on. After I power on again, I see my PC opens up lights on the case etc. but there is no signal to neither the monitor nor the keyboard/mouse. This goes away when I press the restart button on my case after which my PC finally boots up normally. PS. Sometimes on the ntoskrnl loop, it says there's another file missing "winload"? I don't get that as often and when I press enter on that it gives me the ntoskrnl message again.
• When I try to fix these errors by advanced troubleshooting in advanced startup menu by using the cmd option, it doesn't open giving me another BSOD loop, this time giving me the error code "0xc0000098" and saying "windows32/config/system is not found" or something like that. It also says something along the lines of "There is no registry in registry book" it might be saying something different, I'm not using Windows on english so please forgive my translation if it's wrong.
• Sometimes when It try to restart the computer it gives this message with a black screen: "the file is possibly corrupt the file header checksum does not match the computed checksum". When I looked up this error online, nearly every source I found said there's a problem with either my RAM or the RAM slots on my motherboard.

I tried the fixes below:

• I tried running sfc /scannow but it says there's nothing wrong with the pc.
• I tried running chkdsk command but to no avail.
• I tried running some command from advanced startup troubleshooting command prompt but it gives the BSOD I listed above.
• I also tried a clean install from a USB boot drive but that didn't fix it either.
• I ran windows memory test on all my slots and all my RAM modules one by one. It only said there's a problem with the hardware on the first try when I didn't plug anything out before. After that, I started plugging out my RAM modules and started to put them in all the slots one by one, then putting both of them in the slots but the memory test says there's no problem on none of the tests.

I feel like I've done everything there's to do. Nothing I try works. What is the problem with my PC?

:)

 

Windows 10 1709 System Restore problems...

That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.

 

Boot Process

Hi,

Please suggest me a link that can explain the boot process step by step of ...

• Windows 7,
• Windows 8.1,
• Windows 10,
• Windows Server 2008 R2 and
• Windows Server 2012 R2

With Regards

InTech

 

laptop doesnt boot automatically

This is what happened.

1. Did a repair install and later disabled hibertnate in CMD.
2. Enabled legacy option ROM in BIOS.
3. After a few times startup ( i used the system in such mode for 5 days), changed boot option back to default.
4. Vola!! It boots automatically to win10 without any keypress. Tested it with many starts to confirm the same.
5. Re-enabled hibernate option using CMD and later selected Fast Startup.
6. System booted normally, without the need for any keypress.

I do not know exactly whether such steps resolved the problem or what else happened, hence cannot suggest above steps.

Many thanks to all members who helped to troubleshoot problems.