Question Persistent BSODs for several months

Aug 5, 2020
29
1
35
0
Hey everyone, I've been having issues with BSOD's for several months now, I don't remember exactly when they started but probably sometime around March. My system is a weird Frankenstein of part sources, a parts list will be at the end of this post. After looking at posts on this forum and elsewhere for help for months, I've decided to start my own that way I can upload the minidumps. The crashes are pretty persistent, averaging every other day. Here's a list of what I've tried so far, in roughly chronological order:

Scanned HDD and SSD for errors, none found
Scanned Windows files for errors, none found
Reinstalled windows, keeping personal files and apps. Unfortunately this means everything except the past 2 minidumps have been lost. Many had the stopcode or bugcheck of 0x154, and other memory related codes
Scanned memory with memtest86 a total of 12 passes, and one pass with windows memory diagnostic, no errors found
I also ran BlueScreenView in hopes the minidumps would have a simple answer, but unfortunately both point to ntoskrnl.exe, and the same address, +3ddf40. I don't know how to better process the dumps, but am willing to do so if directed to information on how to do it. Many of these threads end with the user uploading the minidump for someone else to look at, with no explanation of how that is done.

If anyone has any advice or would like to see the dumps, I'll do the best I can to comply.

Specs:
CPU: i7-6700, no overclock
RAM: 16 GB (2x8GB) 2133MHz clock, no xmp, DDR4, corsair, SKU CMK16GX4M2Z2400C16
SSD: Kingston SA400S37480G
HDD: ST2000DM008-2FR102, ST2000DM001-1ER164, WDC WD7501AAES-60Z2A0
GPU: EVGA GeForce GTX 1660 XC, RMA'd once
Mobo: Gigabyte GA-H110-D3A, latest BIOS
PSU: Seasonic 620 Watts

Thank you for any and all help.
 
Aug 5, 2020
29
1
35
0
In the meantime another crash happened, this time code ef but the same driver and address.

OCCT shows all below 40c, nothing abnormal. most temps around 30c.

That's a nice program, thanks for telling me about it!
 

Colif

Win 10 Master
Moderator
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Aug 5, 2020
29
1
35
0
Alrighty that's done, I guess I'll just wait for the next crash now.

I already have minidumps in that directory, but they're around 1 MB in size so I assume there are multiple kinds of minidumps. I'll send the file when it crashes again.

Are there any security considerations when uploading a dump?
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://pastebin.com/ahqSFyFj
File information:080520-11500-01.dmp (Aug 5 2020 - 15:39:14)
Bugcheck:MEMORY_MANAGEMENT (1A)
Driver warnings:*** WARNING: Unable to verify timestamp for ntoskrnl.exee
Probably caused by:ntoskrnl.exe (Process: https://www.google.com/search?q=)
Uptime:0 Day(s), 3 Hour(s), 53 Min(s), and 35 Sec(s)

File information:080520-11281-01.dmp (Aug 5 2020 - 21:25:35)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Driver warnings:*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Probably caused by:memory_corruption (Process: https://www.google.com/search?q=)
Uptime:0 Day(s), 5 Hour(s), 45 Min(s), and 44 Sec(s)

File information:080220-10078-01.dmp (Aug 2 2020 - 13:58:08)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Driver warnings:*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Probably caused by:memory_corruption (Process: https://www.google.com/search?q=)
Uptime:0 Day(s), 0 Hour(s), 55 Min(s), and 43 Sec(s)
Possible Motherboard page: https://www.gigabyte.com/Motherboard/GA-H110-D3A-rev-10#kf
You have the latest BIOS already install, version F25.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
WARNING: Unable to verify timestamp for ntoskrnl.exe
NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications.

Win32 0n2 = file not found... I suspect if ntsokrnl wasn't there, you wouldn't be in windows.

It is normally just the victim but you have 3 BSOD all saying its likely cause.

right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

Strange that Google search is what is crashing...

Have you run the intel processor diagnostic tool? Only as this file is old and I am curious which of the programs it might be part of
May 01 2013 - WinRing0x64.sys - Intel Processor Diagnostic Tool or BatteryCare by OpenLibSys.org or Throttlestop (Properties say: OpenLibSys.org) or EVGA Precision X https://www.evga.com/

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

maybe try updating lan drivers - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software
 
Aug 5, 2020
29
1
35
0
Okay, thanks for the suggestions, I'll go through them as I have time. Another crash happened, so I updated the drive folder with it.

I'll run SFC again, hopefully it shows something this time.

I keep chrome running on my pc almost the entire time that its on so it certainly has the opportunity to crash, but it is strange.

Not sure what you're asking with the intel processor diagnostic, I do have EVGA precision X1, are you saying I should run the processor diagnostic?

In my original post I said that I had already run memtest86 for 12 passes total, but I'll redo it with one at a time. What CPU selection should I use?

I'll update the LAN drivers too.

Thank you!
 

Colif

Win 10 Master
Moderator
Oh, so its an error caused by program used to display the conversion, not the actuial result... makes more sense now.

I could guess it probably blames system in all 3 anyway as it was ntoskrnl crashing, unless that is also a bug?

don't run memtest, i missed it in op.
Not sure what you're asking with the intel processor diagnostic, I do have EVGA precision X1, are you saying I should run the processor diagnostic?
I was just wondering if you had any of it on there. If you use one of the programs, its okay. I just looked at driver list to see age of drivers running.
 

gardenman

Admirable
Moderator
Please always put new dumps into a new folder. Otherwise I have to go back and check which ones I have looked at and which ones I have not. I think I found the right file this time (took a guess based on filename). Results: https://pastebin.com/NCjq6Yds

@Colif, test this out: https://jsfiddle.net/u9t8pyb4/show
Click on Run this Fiddle. Thanks to @PC Tailor

File information:080920-12453-01.dmp (Aug 9 2020 - 03:04:52)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:ntoskrnl.exe (Process: ?)
Uptime:1 Day(s), 19 Hour(s), 58 Min(s), and 57 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Last edited:

Colif

Win 10 Master
Moderator
OLD_IMAGE_ntoskrnl.exe << is the OLD IMAge thing also an error in the converter (sorry, converter doesn't normally cause errors)

error not telling me anything really.
The store in question is the memory store, its used by windows to manage virtual memory. Normally these errors show more of what was occuring in background but this one is not telling me anything.

Tempted to get you to remove Norton as it would reduce driver traffic by half and might let us narrow down on the cause.
Oldest drivers are Occulus ones. Age doesn't always mean they are cause though.. just looking :)
 

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/e6cqswv7/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:081620-12453-01.dmp (Aug 16 2020 - 22:05:26)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:ntoskrnl.exe (Process: ?)
Uptime:0 Day(s), 8 Hour(s), 29 Min(s), and 53 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

gardenman

Admirable
Moderator
I have a custom program that I created. It takes the info from the debugger and formats it into an easier readable version, assigns driver descriptions and other stuff. It then gives the output both plain text and HTML formats. Fiddle is just a new place that we can post it. I prefer to post the HTML version but many of the sites where I normally post the files have went down. JSFiddle is a new one (even though I'm not happy with it). We are considering building our own site and working on it as we speak but no definite plans on it yet.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/o359bfm2/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:081720-12453-01.dmp (Aug 17 2020 - 08:05:52)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:0 Day(s), 9 Hour(s), 56 Min(s), and 10 Sec(s)
This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

ASK THE COMMUNITY