New Windows 10 update causing BSoD

[MistahHaskins]

As the title states, I have had BSoD before but those were because of an unstable XMP profile (2600x running 3200mhz RAM) which I left stock 2133mhz until I later upgraded to the 5600x.

 

Now I got a random blue-screen with the error code: ATTEMPTED_WRITE_TO_READONLY_MEMORY

I have the Dump files zipped and one OneDrive if anyone needs it to scan it or something along those lines.

 

Like I have said, this is the first and I found another post on TomsHardware relating to this same issue which was posted today. I am leaning more to a Windows error more than hardware error

[191x7]

Latest BIOS?

[TetraSky]

I got the latest windows 10 update and no error on my side.

 

That said, If your RAM is/was causing BSOD when using XMP... The likely culprit... Is the RAM. Because it shouldn't be doing that. It's rated by the manufacturer to reach these speeds and if it doesn't, it's faulty. Either that or the motherboard (doubt it's the cpu's memory controller since this was happening on your 2600x too)

2 minutes ago, 191x7 said:

Latest BIOS?

Probably considering they got a 5600x and the latest bios update B450 got were to add support for those.

[MistahHaskins]

 

10 minutes ago, TetraSky said:

I got the latest windows 10 update and no error on my side.

 

That said, If your RAM is/was causing BSOD when using XMP... The likely culprit... Is the RAM. Because it shouldn't be doing that. It's rated by the manufacturer to reach these speeds and if it doesn't, it's faulty. Either that or the motherboard (doubt it's the cpu's memory controller since this was happening on your 2600x too)

Probably considering they got a 5600x and the latest bios update B450 got were to add support for those.

Could this be due to the GPU running out of VRAM? I noticed that when it happened I was closing Siege, which without me noticing changed all the settings to max. It was about 400MB over the 4GB this card has to operate with.

 

I never had this problem until now. I doubt it's the motherboard as the 2600x doesn't support 3200mhz RAM speeds but the 5600x does. My board, according to Gigabyte, can operate and run speeds up to 3600mhz so the board isn't the culprit. I knew the 2600x wouldn't like 3200mhz but I tried it anyways getting the result I knew I would get.

 

But this scenario is different because I have been using the system for little over an hour and half without any noticeable issues SINCE the BSoD. Which for me is weird because if it was RAM and especially it being faulty this would've happened sooner.  In fact, I doubt the system would post if this was the case.

[LogicalDrm]

-> Moved to Troubleshooting

[TetraSky]

9 hours ago, MistahHaskins said:

Which for me is weird because if it was RAM and especially it being faulty this would've happened sooner.  In fact, I doubt the system would post if this was the case.

RAM issues can be a mindfck to deal with like that. It doesn't always break down immediately. You could be using it for days, weeks, without issues and then BSOD. That's often why we see people coming here asking why their system is "suddenly unstable" with their overclock when it was fine for so long... But if it crashes once, then it ain't stable now is it.
 

9 hours ago, MistahHaskins said:

Could this be due to the GPU running out of VRAM? I noticed that when it happened I was closing Siege, which without me noticing changed all the settings to max. It was about 400MB over the 4GB this card has to operate with.

Doubt it, if anything it would just make things slower while gaming, normally, as it would need to put the extra stuff into the RAM and Pagefile. Unless the BSOD happened while/right after, playing Siege.

 

 

All that said, if it only happened once... Pray it doesn't happen again and was just a 1 off thing due to windows being crap as usual.
If it does happen again, do go ahead and post the both minidumps so we can see what exactly failed (save your current one until then, so we can compare them and see if the issue was caused by the same thing). If the minidump analysis doesn't result in one particular thing causing it, then you will need to do all the typical troubleshooting steps... Which are long and you can't use the PC during that time, you could be 2 days with no PC while running memtest, hours with prime/ooct/furmark... All to test each components.