Windows 10: Microsoft Surface 3 BSOD

I have a Microsoft Surface Pro 3 256GB that experienced a BSOD this morning. It has a clean install of Windows 10, and has been running for a few months without issue. It was stuck at the Surface logo screen with no circling dots, so I had to do the volume and power button procedure to get it to reboot. I have attached the zip file.

:)

 

Critical_Process_Died

I have a Surface 3 running windows 10. Just last time when I booted my tablet it went to the BSOD saying Critical_Process_Died.

Then today I turned it on and it went to the BSOD saying the same thing, but after restarting itself it looks just fine. But I know I will get another crash, sometime.

What does this BSOD mean, what makes it happen, and how do I fix it?

I love my surface 3 and windows 10, I would hate to switch. Microsoft please make windows more stable, FAST!

I use this for school and I can not have it crashing every time it turns on.

 

Windows 10 Video Scheduler Internal Error BSOD

I have a Surface Pro 3, had this issue as well as a Video_TDR_Failure (IGDKMD64.SYS) BSOD.

 

Hi Chrisfl94,

Welcome to the 10forums *Smile

The crash was caused by a Symantec heuristics driver, though unless you get another crash soon you have nothing to worry *Smile Windows handles single BSOD's by itself.
Driver Reference Table - BHDrvx64.sys
Code: ffffd000`2223f298 fffff801`90122e61Unable to load image \??\C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.6318.6100.105\Data\Definitions\BASHDefs\20160125.011\BHDrvx64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for BHDrvx64.sys *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys BHDrvx64+0xa2e61[/quote]

 

Axe0,
Thanks for analyzing the information, I never would have picked that Symantec driver. When I used a couple of tools I downloaded to find the problem, one said it was caused by ntoskrnl.exe+146f16 and the other said FAULTING_MODULE: fffff8018e020000 ACPI. I wish I knew how you figured that out, I'd like to be able to solve my own problems.
Chris

 

Ntoskrnl.exe is a file of the Windows kernel, basically the Windows kernel files are never the cause but blamed because there is nothing else to blame.
ACPI.sys is another file of Windows, Driver Reference Table - acpi.sys
Windows files are rarely the cause.

I could give you some guidance to find the cause with a 0x9F when the first parameter is 3, but this one holds a parameter 4 which is different from the usual 0x9F. It requires some understanding of a few things to find it out with(out) getting a headache.