Question Various random BSODs throughout the day

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
May 12, 2021
24
1
15
0
can you list your parts again and show whats new/old
NEW:
CPU (Ryzen 5 3600)
RAM (G.SKILL Ripjaws V Series 2x8GB)
Motherboard (ASUS ROG STRIX B450-F)

OLD:
PSU (Corsair CXM 750W)
GPU (EVGA GTX 1070 SC ACX 3.0 Black Edition)
Case (some thermaltake one)
Harddrives (a bunch of different ones)

If you getting bsod before you replaced parts and still are, maybe its something you didn't replace.
I can't remember the frequency of crashes but it definitely wasn't consistent enough for me to be concerned or even take note of it to be honest. That being said it very well could be one of the old parts, I don't know.
 

Colif

Win 10 Master
Moderator
what are the drives?
what makes? Most of the makers have tools we can use to check them out

GPU - only real tests for them are benchmarks like furmark & Heaven, and then you just run them to see if you bsod. Other test is use it in another pc. But not sure if they look like gpu errors.

PSU is pretty difficult. How old is it?
3 ways to test PSU, but one just tests to see if it works, and we know it does
multimeter, which is best way as you can test under load
or in the BIOS to check the +3.3V, +5V, and +12V. - https://www.lifewire.com/power-supply-voltage-tolerances-2624583

PSU is like motherboard, best test is use another and see if it still happens.
Since you replaced mb and it still happens, we can sort of guess its not cause.

If everything checks out and you down to psu, I would get PC tested by a repair store as I don't like guessing hardware.

I doubt its the case.

any forgotten USB devices? WIFI card? just check :)
 

gardenman

Dignified
Moderator
I think both of these are new. I don't see a VERIFIER error, and we usually do when verifier actually works right.

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/2wmv3pe4/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:051621-21625-01.dmp (May 16 2021 - 19:55:53)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: nvsphelper64.exe)
Uptime:0 Day(s), 4 Hour(s), 46 Min(s), and 36 Sec(s)

File information:051421-8593-01.dmp (May 14 2021 - 14:09:18)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 2 Hour(s), 30 Min(s), and 48 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.
 
May 12, 2021
24
1
15
0
For my drives, I have Team L5 LITE SSD as my boot drive, a Kingston SSD that I used to have as my boot drive but decided to switch it to the Team one as it has more storage, 2x WD Blue 1TB, and 1x WD Blue 2TB.

I don't have any wifi cards, all I have connected to usb are my headphones, keyboard, mouse, and the odd charger when I need it.

I remember having shadowplay as the victim of a previous crash a while ago. This would be the second one. Not sure if it's because of the GPU or not.

I'll update the BIOS right now to the latest one and hope I don't get the weird stuttery performance like last time. I'll let you know if it improves anything.

On a different note, I let DV run overnight and once again when I tried to wake my monitors I couldn't. So I did the same thing as last time and forced a restart and another dump file generated. I can't tell whether DV caught a driver or not. Here's the link: http://www.filedropper.com/verifierdump2
 

gardenman

Dignified
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/ehmx3yvb/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:051721-17500-01.dmp (May 17 2021 - 04:39:04)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 7 Hour(s), 42 Min(s), and 35 Sec(s)

Comment: It doesn't look like a VERIFIER crash. Here's a list of VERIFIER bugchecks that I know of.

There could be new ones that I'm not aware of yet listed here.

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
dpc - deferred procedure call - In its simplest form, it is the part of your Windows system that handles driver efficiency. If there is a driver that is taking longer than normal to process, it may prevent other drivers from being processed in time.

DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED - looks to me like it just never responded ... what ever "it" was . I have asked GM about something in report, see what he says.
 

gardenman

Dignified
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/ot3r6wns/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:051921-9031-01.dmp (May 19 2021 - 06:15:22)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:memory_corruption (Process: nvcontainer.exe)
Uptime:1 Day(s), 16 Hour(s), 35 Min(s), and 08 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.
 

Colif

Win 10 Master
Moderator
victim blame - well, its part of nvidia again

actual crash mentions ndu.sys. its the Network Data Usage Monitoring so actual cause could be network drivers

Shadow play crash on 16th could be network drivers too.

Jun 15 2020e1r68x64.sysIntel(R) Gigabit Adapter driver https://downloadcenter.intel.com/

so I have same lan drivers as you do. based on date of your drivers. Currently using them, always do.

curious, what am I missing here?

I missed this bit - Team L5 LITE SSD as my boot drive, a Kingston SSD that I used to have as my boot drive but decided to switch it to the Team one as it has more storage, 2x WD Blue 1TB, and 1x WD Blue 2TB.

i don't think the Teamgroup software is very helpful but, its here under ssd tool - https://www.teamgroupinc.com/en/support/download.php
Kingston - https://www.kingston.com/en/support/technical/ssdmanager
use this on wd drives - https://support.wdc.com/downloads.aspx?lang=en&p=279
 
Last edited:
May 12, 2021
24
1
15
0
Would reverting the network drivers to a previous version fix anything?

As for the harddrives, I will run each software in a bit and let you know the results.
 

Colif

Win 10 Master
Moderator
i don't think its the LAN drivers. I mean, the last one shows outgoing network activity while using nvcontainer which is: This nvcontainer.exe process is receiving or sending data on the LAN (your local network) or on the Internet.

so I may not be sure but the signs look that way

Reason I question drivers as cause as I have the same ones. I am using them right now, I always use Ethernet... so it makes me ¿ whether it is them or not. Same drivers should work on both pc, I mean... yes, there are differences between parts but its not a problem driver... something else is at play

test ssd, if its going to be any of them its the boot drive mostly likely.
 
May 12, 2021
24
1
15
0
Tested the boot SSD and it says it's 100% healthy. I might just reinstall it back to the old SSD to see if that changes anything, but since the crashes were happening before I switched the boot drive I'm not sure how much it will help.

Over the past 2 days had 2 more crashes randomly. Not sure if they will say anything new or not.
http://www.filedropper.com/newminidumps4
 

gardenman

Dignified
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/o8zv2kfL/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:052121-8812-01.dmp (May 21 2021 - 14:07:43)
Bugcheck:APC_INDEX_MISMATCH (1)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:0 Day(s), 15 Hour(s), 54 Min(s), and 48 Sec(s)

File information:052021-9000-01.dmp (May 20 2021 - 22:12:26)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 16 Hour(s), 41 Min(s), and 00 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.
 

Colif

Win 10 Master
Moderator
Tested the boot SSD and it says it's 100% healthy. I might just reinstall it back to the old SSD to see if that changes anything, but since the crashes were happening before I switched the boot drive I'm not sure how much it will help.
okay, so that would lead me to believe your right, its not the drives.

OLD:
PSU (Corsair CXM 750W)
GPU (EVGA GTX 1070 SC ACX 3.0 Black Edition) - BSOD are circling the gpu but its not mentioned in top crash in above post
Case (some thermaltake one) - really unlikely to be case
Harddrives (a bunch of different ones)
how old is PSU? I can't see if I asked that already?

top crash looks like gpu without even looking at dump. dwm.exe is all I need.
 
May 12, 2021
24
1
15
0
PSU is the oldest part in the system being around 7 years old. Aren't crashes due to PSU failure usually very abrupt as the system has a power malfunction?

Also, had a weird BSOD last night. SYSTEM_PTE_MISUSE (da) A driver has corrupted system PTEs. Never seen this before and it seems to point to afd.sys, which is a network related driver. http://www.filedropper.com/newminidump5
 

gardenman

Dignified
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/Ln3eybo7/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:052121-8562-01.dmp (May 21 2021 - 22:24:56)
Bugcheck:SYSTEM_PTE_MISUSE (DA)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 8 Hour(s), 16 Min(s), and 45 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.
 

Colif

Win 10 Master
Moderator
PSU is the oldest part in the system being around 7 years old. Aren't crashes due to PSU failure usually very abrupt as the system has a power malfunction?
CXM 750 watt models have a 5 year warranty, so its possible its the PSU. PSU being source of power can cause bsod if the power supply isn't consistent. 7 years is about time I would consider a new PSU is needed. Sure, they can last forever, or go bang like a 6 year old one I had did. But if they only guarantee 5, and its 2 years past, it could be going bad.

We have tested everything else its likely to be. Only other thing is the case and its even less likely to cause bsod. I don't think I have seen it yet.

its bounced back to network again
crash mentions afd.sys - ancillary function driver for winsock (scary I don't need to look that up anymore) - used by windows to talk to network drivers.

normally if errors move around I blame ram but we tested that.
 

gardenman

Dignified
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/80o9fLzv/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:052821-8734-01.dmp (May 28 2021 - 02:43:57)
Bugcheck:DRIVER_OVERRAN_STACK_BUFFER (F7)
Probably caused by:memory_corruption (Process: httpd.exe)
Uptime:2 Day(s), 0 Hour(s), 36 Min(s), and 38 Sec(s)

File information:052621-8765-01.dmp (May 26 2021 - 02:06:53)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: Teams.exe)
Uptime:1 Day(s), 2 Hour(s), 02 Min(s), and 39 Sec(s)

File information:052521-8703-01.dmp (May 25 2021 - 00:03:46)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: qbittorrent.exe)
Uptime:0 Day(s), 23 Hour(s), 15 Min(s), and 28 Sec(s)

File information:052421-8890-01.dmp (May 24 2021 - 00:47:48)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:0 Day(s), 12 Hour(s), 12 Min(s), and 38 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.
 

Colif

Win 10 Master
Moderator
httpd.exe file is a software component of Apache HTTP Server by Apache Software Foundation. << victim of crash 1, just curious
Teams.exe is part of windows teams
qbittorrent.,. this mentions afd.sys in stack, ancilliary function driver for winsock

you know, even without looking at dumps it looks like... lan again. top 3 are all lan related applications, and afd was just a give away on crash 3.

4th is dwm.exe. I am pretty sure I have said what it does, its windows desktop manager, it sits between GPU and programs
you don't happen to play PUBG? (reminder to self why I asked this link
We going around in circles.

scratches head?

the system PTE Misuse error also mentions afd.sys

what vpn do you use? any updates?
Jan 14 2020tap-pia-0901.sysOpenVPN Private Internet Access driver
 
May 12, 2021
24
1
15
0
Haven't played PUBG in years, never had it installed on this Windows system.

For the vpn I use Private Internet Access. Would that somehow cause the crashes since it's network related? I have it up to date to the latest version.

I'm considering buying a new PSU since you mentioned it could be that. Would you think that's a good idea to try out?
 

Colif

Win 10 Master
Moderator
PSU is the oldest part in the system being around 7 years old
CXM 750 watt models have a 5 year warranty, so its possible its the PSU. PSU being source of power can cause bsod if the power supply isn't consistent. 7 years is about time I would consider a new PSU is needed. Sure, they can last forever, or go bang like a 6 year old one I had did. But if they only guarantee 5, and its 2 years past, it could be going bad.
Yes

Considering you tested everything else.

Other choice is get PC tested by a store and see if they can isolate the cause.
 
May 12, 2021
24
1
15
0
Got the new PSU plugged in and working, a few hours with no crash. Will post again if it decides to crash, and if it's smooth for a week then I can say problems solved.
 
Reactions: Colif

ASK THE COMMUNITY

TRENDING THREADS