New
#11
It's unclear as to why the computer cannot boot using a bootable windows 10 iso and can boot with a windows 7 iso.
Try these troubleshooting steps:
1) Boot from USB Drive on Windows 10 PC Installation Upgrade Tutorials
2) Try another USB stick
3) Try all USB ports (2.0 and 3.0)
4) Maybe when using UEFI Bios you have to temporarily switch to Legacy in BIOS settings
5) Turn off temporarily fast boot, secure boot, CSM if enabled
I've previously tried #2 and #3. Typically, to boot from a USB I just tap F12 a boot up and select the appropriate USB device. This worked from W7 USB and W10 1703, but not for W10 1709. However, I just booted the W10 1703 USB, clicked "Repair This Computer" and launched a Command Prompt and wiped the SSD. I have now downloaded a new 1709 ISO and made a new bootable USB and it appears to be working. I'm at the setup screen to select Language settings and such. I didn't attempt to move the User's directory this time and will see if that's what was causing the issue.
Ok. Finished clean installing W10 1709 without the other HDD hooked up. I shut down the computer a few times and then restarted it. At first, it appeared everything was working correctly. On about the fourth shutdown/restart, I decide to go into CMOS and check out settings. I didn't change anything and upon exiting CMOS it abruptly shutdown. It then attempted to restart and went into a loop again like it had been doing previously. Argh.
I'm going to load W10 1703 tomorrow instead and see if it does the same thing.
Any information on the failure?
What was the error code?
What was the bugcheck?
Remove all but one module of RAM and boot off your Windows PE disc and run Memtest86 for 7 passes for each module separately. Or press F12 and do the Diagnostics. If you get any errors (Red) that module is bad and needs to be replaced.
Sorry for the delay in responding, just got back around to trying things again. I ended up installing 1703 to see if I encountered the same issues as 1709. I've had it installed for the day and have shutdown/restarted the machine multiple times and everything works as it everything works fine.
Just to rule out overheating of the CPU, I just completed a stress test and monitored the temps of the CPU and everything checks out. I did go ahead and enable bootlogging and here is the output from the bootlog file for 1703:
Code:BOOTLOG_NOT_LOADED \SystemRoot\system32\drivers\WdFilter.sysI see that a couple of things are labeled "BOOTLOG_NOT_LOADED", although I haven't yet googled to see whether or not this is important. I can tell you when I originally installed 1709 I had a brief window where I was able to enable bootlogging and actually get to the ntbtlog.txt file. It has way more "BOOTLOG_NOT_LOADED" entries. Think this could be some sort of driver issue? I know Windows Update downloads drivers, maybe some sort of issue there?Code:BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
I've previously run the on-board diagnostics and everything checks out with the RAM. I've also previously attempted booting off various modules of RAM, but it still results in the same problem. I even got the old RAM that originally came in the system and tried it, but it doesn't work either.
It really seems like it something with this Fall Creator's Update that Microsoft just recently (1709). I can't seem to replicate the same boot problem with any other OS or W10 version.
When I install 1709 and try to boot, it restarts a few times before going into Automatic Repair mode. Sometime is reaches a screen where it says "Windows was unable to fix the problem" or something like that, and then points to this location:
I'm not entirely sure why it references E: since I don't have an E: drive. My Windows drive should be C: or D: I would think. I know it's C: in disk management, but I believe Windows sometimes labels them different on boot up (?). I seem to recall using the Command Prompt in WinRE, and it had my System Partition as C: and my Windows Partition as D:.Code:E:\Windows\System32\Logfiles\Srt\SrtTrail.txt
I figure E: would most likely be my flash drive??
I don't receive a BSoD or anything, so how would I go about trying to get further info on the error that is taking place? I tried enabling verbose mode on boot-up, but it doesn't seem to show anything...
Last edited by ahelton; 21 Nov 2017 at 18:19.
Please run the DM log collector and post a zip into thread for troubleshooting:
BSOD - Posting Instructions - Windows 10 Forums
It will automatically collect many files that will be helpful in the troubleshooting: msinfo32, dxdiag, drivers, installed, uninstalled, hosts, mini dumps, services, startup, event log, etc.