Cannot resume from hibernate on Surface Pro 2
Every time I leave my Surface Pro 2 for some time, it evidently hibernates. When I reopen it, I have to use the power button to wake it up and it cold boots (without resuming). Sniffing the event log yields this error:
Windows failed to resume from hibernate with error status 0xC000000D.
Brand new Surface Pro 2 since yesterday (obviously). I've installed VS 2013 with Windows Phone 8 emulators, which so far cannot correctly configure Hyper-V's network switch settings. I bring this up because I know Hyper-V is a fairly low-level change to
the boot configuration so it may be relevant.
October 23rd, 2013 7:08pm
Same here. Surface Pro 2 purchased yesterday.
October 24th, 2013 12:11am
Same here with my Surface Pro (Not 2), it happens after I upgraded to Windows 8.1
October 24th, 2013 4:15am
interestingly enough, it happened after an 8.1 update to my desktop pc as well. still haven't been able to resolve.
October 24th, 2013 6:11am
disable the hibenation file with
powercfg -h off
and enable it again. Does this help?
October 24th, 2013 7:50am
disable the hibenation file with
powercfg -h off
and enable it again. Does this
October 24th, 2013 10:37am
I'm having exactly the same problem. Brand new surface pro 2.
Nothing too crazy about my software load. VS 2010, Office and Creative Cloud. (and I sure hope none of those causes this).
Rather frustrating.
October 30th, 2013 5:06pm
This is not an answer. The problems continue after a reset and after all windows updates. There are tons of threads about these problems.
My surface pro 2 is unexpectedly shutting down frequently during/after sleep/resume. I have reset my device several times and the problem continues after all updates are installed. on top of this once you do a restore to a surface pro 2 an unknown
device surface cover telemetry driver is in device manager and it is impossible to successfully install a device driver for this unknown device. This is repeatable on all surface pro 2s and there are many threads on this. Right now microsoft support
appears to be doing NOTHING and just sending out replacement devices which does not fix the issue.
This is a MAJOR problem.
November 1st, 2013 1:30pm
I'm seeing the same issue on my Surface Pro after updating to Windows 8.1. The device fails to resume from hibernation 100% of the time with error 0xC0000411. I have disabled Hyper-V and installed all updates from WU, but the problem still persists.
- Edited by
Elton Saul
Saturday, November 16, 2013 9:26 AM
November 16th, 2013 12:25pm
i had this problem and the solution for me is that the DisplayLink drivers I was using did not behave well on suspend/resume. I've uninstalled them and my resume problems have gone away.
I'm going to post an issue on the DisplayLink forums.
November 20th, 2013 1:42am
Rob, I have not explicitly installed any DisplayLink drivers on my Surface Pro. My setup includes Office 2013, Visual Studio 2013 and Paint.Net, plus a bunch of modern apps. I've also enabled Hyper-V so I can use the WP8 emulator images. Since updating
to Windows 8.1 my Surface Pro consistently fails to resume from hibernation with error 0xC0000411 (eventvwr.msc). Are the DisplayLink drivers to which you are referring installed as part of the update to Windows 8.1 or did you install them manually?
November 29th, 2013 9:37am
Agreed. Nothing in this thread has solved the problem for me.
November 29th, 2013 9:39am
I agree as well, I can't tell you how much work I have lost just because of this issue. This is after returning two Surface Pro 2's that wouldn't turn back on...
December 10th, 2013 2:54am
I didn't start seeing the problems before today on my Surface Pro, have been using 8.1 since it was released (not the preview).
December 14th, 2013 11:20pm
I am having the same issue.
January 3rd, 2014 9:07am
I am also seeing similar issues. I have also enabled Hyper-V, but I have such problems without Hyper-V installed. For me, it seems exacerbated when I remote desktop into my Surface Pro 2 and then after a long time log into the console. The local display
drivers do not appear to reliably restart correctly. If I am connected over WiFi, the probability of encountering a problem goes up when I remote in over the WiFi link. When the remote desktop connects, the WiFi network (corprorate) requires the console to
be logged onto the WiFi link again. During this transition, the probability that the video fails goes up for future console login attempts.
January 14th, 2014 12:03pm
USB device power to ALWAYS ON,
January 14th, 2014 2:34pm
Other recent topics
