Windows 10: Surface Pro Kernel Memory Dump When It Turn On Every time!

Discus and support Surface Pro Kernel Memory Dump When It Turn On Every time! in Windows 10 Drivers and Hardware to solve the problem; Dear all, I got a very strange thing my Surface Pro Memory Dump when I turn on it everytime, but It don't happen if I just reboot after turn on. I... Discussion in 'Windows 10 Drivers and Hardware' started by Leo_5117, Apr 8, 2019.

  1. LEO_5117
    Leo_5117 Win User

    Surface Pro Kernel Memory Dump When It Turn On Every time!


    Dear all,


    I got a very strange thing my Surface Pro Memory Dump when I turn on it everytime, but It don't happen if I just reboot after turn on.

    I try to understand what happen but the analysis is a little bit complicated for me.

    So I come here ask for help, Please give me a hand!


    Thank you very much!


    The analysis as folow you see and I test some ways but it doesn't help just for you information!

    1.Update all network drives;

    2.Uninstall all network drives then install it automatic;

    3.Cmd SFC /scannow;

    4.Cmd DISM /Online /Cleanup-image /RestoreHealth;

    5.I can't rollback my OS to 1803 (now is 1809) bacause I delete the system recover alreday!


    Dump File download here!



    Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17763 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17763.1.amd64fre.rs5_release.180914-1434
    Machine Name:
    Kernel base = 0xfffff805`330aa000 PsLoadedModuleList = 0xfffff805`334c59f0
    Debug session time: Sun Apr 7 01:42:54.245 2019 (UTC + 8:00)
    System Uptime: 0 days 0:12:49.107
    Loading Kernel Symbols
    ..............................................Page 20014640b too large to be in the dump file.
    .................
    ..Page 200088e73 too large to be in the dump file.
    ..............................................................
    ................................................................
    .....................................
    Loading User Symbols

    Loading unloaded module list
    ..............
    For analysis of this file, run     !analyze -v
    nt!KeBugCheckEx:
    fffff805`3325d5e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff830c`a5c2f7a0=000000000000009f
    1: 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: ffffb487593dfd20, Physical Device Object of the stack
    Arg3: ffff830ca5c2f7d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffb4875fbdb0c0, The blocked IRP

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

    Implicit thread is now ffffb487`64811040

    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER: Microsoft Corporation

    SYSTEM_PRODUCT_NAME: Surface Pro 4

    SYSTEM_SKU: Surface_Pro_4

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

    BIOS_VENDOR: Microsoft Corporation

    BIOS_VERSION: 108.2439.769

    BIOS_DATE: 12/07/2018

    BASEBOARD_MANUFACTURER: Microsoft Corporation

    BASEBOARD_PRODUCT: Surface Pro 4

    DUMP_TYPE: 1

    BUGCHECK_P1: 3

    BUGCHECK_P2: ffffb487593dfd20

    BUGCHECK_P3: ffff830ca5c2f7d0

    BUGCHECK_P4: ffffb4875fbdb0c0

    DRVPOWERSTATE_SUBCODE: 3

    FAULTING_THREAD: ffffb48764811040

    CPU_COUNT: 4

    CPU_MHZ: 9c0

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

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

    BLACKBOXBSD: 1 (    !blackboxbsd)


    BLACKBOXPNP: 1 (    !blackboxpnp)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: LEOZHU

    ANALYSIS_SESSION_TIME: 04-07-2019 19:47:36.0284

    ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

    LAST_CONTROL_TRANSFER: from fffff805331c36c7 to fffff80533264186

    STACK_TEXT:
    ffff830c`a7ac6b70 fffff805`331c36c7 : ffffb487`64811040 00000000`00000000 ffffdb00`a8e75100 ffff830c`00000000 : nt!KiSwapContext+0x76
    ffff830c`a7ac6cb0 fffff805`331c3239 : ffffb487`00000000 ffffb487`00000000 ffffb487`592dcca8 00000000`00000000 : nt!KiSwapThread+0x297
    ffff830c`a7ac6d70 fffff805`331c1fc0 : ffffb487`5928fe00 fffff805`00000000 fffff805`00000000 ffff830c`a7ac6e81 : nt!KiCommitThreadWait+0x549
    ffff830c`a7ac6e10 fffff805`3361721d : fffff805`334e56f0 ffffb487`00000012 00000000`00006f00 00000000`00007000 : nt!KeWaitForSingleObject+0x520
    ffff830c`a7ac6ee0 fffff805`336224c4 : 00000001`00000000 ffffb487`5d207e30 00000000`00000000 00000001`00000001 : nt!MmDuplicateMemory+0x89
    ffff830c`a7ac6f70 fffff805`338ca35e : ffffb487`5d207d40 00000000`706d644c ffffb487`5d207d40 00000000`00000000 : nt!IopLiveDumpEstimateMemoryPages+0x68
    ffff830c`a7ac6fe0 fffff805`338c9aff : ffffb487`5d207d40 ffffb487`5d207d40 ffff830c`a7ac7190 ffff830c`a7ac7298 : nt!IopLiveDumpAllocAndInitResources+0x35e
    ffff830c`a7ac7090 fffff805`338bd3d2 : 00000000`00000000 ffffa48d`f4d06750 ffffa48d`fa93c3f0 ffffa48d`f4d06750 : nt!IoCaptureLiveDump+0x27b
    ffff830c`a7ac7230 fffff805`338bdaf0 : ffffffff`800017d8 00000000`00000000 00000000`00000000 00000000`0000015e : nt!DbgkpWerCaptureLiveFullDump+0x13a
    ffff830c`a7ac7290 fffff805`338bd221 : 00000000`00000002 00000000`00000000 fffff805`52256270 ffff830c`a7ac7508 : nt!DbgkpWerProcessPolicyResult+0x30
    ffff830c`a7ac72c0 fffff805`5221fb31 : ffffb487`5d7931a0 00000000`0000029a 00000000`00000021 ffffb487`6ddf6d18 : nt!DbgkWerCaptureLiveKernelDump+0x1a1
    ffff830c`a7ac7310 fffff805`522d4480 : 00000000`00000000 fffff805`52291d02 ffff830c`a7ac73d0 00000000`00000000 : ndis!ndisMLiveBugCheck+0x45
    ffff830c`a7ac7370 fffff805`522d431d : ffffb487`64811040 ffffb487`6ddf6c50 fffff805`522708d0 00000000`00000000 : ndis!ndisReportTimeoutWaitingForExternalDriver+0x108
    ffff830c`a7ac73b0 fffff805`522d4719 : 00000000`00040b28 ffffb487`6ddf6d18 ffffb487`6ddf6d18 00000000`00000000 : ndis!ndisFindSomeoneToBlame+0x125
    ffff830c`a7ac7420 fffff805`522d419a : ffffb487`6ddf6c50 ffff830c`a7ac7540 00000000`00000000 ffff830c`a7ac7508 : ndis!ndisWaitForExternalDriver+0xad
    ffff830c`a7ac7450 fffff805`522d463a : ffffb487`6ddf6c50 fffff805`52289c65 ffffb487`5d7931a0 ffff830c`a7ac7540 : ndis!NdisWatchdogState::WaitSynchronously+0x6e
    ffff830c`a7ac7490 fffff805`522e58e1 : ffffb487`6ddf6c50 00000000`00000000 00000000`00000000 ffffb487`5d7931a0 : ndis!ndisWaitForEventThenDisarmWatchdog+0x2e
    ffff830c`a7ac74d0 fffff805`52289bbe : ffffb487`5d7945b8 ffffb487`5d7931a0 ffffb487`5d7945b8 ffff830c`a7ac7b10 : ndis!ndisMPauseMiniportInner+0x985d
    ffff830c`a7ac7550 fffff805`5229029f : 00000000`00000000 ffff830c`a7ac7680 00000000`00000001 ffffb487`5d7945b8 : ndis!ndisMPauseMiniport+0x2a
    ffff830c`a7ac7580 fffff805`5228fc73 : ffffb487`5d7945b8 ffffb487`5d7945b8 ffffb487`5d794630 ffffb487`5d7931a0 : ndis!Ndis::BindEngine::Iterate+0x59b
    ffff830c`a7ac76f0 fffff805`522924ed : ffffb487`5d7945b8 00000000`00000000 00000000`00000000 ffff830c`a7ac7770 : ndis!Ndis::BindEngine::UpdateBindings+0x7b
    ffff830c`a7ac7720 fffff805`5228f9d0 : ffffb487`5d7945b8 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!Ndis::BindEngine:Surface Pro Kernel Memory Dump When It Turn On Every time! :DispatchPendingWork+0x75
    ffff830c`a7ac7750 fffff805`522877fe : ffffb487`5d7931a0 00000000`00000020 00000000`00000004 ffff830c`a7ac78f0 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54
    ffff830c`a7ac77a0 fffff805`521df57d : ffffb487`5e8b5a30 ffffb487`5d7931a0 ffffb487`5d7931a0 00000000`00000004 : ndis!ndisIssueNetEventSetPowerEvent+0x7a
    ffff830c`a7ac78a0 fffff805`52287d4f : ffffb487`5d7931a0 00000000`00000005 00000000`00000000 fffff805`33660700 : ndis!ndisPrepForLowPower+0x45
    ffff830c`a7ac7970 fffff805`52287c28 : 00000000`00000000 ffffb487`00000004 ffffb487`5fbdb0c0 00000000`00000000 : ndis!ndisSetSystemPower+0x11f
    ffff830c`a7ac79f0 fffff805`521f3ad1 : ffffb487`5fbdb0c0 ffffb487`593dfd20 ffffb487`5fbdb1d8 fffff805`334c2800 : ndis!ndisSetPower+0xac
    ffff830c`a7ac7a30 fffff805`332155e6 : ffffb487`64811040 ffff830c`a7ac7ae0 ffffb487`5fbdb0c0 ffffb487`65b2aa00 : ndis!ndisPowerDispatch+0xa1
    ffff830c`a7ac7a60 fffff805`33130bc5 : ffffffff`fa0a1f00 fffff805`332153c0 ffffb487`6daf93f0 00000000`00000000 : nt!PopIrpWorker+0x226
    ffff830c`a7ac7b10 fffff805`33264a3c : ffffdb00`a8e65180 ffffb487`64811040 fffff805`33130b70 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffff830c`a7ac7b60 00000000`00000000 : ffff830c`a7ac8000 ffff830c`a7ac1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


    STACK_COMMAND: .thread 0xffffb48764811040 ; kb

    THREAD_SHA1_HASH_MOD_FUNC: 57c4e9fd64b95ffc655be037e689ac9b139b6f60

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 73994988caeab8e0155fc4c5c214830d4b8047a7

    THREAD_SHA1_HASH_MOD: 95a570ad861638dbb963924ca28cc3efe58edfed

    FOLLOWUP_IP:
    ndis!ndisMLiveBugCheck+45
    fffff805`5221fb31 0f1f440000 nop dword ptr [rax+rax]

    FAULT_INSTR_CODE: 441f0f

    SYMBOL_STACK_INDEX: b

    SYMBOL_NAME: ndis!ndisMLiveBugCheck+45

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:     ndis

    IMAGE_NAME: ndis.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 700d408f

    BUCKET_ID_FUNC_OFFSET: 45

    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!ndisMLiveBugCheck

    BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!ndisMLiveBugCheck

    PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_ndis!ndisMLiveBugCheck

    TARGET_TIME: 2019-04-06T17:42:54.000Z

    OSBUILD: 17763

    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: unknown_date

    BUILDDATESTAMP_STR: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: a3e

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_ndis!ndismlivebugcheck

    FAILURE_ID_HASH: {ce0964c4-ec15-7eed-e327-bc190f8eea4c}

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

    :)
     
    Leo_5117, Apr 8, 2019
    #1
  2. SOKTHEARITHYI
    SokthearithYi Win User

    Surface Pro 4 screen not turn on after sleep

    Hi, thank you. I could restart my surface pro 4 but still could not fix the Surface Pro 4 screen not turn on after sleep. I am still looking forward to hearing more suggestions to fix the black screen after sleep.

     
    SokthearithYi, Apr 8, 2019
    #2
  3. BORE07TM
    Bore07tm Win User
    Frequent Memory Dumps

    Thank you for your response.

    I have uninstalled cccleANER as suggested.

    I have turned off real time scanning on McAfee Total Protection.

    A couple of questions:

    1. How can I check that I am not getting Memory dump files anymore? - they were detected by cccleANER
    2. How can I check that I'm not getting interference between Malwarebytes and McAfee? - i.e. I need to know what level of RAM?
    Thank you for your assistance
     
    Bore07tm, Apr 8, 2019
    #3
  4. ARUN B J
    Arun B J Win User

    Surface Pro Kernel Memory Dump When It Turn On Every time!

    Surface Pro 3 won't turn on

    Hi,

    Thank you for posting the query on Microsoft Community.

    We understand how you feel about the situation. We're sorry for the trouble.

    I suggest you to follow the steps below and check, if it helps:

    If you still have the device, please let the device charge at least 2 hours and do the 2-button shutdown one more time to see if you can turn on the device.

    • A 2-button shutdown
      • Press and hold the power button on your Surface for 30 seconds.
      • Press and hold the Volume-up button and the
        Power button on your Surface at the same time for at least 15 seconds, and then release both. The screen may flash the Surface logo, but continue holding the buttons down for at least 15 seconds.
      • After you release the buttons, wait 10 seconds.
      • Press and release the power button on your Surface to turn it back on.

    Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help
     
    Arun B J, Apr 8, 2019
    #4
Thema:

Surface Pro Kernel Memory Dump When It Turn On Every time!

Loading...

  1. Surface Pro Kernel Memory Dump When It Turn On Every time! - Similar Threads - Surface Pro Kernel

  2. Memory Integrity is turned off every time I reboot

    in Windows 10 Gaming
    Memory Integrity is turned off every time I reboot: I turn on Memory Integrity in Windows Security, reboot and it's on. That is until the next reboot where it gets turned off and I have to turn it back on and reboot.So every reboot becomes two reboots which is pretty annoying.Why does this happen?...

  3. Memory Integrity is turned off every time I reboot

    in Windows 10 Software and Apps
    Memory Integrity is turned off every time I reboot: I turn on Memory Integrity in Windows Security, reboot and it's on. That is until the next reboot where it gets turned off and I have to turn it back on and reboot.So every reboot becomes two reboots which is pretty annoying.Why does this happen?...

  4. Memory Integrity is turned off every time I reboot

    in Windows 10 BSOD Crashes and Debugging
    Memory Integrity is turned off every time I reboot: I turn on Memory Integrity in Windows Security, reboot and it's on. That is until the next reboot where it gets turned off and I have to turn it back on and reboot.So every reboot becomes two reboots which is pretty annoying.Why does this happen?...

  5. Surface Pro 8 Keyboard turns off the Surface when connected

    in Windows 10 Gaming
    Surface Pro 8 Keyboard turns off the Surface when connected: Just bought a surface pro 8 bundle from Costco every time I go to hook up the signature type pad the screen turn off, but when I disconnect it screen come back on. I thought it got fixed when I diagnosed it with support team but it's now doing it again. Very frustrating I...

  6. Surface Pro 8 Keyboard turns off the Surface when connected

    in Windows 10 Software and Apps
    Surface Pro 8 Keyboard turns off the Surface when connected: Just bought a surface pro 8 bundle from Costco every time I go to hook up the signature type pad the screen turn off, but when I disconnect it screen come back on. I thought it got fixed when I diagnosed it with support team but it's now doing it again. Very frustrating I...

  7. Memory Dump

    in Windows 10 BSOD Crashes and Debugging
    Memory Dump: I am getting an blue screen and memory dump. Please can someone assist in resolving this matter, I keep on losing work and it is frustrating ******************************************************************************* *...

  8. Memory dump

    in Windows 10 Installation and Upgrade
    Memory dump: Does anyone have an idea what this means The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000008, 0x0000000000000002, 0x0000000000000000, 0xfffff80f1d427218). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id:...

  9. Surface Pro Memory Dump When It Turn On Everytime!

    in Windows 10 Drivers and Hardware
    Surface Pro Memory Dump When It Turn On Everytime!: Dear all, I got a very strange thing my Surface Pro Memory Dump when I turn on it everytime, but It don't happen if I just reboot after turn on. I try to understand what happen but the analysis is a little bit complicated for me. So I come here ask for help, Please give...

  10. Skype pops-up every time I turn on my Surface

    in Windows 10 Software and Apps
    Skype pops-up every time I turn on my Surface: I am in very desperate needs and I keep trying to talk to a representative A.K.A (a real life person) so i can close Skype because every time i shut down my surface it pops up when i turn it back on and sign in. * Moved from MSN * Original title: MICROSOFT ACCOUNT...

Users found this page by searching for:

  1. Surface pro 6 dump