Question BSOD a - Then motherboard not detecting memory

[Chrisvro]

So i was playing Palworld when i randomly got a BSOD (code a). My system restarted, but then failed to reboot and gave a check CPU mobo error. I then reset the system, then i started getting a memory not detected error on my mobo. Upon seeing this, i tried to reset it again, but this didn't work. I then reset the CMOS, which to my surprise did not fix my issue. I did this twice. I then took out the RAM sticks from slots A1 and B1, reset the CMOS again, and then it decided to post. So removing those 2 sticks fixed the issue. I have yet to switch the 2 sticks I didn't remove with the ones I did to see if maybe one of those sticks was the culprit. I have attatched a link to the dump file that was created. I'm not the best at reading and understanding dump files so I was hoping someone who is confident could check it out. Normally if i were to get this type of crash with this code, I would brush it off as a driver issue and go about my day. But it's the fact that my motherboard failed to detect my memory afterwards that is concerning me.

I am going to now (tomorrow):

try the other 2 sticks i removed and see if i get the same memory not detected error.
If i do, then i know one of those sticks is the culprit.
If not, I will then try all 4 sticks again. If I then get the error again, then I'll guess the issue is most likely deeper within.
I will also swap the sticks to different slots to see if a DIMM slot could be the cause (unlikely)

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

Specs:
Mobo: ROG Maximus XIII Extreme Glacial
RAM: Adata XPG Spectrix 32GB (4x8gb)
CPU: I9 10850K
GPU: RTX 3090
PSU: Superflower Leadex Titanium 1600w

 

[LukeHjo]

The system encountered a Blue Screen of Death with the error code IRQL_NOT_LESS_OR_EQUAL. The crash occurred in the context of the svchost.exe process. There appears to be an issue with the Bluetooth driver as well. It tried to access [rax+10h], which is fffffffffffff010. This crash could've just been a trigger to existing issues.

Faulty Memory Controller, Overheating, Power Surges or Fluctuations, Inadequate Power Supply, Faulty DIMM Slots & the list goes on.

 

[Chrisvro]

The system encountered a Blue Screen of Death with the error code IRQL_NOT_LESS_OR_EQUAL. The crash occurred in the context of the svchost.exe process. There appears to be an issue with the Bluetooth driver as well. It tried to access [rax+10h], which is fffffffffffff010. This crash could've just been a trigger to existing issues.

Faulty Memory Controller, Overheating, Power Surges or Fluctuations, Inadequate Power Supply, Faulty DIMM Slots & the list goes on.

To be honest I’m more curious about the fact that my memory became undetectable after rebooting. I have had this issue before, and that was when I first built this rig. When I first installed the memory and powered on for a test, the memory was not detected (code 55) the same issue as tonight. I don’t remember how I fixed it, but obviously I did and had no issues afterwards. Obviously a variety of different issues could cause this, but I thought it was worth mentioning.

Also, regarding the “check CPU” error I initially got when it first tried to reboot, this is not the first time I have seen this either. Sometimes after having the PC unplugged for a few days then trying to boot it up, I would get this issue. At the end of the day, this issue is probably to do with the CPU initialisation. Again, a variety of issues could cause this, but it’s worth mentioning it’s not the first time I have seen it.

What I’m trying to say is… coincidence?

 

[Amdlova]

Clean the DIMM and try again search on youtube how to do that.

 

[LukeHjo]

To be honest I’m more curious about the fact that my memory became undetectable after rebooting. I have had this issue before, and that was when I first built this rig. When I first installed the memory and powered on for a test, the memory was not detected (code 55) the same issue as tonight. I don’t remember how I fixed it, but obviously I did and had no issues afterwards. Obviously a variety of different issues could cause this, but I thought it was worth mentioning.

Also, regarding the “check CPU” error I initially got when it first tried to reboot, this is not the first time I have seen this either. Sometimes after having the PC unplugged for a few days then trying to boot it up, I would get this issue. At the end of the day, this issue is probably to do with the CPU initialisation. Again, a variety of issues could cause this, but it’s worth mentioning it’s not the first time I have seen it.

What I’m trying to say is… coincidence?

As I said earlier, this could've been the trigger to a series of hardware events. Happened to me once.

 

[Chrisvro]

As I said earlier, this could've been the trigger to a series of hardware events. Happened to me once.

Just a little update: I figured out the culprit. One of my RAM sticks was the culprit. I tried every single stick singularly in slot B2, 3 out of the 4 sticks let it boot up fine, and the only one that caused the error was the exact one I thought was going to be the culprit: the one that was always right next to my CPU heatsink/waterblock. That RAM stick sits right next to the waterblock, practically touching it. The outside of the waterblock is metal and gets extremely hot to the touch. My CPU temps were very high at the time of the crash, so it’s pretty obvious that stick overheated and failed. My question is how do I prevent this from happening in the future when I get my new RAM? The design of the board makes it so the stick in A1 is so close to the monoblock, there is no way around this. The stick lasted nearly 2 years there before it failed. I don’t want to have to get new RAM every 2 years. Maybe my RAM is just cheap crap and has a bad heatsink? (It sure looks like it lol, the heatsink is plastic.)

So yes, I’m relieved I have now found the culprit and will be replacing my RAM. It’s really funny this happened because I was actually planning on upgrading my RAM in the next few weeks, now I definitely have an excuse to

 

[Bob.B]

Just a little update: I figured out the culprit. One of my RAM sticks was the culprit. I tried every single stick singularly in slot B2, 3 out of the 4 sticks let it boot up fine, and the only one that caused the error was the exact one I thought was going to be the culprit: the one that was always right next to my CPU heatsink/waterblock. That RAM stick sits right next to the waterblock, practically touching it. The outside of the waterblock is metal and gets extremely hot to the touch. My CPU temps were very high at the time of the crash, so it’s pretty obvious that stick overheated and failed. My question is how do I prevent this from happening in the future when I get my new RAM? The design of the board makes it so the stick in A1 is so close to the monoblock, there is no way around this. The stick lasted nearly 2 years there before it failed. I don’t want to have to get new RAM every 2 years. Maybe my RAM is just cheap crap and has a bad heatsink? (It sure looks like it lol, the heatsink is plastic.)

So yes, I’m relieved I have now found the culprit and will be replacing my RAM. It’s really funny this happened because I was actually planning on upgrading my RAM in the next few weeks, now I definitely have an excuse to

Get a 2x kit of the ram you want and use slots a2 and b2.