Windows 10: System won't boot to W10 (even USB, WinPE, WinRE)

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.sys[/quote] Code: BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys[/quote] I 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?

 

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:

Code: E:\Windows\System32\Logfiles\Srt\SrtTrail.txt[/quote] 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:.

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...

 

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.

 

Here's the info you requested. Sorry for just getting it to you. Went out of town for the holidays and then have been tied up since I returned.

Of note, I reinstalled W10 1709 via USB, but left to network cable unplugged so that it wouldn't download and install any updates and such. After using the system for around 5 to 10 minutes, it eventually shut off by itself and then restarted. After attempting to reboot multiple times, it finally let me get back to my desktop, and I immediately ran the DM Log Collector Tool. Hopefully, it has something helpful in it. This definitely seems to be an issue with 1709 as I can run older versions of W10 just fine.

 

Maybe my computer is MS account , and this software can not be supported , or should I upgrade my computer system if i want to use it ?

 

There was 1 unexpected crash .
There was no bsod or bugcheck.
Place the computer in safe mode for several days.
This can be with networking or with command prompt.

Boot into Safe Mode on Windows 10 Performance Maintenance Tutorials

Please update the system specs in the "My Computer" section:
System Specs - Fill in at Ten Forums Site Use Tutorials
System Info - See Your System Specs - Windows 7 Help Forums

In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab under startup and recovery click settings > post an image into the thread

 

I've got it booted into Safe-Mode. Update my system specs per your request.

 

Please un-check automatically restart.
This will enable you to view the BSOD window for the bugcheck.
Sometimes it may display a misbehaving driver in the form *.sys
If you see a misbehaving driver please record it and post it into the thread.

 

Hi @zbook,

Started messing around with this again. Tried reinstalling W10 once more. Install went fine and things worked for a bit. Decided to leave the computer on over the weekend and, well, when I came back to the office to check on it the fans were spinning at a ridiculously high rate with no output on the screen. I turned off the power via the switch on the PSU. Turned it back on and same result: fans spinning and that's about it. I cleared the CMOS, but that didn't work. I'm planning on grabbing the old RAM that was in the system before I upgraded it and reinstalling it to see if that does anything. Not really expecting it to as I'm pretty sure I tried that previously. I am also going to grab the old CPU that originally came installed with it and see if that does anything. I haven't tried that yet. Do you think it could also possibly be a MOBO issue. It's a Dell Inspiron 560s. Is there a way to figure out if the MOBO is proprietary or ATX? Wondering if I could just replace the MOBO and reuse all other parts. Or perhaps I should just buy a new case and ATX board that will work with the RAM that I purchased. Thoughts?

 

Hi ahelton,

What CPU, RAM and PSU did you replace?

Did you check the PSU provides enough to the 3.3v, 5v, 12v, vcore and RAM voltage?

 

Hi axe0,

I replaced the DELL PSU with a EVGA Supernova G3 Plus Gold, so I don't think the PSU is lacking in power. The old PSU was only 350 watts. I know rails are of importance too, but considering this is anything put a power system I would think that the new PSU is more than enough.

The upgraded CPU is a Intel Core 2 Quad Q9650 3GHz CPU. Everything I read said this CPU was compatible with my board as long as I did a BIOS upgrade, which I did. The old CPU was a Pentium E5500.

As for RAM, I just looked and realized I purchased the wrong item. I meant to grab some PC3 1066 and I purchased 1600 instead. Oops. Unfortunately, after reinstalling the old RAM modules the computer still doesn't boot. I even just tried using one RAM module in different slots. I just get loud, fast spinning fans and nothing else.

I'm going to try the old CPU later this evening or tomorrow when I have a bit more time.