Surface Pro 4 - Screen won't wake from sleep

Thanks that makes much more sense.

1724 is the model number.  The lot number is on the original box in small print on a sticker and says date/lot 15xx or 16xx where xx is month batch I think like mine is model 1724 with date lot 1548 which means 2015 April Batch 8.  Someone correct this if I am misinterpreting the month batch.  I used to think it was on the back as well. 

You are right that the LOT is only on the original white box, starting with 15xx or 16xx. However, most of us will agree that the xx refers to the WEEK number, not month-day/lot. It would of course not make sense that a SP4 was manufactured as early as april 2015 and there would be no room for double-digit months or lots.

So for example mine is 1545, which means roughly the 45th week of 2015, which would be around the first week of November, depending on the calendar in effect. That sounds about right considering that I ordered it in mid-November.

Absolutely correct. Lot 1610 is the 10th week of 2016.

And now I'm suddenly starting to see this as well. I had a couple of bug checks related to the IR camera before the big driver update, but now I get a black screen after waking from sleep, followed by bug check every other time I log (using Windows Hello) on it seems. I don't know if this is significant, but so far the crash/black screen has only happened when another user had locked the screen and was still logged on.

I see a lot of talk about lot numbers? Is that the 4-digit code printed behind the kickstand? In that case mine is #1724. For those interested, these are the bugcheck details:

BugCheck 14F, {0, 100, 0, 50434c45}

Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )

Followup:     MachineOwner

---

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PDC_WATCHDOG_TIMEOUT (14f)

A system component failed to respond within the allocated time period,

preventing the system from exiting connected standby.

Arguments:

Arg1: 0000000000000000, Client ID of the hung component.

Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Arg3: 0000000000000000, The most recent POWER_MONITOR_REQUEST_REASON value for this request.

Arg4: 0000000050434c45, A value indicating the internal path taken to initiate the request.

Debugging Details:

---

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER:  Microsoft Corporation

SYSTEM_PRODUCT_NAME:  Surface Pro 4

SYSTEM_SKU:  Surface_Pro_4

SYSTEM_VERSION:  D:0B:08F:3C:03P:38

BIOS_VENDOR:  Microsoft Corporation

BIOS_VERSION:  104.1121.768

BIOS_DATE:  03/01/2016

BASEBOARD_MANUFACTURER:  Microsoft Corporation

BASEBOARD_PRODUCT:  Surface Pro 4

DUMP_TYPE:  1

BUGCHECK_P1: 0

BUGCHECK_P2: 100

BUGCHECK_P3: 0

BUGCHECK_P4: 50434c45

BUGCHECK_STR:  0x14F_MONITORON_0x0_ELCP

CPU_COUNT: 4

CPU_MHZ: 5e8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: 82'00000000 (cache) 82'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DARTH

ANALYSIS_SESSION_TIME:  06-08-2016 10:51:03.0353

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8002c9f19d9 to fffff802b6d5c780

STACK_TEXT: 

ffffd000224b1a38 fffff8002c9f19d9 : 000000000000014f 0000000000000000 0000000000000100 0000000000000000 : nt!KeBugCheckEx

ffffd000224b1a40 fffff802b6c5cc59 : fffff802b6fad200 fffff802b6ef6040 fffff80000000000 fffff802b6fad340 : pdc!PdcpMonitorOnWatchdogWorker+0x29

ffffd000224b1a80 fffff802b6d07b65 : ffffd0010000007b 0000000000000080 ffffe00162491680 ffffe00170ff9800 : nt!ExpWorkerThread+0xe9

ffffd000224b1b10 fffff802b6d61926 : ffffd00166040180 ffffe00170ff9800 fffff802b6d07b24 0000000000010224 : nt!PspSystemThreadStartup+0x41

ffffd000224b1b60 0000000000000000 : ffffd000224b2000 ffffd000224ab000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  6554c1e422ba11db3654290d3c393f4442aaea94

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  030e8e9deb055c9fca4b56340ef04abec30cf624

THREAD_SHA1_HASH_MOD:  9153fcc24a9debd7fc9e7c503c3c6added606b19

FOLLOWUP_IP:

pdc!PdcpMonitorOnWatchdogWorker+29

fffff800`2c9f19d9 cc              int     3

FAULT_INSTR_CODE:  44cccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  pdc!PdcpMonitorOnWatchdogWorker+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pdc

IMAGE_NAME:  pdc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  571af2a5

BUCKET_ID_FUNC_OFFSET:  29

FAILURE_BUCKET_ID:  0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

BUCKET_ID:  0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

PRIMARY_PROBLEM_CLASS:  0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

TARGET_TIME:  2016-06-07T12:46:28.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-04-23 06:04:21

BUILDDATESTAMP_STR:  160422-1850

BUILDLAB_STR:  th2_release_sec

BUILDOSVER_STR:  10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 1661

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x14f_monitoron_0x0_elcp_pdc!pdcpmonitoronwatchdogworker

FAILURE_ID_HASH:  {b02d0e71-ffbb-2e94-5732-48affd4e19e6}

Reading this thread--and my own experience--seems to indicate that the potential for problems is quite high for lot 1610 and earlier, and lot 1611 and later seem to be much better. That lot number could be off a week or two. My lot 1613 SP4 not only wakes perfectly--my three earlier SP4s were horrible--it also performs better and has much, much, better battery life. If you are having issues, please post your lot number, found only on the original box.

Thanks, MikeKirnak.  Can you direct me to the specific posts you referred to?  I am interested in exactly what you did.  I have little confidence in the anecdotal reports that fill this thread.  But I agree that if the same image performs differently on two platforms, then there is a difference in the platforms.

They're all back a couple of pages. To sum up: I made a backup image of my lot 15xx SP4 about a month ago. Then, I restored it to factory with a downloaded MS image. I had issues immediately. I exchanged the unit for a refurb at a MS store. Issues immediately with the factory image. Tried my backup image. Issues immediately. Tried the MS image. Issues immediately.  Exchanged for a brand new lot 1613 SP4. I tried to load my backup image, but interestingly the new machine could not be loaded with that image despite multiple attempts. It loaded fine on the older two SP4s... Anyways, the factory image was now screwed up by the attempts to load the backup image, so I loaded the downloaded MS image. The lot 1613 SP4 has performed almost flawlessly ever since. The only issue at all is that occasionally the cursor will freeze for a moment while the PC is doing something.

Overall performance on the lot 1613 machine is better as well; web pages and programs load significantly faster than on my first three SP4s. Battery life is hugely improved. I got four hours or so run time watching video before. This machine gets up to seven hours run time watching the same video. I have loaded almost all of the software I had running before with no problems arising as of yet. 

Whether QC is better, or they fixed a problem in the hardware, or I just got lucky, I don't know. It does seem though that people with lot 1611 and later machines are not having these issues near as often as the older machines, at least I haven't read of an issue with the later machines in this thread. I had three older SP4s. Out of those three, three were bad. (The refurb worst of all.) I went from hating the SP4 and wishing desperately I had returned it when I could, to being a very satisfied and happy lot 1613 SP4 owner.