New Windows install BSODing

[Aleksa Djordjic]

Hi, so in short.

Built a new PC, installed everything I needed and got a BSOD...
Specifically I was getting (and still am) KERNEL_SECURITY_CHECK_FAILURE and SYSTEM_SERVICE_EXCEPTION

Was debugging a bit, and from what I could found, that would be because of faulty drivers.
So after trying bunch of stuff, I gave up and reinstalled windows. This time letting it install all the drivers it thinks it needs and not touching anything other than installing Discord and launching Steam to play games.

Same thing, crash... same errors...

 

Reinstalled windows again, this time updated AMD drivers to the latest... crash... same errors...

 

I don't know how to debug this, where to go off from what I currently have or how to read these minidump files

https://drive.google.com/file/d/1CLyW5PKNVU6_N4n3IkEjoD-CV6rrRWVM/view?usp=sharing

Oh and this doesn't want to finish for some reason...

 

What could be the problem, and how can I debug it to fix this?

How to find which driver is faulty, if its even a driver and what are my possible solutions to fix this?
I'm completely clueless...

These BSODs seem to happen at random each couple of minutes, haven't been able to find a link as to when the happen but just now, twice in a row I was streaming a game in Discord and when a friend joined, 5 seconds later it would come up with KERNEL_SECURITY_CHECK_FAILURE

If needed, I didn't build a new PC from the ground up, just replaced some old parts for new ones.
Got a 5900x, x570 Tomahawk and 32GB of Trident Z 3200mhz, CL16
Rest is the same as my old PC which was working fine.
Haven't done a memory diagnosis yet, will do that later if it helps.

[fuzz0r]

Run a memtest on your RAM to make sure they're not faulty.

[Aleksa Djordjic]

13 minutes ago, fuzz0r said:

Run a memtest on your RAM to make sure they're not faulty.

Trying the built in Windows Memory Diagnosis right now, will take a while

 

Edit:

Well this popped up

[fuzz0r]

You might need to RMA the memory.

[Aleksa Djordjic]

4 minutes ago, fuzz0r said:

You might need to RMA the memory.

How can I be 100% sure its the memory though.
Fyi: Still doing the test, almost 50% done

[fuzz0r]

1 minute ago, Aleksa Djordjic said:

How can I be 100% sure its the memory though.
Fyi: Still doing the test, almost 50% done

Run this one afterwards: https://www.memtest86.com/

[Mark Kaine]

27 minutes ago, Aleksa Djordjic said:

How can I be 100% sure its the memory though.
Fyi: Still doing the test, almost 50% done

no you can't, unless you test it, but it definitely looks like it could be. 

 

PRO tip: don't leave your computer check this screen for the results... because in my experience this will not whatsoever display any error logs after its done... 

 

(had this one too once, I did start it manually however... my ram isn't faulty... but yours might, who knows) 

 

PS: for me it was a windows "bug" resolved by simply reverting an update with my backup (the windows internal revert update function will *not* fix these issues typically) running fine since then... win 10 1809 (the best version™) 

 

51 minutes ago, Aleksa Djordjic said:

 

 

Is this windows XP? It's been a while, still looks great though! 

 

Spoiler

 

 

PS: I really hope it's your RAM, otherwise this'll be a pain to troubleshoot... 

[Aleksa Djordjic]

2 minutes ago, Mark Kaine said:

no you can't but it definitely looks like it could be. 

 

PRO tip: don't leave your computer check this screen for the results... because in my experience this will not whatsoever display any error logs after its done... 

 

(had this one too once, I did start it manually however... my ram isn't faulty... but yours might, who knows) 

 

PS: for me it was a windows "bug" resolved by simply reverting an update with my backup (the windows internal revert update function will *not* fix these issues typically) running fine since then... win 10 1809 (the best version™) 

 

Is this windows XP? It's been a while, still looks great though! 

 

  Reveal hidden contents

 

 

PS: I really hope it's your RAM, otherwise this'll be a pain to troubleshoot... 

Its Windows 10, just how those UIs look.
RAM might be the hardest thing for me to replace right now... this one was barely available and it will take days or even weeks for the new one...

Its 32gb, 2 sticks so I hope its only one stick and I can keep using the other one for now, 16gb is enough for games, but won't be able to do some other stuff.

[Mark Kaine]

3 minutes ago, Aleksa Djordjic said:

Its 32gb, 2 sticks so I hope its only one stick and I can keep using the other one for now, 16gb is enough for games

True, if it's just one stick you can use the other... although typically if you RMA they will require both sticks... 

 

I just meant easiest to troubleshoot, not necessarily to replace, sorry, I know it can suck trying to get new parts currently... prices seem to keep going up too!  o.o

[Aleksa Djordjic]

5 minutes ago, Mark Kaine said:

True, if it's just one stick you can use the other... although typically if you RMA they will require both sticks... 

 

I just meant easiest to troubleshoot, not necessarily to replace, sorry, I know it can suck trying to get new parts currently... prices seem to keep going up too!  o.o

Yeah, I know, I just want to be able to use the PC until the postal service arrives to pick them up.
And ummm...

 

Well great...

Enough info, won't do the memtest86.
Will try sticks one by one to see which one is faulty... hopefuly its not both

[Aleksa Djordjic]

1 hour ago, fuzz0r said:

Run a memtest on your RAM to make sure they're not faulty.

Well turns out one of the sticks is faulty.

Tested the first 16gb stick, crash after 5 minutes

Tested the other one... well running it for the past 35min playing games and nothing, looks like it works fine

Will have to send it back and get a new kit...
Thanks for helping out!

[Mark Kaine]

usually if you run memtest and it's faulty it should be quick to detect it... so if it finds something stop and try the other right away