Question Persistent BSODs for several months

[knotimpressed]

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.

 

[knotimpressed]

Update: removing the drive, removing the driver, and changing that setting did not stop the crashes.

 

[Colif]

Software problems tend to show their identity after a few weeks at most, hardware can hide for a lot longer. But after a few months of constant errors it becomes obvious something isn't right.

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

CPU - Can you run this? https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool
ram - passes memtest (not a 100% proof its not cause but usually pretty good)
SSD - Only software for Kingston is - https://www.kingston.com/en/support/technical/ssdmanager
I doubt it is caused by Hard drives but can run these on their associated drives
WD - https://support.wdc.com/downloads.aspx?p=3&lang=en

Seagate - https://www.seagate.com/au/en/support/downloads/seatools/seatools-win-master/

GPU unlikely to cause the kind of errors you are seeing.
Last 2 items hardest parts of PC to test.

 

[DarthLordZuko]

As I'm also having the same BSOD, here are my specs and the recent minidumps...
Processor AMD Ryzen 7 3700X 8-Core Processor, 3593 Mhz, 8 Core(s), 16 Logical Processor(s)
GPU - Nvidia GeForce RTX 2070 SUPER
Motherboard - Asus x570-P
RAM - 16GB x 4 DDR4-2666 (1333MHZ) SK Hynix

Checked ASUS website for driver updates, and updated to the most recent ones.
other than that I did a MemTest86 on the RAM came out good.
stress test on the GPU came out good.
checked temps - nothing out of the ordinary...

Can get BSOD when doing normal web surfing or playing video games... but it's always the same BSOD bug code...

Minidumps - Link

 

[knotimpressed]

Software problems tend to show their identity after a few weeks at most, hardware can hide for a lot longer. But after a few months of constant errors it becomes obvious something isn't right.




CPU - Can you run this? https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool
ram - passes memtest (not a 100% proof its not cause but usually pretty good)
SSD - Only software for Kingston is - https://www.kingston.com/en/support/technical/ssdmanager
I doubt it is caused by Hard drives but can run these on their associated drives
WD - https://support.wdc.com/downloads.aspx?p=3&lang=en

Seagate - https://www.seagate.com/au/en/support/downloads/seatools/seatools-win-master/

GPU unlikely to cause the kind of errors you are seeing.
Last 2 items hardest parts of PC to test.

Hey Colif, thanks for the response!

I’m AFK right now, I installed windows on a partition of a known good drive to see if the crashes persist, and am waiting on those results.

In terms of tests, I can certainly run those, however:

Removing the D drive from the system did not stop the bsods, so I do not think that drive is at fault. I have run seatools on the remaining two drives and both passed, as did HD Tune. I’m pretty sure I ran the Kingston utility before, but I can do it again to make sure.

I’m pretty sure it’s not the GPU either, I tested it when I got it back from RMA.

In terms of CPU, it’s passed both OCCTs test and prime95, I can run that too though when I get the chance. I’ll let you know how they go.

Edit: looks like the time is now, working on those tests as I type this. By the last two parts do you mean PSU and motherboard?

Man this sucks. IPDT shows a pass, and windows hasn't crashed in the last 16 hours against an average mean time between crashes of 10.5 hours. I'm debating hot swapping in my ssd so I can test it while keeping my uptime going for bsod testing, the power cable is already plugged in so I think I should be good to try it.

Edit: No hotswap luck. I'll have to restart my computer and turn on AHCI for the kingston utility too. Taking the crashes from the last week, the mean time between them is 10.5, a standard deviation is 3.5, so if I wait for 17.5 hours of runtime, that's 95% of the predicted dataset, and I'd call that good enough. I guess that means its either the C (SSD) drive, or a software issue.

Edit: Kingston Utility shows nothing helpful, no issues. I'll be running chkdsk on it tonight.

 

[knotimpressed]

I'm going to run chkdskin about an hour with the /b and /v flags on my ssd. Do those flags seem good to you? Should I make a backup of my info before scanning, or run it from safe mode?

 

[SAVAGER]

Update: removing the drive, removing the driver, and changing that setting did not stop the crashes.

Hi,
Sorry the flag switch didn’t resolve your problem.
Have you thought about using a Linux (Ubuntu) Live CD/USB bootable OS to eliminate any Microsoft anomaly and isolate hardware from software issues?
There are a number of ways that you can use Ubuntu to diagnose hardware problems.
Just boot off the Live CD, and start running some applications and test out all the hardware from a working Linux environment. If the system works fine in Linux, the problem is probably a Windows, virus, or driver issue.

 

[knotimpressed]

Hi,
Sorry the flag switch didn’t resolve your problem.
Have you thought about using a Linux (Ubuntu) Live CD/USB bootable OS to eliminate any Microsoft anomaly and isolate hardware from software issues?
There are a number of ways that you can use Ubuntu to diagnose hardware problems.
Just boot off the Live CD, and start running some applications and test out all the hardware from a working Linux environment. If the system works fine in Linux, the problem is probably a Windows, virus, or driver issue.

Yep, I've got lots of experience with ubuntu and linux in general, I have a dedicated small 160 gb hdd with ubuntu on it actually. However I dont have that much experience debugging hardware issues on linux, so while it is my backup option if my primary methods dont work, I'm going to stick to windows for now. All of my workflow is also in windows, so its nice to not have that impacted for days on end as I test.
Thank you though!