[SOLVED] Multiple BSOD with different codes each time

[iMurd]

For the past week I've had 9 BSOD and 7 of them are different codes. Today it seems to be repeating the same codes from last week. The only consistency about them is most are shortly after I wake my computer up. I'm on a pretty clean install of Windows 10 since I just upgraded my PC at the end of November.

The bugcheck codes I have gotten are in order: 0x00000050, 0x0000003b, 0x0000001a, 0x0000007e, 0x00000154, 0x0000001e, 0x000000be, 0x00000050, 0x0000003b, 0x0000007f

I've done the Windows Memory Diagnostic, ran memtest86 for 4 passes, reinstalled my graphics driver, lowered my virtual memory, and updated to the latest version of Windows 10.

My specs are:
GTX 1060 6GB
Ryzen 5 2600
G.Skill Aegis 16GB DDR4-3000 Memory
MSI B450-A Pro ATX AM4
And 2 SSDs- a Sandisk SSD Plus 1TB as the boot and Samsung 860 EVO as a secondary.

 

[cin19]

I just upgraded my PC at the end of November.

Did you get the new MB / CPU? Add the gtx1060?
Also what PSU did you have ?

 

[iMurd]

Did you get the new MB / CPU? Add the gtx1060?
Also what PSU did you have ?

Sorry I forgot to specify. The motherboard, CPU, RAM, and SSDs are all new. And my PSU is a CX750M which wasn't upgraded.

 

[cin19]

From these BSOD, some of them related to RAM, like 0x0000001a, 0x0000001e. And the 0x0000007e related to the SSD, you may use only one, like Samsung 860 EVO , and install the OS first, also the Samsung SSD software to check it to see the SSD is fine or not. Other, like 0x00000154, related to OS or the SSD.

Because you did run the Memtest86, but the RAM may still have the compatibility problem, consider to get the G.Skill FlareX ( for ryzen AM4), even in theory the G.Skill Aegis RAM should work with your AM4, you can check the G.Skill site for more info. And before you change the RAM, may try to lower the RAM speed to 2933MHZ, because the ryzen 5 2600 should work well the RAM at 2933mhz.

 

[iMurd]

From these BSOD, some of them related to RAM, like 0x0000001a, 0x0000001e. And the 0x0000007e related to the SSD, you may use only one, like Samsung 860 EVO , and install the OS first, also the Samsung SSD software to check it to see the SSD is fine or not. Other, like 0x00000154, related to OS or the SSD.

Because you did run the Memtest86, but the RAM may still have the compatibility problem, consider to get the G.Skill FlareX ( for ryzen AM4), even in theory the G.Skill Aegis RAM should work with your AM4, you can check the G.Skill site for more info. And before you change the RAM, may try to lower the RAM speed to 2933MHZ, because the ryzen 5 2600 should work well the RAM at 2933mhz.

Throwing in a new code I just got when I went to restart my computer: 0x0000007f. I got the Sandisk SSD dashboard to check the health since that's the drive with Windows 10 on it and it says it's fine. And would it be worth running memtest86 longer for more passes? Or if there was a problem would it come up with an error fast?

 

[Genralkidd]

I've been having a lot of BSOD's lately too and haven't been able to pinpoint the cause yet either. I'm curious though what usually happens shortly before you get a BSOD? Any strange occurrence? Also were you doing any specific tasks before the BSOD that has a high tendency to lead to a BSOD?

 

[iMurd]

I've been having a lot of BSOD's lately too and haven't been able to pinpoint the cause yet either. I'm curious though what usually happens shortly before you get a BSOD? Any strange occurrence? Also were you doing any specific tasks before the BSOD that has a high tendency to lead to a BSOD?

Mostly it's been after I wake up my computer. I've had it happen a few minutes after waking it in the morning or as soon as it wakes up. Only once has it been while I was in the middle of a game. But the latest one that just happened to me an hour ago was right as I went to restart it, instead of seeing the restarting now screen it was a BSOD. But other than that I haven't noticed anything strange happening right before it crashes.

 

[cin19]

Mostly it's been after I wake up my computer.

Consider to exchange the RAM or MB.

 

[Colif]

If you want to check what cause might be without replacing parts,

Can you follow option one on the following link - 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 file sharing web site, and share the link in your thread so we can help fix the problem

I've been having a lot of BSOD's lately too and haven't been able to pinpoint the cause yet either. I'm curious though what usually happens shortly before you get a BSOD? Any strange occurrence? Also were you doing any specific tasks before the BSOD that has a high tendency to lead to a BSOD?

did you make a thread about it?

 

[iMurd]

Ok I think I fixed it because I haven't gotten a blue screen in 3 days. I had to update BIOS since I found out the version I was on was from June 2018 and the newest version is from November 2019.