Can't Turm off Fast Boot and/or Hibernation(?)

The free space on the windows drive impacts performance and possible file deletion.
There are two main types of dump files: mini and memory dump files.
If the computer has problems with hardware or software drivers or hardware it may produce a bsod.
To troubleshoot the crash, bsod files are needed for debugging.
Windows will often delete memory dump files if the free space is < 25 GB.
So this may eliminate important files that could be used in the troubleshooting.
Mini dump files should be available for troubleshooting.
At times the mini dump files do not have enough information to troubleshoot the dump files and memory dump files are needed.

This is a typical event file entry:

Event ID: 1018 The dump file at location: C:\windows\memory.dump was deleted because the disk volume had less than 25 GB free space

The loss of memory dump files can occur with insufficient drive file space or using software that cleans the dump files.

The Ccleaner settings were modified. However the free space if < 25 is likely to delete the memory dump files.

Thank you - I now understand. Fortunately windows has been/is working fine without any issues like bsod. I'm still having the issue of FastBoot and not sure how memory/free space is stopping me turning this feature off.

The log files were scanned for problems.
Some were reported so that they could be troubleshooted.
The main problem has not yet been fixed.

If an image of the drive is made the drive can then be clean installed.
Then boot problems can be reevaluated.
If the problem persists then the problem is likely in the BIOS.
If the problem is eliminated then further evaluation needs to be made after the image is restored.




To ensure that there are no improper bios settings please reset the bios.
1) Sometimes there can be failure to boot after resetting the bios.
2) Backup the computer files to another drive or to the cloud.
3) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
4) And please create a brand new restore point.


How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how...bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

@ quarkrad, in reference to Post #5

“One of the issues with dual booting is one has to turn off win10 fast boot/hibernation otherwise the dual boot has problems - which it appears I now have.”
--- I wasn’t aware of that as I didn’t have that problem when I was dual booting but I didn’t have UEFI BIOS or SSD at that time so I suppose that would make a difference.

I Know you said “I dual boot with a linux system and up to now all has been fine” but just to verify,
--- Before you had to reinstall Linux, did you have Fast Boot & Hibernation turned off in Windows 10 when it was running fine?
--- Before having to reinstall Linux, was there an issue with the 1-hour time difference?

Hi, to fix the time zone differences between linux and windows, I had to implement this registry patch in windows and then adjust the clock to match current time. Reboot and then the clock will stick to UTC time zone at all times since linux usually uses UTC time zone as opposed to local time zone.

Here's the reg patch:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001

It couldn't hurt to try it out and see if it fixes your clock problem between linux and windows.

@ quarkrad which Linux distro are you using? You might want to go to the appropriate home page and find out how to fix the time difference if titetanium's method doesn't work.

I've been dual booting for some time with windows 10 and Ubuntu - originally when Istarted I had a sata HDD. I can't remember when I changed to a SSD, but I think I was running windows 10 (1709) and ubuntu 16.04. I reinstalled both OSs from scratch months and months ago, windows first, and then ubuntu. I had to to turn off FastBoot/hibernation in 1709 and everything was great. Both win10 and Ubu loaded quickly - although, I never really timed them. As time went on, 1709 became 1803 and still everything was OK. At some point ubuntu 18.04 was released and, using the same partitions, I did a clean install of Ubuntu (18.04). I never checked the status of FastBoot because Ubuntu was loading in about 15sec - as was win10. So .... I was happy. Without going into the reason why I had to do a clean install of Ubuntu - which I did. This is when suddenly I found windows loading almost instantly (in terms of the boot process starting - completing to Desktop in about 11s) whereas ubuntu is taking about 62s. I am working with the ubuntu forum and there are still some tweaks I amm doing on my ubuntu side - but gosh, win10 boots amazingly fast so I suspect despite having turned everything off it is very much still on.

That's a very good explanation. I wonder if it would make sense to go back to just Windows 10.
Disable both fast boot/hibernation and secure boot and see how it runs for a few days, maybe even a week.
When satisfied on Windows 10 operation, then try to include Ubuntu.

Thank you - wonder if I can turn off FastBoot/Hibernate with just Windows install? However:

SORTED - it was my usb card reader and extra USB ports on the front of my pc! One of the admin team on the Ubuntu Forum gave me the lead by suggesting I turn off Quiet Splash in grub (grub is the boot loader I use) - this enabled me to see where in the boot process there was a slowing down. I noticed USB1-7 usb device descriptor read/64, error -110 - that appeared a number of times. This gave me the clue to disconnect these device from my motherboard - ubuntu now boots to Desktop in 8s. I have reconnected and the boot time is unaffected so it was related to bad connections to the motherboard. Thank you to all that have helped me with this issue.

That's excellent news. Thank you for that update.