i5/256 Surface Pro 4 overheats and battery drains while 'sleeping'

There seems to be a problem that the surface pro 4 is draining battery while hibernating. By definition we should see 0% battery drain while hibernating. My surface pro 4 i7 16 gb drains roughly 5-6% overnight while hibernating. I am positive it is under hibernation and not sleep. This is something other users are getting as well, as you can see in this battery report thread, or the below imgur link. 

Can anyone give any update or advice to this issue? While there are already multiple threads about sleep problems, it is very concerning that battery has any movement at all when it is hibernating/turned off.

http://i.imgur.com/52NymoG.png

https://www.reddit.com/r/Surface/comments/3u54uo/post\_your\_battery\_report\_statistics/

I had opened a support case for the SP4 sleep drain issue with Microsoft on 11/21/15.   Today I checked the status via chat and was told that my SP4 needed to be replaced.  I queried the agent about the firmware issue and was told that "a number of units" had this issue and that Microsoft is working on the fix but my unit needed to replaced.  They were emphatic on this point.  So I made arrangements to get a new one from the Microsoft Store where I bought it rather than wait the 3-5 days for Fedex and then return the "defective" unit (all free with no credit card required).  Oh and I was told that the support center was informed of this issue impacting certain devices on 10/27/2015!

I returned the unit to the Microsoft Store.  Store tech support confirmed that this was a firmware issue that they have seen a number of times and that Microsoft support was working on a firmware fix.  They did give me the disclaimer that I might see the same issue on the new unit, but that it would be fixed with the update in work.  Of course they gave me no date for this.  They also confirmed that the Surface Book has the same issues.

I now have the new unit.  Upon set up it ran one quick update.  It is now running build 10240.  This initial sleep session (55 minutes) after charging showed near-zero battery drain (WiFi off during sleep).  The CPU0 Time had a 1 percent active time and the Intel HD Display was not even in the report, both good signs.

So far so good.  I had set Windows update (via policy editor) to not automatically download and install updates and do not intend to manually update until I see progress on this issue in the forums.  I can get Windows Defender updates manually from within Window Defender.  And I can live with the occasional display adapter crashes or whatever issue that are fixed with other updates.  Oh and the unit is very cool -- no hint of overheating.

FYI the display adapter driver is dated 9/24/2015 with version 10.18.15.4293.  The battery Microsoft ACPI-Compliant Control Method Battery is dated 6/21/2006 (yes 2006) with version 10.0.10240.16384. 

Any thoughts?

Same problem, interestingly enough, this does not happen to me if you put to sleep after a reboot (at the login screen)

I have the sp4 i7 512 fully updated as of today and am losing ~18% battery per hour of 'sleep'. The biggest offender is Intel Iris Graphics 540 (\_SB.PCI0.GFX0) at 84% of active time and CPU C0 Time at 59% of active time.

For a high end device this is pretty terrible:


Split from this thread.

My SP4 gets very hot and drains the battery very fast even though it is asleep. I found it very hot in its sleeve and down to 28% earlier today. Found it dead later in the afternoon. This is one of MANY issues this device has.

(My SP4 is not part of the insider program)

I had  similar issues with my surface pro 4 I-5 unit, including battery drain while asleep and even battery drain while doing ordinary surfing and none power hungry functions.  Also the fan was also running a bit "too much" for my tastes and the device was getting hot under normal operations. 

I conducted battery drain tests on it while watching a 1:47 minute  DVD movie with 50 percent brightness and the device only had 11 per cent left after the movie.  This was not acceptable so I contacted Microsoft support and this is what happened:

The tech listened to my complaints and had me hold the power button for 60 seconds without releasing it.  After this he had me power the unit up again and check for any new windows updates, which there was not any.  Then he had me make a note of the battery percentage and instructed me to play a video for a few minutes (while he waited I must admit).  I did not tell him but I turned the brightness up to 75 percent while watching the video.  After watching the video for about 3 minutes he had me check the percentage and amazingly the numbers had not changed! 

I did not get too excited but told him that battery indicators often take jumps a few percentages during power drain so he had me watch the video again to check my theory.  (I forgot to mention that during all of this time the fan never came on-not once and the unit did not get warm) After watching the video again for about 2 minutes the power meter only dropped by about 1 per cent.  My device has been operating fantastic since this phone encounter.  No heat; and honestly I have not heard the fan one single time in the last 4 days of use!  I checked the battery percentage of the device a couple of times before it went to sleep and went back to it a couple hours later and the percentage was "still the same". Most important is my battery performance is much better and lasts much longer.  Its hard to put a number on how long it will last on a charge but I can tell you this, I now use the device without constantly watching the battery indicator and I now am enjoying it much more, for this is truly a very good model. 

The tech explained to me that sometimes when the unit comes from the factory the drivers are not properly seated or (some other word he used) and that when I held the power button down it forced them to reset themselves.   This really was the trick for me, and I hope this works for others.  This is also proof that the Surface Pro 4 units might just have minor bug issues that can easily be corrected by working with Microsoft.  Hope this helps someone like it did for me.