Windows 10: BSOD Win10 constantly crashing (culprit, ntoskrnl.exe?)

  1.    17 Dec 2016 #1

    BSOD Win10 constantly crashing (culprit, ntoskrnl.exe?)


    I was short on cash when my desktop PC died so I bought a chinese Mini PC with great specs and performance for its cost (Beelink BT7), unfortunately it keeps crashing (BSOD), it can be while I surf a webpage, watch a video online, watch a video on the pc, clicking on Cortana or doing something else. It's very random really. 30 secs after first boot up it crashed for the first time, it rebooted and it worked great for maybe 10 minutes before it went down again and then I started to figure out I had a problem. Since then I have:
    • Updated Win10 Home which came with the unit (problem was still present)
    • Installed Win10 Pro and updated it (crashed while configuring the unit before 1st boot up, after succesful boot up -> same problem as before)
    • Re-Installed Win10 Pro (Same as above)
    • Installed Win8.1 (All went fine until I started to use it and then -> BSOD)
    • Installed Win10 (Home version 1607 Buid 14393.479) -> same problem, BSOD at random points


    Other problem I've had which I believe to be linked to the main one is: While surfing using Chrome, I get the "Aw, Snap!" error often, never before had I experienced it. Firefox just crashes.

    Trying to solve the problem I booted in safe mode, the unit works great there except for the no wifi/bt, audio and overall limited functionality. In Youtube and opened several (8+) videos using Chrome and no problem, in normal boot up I can more or less force a crash if I open just a few Youtube videos. I didn't get the "Aw, Snap!" error in SafeMode.

    Last fresh install was yesterday before I went to work so the crash dumps are a few, but using BlueScreenView the offending program seems to be ntoskrnl.exe (caused by address ntoskrnl.exe+14a6f0).

    I already gave it a shot at trying to locate the offending service/process that seems to be causing the problem and so far no luck, to be honest I'm new at this kind of thing so I'm requesting some help, I really don't want to try and send the unit back to China, something tells me it won't arrive and I'll lose my money.

    PD1: I'll add the list of Services (net start), Processes (tasklist) and SVC (tasklist /SVC) that were running on Normal and SafeMode.
    PD2: Forgot to mention I ran FurMark benchmark for graphics, Windows Memory Diagnostics for memory and I forget which other program for stressing CPU. No crash or problem when running them.
    BSOD Win10 constantly crashing (culprit, ntoskrnl.exe?) Attached Files
    Last edited by kaelthasw3; 17 Dec 2016 at 17:03.
      My ComputerSystem Spec

  2.    17 Dec 2016 #2

    Hi kaelthasw3,

    Looking at the minidumps I have noticed that there are several pieces of evidence that point towards your graphics driver.

    igdkmd64lp.sys - in 121716-21406-01.dmp (Intel Graphics Kernel Mode Driver)
    dxgmms2.sys - in 121716-14531-01 (DirectX Graphics MMS)
    dxgkrnl.sys - in 121716-14984-01.dmp (DirectX Graphics Kernel)
    igfxEM.exe - in 121716-14984-01.dmp (Intel Common User Interface)

    I would strongly suggest updating to the latest Intel graphics driver available, you should able to update it using Intel's latest driver package. Let me know if this update works, per Intel's PDF it should support your CherryTrail system.
      My ComputerSystem Spec

  3.    18 Dec 2016 #3

    Spectrum said: View Post
    Hi kaelthasw3,

    Looking at the minidumps I have noticed that there are several pieces of evidence that point towards your graphics driver.

    igdkmd64lp.sys - in 121716-21406-01.dmp (Intel Graphics Kernel Mode Driver)
    dxgmms2.sys - in 121716-14531-01 (DirectX Graphics MMS)
    dxgkrnl.sys - in 121716-14984-01.dmp (DirectX Graphics Kernel)
    igfxEM.exe - in 121716-14984-01.dmp (Intel Common User Interface)

    I would strongly suggest updating to the latest Intel graphics driver available, you should able to update it using Intel's latest driver package. Let me know if this update works, per Intel's PDF it should support your CherryTrail system.
    Thanks for the suggestion. I just tried it:

    When trying to install the suggested drivers (win64_154510.4542) I got "This computer does not meet the minimum requirements for installing the software"

    So I installed the Intel(R) Driver Update Utility 2.6 and it suggested different drivers (win64_154028.4501). First try crashed the pc while installing them, though it was not a BSOD, it just restarted. Second try was succesful and after a reboot I went to Youtube to test them out. First video played maybe 3 secs then the screen blinked black and then BSOD with the message "ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY"

    EDIT: I've been watching some Youtube videos and I notice the system more stable, yet it still crashes. I'm attaching the last 2 minidumps.
    BSOD Win10 constantly crashing (culprit, ntoskrnl.exe?) Attached Files
    Last edited by kaelthasw3; 18 Dec 2016 at 02:34.
      My ComputerSystem Spec

  4.    18 Dec 2016 #4

    The few dumpfiles i analysed all mention memory corruption
    Code:
      BugCheck 50, {ffff8701ffe60b80, 0, fffff801e08a1108, 0}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    
    BugCheck FC, {ffff9b8a42461140, 80000001348009e3, ffffbe817d51f710, 4}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13d7e )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: ffff9b8a42461140, Virtual address for the attempted execute.
    Arg2: 80000001348009e3, PTE contents.
    Arg3: ffffbe817d51f710, (reserved)
    Arg4: 0000000000000004, (reserved)
    
    BugCheck 1A, {41792, ffff98809eab9808, 100000000000000, 0}
    
    Probably caused by : memory_corruption ( ONE_BIT )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    	the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: ffff98809eab9808
    Arg3: 0100000000000000
    Arg4: 0000000000000000
    Test your memory with memtest 86+
    Memory Test.
    Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+" to stress test the RAM.

    How to run "Memtest" - RAM - Test with Memtest86+ - Windows 7 Help Forums
    MemTest86+ - Test RAM
    Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

    You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.

    But first update these older/outdated drivers.
    bcmdhd63 Thu Jul 09 10:20:44 2015 (559E2EDC)
    bcmfn2 Thu Jul 09 10:14:24 2015
    Driver Description: Broadcom SDIO WiFi Driver
    Driver Update Site: OEM - no wireless drivers available at
    Support

    dptf_acpi.sys
    Driver Description: Dynamic Platform Thermal Framework Driver
    Driver Update Site: Drivers & Software or the OEM of your particular system

    GKS16Fltr Tue Dec 20 02:26:10 2011 - No idea but the driver is from 2011 and maybe not compatible windows 10

    iai2c Tue Sep 22 08:53:03 2015 (5600FACF)
    iaspie Wed Jun 24 15:46:37 2015 (558AB4BD)
    iauarte Wed Jun 24 15:43:15 2015 - No idea but seems related to your intel atom processor maybe chipset?

    PMIC Wed Sep 30 18:55:49 2015
    Driver Description: Intel Power Management IC Device driver
    Driver Update Site: Drivers & Software

    TXEIx64 Tue Jun 16 12:32:43 2015
    Driver Description: Intel(R) Trusted Execution Engine Interface
    Driver Update Site: Drivers & Software
    OR
    OEM

    Look first at the driversupportpage of your system.
    Advice: update all the avaliable drivers from the supportpage.
      My ComputerSystem Spec

  5.    18 Dec 2016 #5

    I couldn't find some of the updated drivers so I installed IObit Driver Booster and it suggested 16 different drivers that needed to be updated.

    After that I tested the system for a few hours and the problem persists. So my next step was to run Memtest86+ which I couldn't since the system ignores the Bootable USB. I already tried in 2 different sticks with the same result, windows boots up. I went into the BIOS and Disabled all booting devices/options but the USB stick, Memtest86+ didn't boot still. So, is there any way to program the start of Memtest86+ from inside windows? Or an alternative?

    I'm attaching the files with the updated situation. I would like to thank you all for your time. Thanks!
    BSOD Win10 constantly crashing (culprit, ntoskrnl.exe?) Attached Files
      My ComputerSystem Spec

  6.    21 Dec 2016 #6

    Sorry for the delay,

    Your latest crashes (from Sunday the 18th) are showing aswSP.sys as a potential culprit, this is the avast! antivirus driver. Please uninstall the program, at least temporarily, to help troubleshoot this issue.

    If that does not resolve the issue, you may wish to try a manual update of your Intel Graphics driver using device manager (this works the same in Windows 10 as it does in 7). You'll need to download the .zip version of the driver package, extract it, and then navigate to the extracted folder to update the driver.
      My ComputerSystem Spec

  7.    23 Dec 2016 #7

    No problem. I appreciate all the help.

    I already uninstalled Avast Antivirus, the PC crashed still.At the moment I'm using Windows Defender.

    Manually updating the Graphic drivers was a No Go. It says that windows determined the drivers are up to date, I have the 4539. And now in a stroke of luck my LED monitor died, so it seems I will not only need to replace the PC but the monitor as well.

    Attaching last 2 crashes. May I mention I haven't used the pc much since I my monitor died.
    BSOD Win10 constantly crashing (culprit, ntoskrnl.exe?) Attached Files
      My ComputerSystem Spec


 

Related Threads
My PC Win 10 won't post up and gives no beeps. Simply pressing the power button shuts the power off instantly, I don't have to hold it for seven seconds. Recent changes include replacing one Logitech trackball with another trackball a month ago....
BSOD ntoskrnl.exe and crashing in BSOD Crashes and Debugging
I have a PC running windows 10 and recently it will just crash, I haven't had the typical blue screen error message but the PC will either freeze or restart. It started about a week ago when the PC randomly restarted while I was in the middle of...
Hello, After my upgrade to Windows 10 I'm been experiencing BSOD every 2 to 30 minutes (sometimes even at startup). I tired uninstalling drivers and installing from safe boot mode, without success. I've uploaded my last few crash dumps (last...
Hello, I need help with my Windows 10 PC not creating memory.dmp files upon BSOD. The attached debug files are likely referencing the last BSOD for which a minidump or memory.dmp was created. Since then I have had 2 more BSOD's, each time forgetting...
Atleast that is what I think is happening. I got the OK to upgrade to win10 from win7 on my laptop.. I went through the prossess as instructed and everything seemed to be going just fine. Then when my lesktop came to life...it was good for a few...
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 09:49.
Find Us