Windows 10: New Build - Win10 Home x64 - 2x BSODs, Partial Boot Issue
New Build - Win10 Home x64 - 2x BSODs, Partial Boot Issue
I've built an entirely new system over the last few days and I'm having some unexpected issues with Windows 10 Home x64 and it's driving me insane. This new build, and all components in the build are brand new... Software wise, I purchased a new key and used the Microsoft Windows Media Creation Tool to perform a fresh install. The other PCs in my home run Windows 10 with no little to no issues at all so I'm very concerned that I have a driver/hardware issue.
- Initial Boot to UEFI - Verified All Peripheral's Connected and Configured UEFI Settings (SSD & HDD set to AHCI) to allow boot priority to SSD & USB.
- RESTART - Booted to USB with Media Creation Tool. Selected SSD on SATA Port 0 for installation.
- INSTALL - No issues encountered, rebooted and installed LAN drivers to access internet. Began driver installation for MB, SSD and GPU. Restarted for windows updates and updated UEFI to latest version.
- Boot Failure - Windows Logo with black screen, no cursor. Restarted and entered UEFI to check boot settings, noticed a "Windows Boot Manager Port 0 SSD" and "SSD Port 0" option. Set to Windows Boot Manager, restarted and failed twice. Set to SSD and failed twice. Set to Windows Boot Manager and it finally booted to desktop. Some failures were a blue windows 10 logo with no mouse, no circle, nothing... other times "Preparing for Automatic Recovery" and one occasion it hung on the UEFI splash screen.
- Finished Windows Updates, completed all driver installations, begin software installation. Restart to verify everything and tweak UEFI settings and again, same issues with booting. Finally managed to get recovery to work, selected option for system restore point and it took me back to the first restart with no drivers installed.
- Inserted Media Creation Tool, deleted all SSD partitions and reinstalled Windows 10. I delayed the LAN driver until I had ALL driver's installed (including Samsung Magician) and then I installed the LAN driver and rebooted.
- After Windows updates, everything was smooth, no issue with booting, and the "Windows Boot Manager" partition was gone, only "Port 0 SSD" in UEFI.
- Restarted after a few updates and the system booted to a black screen with windows logo, no mouse, no status circle indicator. Restarted and it was fine.
- After joining my LAN home group and renaming the PC to match the scheme on my LAN I attempted to access another Windows 10 PC on my network and I got the first BSOD. Happened so fast I couldn't write the code down.
- Restarted fine, continued with file transfers and software.
- Today, another BSOD with "BSOD DRIVE IRQL NOT LESS OR EQUAL (lltdio.sys)" restarted fine and here I am.
My concern, I intend to overclock this system and without some semblance of stability, I cannot proceed. I'm not fully versed with Windows 10 but I have been keeping an eye on Event Viewer and both times I experienced the BSOD it was when accessing my LAN. The boot issue lingers but it's not nearly as bad for this second installation. Any help or assistance you can provide would be incredibly useful and appreciated.
Both dumpfiles blames your Killer network drivers.
The drivers are from Timestamp: Mon Apr 27 21:36:50 2015 (553E8FD2) predating windows 10.
Update your Bigfoot Lan driver from http://www.gigabyte.us/products/prod...1&RWD=0#driver
@lifetec - Wow, the installation I used is that exact one, is Windows 10 installing it's own driver perhaps afterwards? I'll certainly keep an eye on the Ethernet driver and reinstall the latest version, again.
As for the intermittent boot issues, any ideas there? My concern is that I've frelled up the Windows 10 installation or missed a crucial step/option. Could the lack of a solid Ethernet driver cause the boot issues as well?
I checked the drivers in the download from Gigabyte and they are the same ones as I have installed. I went to Killer's website and installed Killer Networking - Killer Suite it directly which updates the driver to version 18.104.22.168 dated, 9/22/2015. I haven't tested it yet but during the installation I booted to a black screen with a cursor and had to reset the system again. It's back up on the desktop now but the boot issue is still here.
This is a brand new build that I completed a few days ago, and I'm pretty baffled. I've done almost everything in my knowledge to fix the issue. Uninstalled drivers, one at a time, unplugged my additional SSD, and HDD drive, I've re-seated my RAM,...
This Problem has been happening since the Later Updates of Windows 10. (I remember when Windows 10 was first released, I had Zero problems with the OS, my PC was running fine. So, it confuses me, makes me think that it could be Windows 10, but it...
I just build a new machine with a Gigabyte B85M-D3H mobo, Intel Pentium G3258 CPU, 4GB Corsair Value Select DDR3 1333 and 120GB Samsung EVO SSD. I now want to clean install Windows 10 Home (64-bit) from USB drive (created with media...
I have been a Windows 10 Insider since the beginning. My main "test" machine for the builds is on my Mac but in Parallels Desktop. I'm considering moving to Boot Camp instead and just use Parallels to boot from the Boot Camp partition...
I currently dual boot win7 home premium and win10 pro TP. my question is if I upgrade or clean install over win7 will I be able to keep the win10 installation.
Also want to know if I clean install win10, can I use my win7 key so I get the...