Windows 10: 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.

Notes:
- 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)

:)

 

keep getting BSOD when playing CSGO with skype running in the background.

Original title: BSOD confusion

I keep getting BSOD when playing CSGO with skype running in the background. After numerous runs of driver verifier it has left me confused, each mini dump says it is a different driver however blue screen viewer says its ntoskrnl.exe everytime (ive read
about this being a memory error however i ran memtestfor close to 22 hours and no errors occured.

 

ntoskrnl.exe driver causing numerous BSOD's

I understand. Without verifier running all we can tell is that there is memory corruption going on. I would do one last thing before considering wiping and re-installing. I would run a system file check. If there are no violations found you might want
to start thinking about a re-install

Please run a system file check (SFC) & DISM if you are on win 8 or higher



All instructions are in our Wiki article below...

Should you have any questions please ask us.


System file check (SFC) Scan and Repair System Files

 

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.

Code: 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[/quote] 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.

 

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.

 

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?