Windows 10: Numerous BSODS all referring to ntoskrnl.exe

  1. Posts : 57
    Windows 10 Home (64-bit)
       24 Mar 2018 #1

    Numerous BSODS all referring to ntoskrnl.exe

    I have built a custom PC recently but it seems to be really unstable, giving loads of different BSOD error codes, always referring to ntoskrnl.exe. (codes like KMODE_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION, etc etc)
    ntoskrnl.exe is not specific enough to diagnose anything in my opinion and for some reason the older dump files have disappeared from c:/windows/minidump.

    I have 4 dump files, 3 from yesterday and 1 from today which I can attach. Hopefully someone can help me out because it's a real pain trying to figure it out.

    - It's a Ryzen 1700X system, using 16GB of G.Skill FlareX RAM which was on the motherboard's QVL list. (so it should be compatible)
    - After one of the BSODs, something strange happend with the SD card reader on my case, it simply doesn't recognize SD cards anymore and it always pops up as mounted in Win10 as drive letter F:, but with three dots as the name. The driver in device manager is "Generic STORAGE DEVICE USB Device" and uninstalling it and anything else related to it just makes it reappear after reboot. Disconnecting the USB 2.0 and SD card header from the motherboard made the "safely remove" icon disappear, but didn't solve the bsods (hence the crash from today)
    Numerous BSODS all referring to ntoskrnl.exe Attached Files
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       27 Mar 2018 #2

    Hello Sonar637,

    I can't find very much from the crash dumps but I'm thinking it is most likely graphics driver related.

    In the three earlier crash dumps two have the nvlddmkm.sys driver in the thread and the other mentions display parameters so I'm thinking it has something to do with the graphics processes.

    The recent crash happened while Adobe was updating and appears to be different.

    Start memory scan  : 0xfffff802ed27a2a8 ($csp)
    End memory scan    : 0xfffff802ed27b000 (Kernel Stack Base)
                   rsp : 0xfffff802ed27a2a8 : 0xfffff802eb223529 : nt!KiBugCheckDispatch+0x69
    0xfffff802ed27a2a8 : 0xfffff802eb223529 : nt!KiBugCheckDispatch+0x69
    0xfffff802ed27a2d0 : 0xfffff802eb13007a : nt!KiAbSetMinimumThreadPriority+0x3a
    0xfffff802ed27a2d8 : 0xfffff80affb4a378 : dxgmms2!VidSchiProfilePerformanceTick+0x178
    0xfffff802ed27a3e8 : 0xfffff802eb21f659 : nt!KiPageFault+0x519
    0xfffff802ed27a3f0 : 0x0000000000000000 :  Trap @ fffff802ed27a3f0
    0xfffff802ed27a558 : 0xfffff802eb13007a : nt!KiAbSetMinimumThreadPriority+0x3a
    0xfffff802ed27a628 : 0xfffff802eb156a68 : nt!KiAbProcessContextSwitch+0x358
    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvaki.inf_amd64_1cce6cb8fb27a94d\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    0xfffff802ed27a658 : 0xfffff802eb164398 : nt!PpmUpdatePerformanceFeedback+0x138
    0xfffff802ed27a668 : 0xfffff802eb164cac : nt!KeResumeClockTimerFromIdle+0xac
    0xfffff802ed27a678 : 0xfffff80afff08865 : amdppm!ReadGenAddr+0x21
    0xfffff802ed27a6a8 : 0xfffff802eb1645e0 : nt!KeAccumulateTicks+0x30
    0xfffff802ed27a6d8 : 0xfffff80afff074f0 : amdppm!AcpiCStateIdleExecute+0x20
    0xfffff802ed27a848 : 0xfffff802eb0ae004 : nt!EtwpLogKernelEvent+0x344
    0xfffff802ed27a8c8 : 0xfffff802eb133129 : nt!KiGetNextTimerExpirationDueTime+0x101
    0xfffff802ed27a8d8 : 0xfffff80afff07466 : amdppm!AcpiCStateIdlePrepare+0x26
    0xfffff802ed27a908 : 0xfffff802eb16535f : nt!PpmIdlePrepare+0x43f
    0xfffff802ed27aa08 : 0xfffff802eb1724b5 : nt!KiTransitionSchedulingGroupGeneration+0x105
    0xfffff802ed27aa30 : 0xfffff802eb4b4380 : nt!KiInitialThread
    0xfffff802ed27aa40 : 0xfffff802eb4b4380 : nt!KiInitialThread
    0xfffff802ed27aa58 : 0xfffff802eb1606f1 : nt!KiRetireDpcList+0x171
    0xfffff802ed27aa70 : 0xfffff802eb4b4380 : nt!KiInitialThread
    0xfffff802ed27aa78 : 0xfffff802eb16fccd : nt!KiStartThreadCycleAccumulation+0x6d
    0xfffff802ed27aa90 : 0xfffff802eb4b4380 : nt!KiInitialThread
    0xfffff802ed27aa98 : 0xfffff802eb01f356 : hal!HalPerformEndOfInterrupt+0x16
    0xfffff802ed27aaa8 : 0xfffff802eb1721eb : nt!KiGroupSchedulingGenerationEnd+0xab
    0xfffff802ed27aaf8 : 0xfffff802eb1628f0 : nt!PoIdle+0x340
    0xfffff802ed27ac58 : 0xfffff802eb213dcc : nt!KiIdleLoop+0x2c
    0xfffff802ed27ac70 : 0xfffff802eb4b4380 : nt!KiInitialThread
    You could try reverting to an earlier graphics driver or seeing if there have been any recent updates.
    The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
      My ComputersSystem Spec

  3. Posts : 57
    Windows 10 Home (64-bit)
    Thread Starter
       31 Mar 2018 #3

    Unfortunately I have tried that numerous times already, not fixing the BSODs.

    I indeed had an NVIDIA driver error message popping up twice in Windows' Reliability Monitor. But even then BSODs remained to happen without always giving that error.

    For the moment, I have disconnected the USB 2.0/SD card header from the motherboard, disconnected the secondary HDD and downgraded the AsRock's bios from 4.40 to 3.00 and no more BSODs for a whole week so far. However I wouldn't get my hopes up just yet.

    Still, I don't understand what the problem is with the SD card reader, as I described. It occured after on of the BSODs, having me believe it is related.
      My ComputerSystem Spec

  4. Posts : 57
    Windows 10 Home (64-bit)
    Thread Starter
       01 Apr 2018 #4

    I've found 2 older minidumps from March 18th, maybe you could find more info in these?
    Numerous BSODS all referring to ntoskrnl.exe Attached Files
      My ComputerSystem Spec

  5. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       05 Apr 2018 #5

    Sonar637 said: View Post
    I've found 2 older minidumps from March 18th, maybe you could find more info in these?
    I could not find anything conclusive from these dumps. Now that you have reverted to an earlier BIOS I would monitor for a while.

    The SD card reader issue is odd - has it happened again?
      My ComputersSystem Spec


Related Threads
Numerous BSODs while playing various games in BSOD Crashes and Debugging
Hi all, I have been encountering numerous BSODs of different bug check strings since 30th Aug (last Wed). I noticed that the BSODs happen whenever I'm in any game, from Just Cause 3 to Euro Truck Simulator 2. The BSOD would occur after 30mins - 1...
I realise the title isn't greatly descriptive but that's because nearly every BSOD I get is a new one so trying to pinpoint a particular bugcheck seems like a wasted effort. For clarity, my specs are as follows: OS: Windows 10 Home 64 Bit CPU:...
BSODs during general use, numerous error codes in BSOD Crashes and Debugging
Been randomly getting BSODs on Windows 10 for a while, and I haven't been able to determine the source, mainly because I've been getting such a range of different stop codes. My PC will also occasionally restart itself or completely freeze. I'm...
Greetings TenForums, I have had this Dell XPS 13 2015, running Windows 10 Home (10586) to my dismay, in my possession since June 2016. I've been using it as a "back up", but i'm eventually looking to sell it. However, it appears it may be a bad...
Solved Random bsods - ntoskrnl.exe in BSOD Crashes and Debugging
Hey there, this my first time here. And sorry if BSOD of this type already have already been fixed. These bsods started appearing out of nowhere. I have no idea what is the cause. They usually appear when I am playing games or watching youtube...
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 18:08.
Find Us