Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, November 27, 2016 8:28 PM
My computer has been unable to enter sleep mode (S3) or hibernate since upgrading to Windows 10.
- Event log errors:
Event Log: 11/26/2016 7:05:30 PM
General: The system could not sucessfully load the crash dump driver.
Source: volmgr
EventID: 45
Event Log: 11/26/2016 7:05:30 PM
General: Crash Dump initialization failed!
Source: volmgr
EventID: 46
I have tried the following steps to correct this issue:
- Checked BIOS settings and insured S3 is enabled
- Updated motherboard bios and chipset drivers and removed all peripheral devices, usb, PCIe and sata disks besides boot drive. Also ran test mem on all memory, one stick at a time. Attempting to sleep/hibernate after each test.
- Disabled hibernate via command line via: powercfg /H off, and also removed the pagefile in System properties > Advanced system settings > Advanced tab> Performance settings > Advanced. Rebooted PC and re-enabled hibernate and pagefile (custom size of 110% of ram size) No luck. After each change I also verified the they took in regedit.
- Noticed new error in event log at this point: *"Error EventID: (49) Configuring the Page file for the crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory" * But the page file is there C:\ 11/26/2016 07:33 PM 13,212,057,600 pagefile.sys
At this point I believe it the systems inability to create a crash dump file that is hanging up the sleep modes. I followed the following guide to try to manually create FULL dump files. https://support.microsoft.com/en-us/kb/969028. Using notmyfault.exe
It generated a BSOD but did not actually create a dump file.
I tried generating dump in safe mode as well.
At this point I'm at a loss to what to do next. Looking for some help
All replies (4)
Sunday, November 27, 2016 10:35 PM
Did you use TrueCrypt?
See this report:
No Hibernate and volmgr Error with Event ID 45 in System Log
the description will probably also help you when its not due to TrueCrypt.
Wednesday, November 30, 2016 9:28 AM
Hi,
Beside that, please also refer to this similar thread:
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, December 31, 2019 3:45 PM
I know this old, but it's at the top of Google searches and none of the posts had a solution that worked for me. I had this same error on a new system build where win10 wouldn't sleep or hibernate due to the above event 45 error. Even a full windows reset didn't help.
In my case, the problem was due to the system drive being Dynamic instead of Basic. Apparently that conversion lost some key attributes for dump drive. Since windows won't natively allow conversion back to basic, I just cleaned the drive via diskpart (this wiped the volumes) and reloaded the OS.
Problem solved. Hope that helps somebody.
Monday, January 13, 2020 6:15 AM
You have confirmed my worst nightmare on this error. I just finished setting up a brand new machine with nearly 4 TB of data across two M2 disks, dynamically spanned as a single drive letter, and I cannot hibernate/sleep with this error. I suspected that it might be due to the dynamic disks, but thought surely that MS wouldn't have such a problem with this setup. Thanks for pointing me in the right direction.