Windows 10: Since TH, ntoskrnl.exe crash all the time

Discus and support Since TH, ntoskrnl.exe crash all the time in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi people, you really are my last hope. Please read my post carefully. My PC completly freeze without any noticable moment and restart. When also a... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Morku, Dec 19, 2015.

  1. MORKU
    Morku Win User

    Since TH, ntoskrnl.exe crash all the time


    Hi people, you really are my last hope. Please read my post carefully.

    My PC completly freeze without any noticable moment and restart. When also a sound is played, it also get the "freezed" sound before my PC restart.
    This behavior started when my PC downloaded Windows 10 TH2. I never had a problem with Windows 10 TH1, Windows 8.1 and before. I only noticed when always my PC crash, also Firefox was running. This could be always a unhappy coincidence, because Firefox is mostly always running.
    There are only moments without Firefox running, when my PC is encoding some of my video stuff with x264 over night. It never crashed these hours (could be coincidence, too...)!
    There is no noticable structure if I could force "that crash". It just happen. Maybe 2 times a day, maybe after 3 days again. I hoped, my PC will get over after the update from Firefox 42 to 43, but nope...

    Things I did:

    - the typical stuff like, latest driver updates (also some older drivers), latest Windows updates, sfc /scannow (there is always that annoying bad opencl.dll error since TH2)
    - I unplugged my soundcard, my webcam, one of my HDD, still got crashes.
    - set UEFI back to default
    - Memtest+ with my RAM without an error, because of my video encodings, it should be cpu stresstest enough, I did graphical benchmarks without any crash, S.M.A.R.T. of my drives are fine..., did the 'Video Memory Stress Test' for a few minutes

    Nothing helped! And I always got a useless bad dump. So I gave up. This PC was a ASRock Z77 Extreme 4, Intel Core i7 3770k, 16GB DDR3 1600MHz RAM, Asus ROG Phoebus, Enermax Modu82+ 525W.
    I thought, if Windows don't know whats the problem (and some other people in forums), it have to be the hardware (maybe the power suply. It's already about 7 years old...).
    Now I replaced my Mainboard, CPU, RAM and power supply. So my new PC: ASRock Z170 Extreme 4, 16GB DDR4 3000MHz, Intel Core i7 6700K, bequiet Dark Power Pro 11 550W, Asus ROG Phoebus, EVGA GTX 980Ti, Samsung SSD 840 Pro 128GB, WDC WD1003FZEX

    Windows 10 v1511 was installed completly new and clean (no upgrade) and guess what? It's still crashing the same behavior like before! All that hardware trouble for nothing!
    Even worse, My third SSD drive in PC, a Corsair Force Series F80 was always shown in task manager many times as 100% busy without any reason. No writing, no reading task, just 100%. Not always, but in that moments completly unusable. Also here, I replaced SATA cable, replaced power cable, changed port, still 100% busy. It only works fine in my SATA2USB docking station (bus yes, it's another new story).

    So, now I am here. Completly helpless. Hoping to get the 100% hint. I invested much money in the PC and really don't want pay more money and pation to fix mayybeeee an annyoing crash... (at least I know my replaced hardware is not the fault...)

    Thanks to anyone who read my long message and have a good christmas time.
    Attachment 54556

    :)
     
    Morku, Dec 19, 2015
    #1
  2. MIćA
    Mića Win User

    BSOD (Blue screen error) on Windows 10 PC.

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

    <html><head><title>Crash List</title></head>

    <body>

    <h3>Crash List</h3>

    <br><h4>Created by using <a href="NirSoft - freeware utilities: password recovery, system utilities, desktop utilities" target="newwin">BlueScreenView</a></h4><p><table border="1" cellpadding="5"><tr bgcolor="E0E0E0">

    <th>Dump File

    <th>Crash Time

    <th>Bug Check String

    <th>Bug Check Code

    <th>Parameter 1

    <th>Parameter 2

    <th>Parameter 3

    <th>Parameter 4

    <th>Caused By Driver

    <th>Caused By Address

    <th>File Description

    <th>Product Name

    <th>Company

    <th>File Version

    <th>Processor

    <th>Crash Address

    <th>Stack Address 1

    <th>Stack Address 2

    <th>Stack Address 3

    <th>Computer Name

    <th>Full Path

    <th>Processors Count

    <th>Major Version

    <th>Minor Version

    <th>Dump File Size

    <th>Dump File Time

    <tr><td bgcolor=#FFFFFF nowrap>010216-11375-01.dmp<td bgcolor=#FFFFFF nowrap>2.1.2016. 17:33:57<td bgcolor=#FFFFFF nowrap>&nbsp;<td bgcolor=#FFFFFF nowrap>0x00000139<td bgcolor=#FFFFFF nowrap>00000000`00000003<td bgcolor=#FFFFFF nowrap>ffffd000`22dcd730<td
    bgcolor=#FFFFFF nowrap>ffffd000`22dcd688<td bgcolor=#FFFFFF nowrap>00000000`00000000<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+142760<td bgcolor=#FFFFFF nowrap>NT Kernel &amp; System<td bgcolor=#FFFFFF nowrap>Microsoft®
    Windows® Operating System<td bgcolor=#FFFFFF nowrap>Microsoft Corporation<td bgcolor=#FFFFFF nowrap>10.0.10586.17 (th2_release.151121-2308)<td bgcolor=#FFFFFF nowrap>x64<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+142760<td bgcolor=#FFFFFF nowrap>&nbsp;<td bgcolor=#FFFFFF
    nowrap>&nbsp;<td bgcolor=#FFFFFF nowrap>&nbsp;<td bgcolor=#FFFFFF nowrap>&nbsp;<td bgcolor=#FFFFFF nowrap>C:\Windows\Minidump\010216-11375-01.dmp<td bgcolor=#FFFFFF nowrap>4<td bgcolor=#FFFFFF nowrap>15<td bgcolor=#FFFFFF nowrap>10586<td bgcolor=#FFFFFF nowrap>136.764<td
    bgcolor=#FFFFFF nowrap>2.1.2016. 17:34:25

    </table>

    </body></html>
     
    Mića, Dec 19, 2015
    #2
  3. ETHE COLI
    EThe coli Win User
    BSOD errors without an identifiable cause

    Okay I may or may not be onto something now. Since, from what I've read, it seems that most ntoskrnl.exe BSODs are not actually caused by ntoskrnl, but by another driver that takes up the krnl's space. When ntoskrnl.exe finds it, it throws the system into
    a BSOD to prevent damage. Looking the the dump files, I found that there was a driver called hal.dll, but the crash address was different from the driver address. The crash address was ntoskrnl.exe+14ec00, the same as my above post. There is also another driver
    called dxgmms2.sys who's crash address was ntoskrnl.exe+14ec00. I'm not sure if this will help or if it means anything but I'm looking for anything at this point.
     
    EThe coli, Dec 19, 2015
    #3
  4. MORKU
    Morku Win User

    Since TH, ntoskrnl.exe crash all the time

    Morku, Jan 11, 2016
    #4
  5. LIFETEC
    lifetec Win User
    All 3 dumpfiles are
    Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f59225c3577, b3b72bdf74dcef20, 1, 18} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver...tPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a01f59225c3577, Reserved Arg2: b3b72bdf74dcef20, Reserved Arg3: 0000000000000001, Failure type dependent information Arg4: 0000000000000018, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification[/quote] But going through your driverlist you have a few programs with predated windows 10 drivers.
    VMWare from 2014

    Driver Description: ArcSoft Total Media Theatre 6 Driver
    Driver Update Site: Official Support has ended.
    For more info - http://www.myce.com/news/arcsoft-end...theater-72722/

    Some Logitech devices with drivers from 2012


    Driver Description: Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
    Driver Update Site: http://forums.pcsx2.net/Thread-XInpu...6161#pid186161

    Update to windows 10 compatible versions or uninstall/remove from your system.
     
    lifetec, Jan 12, 2016
    #5
  6. MORKU
    Morku Win User
    Thank you very much for the answer.
    Yes... Beside Hardware, I also had the drivers in focus. Let me say.
    VMware Workstation is version 12.1.0 installed. It's the latest version and supports Windows 10. Why the driver is from 2014... well, ask vmware.

    The Logitech drivers came from Windows Update (under Windows 10). And on official Logitech Website, they still share driver from 2012, also for Windows 10: [Produktname] - Logitech Support

    Scp drivers are now developed here: Release ScpToolkit v1.6.238.16010 · nefarius/ScpToolkit · GitHub And latest version is also installed. The latest crash also happen when it wasn't installed. So here I can say 100% for sure, it's not because of that driver.

    Now Arcsoft TotalMedia. You are right, the support ended which sucks. There are no good Blu-ray Players outside for Windows. So R.I.P Blu-ray Disc.
    I found this topic: http://answers.microsoft.com/en-us/i...b-2a94a63f6902
    Also users reported about BSOD since Windows 10 november update. So I am in very good hope, that this one finally fix the issue. But to be 99,9% be sure, about a month have to pass with no crash. So don't expect a "Solved" the next days.
    Fun fact: Uninstall TotalMedia Theatre wont delete the driver. You first have to prevent loading the driver, reboot and after delete ArcCtrl.sys in C:\Windows\System32\drivers.

    So thank you very much for the hint *Smile
     
    Morku, Apr 5, 2018
    #6
Thema:

Since TH, ntoskrnl.exe crash all the time

Loading...

  1. Since TH, ntoskrnl.exe crash all the time - Similar Threads - Since ntoskrnl exe

  2. App crashing all the time

    in Windows 10 Gaming
    App crashing all the time: Hi,I bought a new computer and installed Huawei Theme Studio.My OS is Windows 11 but one app crashes all the time, on my old computer with Windows 11 it works.Here is the crashlog:Crash log: The error occurred in the program named: ThemeStudio.exe, version 11.301.0.0,...

  3. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...

  4. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...

  5. re crashing all the time

    in Windows 10 BSOD Crashes and Debugging
    re crashing all the time: have no idea what's up with it', about go out and buy another motherboard and processor bundle on windows 10 64 bit motherboard is over 2 years old 8.00 GB AMD Ryzen 7 2700X Eight-Core Processor 3.70 GHz any help would be a great thanks regards...

  6. Games crashing all the time

    in Cortana
    Games crashing all the time: [ATTACH]this wont stop crashing my games any help ? https://answers.microsoft.com/en-us/windows/forum/all/games-crashing-all-the-time/b9526734-cd85-4b94-a49a-d824f5406bca"

  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...

  8. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...

  9. BSOD since Windows update (ntoskrnl 8x)

    in Windows 10 BSOD Crashes and Debugging
    BSOD since Windows update (ntoskrnl 8x): 9 days ago I updated windows, the updated looked very similar to the windows 8.1 to windows 10 (windows cumulative update). This update brought some problems with it. Since the update I have had lots of BSOD. Never before I had one blue screen. Now it looks like I am...

  10. NTOSKRNL Crash

    in Windows 10 BSOD Crashes and Debugging
    NTOSKRNL Crash: Hey guys, I have been having an issue with my computer randomly shutting off (when I am not near the computer). My PC almost almost posts a BSOD when I manually restart or shutdown the computer. I have checked the dump logs, which point back to ntoskrnl.exe as the problem. I...
  1. KAPITANLUFFY
    Thread

    Bluescreen help! PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe

    This just happened recently. It commonly happens when I leave my computer idle. Here is a zip of the dmp file:...
    Thread by: kapitanluffy, Oct 10, 2019, 3 replies, in forum: Windows 10 Installation and Upgrade
  2. VICTOREMA
    Thread

    Crashes caused by ntoskrnl.exe (dmp files inside)

    Hi all. I've been getting constant black screens followed by a loud buzzing sound on my newly built rig every few hours or so. Initially my...
    Thread by: VictorEMA, Oct 9, 2019, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  3. JILYCN
    Thread

    BSOD keep happening from Hal.dll, ntoskrnl.exe and PSHED.dll, please help.

    BSOD keep happening from Hal.dll, ntoskrnl.exe and PSHED.dll, please help....
    Thread by: jilycn, Oct 2, 2019, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  4. UVISSENKANS
    Thread

    Store data structure corruption by ntoskrnl.exe

    I have an issue where I would frequently get BSOD with error: STORE_DATA_STRUCTURE_CORRUPTION when using google meet. It may have happened other...
    Thread by: uvissenkans, Oct 1, 2019, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  5. XDSTICK
    Thread

    Bluescreen caused by ntoskrnl.exe

    I have been having this issue so I clean installed windows 10. The problem was still happening and I downloaded bluescreenview and it told me the...
    Thread by: xdstick, Sep 29, 2019, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags: