Taking a Long Time To Return From Hibernate

Just the last few days BUT.  Only because that is when I started experimenting with shutting down (or hibernating) then restarting soon.   Before I just shutdown or hibernated for the night and restarted the next AM.  Then it took many minutes. (long restart).  So I never shutdown or hibernated soon because I thought it would take forever. 

So I bought the SDD and still long restarts if shutdown for a long time.  So I started shutting down and restarting soon and that is when I discovered that restarting soon went really fast.

So I went back to the HDD.  It does the same thing.  Shutdown for a long time and it takes a long time to restart.  Shutdown and restart right a way and it is back soon.  Not a soon as the SDD but a minute or two.

Twilight Zone.

I am going to shutdown for a few hours now and will start again and time it.

Edited by PeteCal, 09 December 2022 - 06:27 PM.

My hiberfil.sys is 5,949,771,776 bytes. but I have not used it since 12/7/22 @3:11 PM (2+ days ago)

I just updated the drivers and BIOS a few days ago  Actually all drivers were up to date.  The BIOS was updated.

FYI I just rebooted after being shut down for almost 2 hours.  It took 8 minutes and 02 seconds.

I feel there is some correlation between how long it was shut down before restarting but I haven't done quantitative measurements.  I usually just shutdown for 3>4 hours or overnight.

Now I will shutdown, restart after 60 seconds and reset the BIOS.

See you on the other side.

I shutdown. 

Waited 60 seconds. 

Restarted to the BIOS conrol screen. 

Set to default.

Restarted.

Restart completed in 50.13 seconds.

I will now shutdown for overnight.

I could not delete nor rename hiberfil.sys "because the file is open in another program".

I removed hibernate from the power options but I still get that message.

It may not be important because I stopped using hibernate 3 or 4 days ago.  After I discovered the long boot ups happened if I shutdown also.  It seemed best to just stick to one type of stopping and boot up.  Especially since I could duplicate the long and short boot times in the (full) shutdown case.

This morning after 12 hours shutdown it took a little over 16 minutes to boot up.

I am starting to feel that if I collected enough data points on startup times verses shutdown time I would be able to draw a pretty curve,  Maybe do a regression analysis and have an equation. 

So far I have just done long shutdowns because I had other things to do or sort ones while experimenting.

Before you reinstall, unplug and replug your data cable, check the HDD for errors with chkdsk and one of the popular disk diagnostic tools.

S.M.A.R.T attributes
01
Attribute name: Read Error Rate
Real value: 0
Current: 119
Worst: 99
Threshold: 6
Raw Value: 000CC81480
Status: Good

Note this is a brand new SDD. 

chkdsk reports no errors.

I have unplugged and plugged the disk cable many times over the last few days.

I don't know where to go with this problem.  I hesitate to reinstall because based on my experience with windows (going all the way back to Windows 95} brute force blasts seldom improve things.

I used to have a signature on my emails:

 

If I had $0.01 for every time Windows crashed I would be richer then Bill Gates

Did you run DISM and SFC, in that order?  Probably won't fix it but...

I don't know what is going on and tend to agree with Dan, you should re-install, but I would suggest to use Windows 10.  I will keep watching you guys to see if you come up with a fix but I don't have time to spend on such corruption.  

What if you set Power Options to Balanced and reboot, then shutdown or whatever sequence you deem best to re-test it.  

You can also try a Repair Install, read carefully before proceeding

This may not work in your situation, don't know how many drive slots you have as you have not posted the model of the computer.  Put your OS on a smallish ssd and keep all your storage on other drives.  This will minimize your OS Image times or reinstall times.  Or you could always Partition the OS to a smaller Partition and keep storage on a storage partition.  This is what I do as my main computer only has one drive slot.  OS Images only take 8 minutes.  A reinstall without all my files takes less time too...obviously.

 I actually plan to upgrade from Windows 8.1 to  Windows 10 then Windows 11.  That seems to be the recommended sorceress.

But I wanted to fix this problem first.

Since I can recreate both Long startup and Quick startup when ever I want it seems to me that, if I could find out "what the CPU is doing" during these startups I could compare and find the problem,

I thought I could use the boot log but that had problems.  I got a Long and Quick and pasted them into a spreadsheet, side by side,  There were a few differences or places where the order was different but nothing that caught my eye,  Then the boot log stopped working.  No new entries but it is back now so I will try that again.

I also found out there is an Event log so I will try to compare Long vs Quick there.

SFC ran fine.DISM looks like it could do some damage if I run it willy nilly so I need to read up on it.

I'll update this thread if I find anything.

Thanks

Well it as been 9 days of troubleshooting including working with Crucial, the maker of this SSD.

Here is the message I just sent them.

 

Well, bad news for me, good news for you.  I have been doing a lot of troubleshooting.
I have a theory that the long startup time is due to the computer needing to "come up to temperature".
I know, temperature problems are usually due to too much heat but here is what I have found.

(1) If the computer is shut down for hours it takes many minutes (sometimes more then 20 minutes) to get the desktop screen.

(2) If I shut it down and start it again in a few minutes I will get the screen in less then a minute typically. That is, the computer is still warm.

(3) This desktop is networked with another desktop.  I can have this desktop in a "cold" state.  That means around room temperature overnight.  I can have the other desktop up and ready to network to this desktop.  If I power up this desktop and wait about 1 minute I can use the other computer to access this computer.  IT WORKS!  I can view files all over this desktop.  My documents, program files, almost everything.  So this computer is up and running but the screen is still blank and won't show the desktop for many minutes.

(4) I eliminated a temperature problem with the monitor by leaving the monitor powered up over night.  Next day this computer still took many minutes to show the desktop screen.

So, I guess I can eliminate problems with your SSD since I can access it from  the remote desktop within a minute of power up.

Sorry to have brought you this problem.

And if you or some other guru in your organization has any ideas, I'm all ears.

Thanks for your patients.

Pete
 

 

What do you folks think?

I have been trying to find a program that reports and logs the internal temperature.  So far I haven't found one one gives me valid readings.  SpeedFan reports

HDD= 28C reasonable

GPU = 4C and changing to 3C or 5C.  Seriously, the room is at 22C

Core 5C and changing to 6 or 7 sometimes,

I guess I need to debug SpeedFan before I can debug my problem.

Compare those to the ones reported in the BIOS / UEFI.  That will give you an idea if they are accurate.

Run these commands in this order to see if it will fix any corruption.  Then you can post the .cbs logs for members to look at, google where to find them.  If that don't help do a repair install, if that don't work do a Clean Install.  You don't need to upgrade to 10, you can just clean install and the product key on the board will be used automatically.  

DISM and SFC Tutorial

Before running any Diagnostics it is best to Image your Drive or at least Back-up all your important files if possible.  These tools are pretty safe so I will let you decide.  Make sure to be connected to the Internet first.

Run the DISM Tool as Administrator to Repair the Image.  Click on Start Menu and type cmd or Command, when the Command Prompt comes up right click on it and choose More > Run as administrator

Copy Paste the below command and press Enter

DISM /Online /Cleanup-Image /RestoreHealth

Then run the System File Checker the same way: Run as administrator

sfc /scannow

It may take an hour or so to run so be prepared.  Do not stop it till it finishes.

If sfc /scannow finds errors run it two more times to make sure they are repaired.  Reboot the computer between each run.

If SFC comes up with errors or fails then run this command to try and fix it.

dism /online /cleanup-image /startcomponentcleanup

Then run System File Checker again

PROBLEM SOLVED!!!!!

It was not the computer.  It was the monitor.

It uses a CCFL to backlight. One of the failure modes of a CCFL is taking a long time to make the screen visible.

I bought a new monitor.

Thanks everybody.

Edited by PeteCal, 31 December 2022 - 03:08 PM.