PC longer starting time

soumya.chakraborty6 · Feb 24, 2018

For the past two days my pc is taking longer time to start up. It is taking nearly 2 minutes to start up after pressing the on button on my cpu. Before that the monitor is simply showing "No signal". Once started, its working fine.
What is the reason behind this and what would be the appropriate solution? Urgent help needed!
(I am using Windows 7, my motherboard is Gigabyte 78LMT-USB3, and processor is AMD FX 4100)

ragnar-gd · Feb 24, 2018

There are some reasons of which i know why this might happen (there may be more). I assume from your description this sudenly happened, and you didn't change any components.
- Your MoBo has problems, esp. detecting components
- The first component to be detected, the GPU, has problems
- If your Harddisk had problems, you should be able to see it, so the problems ought to be on sopmesing initialized before. But I may be wrong.

Do you have some spare parts, i.e. a GPU, to compare?

soumya.chakraborty6 · Feb 24, 2018

ragnar-gd :

Sadly, no, I don't have a spare GPU to compare.. 2 days back it was working fine. The problem started suddenly. And no, I have not installed/changed any component/s. Do you have a solution to this? Would be of great help

ragnar-gd · Feb 24, 2018

Do you use the onboard-graphics? Or do you have a separate Add-On GPU?

soumya.chakraborty6 · Feb 24, 2018

ragnar-gd :

Yes, I do use onboard graphics. I don't have any add-on GPU

ragnar-gd · Feb 24, 2018

There is no easy way to detect pre-boot problems, except for using replacement parts. If you had changed anything, repeating the steps would be a good idea - but this isn't the case here. Pre-boot problems as you describe hint to (slowly) failing hardware, that is, here, your MoBo.

In any case, this is the time for a backup of your data!

Did you look at the windows eventlogs, to see if any warnings come up related to hardware?

soumya.chakraborty6 · Feb 24, 2018

ragnar-gd :

Yes I have gone through Event logs but there is no hardware event noted

Karadjgne · Feb 24, 2018

What changed 2 days ago. Windows updates? Added software that is in startup, updated software so now it's using startup? Have you installed the last version of all motherboard drivers for that board because Windows 10 Creators can play havoc with legacy drivers.

Something changed 2 days ago, figuring out what will be the first step to fixing the problem.

ragnar-gd · Feb 24, 2018

As long as you do your backups (and check if they succeed), and do not have any means of check with i.e. an add-in GPU, you cannot do much, but wait. If you have a shop that repairs PCs close by, you might visit them, and ask for advice (i.e. "Could i bring it in, and check with one of your spare parts? Here is some chocklate...")

soumya.chakraborty6 · Feb 25, 2018

Karadjgne :

I've not updated windows for about a month. Neither did I install any software. It started all of a sudden. The software part does'nt come into the picture though as it is taking time even before booting. To state simply, when I am switching the "on" button of my cpu, it is taking about 2 minutes to make the beep sound and thereafter it is booting and working fine. Note that when I am restarting my machine, it is starting up normally without any delay.

soumya.chakraborty6 · Feb 25, 2018

ragnar-gd :

Okay mate. Thank you for your advice.

Karadjgne · Feb 25, 2018

Ack. I've seen this before. Cold boot takes forever, reset is normal. Every time I've seen this it's due a driver error caused by fastboot. When you windows shutdown a pc, everything in your ram gets shutdown. Ram is blank. If fastboot is enabled it saves all that info on C drive first, so when you hit power on a cold boot, all your drivers are immediately returned to the ram. It means not having to find and reload all the drivers from scratch, can be much faster boot. Reset is different, it's a total wipe of the drivers and a full blank start from scratch, no fastboot.

So, that said, when you are operating windows, at sometime it's loading a driver that's in conflict with another, but currently not used. During fastboot, that conflicting driver is loaded to ram, and bios uses/checks every driver, so you get loops. If you really dig through your bootlogs and windows event viewer, you can probably find the culprit driver, but mostly they'll be legacy drivers from audio or lan that are conflicting with what windows wants to use.

Best immediate fix is to disable fastboot. With an SSD as OS drive, it really doesn't hurt, your cold boot times will be identical to reset boot times.

http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html

Use option #1 in a admin window. Should fix the issue. You also might be able to revert to fastboot at a later time, after most drivers go through upgrades.

Oh, it's Windows 10. Just because you didn't update, or authorize any updates, doesn't mean it didn't get updated. Windows will automatically update itself for minor fixes, bug fixes, security updates etc and never tell you. It's really only major updates that require your permission, like build changes etc.

soumya.chakraborty6 · Feb 25, 2018

Karadjgne :

Ack. I've seen this before. Cold boot takes forever, reset is normal. Every time I've seen this it's due a driver error caused by fastboot. When you windows shutdown a pc, everything in your ram gets shutdown. Ram is blank. If fastboot is enabled it saves all that info on C drive first, so when you hit power on a cold boot, all your drivers are immediately returned to the ram. It means not having to find and reload all the drivers from scratch, can be much faster boot. Reset is different, it's a total wipe of the drivers and a full blank start from scratch, no fastboot.

So, that said, when you are operating windows, at sometime it's loading a driver that's in conflict with another, but currently not used. During fastboot, that conflicting driver is loaded to ram, and bios uses/checks every driver, so you get loops. If you really dig through your bootlogs and windows event viewer, you can probably find the culprit driver, but mostly they'll be legacy drivers from audio or lan that are conflicting with what windows wants to use.

Best immediate fix is to disable fastboot. With an SSD as OS drive, it really doesn't hurt, your cold boot times will be identical to reset boot times.

http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html

Use option #1 in a admin window. Should fix the issue. You also might be able to revert to fastboot at a later time, after most drivers go through upgrades.

Oh, it's Windows 10. Just because you didn't update, or authorize any updates, doesn't mean it didn't get updated. Windows will automatically update itself for minor fixes, bug fixes, security updates etc and never tell you. It's really only major updates that require your permission, like build changes etc.

Thanks for your advice. But, I'm not using Windows 10, but Windows 7 ultimate. So option #1 will not be of any use I guess.

Karadjgne · Feb 25, 2018

Oh no. That works for any windows from XP onwards. As is, that particular post was from the Seven forums, so is explicit to win7. Win10 is the same thing, but there's a few different screens.

soumya.chakraborty6 · Feb 27, 2018

Karadjgne :

Thanks for your suggestion. But unfortunately,even after doing the mentioned thing my pc is taking long time before boot. And the time has increased to double. It now takes almost 4 minutes to start up.

Karadjgne · Feb 27, 2018

Wierd. Ok, well you can reverse the fastboot, turn it back on, same procedure but it's powercfg -h on instead of powercfg -h off

And you've tried sfc /scannow from that same window?

soumya.chakraborty6 · Feb 28, 2018

Karadjgne :

Yeah I've tried sfc /scannow. "Windows Resource Protection did not find any integrity violations" is all that I've got

soumya.chakraborty6 · Feb 28, 2018

Karadjgne :

Yeah I've tried sfc /scannow. "Windows Resource Protection did not find any integrity violations" is all that I've got

Karadjgne · Feb 28, 2018

On the one hand, that's good, no system files are corrupt, on the other, no issue got fixed. Have you used anything like CCleaner and run it a couple times through, and the registry cleaner too? Ake sure the boxes are checked to remove any temp files or inet cache files etc.

I'm grasping at straws because you are one of the few people who didn't get fixed by killing hiberfil.sys/fastboot/hibernation.

soumya.chakraborty6 · Mar 1, 2018

Karadjgne :

Yeah I do run CCleaner almost every 2-3 days to clear out all caches and also manually delete %temp% files once in a while. I'm starting to think that this a hardware problem, specifically on the motherboard, or else I don't see any reason for such an abnormal behavior which started out of nowhere. What I fear is one fine day my PC would not even turn on

Karadjgne · Mar 1, 2018

Nah, it's almost certainly not a hardware issue at all. I'm almost positive it's a driver issue. Cold boot takes forever because it's loading stuff that was in your ram before shutdown that gets saved to C temp file, reset doesn't, it manually searches windows and loads drivers from scratch. Somewhere in there is a program/app that's loading a different version or corrupted driver. To the ram, replacing the one loaded by the reset, you then save it at shutdown and get a loop at startup. Usual culprits are audio, Lan or gpu drivers. Since it's not a fastboot error.

soumya.chakraborty6 · Mar 1, 2018

Karadjgne :

Understood. But the thing is all my drivers are updated. So that's why it is all the more confusing. Anyways, thanks a ton for all your inputs. Will surely get back to you here if I can discover the reason behind all this.

soumya.chakraborty6 · Mar 1, 2018

Karadjgne :

I'd mention one thing though, when I'm rapidly switching my machine on/off, or when I'm restarting, it is starting normally. That is something to think about :??:

Karadjgne · Mar 1, 2018

Instant shutdowns or resetp clear your ram, so a boot is starting from scratch. A soft shutdown using windows saves all ram as part of fastboot, because normally a hardboot/reset should take longer.

PC longer starting time

Reputable

Reputable

Reputable

Titan

Reputable

Titan

Titan

Titan

Titan

Titan

Titan

Share this page