hibernation problem vwifibus.sys

Discussion in 'Microsoft Surface Pro 3' started by test3jkkja, Sep 16, 2014.

  1. test3jkkja

    test3jkkja New Member

    Joined:
    Sep 16, 2014
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    3
    hi
    I've got a Problem with the Surface 3 pro (I7 512 GB).
    connected sleep-mode is working fine, but after some hours it Needs to go to Hibernation and if then the Computer is started, it performs a restart, because it is not able to resume from Hibernation.
    Analysis of the Crash dump file by windbg Results in the message (see below) that this error is caused by ntoskrnl.exe and vwifi.net.
    Do you have any idea to resolve it? Because as far as I could see, there a many vwifinet.sys Drivers even in the winsxs, thus they cannot just be deleted....
    THANKS!!!!!!!!

    The Output of windbg:

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

    Loading Dump File [C:\temp\091514-7734-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    Machine Name:
    Kernel base = 0xfffff802`89a14000 PsLoadedModuleList = 0xfffff802`89cde350
    Debug session time: Mon Sep 15 02:52:48.692 2014 (UTC + 2:00)
    System Uptime: 0 days 0:17:43.682
    Loading Kernel Symbols
    .
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    ..............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, ffffe001dfabee20, ffffd0010ca86c80, ffffe001ddcf6cf0}
    Probably caused by : vwifibus.sys
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------
    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: ffffe001dfabee20, Physical Device Object of the stack
    Arg3: ffffd0010ca86c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ddcf6cf0, The blocked IRP
    Debugging Details:
    ------------------

    OVERLAPPED_MODULE: Address regions for 'mrxdav' and 'IntcDAud.sys' overlap
    DRVPOWERSTATE_SUBCODE: 3
    IMAGE_NAME: vwifibus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f854
    MODULE_NAME: vwifibus
    FAULTING_MODULE: fffff800452a7000 vwifibus
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x9F
    PROCESS_NAME: MsMpEng.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    DPC_STACK_BASE: FFFFD0010CA86FB0
    STACK_TEXT:
    ffffd001`0ca86c48 fffff802`89c10586 : 00000000`0000009f 00000000`00000003 ffffe001`dfabee20 ffffd001`0ca86c80 : nt!KeBugCheckEx
    ffffd001`0ca86c50 fffff802`89c104a6 : ffffe001`e31582e0 ffffe001`dbdeb060 ffffe001`e06ef080 fffff802`89a5a190 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`0ca86cb0 fffff802`89a56760 : 00000000`00000000 ffffd001`0ca86e00 ffffe001`e3158318 ffffd001`00000f45 : nt!PopIrpWatchdog+0x32
    ffffd001`0ca86d00 fffff802`89b6add5 : 00000000`00000000 ffffd001`0ca52180 fffff802`8a1f1e00 0000001d`43377f6f : nt!KiRetireDpcList+0x4f0
    ffffd001`0ca86fb0 fffff802`89b6abd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd001`0f8e9ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    IMAGE_VERSION: 6.3.9600.16384
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    BUCKET_ID: 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_vwifimp_image_vwifibus.sys
    FAILURE_ID_HASH: {0723cd8f-d174-0851-252b-1f5f4bf49d7c}
    Followup: MachineOwner
    ---------

    [edit] ZIP file download removed.
     
    Last edited by a moderator: Sep 16, 2014
  2. jnjroach

    jnjroach Administrator Staff Member

    Joined:
    Nov 9, 2012
    Messages:
    7,096
    Likes Received:
    1,724
    Trophy Points:
    113
    Location:
    Seattle, WA USA
    My Device:
    Surface Book
    That is part of the Network Stack, have you applied the latest Firmware? Is your SP3 joined to an Active Directory Domain that is using Network Access Protection? What are you using for Anti-virus/security?
     
  3. surfdock

    surfdock Active Member

    Joined:
    Jan 21, 2014
    Messages:
    199
    Likes Received:
    47
    Trophy Points:
    28
    Location:
    Seattle, WA
    My Device:
    SPro3
    Hi I don't think 0x9F_3_POWER_DOWN_vwifimp_IMAGE_vwifibus.sys is a particularly common failure on Surface. Can you save a FULL system dump as opposed to mini/kernel dump and post up on onedrive somewhere? You can PM me the location/password if you prefer not to send out broadly.

    I see MsMpEng.exe is running which correspnds to Windows defender/Security essentials. Can you check to see that AVG or Avast isn't also loaded? Windows and the 3rd-party anti-virus tools are supposed to prevent loading multiple virus scanners /anti-malware simultaneously, but if two are running, or if an alternate scanner was installed and not fully uninstalled, that could be the culprit.

    If you can rum "lm" in the debugger to output the loaded modules list, that might help too. Its usually a long list so you might have to attach a txt file :)
     
    Last edited: Sep 16, 2014
  4. test3jkkja

    test3jkkja New Member

    Joined:
    Sep 16, 2014
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    3
    thanks for your answers to both of you!
    @jnjroach: yes, latest Firmware is installed. Furthermore only the anti Virus tool which is built-in Windows with Default Settings. No active Directory Domain.
    is it possible to completely reinstall the Network stack?

    @surfdock: you can find the full dump and list of modules under:
    http://1drv.ms/1so8Qm7
    Yes MsMpEng.exe is running, but no other 3rd Party tool, just the Windows built-in Defender. No AVG or Avast.

    Thanks again!!
     
  5. jnjroach

    jnjroach Administrator Staff Member

    Joined:
    Nov 9, 2012
    Messages:
    7,096
    Likes Received:
    1,724
    Trophy Points:
    113
    Location:
    Seattle, WA USA
    My Device:
    Surface Book
    I wouldn't try to troubleshot it at this point, back up your personal data and do a Reset, or if you want to attempt a refresh you wouldn't need to back your data...
     
  6. test3jkkja

    test3jkkja New Member

    Joined:
    Sep 16, 2014
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    3
    oh... no other way??? will take Ages to reinstall all that.... :-(
     
    Telstar1948 likes this.
  7. jnjroach

    jnjroach Administrator Staff Member

    Joined:
    Nov 9, 2012
    Messages:
    7,096
    Likes Received:
    1,724
    Trophy Points:
    113
    Location:
    Seattle, WA USA
    My Device:
    Surface Book
    A refresh will take about 30 minutes a full reset will take 45 minutes, patching another hour...

    If you want to advanced troubleshooting, you can try from an elevated CMD Prompt run:

    C:\>sfc /scannow

    And see if it can fix any corrupted files...
     
  8. test3jkkja

    test3jkkja New Member

    Joined:
    Sep 16, 2014
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    3
    I've performed the sfc /scannow. Unfortunately, sfc does not find any corrupted files.......
     
  9. jnjroach

    jnjroach Administrator Staff Member

    Joined:
    Nov 9, 2012
    Messages:
    7,096
    Likes Received:
    1,724
    Trophy Points:
    113
    Location:
    Seattle, WA USA
    My Device:
    Surface Book
    Then it is either a Hardware Fault or bad Driver, you can uninstall the Marvell Driver and reboot....
     
  10. surfdock

    surfdock Active Member

    Joined:
    Jan 21, 2014
    Messages:
    199
    Likes Received:
    47
    Trophy Points:
    28
    Location:
    Seattle, WA
    My Device:
    SPro3
    Unfortunately, I concur with jnjroach's advice. I reported this internally at MS and some folks are looking into it but no root cause/solution at this point. If it still reproduces after the full system restore, then I'd return/exchange the unit. Also do call MS support and get a ticket started. Yes its sometimes a hassle talking with support on the phone, but its better to have this stuff tracked officially in case of future warranty claims etc. You can also do live chat which is slightly less of a hassle imho.
     
  11. test3jkkja

    test3jkkja New Member

    Joined:
    Sep 16, 2014
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    3
    Thanks for all your advices! Good news: it was related with VPN Driver from AVM (Fritzbox). after deinstalling and rebooting all works fine and Hibernation mode is okay! Thanks!!!
     
  12. surfdock

    surfdock Active Member

    Joined:
    Jan 21, 2014
    Messages:
    199
    Likes Received:
    47
    Trophy Points:
    28
    Location:
    Seattle, WA
    My Device:
    SPro3
    That's great! I'll pass along this info too. Microsoft partners with some VPN vendors but I'm not sure if AVM is one of them.
     

Share This Page

Search tags for this page

driver vwifibus surface pro 3

,

surface 3 pro problems after hibernation

,

validation 87271 dell

,

vwifibus

,

vwifibus crash