Windows 10 update and boot issues

Post Reply
User avatar
yipcha
Private
Private
Posts: 13
Joined: Sat Jun 23, 2012 8:54 pm
City: Portland
State: Oregon

Windows 10 update and boot issues

Post by yipcha » Fri Nov 02, 2018 6:52 pm

Is anyone else running into issues with windows 10 giving a blue screen referencing winload.exe after a recent update?

User avatar
yipcha
Private
Private
Posts: 13
Joined: Sat Jun 23, 2012 8:54 pm
City: Portland
State: Oregon

Re: Windows 10 update and boot issues

Post by yipcha » Sat Nov 03, 2018 8:35 am

Was just my computer forgetting the boot drive. I got it working again. Is weird though because it locked up while I had a browser open and I had to turn it off. My friend had the same ROG board and said his SATA controller went bad and known issue with that board. I guess he might be right, but I'm super stubborn and hesitant to blame hardware.

User avatar
thetruejaster
Sergeant
Sergeant
Posts: 137
Joined: Sun Feb 19, 2012 2:30 pm
City: Gresham
State: Oregon
Contact:

Re: Windows 10 update and boot issues

Post by thetruejaster » Sun Nov 04, 2018 2:31 pm

You might have a bad controller on your SSD. I had a drive act similar to your issues and then disappear completely. Worked in SOME other PCs but never again in mine. Looked like my ROG board was having issues, but it was a controller issue on the drive. That drive is currently in use in another person's machine like nothing ever happened.
T24 Group Lead since 22
PDXLAN: 20-32ab, F18
NovLAN: 20.5, 2015-2017
VectorLAN: 5, 7, 8

User avatar
citizenskippy
Specialist
Specialist
Posts: 48
Joined: Sat Oct 01, 2011 11:45 pm
City: Beaverton
State: Oregon

Re: Windows 10 update and boot issues

Post by citizenskippy » Mon Nov 05, 2018 1:26 pm

I had a problem on a fresh install. Browsers were freezing and timing out and system would lock up. If you stop and restart your crypto services and that fixes it, then you are experiencing the same bug I did from the Windows 10 April update.

If restarting the services fixes the issue you can search for a fix. I, too, thought it was a bad SATA controller or motherboard issue.

Post Reply