Long boot times in Windows 10 and CPU temps higher in UEFI

Toggle sidebar Toggle sidebar
B

bama_boy_2f2f

Prominent
Oct 6, 2017
31
0
530
Hi, everyone!
So I finally built my gaming pc after cca 6 months of savings, with brand new components:
Asrock B360 Gaming K4 mobo,
i5 8400 CPU with Silentium PC Grandis 2 XE1436 cooler,
16 GB DDR4 2666mhz HyperX,
Samsung 860Evo 500 GB SSD,
GTX 1060 6GB Msi Armor,
Corsair TX750M PSU,
Aerocool Aero 1000 Case (3 *120mm fans - two front intakes and one rear exhaust),
Windows 10 Pro OS.
I am having the following two issues:
1) Sometimes (not always), the boot times in Windows are quite long (about 1-2 minutes). It happens upon showing the motherboard logo - it just freezes there. After 1 or 2 minutes, the Windows loading screen appears, and it starts perfectly, in under 5 seconds. What seems to be the problem here? Is it a faulty ssd or motherboard?
2) CPU temps are higher in the UEFi bios. HWMonitor shows an average temperature of 31-35 degrees Celsius in idle, but UEFI displays an average of 40 degrees Celsius. I'm pretty sure I applied a good amount of thermal compound (the one which came with the CPU cooler - it was called Pactum). Should I worry about this or just let it be? I tested only one game until now - The Awesome Adventures of Captain Spirit, and MSI Afterburner showed an average of 35-37 degrees Celsius after about one hour of gameplay.

 
Solution
J
What I meant to say was that the 840, 850 and 960 are in my laptops and the other in in my desktop. The Windows Boot Manager always switches my SATA from AHCI to RAID and the Samsung SSD's have internal controllers that do that; in fact the 960 does not even utilize RAID. The WBM even tries to run drives that I have completely removed from my putters first! Placing them in the priority positions instead of the order which I have designated them every time it does its takeover of my OS. I wish someone could give me a method of completely killing this thingy off once and for all! Anyway try opening up your BIOS and checking to see if Windows Boot Manager has hijacked your system again...and again...and again. I would bet you a dime to a...
Sort by date Sort by votes
Lutfij

Lutfij

Titan
Moderator
Oct 7, 2009
54,048
4,741
173,390
Are you on the latest BIOS update for your motherboard(if there are any)? Define, good. If you added too much you would be experience some heat retention. Honestly, you didn't need an aftermarket cooler. You were fine with the stock cooler that came with the i5-8400.
 
Upvote 0 Downvote
B

bama_boy_2f2f

Prominent
Oct 6, 2017
31
0
530


No, I didn't mess with the Bios, it is the version that came with the motherboard. There are about two updates on Asrock's website. Good = the pea method. I'm sure I didn't put too many or too less, just the normal amount. The stock cooler seems like a joke to me, it shouldn't even exist.
 
Upvote 0 Downvote
J

jmatacola

Honorable
Jan 31, 2014
21
0
10,520
What does the Windows Boot Manager you set at; is it RAID or AH? I think that the Samsung 860 EVO has internal controls for those settings. I have a constant fight with my WBM every time there is any type of update and need to reset my BIOS for my 960 EVO and my 840 and 860 on my other 2 laptops. I really do not know why Microsoft is so annoying in this regard. You might want to look at that; it may be attempting to boot from drives you do not even have which occurs frequently on mine and slows me down and eats up my juice too. Good luck, do not know if this will help but, I hope it is not a wild goose chase and wastes your time
j
 
Upvote 0 Downvote
J

jmatacola

Honorable
Jan 31, 2014
21
0
10,520
What I meant to say was that the 840, 850 and 960 are in my laptops and the other in in my desktop. The Windows Boot Manager always switches my SATA from AHCI to RAID and the Samsung SSD's have internal controllers that do that; in fact the 960 does not even utilize RAID. The WBM even tries to run drives that I have completely removed from my putters first! Placing them in the priority positions instead of the order which I have designated them every time it does its takeover of my OS. I wish someone could give me a method of completely killing this thingy off once and for all! Anyway try opening up your BIOS and checking to see if Windows Boot Manager has hijacked your system again...and again...and again. I would bet you a dime to a donut this is where your drain and frustration are coming from.

j
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom