Jump to content

Multiple BSOD for multiple reasons

sambouchard
Go to solution Solved by sambouchard,

Finally, after 3 months, I've found what the problem was, I had not one, but two bad RAM stick from the RMA, so i guess that I will RMA it again!

So I am posting here since It's been 3 days since I am working on this issue. I am having BSOD after BSOD after BSOD, here are the code of my bsod(s):

-SYSTEM_SERVICE_EXCEPTION
-MEMORY_MANAGEMENT
-KMODE_EXCEPTION_NOT_HANDLED

Here are my specs:

-CPU : AMD Ryzen 5 2600 6 cores
-RAM: 16 GB Corsair vengeance 2400 mHz (DISCLAIMER : these are brand new, i had one dead stick so I RMAed it to corsair and they sent me a new kit about a week ago)
-GPU : Sapphire Nitro+ Radeon Rx 580 4Gb
-Mobo : MSI B450I Gaming Plus AC mini ATX
-PSU : SeaSonic M12II 520 Bronze Evo Edition
-SSD(on wich the os is installed) : SAMSUNg SSD 850 evo 120 Gb
-Hdd (On wich i installed games to test) : Western Digital Blue 1 TB

Every part is less than 10 months old( invoice to prove it)from a very good and trustable friend, I immediatly noticed that a ram stick was dead. I than used the PC for a whole week on 1 ram stick without any kind of problem than i RMAed it. Ever since, i constantly get BSOD for multiple reason mainly while playing games. Here s is what i tried:

-Switching Graphics card
-Reinstalling OS
-Updated Bios
-Only using 1 RAM stick on either of the slots
-Reinstalled OS again
-Memcheck
-Chkdsk(Altough in the log files it is said to have found corrupt files)

Also when i run sfc /scannow , it says that it found corrupt files but that it couldnt fix them. Here are the module that caused the BSOD:
 

I am going to be honest, i tried to copy the OS from my old cpu to my new with a free online tool (before completely wiping and reinstalling) since the os on the new PC wouldnt even boot(this was after the 1 week prior to the RMA just before RMAing the RAM)


Any help would be immensely appreciated

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, sambouchard said:

I am 99% sure that these are linked to unstable overclocks. If I were to have my CPU Overclocked at around 5/5.1 GHZ regardless on temps I will still ocasionally BSOD with the System Service Exception message.

About Memory management I would suggest turning XMP off, or on if its off. Otherwise I dont know too much, and I would contact to try and RMA your mobo

idk tbh

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Greenish said:

I am 99% sure that these are linked to unstable overclocks. If I were to have my CPU Overclocked at around 5/5.1 GHZ regardless on temps I will still ocasionally BSOD with the System Service Exception message.

About Memory management I would suggest turning XMP off, or on if its off. Otherwise I dont know too much, and I would contact to try and RMA your mobo

All my components(CPU, GPU, and RAM) are running at base clock. RMAing another part will be tricky since I'm not the original buyer

Link to comment
Share on other sites

Link to post
Share on other sites

I was having this exact issue. I was getting the same blue screens and am actually also using a 2600. It seems to have been fixed by running DISM.exe /Online /Cleanup-image /Restorehealth and then booting into safe mode and running sfc /scannow. Instead of failing it finally said it found corrupt files and was able to fix them and I haven't had another crash yet.

Link to comment
Share on other sites

Link to post
Share on other sites

7 minutes ago, Random_User said:

I was having this exact issue. I was getting the same blue screens and am actually also using a 2600. It seems to have been fixed by running DISM.exe /Online /Cleanup-image /Restorehealth and then booting into safe mode and running sfc /scannow. Instead of failing it finally said it found corrupt files and was able to fix them and I haven't had another crash yet.

I changed My SSD to another HDD and reran sfc /scannow and it didn't find any corruption but i still had a BSOD with the new hard drive. I will still try your solution tonight and will post the update, many thanks!

Link to comment
Share on other sites

Link to post
Share on other sites

30 minutes ago, sambouchard said:

I changed My SSD to another HDD and reran sfc /scannow and it didn't find any corruption but i still had a BSOD with the new hard drive. I will still try your solution tonight and will post the update, many thanks!

Scratch that. Just crashed again actually :(

Link to comment
Share on other sites

Link to post
Share on other sites

8 minutes ago, Random_User said:

Scratch that. Just crashed again actually :(

I will do multiple test and troubleshooting tonight and will give you the update. Have you tried with a differenct CPU?

Link to comment
Share on other sites

Link to post
Share on other sites

So I finally found what the problem was (well I am 95% sure) I did memtest86 on both stick of ram, 1 stick at a time in each slot, one stick Showed 0 error on both test, the other one showed 188 errors and over 1000+ errors, I am almost sure that I have yet again a bad RAM stick. I am going to rma it once again but is there anyway to make sure that my MOBO isnt killing my RAM since its the second RAM stick that I have to send back?

Link to comment
Share on other sites

Link to post
Share on other sites

On 8/2/2019 at 8:17 AM, sambouchard said:

So I finally found what the problem was (well I am 95% sure) I did memtest86 on both stick of ram, 1 stick at a time in each slot, one stick Showed 0 error on both test, the other one showed 188 errors and over 1000+ errors, I am almost sure that I have yet again a bad RAM stick. I am going to rma it once again but is there anyway to make sure that my MOBO isnt killing my RAM since its the second RAM stick that I have to send back?

Wow, I hadn't seen this comment but I was coming back to this thread to let you know the same exact thing. Ran memtest on both sticks of RAM and one was bad (it actually had so many errors that the test had to stop before completing). I've been using just the one stick while I wait for a replacement and I haven't had any more blue screens. Were both of your sticks of RAM that were bad the same model?

Link to comment
Share on other sites

Link to post
Share on other sites

20 hours ago, Random_User said:

Wow, I hadn't seen this comment but I was coming back to this thread to let you know the same exact thing. Ran memtest on both sticks of RAM and one was bad (it actually had so many errors that the test had to stop before completing). I've been using just the one stick while I wait for a replacement and I haven't had any more blue screens. Were both of your sticks of RAM that were bad the same model?

Yup I had two corsair stick, one was bad, RMAed it one time, than again, I still have one bad stick, but my problems are far from gone lol. I dont get blue screen anymore but I still have some Game Crashes where my display disconnect and the game quit. I tried alot of things to no avail. I supsect my motherboard to be at fault.. but then again, i dont have a spare to test it :( Ive asked the questions on another forum https://forums.tomshardware.com/threads/multiple-bsod-with-different-code-windows-10.3506835/ and im still looking for a solution.

 

 

I suspect three things from most likely to less likely: 

  1. I indeed have a faulty mobo, wich might explain why it "killed" two RAM stick
  2. It could be a windows problem so I am going to install a full fledged distros of Linux and make some test on it , but this is highly unlikeable
  3. Agaisnt all oddds, my CPU is at fault, wich is more than unlikely but in the states of things right now, I cant ignore that possibility

 

 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

  • 1 month later...

Wll I rmaed my motherboard, now I have the AMDKMDAP driver that keeps crashing randomly(more often when I am gaming) and the screen going black for a couple second before turning on again.

Link to comment
Share on other sites

Link to post
Share on other sites

Finally, after 3 months, I've found what the problem was, I had not one, but two bad RAM stick from the RMA, so i guess that I will RMA it again!

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×