BSOD and Red Screen (no text for red screen, but both have buzzing).

[Jake_36]

System:
Windows 10
FX 6350 (4.3ghz with noctua nh-14u fan)
radeon pulse rx 580 8gb
asus m5a78l-m motherboard (added small heatsinks to vrm mosfets)
corsair gold 650w psu
kingston ssd (120gb for OS)
two terabyte and one terabyte hard drives both from western digital.

Problem:
I have have had 4 or so crashes over the past two days. I believe two have been bsods, and two have been blank red screens (completely blank red screen with no text). Both have buzzing audio. The errors given in the logs of the latest blue screen were:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x0000000000000004, 0x00000000000000fb, 0x0000000000000001, 0xffffa50411d641c8). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e7762901-24d1-4575-97c9-0db0b660ce93.

and

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

(the second one was shown four times).

I have benchmarked both my CPU and GPU for over half an hour sessions (even though the crashes seem completely random as they even happen when just browsing and not playing games) with valley, heaven, intelburntest, and prime95 - it doesnt crash.

Any help would be appreciated. Thank you.

 

[Colif]

Can you follow option one 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 cloud server and share the link here and someone with right software to read them will help you fix it

red screens of death are GPU errors.

 

[Jake_36]

Thanks for the reply, ill give that ago. However, in regards to the red screen, should i be concerned for my gpu itself or could this just be a driver issue as iv only had the red screen when playing pubg and tabbing out to do something else.

 

[Colif]

RSOD can be caused by drivers so try this - http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

The BSOD is a bad pool caller, could be caused by GPU drivers as well.

 

[johnbl]

something overwrote another drivers data and caused the second driver to crash.

Pool is just a section of memory that windows gives to a device driver so it can store its data. when it is done the device driver gives it back to windows and windows recycles it and gives it to the next device driver that needs to store something. Pool corruption happens when a driver stores something in a pool block it has already give back to windows, or if one driver overwrites its block and into another block.

these are hard to find, sometimes looking at the mindump for old drivers will help but often you have to run verifier to force windows to bugcheck at the time of corruption so the name of the bad driver can be found.
Otherwise windows can bugcheck later when the second driver uses the corrupted data.


a general fix for a bugcheck is to update the BIOS and motherboard drivers from the motherboard vendors website.

otherwise, you would want to change the memory dump type to kernel (from minidump) turn on verifier functions and provide a kernel memory dump so it can be looked at with a windows debugger.

even the minidump can help since old drivers can be detected or often drivers will corrupt their own data and will point to the correct driver name that needs to be updated or removed.

 

[adityagiri657]

http://www.resplendence.com/whocrashed_os

You can try this to find out any drivers causing the BSODs. I had BSODs on my laptop ran WhoCrashed and found out my sound drivers causing it. Updated them, running fine for a year now.
Adi.

 

[Colif]

I find who crashed is good to show you what crashed but not often why. Its a start, its better than nothing, but 50% of time it blames ntoskrnl which might have been what crashed but doesn't explain what crashed it.

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

I used to suggest it but learned it was better to get the dumps if there are people like John around who can read them without assistance

@ op, if you follow Johns suggestion about driver verifer, see my notes below -

driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again.

Also helps to run system restore before hand to create a restore pointp to roll back to if necessary.

Download the Windows 10 media creation tool and use it to make a win 10 installer on USB
Once it bsod, upload the minidump file and we see what it shows us.

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC

 

[adityagiri657]

Interesting. Thank you for the knowledge Colif!

 

[Jake_36]

Alright the solution to the crashes seemed to be the drivers as you suggested by colif, however, even though i havent had any crashes, all my games have also become unplayable. I used to get mainly 60frames on pubg, rise of the tomb raider, and doom. Now however, they are all playing (stuttering), at around 40-50frames. My userbenchmark results have also gone down pretty badly:
Old: http://www.userbenchmark.com/UserRun/6400735
New: http://www.userbenchmark.com/UserRun/7943228

 

[Jake_36]

I should probably add to this, Idk if this is the cause but, before all this happened I had a problem where the computer would randomly blackscreen and restart. I found that the cause of this problem was that the reset button on my case was automatically sending a signal button every day or so. To solve this (which it does seem to have) I removed the wire that goes from the case front panel to my motherboard. Every problem I have had with my PC came a day after I did this.

 

[Colif]

I would run driver verifer as suggested but first change the memory dump type as suggested by john.
Go here: https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html#Part1
follow the steps and then do the Kernel Memory Dumps step so it creates the type John was after. Run verifer after taking note of what i said before.

Until we can see an actual dump we are just guessing

that creates a Memory.dmp file in c windows after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here. John hopefully read it for you.

 

[Jake_36]

Alright I'm gonna give Colif the solution because my question about crashes was solved by him (drivers). However what made my games run well again was turning off radeon relive and allowing my less than top of the line ssd to relax a bit. Thanks again to everyone for the help.