Windows 10: Regular bugchecks during asleep (Error: 0x00000139)

My Surface Pro 3 (Win 10.14393) regularly reboots during the night and goes to sleep on the login screen again.

I am leaving it docked to the Surface 4 Dock plugged into an external screen through the dock.

Most mornings the Reliability Monitor has reports of the type:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffff8600f5e5cec0, 0xffff8600f5e5ce18, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 726e7b19-dd7a-442d-891b-7742db547238.

I am attaching the log collector output.

Thanks for any help!

:)

 

Windows 10 BSODs

I've experienced three BSODs for the second day in a row. The first stated:

• The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xfffff802225dc9f0, 0xfffff802225dc948, 0x0000000000000000).

The second stated:

• The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffd000b8eed5a0, 0xffffd000b8eed4f8, 0x0000000000000000)

And the third stated:

• The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffd001c93da5a0, 0xffffd001c93da4f8, 0x0000000000000000)

These occurred while I was gaming, so is it a gpu driver issue?

 

BSOD errors bugcheck: 0x00000139

There are two BSODs, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) and KERNEL_SECURITY_CHECK_FAILURE (139), both referencing the ntfs.sys.

Can you try a "clean boot" and see if it makes a difference:

https://support.microsoft.com/en-us/kb/929135

Reset the computer to start normally after using the clean boot.

If the error persists after a clean boot can you provide the resulting minidump file(s).

 

Hello wigster and welcome to TenForums *Smile

The crash dump does not help very much. I looked in your eventlog for any problems that occurred prior to the crash and I see the following fatal error associated with your Surface Ethernet Adapter.

Code: Event[36427]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-02-14T16:12:02.595 Event ID: 10317 Task: PnP Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: gimpette.CHAMBREDUPEINE.local Description: Miniport Surface Ethernet Adapter, {7FB1E1EF-424F-442C-AA75-FECB32989210}, had event Fatal error: The miniport has detected an internal error[/quote] It may not be related to the crash but it suggests the driver for that device is buggy. It should be possible to look in the properties for that adapter in Device Manager and disable selective suspend.

 

Code: Event[30290]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-02-03T10:42:29.617 Event ID: 10317 Task: PnP Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: gimpette.CHAMBREDUPEINE.local Description: Miniport Marvell AVASTAR Wireless-AC Network Controller, {184AE1FB-C5C4-40BD-B0D0-01CB5CCB3449}, had event Fatal error: The miniport has detected an internal error[/quote] And the wireless adapter....


Code: 0x00000139: KERNEL_SECURITY_CHECK_FAILURE (2.02.2017 16:17:55) [Windows 10] CAUSED BY: ntoskrnl IntcDAud.sys [10.05.2016] * Intel Graphics Media Accelerator HD Driver * => Drivers & Software PROCESS: System[/quote]
Please update or roll back the Intel GPU Driver:

IntcDAud.sys [10.05.2016] * Intel Graphics Media Accelerator HD Driver * => Drivers & Software