Jump to content

I just installed Windows 10 home with a usb drive. I got it installed on my SSD and everything seemed fine, after I reset to install drivers it wouldn't boot into the OS (Error message is attached) I checked the BIOS if the boot order was correct and it is. Does anyone know how to fix this issue? 

20171008_173638.jpg

Link to comment
https://linustechtips.com/topic/844067-windows-10-installboot-error/
Share on other sites

Link to post
Share on other sites

Moved to Troubleshooting forum section. Please go through the forum sections, and go to the section that best fits your question or problem.

 

Before we can start. all I am seeing is faulty GPU memory.

Switch graphics card and see if it foxes the problem.

Link to post
Share on other sites

14 minutes ago, GoodBytes said:

Moved to Troubleshooting forum section. Please go through the forum sections, and go to the section that best fits your question or problem.

 

Before we can start. all I am seeing is faulty GPU memory.

Switch graphics card and see if it foxes the problem.

Why would there be something wrong with my GPU memory when the GPU was fine a few days ago, I just did a clean install of Windows

Link to post
Share on other sites

16 minutes ago, HK_The_Almighty said:

Why would there be something wrong with my GPU memory when the GPU was fine a few days ago, I just did a clean install of Windows

Corrupted characters at the pre-OS level is due to faulty GPU memory. The BIOS sends the characters to the GPU to display it, but there corruption that happens.

If you have the Intel integrated graphics, remove your graphics card, connect your display to it, and see if the error changes.

Link to post
Share on other sites

22 minutes ago, GoodBytes said:

Corrupted characters at the pre-OS level is due to faulty GPU memory. The BIOS sends the characters to the GPU to display it, but there corruption that happens.

If you have the Intel integrated graphics, remove your graphics card, connect your display to it, and see if the error changes.

That worked, how am I going to get it working with my GPU?

Link to post
Share on other sites

1 hour ago, GoodBytes said:

Corrupted characters at the pre-OS level is due to faulty GPU memory. The BIOS sends the characters to the GPU to display it, but there corruption that happens.

If you have the Intel integrated graphics, remove your graphics card, connect your display to it, and see if the error changes.

I have tried two diferent GPU's, but it won't work. How can I solve this?

Link to post
Share on other sites

21 hours ago, GoodBytes said:

Corrupted characters at the pre-OS level is due to faulty GPU memory. The BIOS sends the characters to the GPU to display it, but there corruption that happens.

If you have the Intel integrated graphics, remove your graphics card, connect your display to it, and see if the error changes.

bump

Link to post
Share on other sites

Just now, HK_The_Almighty said:

I got two 8 gig sticks, should I test with one stick and see if that does anything? 

I did not install the English version of Windows.

Ah! So it could be outputing text in your langauge, but the BIOS/UEFI can only display ASCII characters and so the message appears broken.

Well that is a problem, as this would mean we are playing a guessing game.

All we know it is something related to NTFS...

 

So let's start with with the basics:

  • Is your computer BIOS based or UEFI based (if you don't know: what is your CPU... I'll guess from that?)
  • Try replacing your SATA cable for your HDD/SSD
  • Is this a new HDD/SSD?
  • Was your copy of WIndows 10 made using Microsoft Media Creation Tool?
  • Are you using USB Flash drive or Disk?
Link to post
Share on other sites

1 minute ago, HK_The_Almighty said:
  • CPU is a 3770K
  • SATA cable worked fine last week, but I will change it if I must 
  • My SSD is about 2 years old but no issues 
  • Yes I used Media Creation Tool to create a bootable USB Flash drive

Ok, going with the logic of the age of the CPU, and assuming you have a consumer grade motherboard, you have the new fancy UEFI.

But before we start: Ensure that your SSD is connected to SATA-0 on your motherboard

 

So let's make sure that your UEFI is properly configured (As every UEFI from each motherboard even models is different, I can't guide you exactly where to go, and some of the words might be different, and that is OK. Go with keywords and look through the UEFI settings. Use the motherboard manual for assistance):

  • Ensure that AHCI mode for your SATA Controller is enabled/selected
  • Make sure your SSD is part of the boot order list (to maximize startup speed, once everything is up and running, you can set it to first boot device). If you have the option between "<Your SSD model>" and "UEFI : <Your SSD Model", or "EFI : <Your SSD Model>", pick the UEFI/EFI one. The other is for legacy OSs or if you have legacy hardware.
  • Make sure that CSM (Compatibility Support Module) is DISABLED (only needs to be enabled for legacy OS (Windows 7 and older), or if you have legacy hardware that doesn't support UEFI
  • Make sure that Fast Boot is enabled or set to the highest speed.
  • Make sure that Delay is set to 0
  • Make sure that Wake on LAN is disabled (might also have: Wake up on Magic Packet, disable that as well)
  • Make sure booting from LAN is disabled (might not exists)
  • Disable any unused hardware
  • Make sure that your are set to "UEFI model" and not "Legacy" or "Compatibility" or "BIOS" mode anywhere
  • If you have HPET option, make sure it is set to HPET-64 bit
  • Make sure that you are not OC (you can OC after once you are up and running). Write down your OC settings to not loose them, if any.
  • Make sure that your RAM XMP (eXtreme Memory Profile) is set to Profile 1
  • Make sure that all CPU power saving options are not disabled, if you disabled them for your OC, if any.
  • Make sure that Secure Boot is enabled

Hopefully I didn't forget anything.

 

Link to post
Share on other sites

1 minute ago, HK_The_Almighty said:

So, I just booted with my GPU installed and it boots normally now. Thank you for helping me :D

Hmm ok. Good I guess.

I am still worried. But if the problem is solved we can't dig to find what is the problem until it happens again.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×