Nerding out with Surface Book

Play Nerding out with Surface Book

The Discussion

  • User profile image
    schlinder

    excelent

  • User profile image
    Randum Ghrryl

    Great! When will Microsoft release a patch to fix the screen flickering when Hyper-V is installed? The flickering/flashing is so bad, people are returning their new Surfaces to the store...

  • User profile image
    Joe

    Hey Simon, here's a list of Surface Book day 1 bugs. Can you share with the Microsoft Surface team so that they can log into their issue tracker and fix them?

    http://surfacebookinfo.blogspot.com/2015/10/surface-book-launch-issues-part-1.html

  • User profile image
    Tauqeeraziz

    Hey Simon,

    Thanks for share this post,I came on your post through one new site. can you explain when the surface book will launch in India. I am eager to buy this product.

     

  • User profile image
    Suave

    Loving mine. Great work guys!

  • User profile image
    MiladMSFT

    @paramhi5:Surface Book works great on Windows 10 and all applications that support the operating system. We have spend a lot of time to ensure we have the best possible experience in particular for creatives like you.

    @Randum Ghrryl: Surface Book works great on Windows 10 and all applications that support the operating system. We have spend a lot of time to ensure we have the best possible experience in particular for creatives like you.

  • User profile image
    androidi

    Can Surface Book expose the display as say 1500*1000 to full screen games/apps? What about doing 1280*960 such that it's doubled to 2560x1920, leaving black borders & not fuzzying/stretching anything?

     

  • User profile image
    Dimitris​Papadakis

    Thanks for transferring us the feeling of designing the product. Both are superb machines.

  • User profile image
    Surface Pro 4 Wake up Issues

    Dear Surface Team,

    Countless Surface Pro 4 machines (including mine) don't properly wake up 20% of the time after going to sleep (on closing the Type Cover). When you open the Type Cover and press the power button to wake it up, about 20% of the time, it doesn't wake up (sometimes the IR light turns on with dark screen or no light at all) and I am forced to hard-reboot. Very frustrating as my Android and iOS devices wake up 100% of the time when pressing the power button. Surface Pro 4 waking up just 80% of the time is a shame. Hopefully you can reproduce and fix this!

  • User profile image
    Surface Pro 4 Wake up Issues

    Dear Surface Team,

    Here's one error with Desktop Windows Manager (from Event Viewer) on waking up from sleep:

    -----
    Faulting application name: dwm.exe, version: 10.0.10240.16384, time stamp: 0x559f3907
    Faulting module name: dwmcore.dll, version: 10.0.10240.16461, time stamp: 0x55d2d629
    Exception code: 0xc0000602
    Fault offset: 0x00000000000aca77
    Faulting process id: 0x1b58
    Faulting application start time: 0x01d119e0f89fcebc
    Faulting application path: C:\windows\system32\dwm.exe
    Faulting module path: C:\windows\system32\dwmcore.dll
    Report Id: 6f5cc0a1-22b7-4c88-8ceb-9d31c97a5f21
    Faulting package full name:
    Faulting package-relative application ID:
    -----

    Here are some other errors immediately after that:

    -----------
    Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.
    ------------
    Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
    -------------
    Faulting application name: svchost.exe_WbioSrvc, version: 10.0.10240.16384, time stamp: 0x559f38cb
    Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3
    Exception code: 0xc0000420
    Fault offset: 0x000000000002a1c8
    Faulting process id: 0x1b2c
    Faulting application start time: 0x01d119e0f6b5850d
    Faulting application path: C:\windows\system32\svchost.exe
    Faulting module path: C:\windows\system32\KERNELBASE.dll
    Report Id: b887e346-3566-4b9d-8765-c22611fce176
    Faulting package full name:
    Faulting package-relative application ID:
    ---------------------

  • User profile image
    Surface Pro 4 Wake up Issues

    Dear Surface Team,

    My Surface Pro 4 is up-to-date with the latest Windows updates. But I am still having problems with the Surface Pro 4 waking up from sleep on pressing the power button. This sometimes happens even if I try to wake it up within a couple of minutes after closing the fingerprint Type Cover.

    THIS IS SO FRUSTRATING!!

    I even had to download WinDbg and figure out how to use it with the crash dumps. Here's one to help you troubleshoot this issue. I get this VIDEO_TDR_TIMEOUT_DETECTED (117) error at least a couple of times a day!

    ============================================================================

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_TDR_TIMEOUT_DETECTED (117)

    The display driver failed to respond in timely fashion.

    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: ffffe00062fa74c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff80022c86770, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 00000000000002c4, Optional internal context dependent data.

    Debugging Details:
    ------------------


    BUGCHECK_P1: ffffe00062fa74c0

    BUGCHECK_P2: fffff80022c86770

    BUGCHECK_P3: 0

    BUGCHECK_P4: 2c4

    FAULTING_IP:
    igdkmd64+16770
    fffff800`22c86770 ?? ???

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

    TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


    CPU_COUNT: 4

    CPU_MHZ: 9c0

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

    BUGCHECK_STR: 0x117

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    STACK_TEXT:
    ffffd000`21b008f0 fffff800`213411d1 : ffffe000`62fa74c0 00000000`80000000 ffffe000`62fa74c0 ffffe000`5fc198f0 : watchdog!WdDbgReportRecreate+0x104
    ffffd000`21b00940 fffff800`2134074f : ffffc000`00000000 ffffc000`20d42400 ffffe000`62fa74c0 ffffe000`62fa74c0 : dxgkrnl!TdrUpdateDbgReport+0xe1
    ffffd000`21b00990 fffff800`2132c830 : ffffc000`24f71335 ffffe000`637c7010 ffffe000`637c77b0 ffffe000`62fa74c0 : dxgkrnl!TdrCollectDbgInfoStage2+0x1df
    ffffd000`21b009c0 fffff800`21340e45 : 00000000`03d70115 ffffffff`fffe7960 ffffffff`fffe7960 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x168
    ffffd000`21b00a10 fffff800`21340f9b : 00000000`00000000 fffff803`735e2340 ffffe000`643ff2c0 fffff803`732835d0 : dxgkrnl!TdrResetFromTimeout+0x15
    ffffd000`21b00a40 fffff803`73282dd9 : ffffe000`79d11040 fffff800`21340f40 ffffe000`69b994b0 00000000`03d7fc15 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b
    ffffd000`21b00a70 fffff803`732ef558 : 00000000`00000000 00000000`00000080 fffff803`735e2340 ffffe000`79d11040 : nt!ExpWorkerThread+0xe9
    ffffd000`21b00b00 fffff803`7335c3c6 : fffff803`7356c180 ffffe000`79d11040 ffffe000`6a99a080 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`21b00b60 00000000`00000000 : ffffd000`21b01000 ffffd000`21afa000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    igdkmd64+16770
    fffff800`22c86770 ?? ???

    SYMBOL_NAME: igdkmd64+16770

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME: igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5629d0c5

    FAILURE_BUCKET_ID: LKD_0x117_IMAGE_igdkmd64.sys

    BUCKET_ID: LKD_0x117_IMAGE_igdkmd64.sys

    PRIMARY_PROBLEM_CLASS: LKD_0x117_IMAGE_igdkmd64.sys

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:lkd_0x117_image_igdkmd64.sys

    FAILURE_ID_HASH: {df5cc292-6e03-34f8-7849-e22c43f13df4}

    Followup: MachineOwner
    ---------

    ============================================================================

  • User profile image
    Scott Stauffer

    Hey "Surface Pro 4 Wake up Issues"

    I have a Surface Pro 4 with Bio-metrics too and when I searched on "Activation of application Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error"

    I got this page.

    I feel for you this is the second time I've purchased a device that just came off the assembly line... it is really frustrating, yes, but Likely posting on Channel9 isn't going to get a lot of results. BTW, the other device was a Dell, but hey, all manufacturers experience this. The numerous possibilities for issues are impossible to reproduce. If we want a stable machine, buying one that has been out for 6 months is the best solution? But hey, you want the latest and greatest... so you now know what living on the bleeding edge means...

    I want the blood letting to stop... but I really like what the i7 Surface Pro offers, so I put up with it...

    in time the bugs will be ironed out.

    in the mean time, save to the cloud, turn auto sleep and auto lock off, shut down as opposed to sleep. And have Windows automatically send Microsoft your errors?

    Open a case with Microsoft apparently 1-800-Microsoft and it's free for the first year.

    On the other hand if someone on Channel9 said to post your questions here, then I will shut my mouth :D

    Best of luck,
    A fellow Bleeding Edge victim...


Add Your 2 Cents