Slow Cold boot and GPU Issue

InglisF

Commendable
Sep 1, 2016
1
0
1,510
Hi

I've been having a problem with my PC since i built it and that is that every morning when i boot it up again (after it being off all night, so a cold boot) the PC takes ages to post and then ages to load windows off my SSD. After a restart or two it starts to boot normally.
The second part of the issue is that the above only happens with my onboard motherboard graphics and if i try to boot with my MSI GTX 980 GPU, then the system posts but usually there is no display and if there is it boots very slowly and there is general lag when i finally get into windows. When it doesn't load windows, The q code on my motherboard displays B2 and the VGA Led stays white, nothing appears on the screen

My preliminary thoughts were that my GPU was not getting enough power and so my PSU was drained causing lag and slow booting. I RMA'd my GPU and when i got it back, the problem persisted, so i can assume that the GPU is not at fault. Any help on the issue would be greatly appreciated. Thank you.

My System Specs:

Processor: Intel i7 6700k
Motherboard: ASUS MAXIMUS VIII HERO
GPU: MSI GTX 980
SSD: Samsung 850 Evo 250GB
HDD: Seagate Barracuda 3TB
PSU: EVGA Supernova G2 650W
 

Lutfij

Titan
Moderator
1| Have you made sure your motherboard BIOS is up to date?

2| I would suggest that you make sure your GPU drivers are also in order. Use DDU and uninstall your drivers and reinstall it with the latest revisions.

3| Apparently the common denominator in threads I've faced of this similar nature is that the PSU is by EVGA or the board is from MSI or that the GPU is from Nvidia. I'm lead to believe that eh drivers are the cause of the issue if it's the GPU(it's been known before that the latest drivers after Windows 10 firs came out caused the display's to go black).

4| You forgot to include your OS. Are you on Windows 10? If so, it might be a good idea to back up your critical content and reinstall your OS after you've recreated the bootable USB installer off of MSDN. If you think that's too much work, try a repair install and see if the issue persists.
 

TRENDING THREADS