Question BSoD Issue - Attempted to write to read only memory.

MentalThinking

Distinguished
Sep 6, 2014
34
0
18,530
Hello -

For the last few weeks, I have had intermittent BSoD issues, always with the same stop code. I have run the suggested memory test on the Microsoft page related to this error and it says there's no issue with my RAM. I have also gone through the device manager and checked all drivers - all of which are up to date, including of course my graphics driver.

Using BlueScreenView is not helpful to me, as it only points towards ntoskrnl. So, I am here, asking the experts before I pull out my hair and reinstall windows. Linked below are two minidump files. Oddly, the latest minidump files refuse to upload, but the state of my computer was essentially the same in every single situation.

During each BSoD, I am playing a game via Steam, with a browser window open and perhaps Overwolf (a gaming overlay software).

Minidump 12/16/24
Minidump 12/17/24

Edit:
Computer Type: PC/Desktop
System Manufacturer/Model Number: Custom
OS: Windows 10 version is 22H2 (OS Build 19045.5247)
CPU: AMD Rayzen 5 7600 3.8GHz
Motherboard: Gigabyte B650M AORUS ELITE AX
Memory: G.SKILL Ripjaws S5 32GB (2x16GB)
Graphics Card: GeForce RTX 4070 WindForce 3 OC 12GB
PSU: Corsair RMx Series RM750x 80+ Gold Modular Power Supply 750W
SSD: Solidigm 670p QLC NAND PCIe 3.0 x4 NMVe m.2 2TB

All items in my PC are new, and were purchased in May of '23. The total used space on my SSD is 248GB.


Regards,

MT
 
Last edited:
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used).

Disk drive(s): make, model, capacity, how full?

Look in (as a starting point) Reliability History/Monitor for error codes, warnings, and even informational events be captured just before or at the time of the BSoDs. Click entries as applicable to obtain more details. The details may or may not be helpful.

Run "dism" and "sfc /scannow" to find and fix possibly corrupted files.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161
 
Ralston18 -

Thank you for your reply. I have updated my original post with the specified information. I did look through those files before posting, but was unable to find anything that seemed anomalous or problematic - certainly nothing that trumpets 'this is the problem, fix this.'. In fairness, I am not an IT professional, so it's possible I overlooked something.

I will run the commands you suggested.

Edit: I have run both the sfc and DISM commands as outlined in the links provided, and both came back clean and error free.

Regards,

MT
 
Last edited: