Windows 10: Surface Pro 3 BSOD when Idle/Sleeping

I have a Surface Pro 3 and it has an issue where when it sleeps, it will crash and power off.

There is a critical Kernel-Power event (41) whenever this happens, and sometimes it's accompanied by a BSOD, other times it's not - The BSOD bugcheck message does seem to vary too.

I've attached the latest Memory Dump, it has the message:

FAULTY_HARDWARE_CORRUPTED_PAGE

I have BlueScreenView installed, but I am aware this doesn't necessarily tell you anything concrete, the reason I'm mentioning it is that entry for this BSOD in that app doesn't show a Bug Check String, but I can confirm from seeing it happen at the time that it was the message above.

Here is a memory dump, hoping somebody can help me determine what the issue is. I have a range of BSOD errors, but I've only attached the newest one from yesterday for now - Let me know if it's inconclusive and if the additional dumps are required.

Really appreciate anybody having time to take a look at the dump.

Attachment 121355

:)

 

Silent BSOD on my Surface Pro 3 while sleeping

Mine is doing this to does it sound like a mini jet engine with the fans in hypermode ready for take-off? no keybrd or mouse response have to do a hard reset? mine is an old desktop.

 

Silent BSOD on my Surface Pro 3 while sleeping

Hi, I have a strange issue with my SP3.

Sometimes when I wake it up it does as if it's just started (none of my programs opened)

I just did a clean install of latest Windows 10 (via bootable USB, reformatting my C drive and all) because I was having issues, but this is still happening.

Doesn't have to be overnight that this happens. Last time I closed it and I reopened two hours later and it was restarted

I looked into Event Viewer and it marks a Kernel-Power error

I've installed window debugging tools to watch Memory Dump file and this is what shows

Microsoft (R) Windows Debugger Version 10.0.15063.468 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.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 15063 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 15063.0.amd64fre.rs2_release.170317-1834

Machine Name:

Kernel base = 0xfffff803`5f401000 PsLoadedModuleList = 0xfffff803`5f74d5a0

Debug session time: Wed Jul 5 13:53:15.564 2017 (UTC - 3:00)

System Uptime: 0 days 19:08:46.403

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.........

Loading User Symbols

PEB is paged out (Peb.Ldr = 00000085`5f461018). Type ".hh dbgerr001" for details

Loading unloaded module list

..................................................

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, fffff80361864e70, fffff80361855f70, fffff8032c77e50c}

Probably caused by : BTHUSB.sys ( BTHUSB!BthUsb_WriteHciCommand+290 )

Followup: MachineOwner

When I run !analyze -v shows me this:

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault). The first number in the

bugcheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a *portion* of those codes:

If kv shows a taskGate

use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

use .trap on that value

Else

.trap on the appropriate frame will show where the trap was taken

(on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

Arg2: fffff80361864e70

Arg3: fffff80361855f70

Arg4: fffff8032c77e50c

Debugging Details:

------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER: Microsoft Corporation

SYSTEM_PRODUCT_NAME: Surface Pro 3

SYSTEM_SKU: Surface_Pro_3

SYSTEM_VERSION: 1

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3.11.2150

BIOS_DATE: 04/26/2017

BASEBOARD_MANUFACTURER: Microsoft Corporation

BASEBOARD_PRODUCT: Surface Pro 3

BASEBOARD_VERSION: 1

DUMP_TYPE: 1

BUGCHECK_P1: 8

BUGCHECK_P2: fffff80361864e70

BUGCHECK_P3: fffff80361855f70

BUGCHECK_P4: fffff8032c77e50c

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: fffff80361864e70 -- (.trap 0xfffff80361864e70)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000001 rbx=0000000000000000 rcx=ffffc30b35a5af70

rdx=ffffc30b374f5010 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8032c77e50c rsp=fffff80361855f70 rbp=fffff80361855ff9

r8=ffffc30b35a5ae20 r9=0000000000000001 r10=00000000000000b2

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

Wdf01000!Mx::MxAcquireRemoveLock+0x6:

fffff803`2c77e50c c744242020000000 mov dword ptr [rsp+20h],20h ss:0018:fffff803`61855f90=????????

Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 9be

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 1D'00000000 (cache) 1D'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: dasHost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: SP3-GIS

ANALYSIS_SESSION_TIME: 07-06-2017 10:03:03.0272

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

DPC_STACK_BASE: FFFFF8036185BFB0

STACK_OVERFLOW: Stack Limit: fffff80361855fb0. Use (kF) and (!stackusage) to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xfffff80331523a4c was blamed for the stack overflow. It is using 2112 bytes of stack total in 11 instances (likely recursion).

FOLLOWUP_IP:

BTHUSB!BthUsb_WriteHciCommand+290

fffff803`31523a4c 488b0dadc50000 mov rcx,qword ptr [BTHUSB!WPP_GLOBAL_Control (fffff803`31530000)]

STACK_COMMAND: .trap 0xfffff80361864e70 ; kb

THREAD_SHA1_HASH_MOD_FUNC: cdbfcae35b24f70079c588cc3b30bdaa490a2719

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 860082b027ce2f5a7ec9f02e7f57a69e5d985a3c

THREAD_SHA1_HASH_MOD: a59ce36359c0e9420e5116457ac8f15e34be9104

FAULT_INSTR_CODE: ad0d8b48

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: BTHUSB!BthUsb_WriteHciCommand+290

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: BTHUSB

IMAGE_NAME: BTHUSB.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID_FUNC_OFFSET: 290

FAILURE_BUCKET_ID: 0x7f_8_STACK_USAGE_RECURSION_BTHUSB!BthUsb_WriteHciCommand

BUCKET_ID: 0x7f_8_STACK_USAGE_RECURSION_BTHUSB!BthUsb_WriteHciCommand

PRIMARY_PROBLEM_CLASS: 0x7f_8_STACK_USAGE_RECURSION_BTHUSB!BthUsb_WriteHciCommand

TARGET_TIME: 2017-07-05T16:53:15.000Z

OSBUILD: 15063

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: 2017-06-03 05:53:36

BUILDDATESTAMP_STR: 170317-1834

BUILDLAB_STR: rs2_release

BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: 74e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7f_8_stack_usage_recursion_bthusb!bthusb_writehcicommand

FAILURE_ID_HASH: {7bbcb0e3-d29f-392a-7103-c06379ed51a5}

Followup: MachineOwner

---------

It seems some driver is messing with Windows but I wouldn't know where to start. This is my work machine and all I have installed is really (and only) what I need.

Any hint would be really appreciated

Thanks

German

 

Hello and welcome to TenForums *Smile

If you are able to provide the full set of logfiles it will be more helpful.

See: Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions