02-24-2017 01:15 AM
38 12
tools
  1. brosenz's Avatar
    Yesterday I got my new SB, I haven't really installed much, mostly office and project 2016, and did a full Windows Update as well. I left the SB last night around 1AM in Sleep Mode with many apps open, Edge, Outlook and Explorer. This morning around 7AM I opened and to my surprise the SB was rebooting from a Shutdown, after checking the logs in Event Viewer I found "The Previous system shutdown at 3:26AM on 11/26 was unexpected", "The system has rebooted without cleanly shutting down first....." and "The computer has rebooted from a bugcheck.......".

    I've read all over about this issue called "The Sleep of Death" on the SB, I thought this problem would have been resolved already, it is almost 18 months since the release.

    Any idea if there is a fix? For me stability and reliability are the two most important attributes of a laptop/tablet device, when I open it, it has to work, at least most of the time.

    Thanks for the feedback. I am thinking on returning it but I want to give it a try first.
    11-26-2016 10:53 AM
  2. decider's Avatar
    I think the best fix for the SBs is return for complete refund. For whatever reasons it seems the SBs and now including your newest with the performance base are not a product worth the money paid. Just my opinion.
    11-26-2016 01:32 PM
  3. petvas72's Avatar
    My Surface Book doesn't have any crashes. Everything works great. I suggest you do some basic troubleshooting and see what the problem might be. It would also be a good idea to run the Surface Book diagnostics to eliminate any hardware issues. Returning the Surface Book is not really a good option. This is the best laptop on the market right now.
    Last edited by petvas72; 11-26-2016 at 03:37 PM.
    rdubmu likes this.
    11-26-2016 02:46 PM
  4. beman39's Avatar
    instead of panicking and rushing to return it, why don't you just give it a few days to settle after doing the updates and settle itself out, probably I also suspect that the SB isn't done with all the updates and you still might have updates to do or maybe firmware updates also... also I'm sure there is APPS that need to be updated in the store too. I have friends who have the SB and they NEVER have problems with it... which makes me want to buy one so badly, but I'm content with my SP3... perhaps soon maybe..
    neo158 likes this.
    11-26-2016 03:59 PM
  5. Cane Prevost's Avatar
    I found my Surface Book was buggy for the first week. Not sure why that happens but it's pretty good now. I'd wait a few days like the previous post indicates to see if it gets better.
    11-27-2016 12:17 PM
  6. zerospace-net's Avatar
    This behavior (unexpected sleep shutdowns) was an issue with all Surface Books awhile ago (earlier this year), but it was resolved with firmware updates for pretty much everyone (there may have been a few that continued to have issues).

    Is this unit one of the new "performance base" models? Have you made sure the firmware is totally up-to-date?
    11-28-2016 02:02 PM
  7. Boomwaller's Avatar
    I agree with what others have said, let the system settle in and check store for App updates etc... Also check your hibernate settings on battery etc, and battery saver. It can put the machine into hibernate/deep sleep, which will act like the system is fully off. Most issues I had were within the first 2 days, and then a self created issue running Ubuntu via Hyper V Manager.

    Let us know if it happens again.
    11-29-2016 12:22 PM
  8. hopmedic's Avatar
    I've had mine for almost two weeks now, and the only shutdowns I've had overnight were updates that required restart. I have, however, seen several blue screens, and with my (former) SP3, I had gotten used to never seeing those.
    11-29-2016 11:33 PM
  9. zerospace-net's Avatar
    BSoDs (blue screens) should no longer be the norm. If you're seeing them, you may want to try running the system file checker (admin command prompt, type SFC /scannow). Then run the DISM command to find and fix any corrupt files. Windows Central has a nice article about how to run both of these. I had horrible blue screen issues on my Surface Book after every windows update for awhile (MS acknowledged that the update process itself was introducing corruption) but the anniversary update and subsequent firmware updates that were designed to deal with this exact issue have done just that.

    Also, sleep shutdowns are NOT normal and are not likely to resolve themselves. That said, if it only happens once and not again, it's likely just a fluke, and I wouldn't be worried about it. If it continues to happen, there's something else going on and you should act quickly to make sure you get a brand new replacement unit if it's necessary. If the system enters hibernation, open programs are remembered -- and no log entry is generated regarding an unexpected system shutdown. If you bought your Surface Book directly from Microsoft and the sleep shutdowns continue, contact their support. You have 30 days to return it for a full refund and if you have a nearby MS store, they will also do a direct exchange for you if your unit is faulty. Take advantage of this. Do not wait too long for the system to "settle in" and lose these opportunities.
    11-30-2016 09:47 AM
  10. hopmedic's Avatar
    BSoDs (blue screens) should no longer be the norm. If you're seeing them, you may want to try running the system file checker (admin command prompt, type SFC /scannow). Then run the DISM command to find and fix any corrupt files. Windows Central has a nice article about how to run both of these. I had horrible blue screen issues on my Surface Book after every windows update for awhile (MS acknowledged that the update process itself was introducing corruption) but the anniversary update and subsequent firmware updates that were designed to deal with this exact issue have done just that.
    Hmmm... I just ran the SFC and it found no problems. There was just an update last night (I'm on the Release Preview ring), so I'll watch to see if it happens again. I've had the PC for 10 days, so there's plenty of time for an exchange (plus I would never spend this much on a PC that I can't fix, without buying the extended warranty).
    11-30-2016 10:24 AM
  11. Boomwaller's Avatar
    Also to clarify my point on hibernate, some people notice/think there machine was shut down when the press the power button after say 5 hours and see the Surface Logo like it was shutdown. Anyways to test Hibernate just swap your power button to hibernate instead of sleep. Leave open Edge browser and notepad, press the power button, Surface should go into hibernate wait 5-10 seconds press it again, should wake out of hibernate (Surface Logo) login and Edge/Notepad should still be open.

    I do agree shutdown during hibernate/sleep is not good, and I would monitor it for 1 - 2 days if it happens again do a quick exchange!
    11-30-2016 01:01 PM
  12. hopmedic's Avatar
    I intentionally set my button action to hibernate instead of sleep, because I have Visual Studio installed, with the phone emulators, and with my Surface Pro 3, I had problems with it not being able to sleep because of Hyper-V. For that reason, I just always automatically set it to hibernate when the button is pressed, or when it times out on battery (never sleep or hibernate while powered).
    11-30-2016 11:24 PM
  13. zerospace-net's Avatar
    Hmmm... I just ran the SFC and it found no problems. There was just an update last night (I'm on the Release Preview ring), so I'll watch to see if it happens again. I've had the PC for 10 days, so there's plenty of time for an exchange (plus I would never spend this much on a PC that I can't fix, without buying the extended warranty).
    Ohh, you're running insider builds. NVM then. That changes things a bit. On production builds, BSoDs aren't normal. I don't know about any of the insider builds.
    12-01-2016 04:49 PM
  14. zerospace-net's Avatar
    Also to clarify my point on hibernate, some people notice/think there machine was shut down when the press the power button after say 5 hours and see the Surface Logo like it was shutdown. Anyways to test Hibernate just swap your power button to hibernate instead of sleep. Leave open Edge browser and notepad, press the power button, Surface should go into hibernate wait 5-10 seconds press it again, should wake out of hibernate (Surface Logo) login and Edge/Notepad should still be open.

    I do agree shutdown during hibernate/sleep is not good, and I would monitor it for 1 - 2 days if it happens again do a quick exchange!
    While hibernate can appear like a shutdown, on a Surface Book there is one telltale sign if no programs were left open before the "shutdown" -- the Surface DTX process is NOT in the system tray when the desktop first loads. It takes a few seconds to see the detach button appear in the system tray from a cold boot.
    12-01-2016 04:51 PM
  15. Boomwaller's Avatar
    While hibernate can appear like a shutdown, on a Surface Book there is one telltale sign if no programs were left open before the "shutdown" -- the Surface DTX process is NOT in the system tray when the desktop first loads. It takes a few seconds to see the detach button appear in the system tray from a cold boot.
    You are exactly right! I just wanted to clarify it for anyone reading the thread and for the OP. Also I am not on insider either Surface Book is my daily driver and, not enough time to test builds. I can however stress test insider this weekend and see if I stumble upon similar things. Also by chance do you have a BSOD dump file you could share?
    12-02-2016 12:14 AM
  16. zerospace-net's Avatar
    I, too, would be curious what the BSoD code is (this should be visible in the event viewer on the "the computer has rebooted from a bugcheck" error). The most common ones, previously were things like pdc_watchdog (related to the screen waking after sleep), nvidia driver (again, usually on wake from sleep), and a couple of others. I remember running memory tests and other hardware diagnostics trying to decide if my BSoD issues were hardware or firmware. In the end, I determined they were firmware or Win10 issues and waited it out. I must've been right because I haven't seen a BSoD in quite awhile.

    One other thing -- some folks get BSoDs related to memory cards and exfat.sys on Win10. Depending on the OPs config, this could be that, too.
    12-05-2016 09:58 AM
  17. hopmedic's Avatar
    Here are my dump files. As you can see, there are several, and it is happening far too often for my liking.
    https://1drv.ms/f/s!AmcHRyKotEWU2qddMhC7Tl2fvMwA4A
    Let me add that I have no idea what I'm looking at.
    12-05-2016 09:14 PM
  18. zerospace-net's Avatar
    Have you run the win diagnostics utility on these dump files to see what it points to as the culprit of each?
    12-08-2016 09:20 AM
  19. hopmedic's Avatar
    Have you run the win diagnostics utility on these dump files to see what it points to as the culprit of each?
    I haven't had the time to take a look and see how to run the utility, so no.
    12-09-2016 03:01 PM
  20. zerospace-net's Avatar
    I haven't had the time to take a look and see how to run the utility, so no.
    It's the fastest way to get an idea of what the root cause of the crashes really is. I started using it on my SB 6+ months ago when I was having serious, regular BSoD issues. My issues, though, were Windows 10 and drivers and I just had to wait until MS, Intel and nVidia fixed the problems.
    12-10-2016 11:48 AM
  21. hopmedic's Avatar
    Got a link?
    12-10-2016 07:43 PM
  22. zerospace-net's Avatar
    Got a link?
    It's part of MS's windows debugging tools: https://developer.microsoft.com/en-u...ows-driver-kit

    Scroll down to the WinDbg area and you'll see this:

    Windows 10 (WinDbg)

    If you just need the Debugging Tools for Windows 10, and not WDK 10 or Visual Studio 2015, you can install the debugging tools as a standalone component from Windows SDK. In the installation wizard, select Debugging Tools for Windows, and deselect all other components.

    Get Debugging Tools for Windows (WinDbg) (from the SDK)
    That's basically all you need. Note that you need to launch it as administrator in order to analyze a crash dump file.
    12-12-2016 10:29 AM
  23. brosenz's Avatar
    This is the output on my system, how do I know what is the root cause of the problem, sorry I am not super familiar with the Debug tool, it seems the issue is related to the NDIS driver:

    Loading unloaded module list
    ..................................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, ffffe382903d8740, fffff802e0bd28e0, ffffe382a02eb010}

    CompressedPageDataReader warning: failed to get _SM_PAGE_KEY symbol.
    CompressedPageDataReader warning: failed to get _SM_PAGE_KEY symbol.
    Implicit thread is now ffffe382`88482040
    Page f00 not present in the dump file. Type ".hh dbgerr004" for details
    Page f00 not present in the dump file. Type ".hh dbgerr004" for details
    Page f00 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : ndis.sys ( ndis!KWaitEventBase::Wait+22 )

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

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe382903d8740, Physical Device Object of the stack
    Arg3: fffff802e0bd28e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe382a02eb010, The blocked IRP

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

    Implicit thread is now ffffe382`88482040
    Page f00 not present in the dump file. Type ".hh dbgerr004" for details
    Page f00 not present in the dump file. Type ".hh dbgerr004" for details
    Page f00 not present in the dump file. Type ".hh dbgerr004" for details

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 14393.576.amd64fre.rs1_release_inmarket.161208-2252

    SYSTEM_MANUFACTURER: Microsoft Corporation

    SYSTEM_PRODUCT_NAME: Surface Book

    SYSTEM_SKU: Surface_Book

    SYSTEM_VERSION: D:0B:14F:1C:03P:38

    BIOS_VENDOR: Microsoft Corporation

    BIOS_VERSION: 90.1380.768

    BIOS_DATE: 11/04/2016

    BASEBOARD_MANUFACTURER: Microsoft Corporation

    BASEBOARD_PRODUCT: Surface Book

    DUMP_TYPE: 1

    BUGCHECK_P1: 3

    BUGCHECK_P2: ffffe382903d8740

    BUGCHECK_P3: fffff802e0bd28e0

    BUGCHECK_P4: ffffe382a02eb010

    DRVPOWERSTATE_SUBCODE: 3

    FAULTING_THREAD: 88482040

    CPU_COUNT: 4

    CPU_MHZ: af8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

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

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: SURFACE

    ANALYSIS_SESSION_TIME: 01-02-2017 09:22:29.0155

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    LAST_CONTROL_TRANSFER: from fffff802decf0f5c to fffff802dedda506

    STACK_TEXT:
    ffffcd00`bdef0480 fffff802`decf0f5c : fffff802`defcd180 fffff802`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76
    ffffcd00`bdef05c0 fffff802`decf09ff : ffffe382`a02e9680 ffff4be7`bbd68885 00000000`00000000 fffff802`dece09d1 : nt!KiSwapThread+0x17c
    ffffcd00`bdef0670 fffff802`decf27c7 : ffffe382`00000000 fffff802`be71610d ffffe382`a02e9680 00000000`00000000 : nt!KiCommitThreadWait+0x14f
    ffffcd00`bdef0710 fffff802`be79de6e : ffffe382`8d5ee618 fffff802`00000000 ffffcd00`bdef0800 00000000`00000000 : nt!KeWaitForSingleObject+0x377
    ffffcd00`bdef07c0 fffff802`be7a56df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!KWaitEventBase::Wait+0x22
    ffffcd00`bdef0800 fffff802`be79d808 : ffffe382`8d5ed1a0 ffffe382`8d5ed1a0 ffffe382`a02eb680 fffff802`be7778f8 : ndis!Ndis::BindEngine::ApplyBindChanges+0x5f
    ffffcd00`bdef0850 fffff802`be711450 : ffffe382`8a3b78e0 ffffe382`8d5ed1a0 ffffe382`a02eb010 00000000`00000003 : ndis!ndisIssueNetEventSetPowerEvent+0x60
    ffffcd00`bdef0950 fffff802`be731590 : 00000000`00000800 ffffe382`a02eb010 ffffe382`a02eb010 fffff802`dece09b0 : ndis!ndisPrepForLowPower+0x38
    ffffcd00`bdef0a20 fffff802`be79d302 : 00000000`00000000 ffffe382`8d5ed1a0 ffffe382`a02eb680 00000000`00000000 : ndis!ndisSetDevicePower+0x204cc
    ffffcd00`bdef0a90 fffff802`be71fc28 : ffffe382`a02eb010 ffffe382`903d8740 ffffe382`a02eb680 fffff802`def8b620 : ndis!ndisSetPower+0x56
    ffffcd00`bdef0ac0 fffff802`deda51c2 : ffffe382`88482040 ffffcd00`bdef0b70 fffff802`def8b600 ffffe382`8d5ed050 : ndis!ndisPowerDispatch+0xa8
    ffffcd00`bdef0af0 fffff802`dec8d729 : 00000000`00000000 fffff802`deda4fe4 00000000`00000000 00000000`0000004b : nt!PopIrpWorker+0x1de
    ffffcd00`bdef0b90 fffff802`deddabb6 : ffffcd00`bdf00180 ffffe382`88482040 fffff802`dec8d6e8 ffffc28d`00000000 : nt!PspSystemThreadStartup+0x41
    ffffcd00`bdef0be0 00000000`00000000 : ffffcd00`bdef1000 ffffcd00`bdeea000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: .thread 0xffffe38288482040 ; kb

    THREAD_SHA1_HASH_MOD_FUNC: 3816aecaf706bb13db2af94abf3442783a78ddec

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7c88fb659d7ca57c42bd9625762c96156940327c

    THREAD_SHA1_HASH_MOD: 2e7463c4a06613ca32bf00f4fe630ce53f51e143

    FOLLOWUP_IP:
    ndis!KWaitEventBase::Wait+22
    fffff802`be79de6e 4883c438 add rsp,38h

    FAULT_INSTR_CODE: 38c48348

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: ndis!KWaitEventBase::Wait+22

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ndis

    IMAGE_NAME: ndis.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 57f4c58d

    BUCKET_ID_FUNC_OFFSET: 22

    FAILURE_BUCKET_ID: 0x9F_3_ndis!KWaitEventBase::Wait

    BUCKET_ID: 0x9F_3_ndis!KWaitEventBase::Wait

    PRIMARY_PROBLEM_CLASS: 0x9F_3_ndis!KWaitEventBase::Wait

    TARGET_TIME: 2017-01-02T06:08:52.000Z

    OSBUILD: 14393

    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-12-09 03:23:02

    BUILDDATESTAMP_STR: 161208-2252

    BUILDLAB_STR: rs1_release_inmarket

    BUILDOSVER_STR: 10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252

    ANALYSIS_SESSION_ELAPSED_TIME: 634

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x9f_3_ndis!kwaiteventbase::wait

    FAILURE_ID_HASH: {37b67c78-0c57-7222-0ec7-71f6203e422c}

    Followup: MachineOwner
    ---------
    Last edited by brosenz; 01-02-2017 at 10:58 AM.
    01-02-2017 09:29 AM
  24. hopmedic's Avatar
    Well, I finally took a look at the debugger tool. I'm not sure what I'm looking at, but here's all of the "probably caused by"s of my blue screens:
    Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5850C932820000 )
    Probably caused by : memory_corruption
    Probably caused by : IntcOED.sys ( IntcOED+14626 )
    Probably caused by : dxgkrnl.sys ( dxgkrnl!COREDEVICEACCESS::COREDEVICEACCESS+5 )
    Probably caused by : nvlddmkm.sys ( nvlddmkm+18e856 )
    Probably caused by : dxgmms2.sys ( dxgmms2!VidMmiUnlockAllocation+20 )
    Probably caused by : memory_corruption
    Probably caused by : iaPreciseTouch.sys ( iaPreciseTouch+27f4d )
    Probably caused by : NTFS.sys ( NTFS!NtfsFullDeleteLcb+153 )
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1a8634 )
    Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+f4 )
    Probably caused by : ntkrnlmp.exe ( nt!CmpDoParseKey+553 )
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+5748d )
    Probably caused by : hardware ( nt!HvlGetPpmStatsForProcessor+11 )
    Probably caused by : memory_corruption
    Probably caused by : memory_corruption
    Probably caused by : memory_corruption
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiPowerArbiterThread+120 )
    Probably caused by : memory_corruption
    Probably caused by : memory_corruption
    This list is in reverse chronological order, so at least the memory corruptions have gotten less frequent. I don't know what to make of any of it other than that and the fact that it's not just one problem. I know I'm fed up.
    01-04-2017 12:06 PM
  25. zerospace-net's Avatar
    Well, I finally took a look at the debugger tool. I'm not sure what I'm looking at, but here's all of the "probably caused by"s of my blue screens:

    This list is in reverse chronological order, so at least the memory corruptions have gotten less frequent. I don't know what to make of any of it other than that and the fact that it's not just one problem. I know I'm fed up.
    Sounds like you should run a memory diagnostic. Windows has one built it, but some say it isn't as good as using memtest. If a memory test returns a lot of errors, then you need to get your machine replaced as you probably have some bad RAM.
    01-10-2017 11:44 AM
38 12

Similar Threads

  1. Painting the back cover w the Surface color
    By bulls96 in forum Microsoft Lumia 950 XL
    Replies: 19
    Last Post: 01-05-2017, 03:59 PM
  2. Unable to login in Disqus in News app
    By garisa in forum Windows 10 Mobile
    Replies: 2
    Last Post: 11-29-2016, 02:09 PM
  3. Partial Glance Screen missing on new Lumia 950,
    By Windows Central Question in forum Ask a Question
    Replies: 3
    Last Post: 11-26-2016, 11:56 AM
  4. sorting by genre in groove music app
    By gbafam in forum Groove Music
    Replies: 1
    Last Post: 11-26-2016, 10:53 AM
  5. How to fix lag spikes and micro-freezes in Battlefield 1 on Windows 10
    By WindowsCentral.com in forum Windows Central News Discussion
    Replies: 0
    Last Post: 11-26-2016, 06:11 AM
LINK TO POST COPIED TO CLIPBOARD
";