Microsoft Surface 3 BSOD


  1. Posts : 7
    Windows 10 Pro
       #1

    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.
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi Chrisfl94,

    Welcome to the 10forums :)

    The crash was caused by a Symantec heuristics driver, though unless you get another crash soon you have nothing to worry :) 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
      My Computers


  3. Posts : 7
    Windows 10 Pro
    Thread Starter
       #3

    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
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #4

    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.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:53.
Find Us




Windows 10 Forums