Question Plagued by BSODs

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Colif

Win 10 Master
Moderator
everytime its a new error... that is why everytime i look at thread I think, did he check ram.. we have and storage.

Yes, we trying to fix BSOD but it keeps bouncing around and not blaming a driver. Or showing a pattern. Often if the BSOD is something different everyday I go looking at a hardware cause as ram (for instance) will cause a different error in a different driver, almost everytime. Bad sectors on drives can do same...

what is a full list of parts you have?

Is it normal for the cause of BSODs to be so well-hidden? I don't know how many more methods I have left to identify what the problem is with my PC.
unfortunately, yes. Its very rare for the actual BSOD to come out and say what driver caused the crash, most of time the BSOD shows what crashed, not underlying causes.

Try the 2nd post here, I don't recommend it right away as it can cause a boot loop. Its part of windows designed to test drivers, so if the cause is a driver, it will show us - https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/
 

badsoup

Reputable
May 15, 2016
34
0
4,530
0
I'm noticing my wifi card failing lately. The computer has sudden freezes and I get disconnected from the wifi. I have to go in device manager and disable and renable the network adapter for my card to connect to the internet. what on earth is going on.
 

badsoup

Reputable
May 15, 2016
34
0
4,530
0
everytime its a new error... that is why everytime i look at thread I think, did he check ram.. we have and storage.

Yes, we trying to fix BSOD but it keeps bouncing around and not blaming a driver. Or showing a pattern. Often if the BSOD is something different everyday I go looking at a hardware cause as ram (for instance) will cause a different error in a different driver, almost everytime. Bad sectors on drives can do same...

what is a full list of parts you have?


unfortunately, yes. Its very rare for the actual BSOD to come out and say what driver caused the crash, most of time the BSOD shows what crashed, not underlying causes.

Try the 2nd post here, I don't recommend it right away as it can cause a boot loop. Its part of windows designed to test drivers, so if the cause is a driver, it will show us - https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/
Sorry, I've been busy.

Parts:

CPU: Intel Core i5 4460 @ 3.20GHz
RAM: RipjawsX Series 16GB PC3-12800 Dual Channel DDR3 Kit 1600 MHz
Motherboard: Gigabyte Technology Co., Ltd. H97-D3H
GPU: MSI VGA Graphic Cards RX 580 ARMOR 8G OC
Power Supply: EVGA 500B 500W
Wifi Card: ASUS PCE-AC55BBT dual band wireless-AC1200

I'm gonna have to buy an Ethernet cable. When I do, I'll remove my wifi card and test it out. Onedrive is now demanding my phone number to keep using its service too lol.
 

Colif

Win 10 Master
Moderator
Onedrive is now demanding my phone number to keep using its service too lol.
that is just rude... wonder when I get asked? Maybe it knows it already, probably linked it some time in the past.

I been busy too and sidetracked to point I will have to get back to this post once you checked the wifi angle out.
 

badsoup

Reputable
May 15, 2016
34
0
4,530
0
that is just rude... wonder when I get asked? Maybe it knows it already, probably linked it some time in the past.

I been busy too and sidetracked to point I will have to get back to this post once you checked the wifi angle out.
Oh nvm. I got away with just giving another email address.

So I removed my wifi card and plugged in the ethernet and got another BSOD. Link: https://1drv.ms/u/s!Am9WlWp_gAG9d-pBL8pmvf4HN-s?e=6sow1B

Do you want me to try the thing that might cause boot loops now?
 

gardenman

Admirable
Herald
I ran the dump file through the debugger and got the following information: https://chariestgeinus.htmlpasta.com/

File information:020720-34218-01.dmp (Feb 7 2020 - 14:47:05)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:dxgmms2.sys (Process: System)
Uptime:0 Day(s), 23 Hour(s), 59 Min(s), and 52 Sec(s)

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

Colif

Win 10 Master
Moderator
dxgmms2.sys = DirectX. 9 out of 10 times I see this crash its Nvidia drivers. Or should I say DIsplay drivers, since you have a Radeon (almost makes a nice change) . As soon as I saw that it was directx in GM's spoiler I just checked driver list...

dump text shows it was display drivers, it doesn't mention them by name but its obvious
ffff95820a6ca430 fffff8075493d2f9 : ffffce05b528fba0 000000000e880000 0000000000000000 000000000f1f8000 : dxgmms2!VIDMM_LINEAR_POOL::AllocateBlock+0x111
ffff95820a6ca460 fffff8075493d1a4 : ffffce05b528fba0 ffff95820a6ca530 ffffe38aed1ae558 0000000000000001 : dxgmms2!VIDMM_LINEAR_POOL::SplitBlock+0x71
ffff95820a6ca4b0 fffff8075493cf02 : ffffe38adeefddf0 0000000000000000 ffffce05a9731dd0 0000000c00000108 : dxgmms2!VIDMM_LINEAR_POOL::Allocate+0x12c
ffff95820a6ca560 fffff8075493cb8e : 0000000000000000 0000000000001000 ffffe38adeefddf0 0000000000000001 : dxgmms2!VIDMM_SEGMENT::ReserveResource+0x312
ffff95820a6ca620 fffff8075492c3da : 0000000000000000 0000000000000000 0000000000000000 ffffe38aeae45670 : dxgmms2!VIDMM_MEMORY_SEGMENT::ReserveResource+0x3e
ffff95820a6ca670 fffff8075492c6a2 : ffffce05a9731dd0 fffff80756239c1d ffffe38a00000000 ffffce0500000001 : dxgmms2!VIDMM_GLOBAL::AcquireGPUResourcesFromPreferredSegmentSet+0x12a
ffff95820a6ca6f0 fffff8075492c900 : ffffe38ae738b010 ffffe38aebf36000 0000000000000000 0000000000000000 : dxgmms2!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x56
ffff95820a6ca740 fffff8075491d2d6 : 0000000000000000 ffffe38aebf3fc10 ffff958200000000 ffffe38ae738b010 : dxgmms2!VIDMM_GLOBAL::pageInOneAllocation+0x150
ffff95820a6ca850 fffff8075491d1be : ffffe38ae738b010 0000000000000002 0000000000000000 fffff807562886d6 : dxgmms2!VIDMM_GLOBAL::pageInFaultedAllocation+0xb6
ffff95820a6ca8b0 fffff8075491d3a4 : ffffe38aebf36000 ffff95820a6cabf8 ffffe38ae27f3401 ffff95820a6cabf8 : dxgmms2!VIDMM_GLOBAL::pageInDeviceInternal+0x18a
ffff95820a6ca930 fffff8075493c267 : ffff95820a6caa68 ffff95820a6cabf8 0000000000000000 ffffce05b03fb190 : dxgmms2!VIDMM_GLOBAL::TryPageInDevice+0x50
ffff95820a6ca970 fffff80754948678 : 000000000000000c ffff95820a6caae0 fffff807549020e4 ffffe38aebf3fc48 : dxgmms2!VIDMM_DEVICE::Resume+0x73
ffff95820a6ca9e0 fffff80754946ee9 : ffffce05b03fb110 ffff9781d8cd1101 ffffe38ae45ea601 0000000000000100 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1778
ffff95820a6cabe0 fffff8075632a7a5 : ffffe38ae45ea680 fffff80754946ee0 ffffce05b03fb110 00002425bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9

normal answer is to run ddu and reinstall GPU drivers. Either from AMD or via running windows update - https://forums.tomshardware.com/faq/how-to-perform-a-clean-install-of-your-video-card-drivers.2402269/
 

ASK THE COMMUNITY

TRENDING THREADS