Question Relentless ATTEMPTED_WRITE_TO_READONLY_MEMORY bluescreens after Windows reinstall

Toggle sidebar Toggle sidebar
F

finn183

Reputable
Jan 18, 2017
62
2
4,535
I currently have a Ryzen 3 2200G as the CPU and the Asrock AB350M-HDV as the mobo.
After updating my BIOS to the latest version (includes support for Zen 2) my Windows installation suddenly stopped working, sending me to the Recovery menu every time. I've noticed that the SSD partition (which is also the boot partition) is suddenly placed under the 2 hard drive partitions (so instead of the boot drive being labeled C:\, it's E;\ instead). After a long time of trying to find out the cause, I gave in and reinstalled Windows (to build 1903; for some reason the old installation [build 1803] just refuses to update outright).
Then not long after reinstallation I was bombarded with relentless freezes and bluescreens (6 unique BSODs at one point.) After installing drivers, the number of bluescreens has since reduced to just ATTEMPTED_WRITE (along with a few others here and there).
The system seems to crash seemingly at random (sometimes within a minute of rebooting from a bluescreen, other times several hours). That said a crash seems more likely if I access the system drive (such as opening Event Viewer or using a browser installed on C:\)
Here are the minidumps for the last 5 bluescreens. If MEMORY.DMP is requested I'll gladly provide that as well.
Before you ask, SFC, CHKDSK, DISM and resetting the PC didn't help. Memtest86 came out fine. Any other suggestions will be gladly accepted.
 
Sort by date Sort by votes
Hello my friend!

I have ran 3 of the 5 dumps and you can view the full reports here:

Report 1 (Oldest DMP): https://pste.eu/p/MU6v.html
Report 2 (Middle DMP): https://pste.eu/p/emN5.html
Report 3 (Most Recent DMP): https://pste.eu/p/Hhvb.html

Summary of findings
Report 1:
BugCheck BE, {ffffa60033068d10, 8a00000000200121, ffffe607d32301a0, a}
Probably caused by : memory_corruption ( nt!MiRaisedIrqlFault+12a61d )

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffa60033068d10, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: ffffe607d32301a0, (reserved)
Arg4: 000000000000000a, (reserved)

PROCESS_NAME: ravenfield.exe
MODULE_NAME: nt
IMAGE_NAME: memory_corruption

Report 2:
BugCheck BE, {ffffa300344a9e50, 8a00000000200121, ffffe586b28301a0, a}
Probably caused by : memory_corruption ( nt!MiRaisedIrqlFault+12a61d )

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffa300344a9e50, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: ffffe586b28301a0, (reserved)
Arg4: 000000000000000a, (reserved)

PROCESS_NAME: ravenfield.exe
MODULE_NAME: nt
IMAGE_NAME: memory_corruption

Report 3:
BugCheck 139, {4, ffffd6818b0d7ff0, ffffd6818b0d7f48, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000004, The thread's stack pointer was outside the legal stack
extents for the thread.
Arg2: ffffd6818b0d7ff0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd6818b0d7f48, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

PROCESS_NAME: System
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
Click to expand...

Typically the BSOD here are driver related or RAM related. And you often had the same drivers running, and they were minimal, so there is every likelihood it could be hardware. Some things to consider:
  • Do you have latest BIOS installed?
  • Do you have latest MB / Chipset drivers installed?
  • Are you running an overclock anywhere? Have you reset BIOS first?
  • Have you recently installed any hardware or software?
  • I couldn't deduce your SYSINFO, could you share your full system spec and also confirm that your RAM modules came from the same pack?
  • Have you run virus scans?
  • Hvae you checked the integrity of your storage drive?
 
Upvote 0 Downvote
PC Tailor said:
Hello my friend!

I have ran 3 of the 5 dumps and you can view the full reports here:

Report 1 (Oldest DMP): https://pste.eu/p/MU6v.html
Report 2 (Middle DMP): https://pste.eu/p/emN5.html
Report 3 (Most Recent DMP): https://pste.eu/p/Hhvb.html

Summary of findings


Typically the BSOD here are driver related or RAM related. And you often had the same drivers running, and they were minimal, so there is every likelihood it could be hardware. Some things to consider:
  • Do you have latest BIOS installed?
  • Do you have latest MB / Chipset drivers installed?
  • Are you running an overclock anywhere? Have you reset BIOS first?
  • Have you recently installed any hardware or software?
  • I couldn't deduce your SYSINFO, could you share your full system spec and also confirm that your RAM modules came from the same pack?
  • Have you run virus scans?
  • Hvae you checked the integrity of your storage drive?
Click to expand...
BIOS update is latest version.
Chipset drivers are latest.
Everything is at stock clocks.
The only recent hardware installation is the SSD a month ago.
No viruses were found.
SMART status is still fine.
Full specs: Ryzen 3 2200G/AB350M-HDV/ADATA XPG Z1 8GB 2400MHz/Gigabyte Windforce GTX 1060 3GB
 
Upvote 0 Downvote
PC Tailor said:
I would be tempted to look at this first then, SMART status is an indicator, but not a guarantee.
Do you have another storage drive you can try?

Are your RAM modules from the same pack (if you have more than 1?).
Do you only encounter the BSOD when you attempt an OS install?
Click to expand...
I only have 1 stick of RAM and no spare hard drive.
I did encounter a BSOD when I attempted an install but reformatted and tried again.
 
Upvote 0 Downvote
magically you don't appear to have any LAN drivers, it should have realtek but the only realtek drivers running are HD Audio. Latest on Asrock site are from 2019/4/12

apart from AMD all in one driver you have already, there aren't many drivers to download for the motherboard (since all in one has many)
 
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
PC Tailor said:
Are you able to verify if the BSOD still occurs in safe mode?
Is it a legit version of Windows?
So the BSOD can be random anytime you are in windows?
Did the problems occur before the reinstall?
Click to expand...
the issue only popped up when I reinstalled Windows. And it seems like the bluescreen still pops up in Safe Mode, yes.
And yes, it's very random with no specific pattern (if you can call it a pattern then it often happens when I click on something or waiting for something to load.)
 
Upvote 0 Downvote
Try running memtest86 on your ram stick, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

most times ram is more random and doesn't blame same process for 2 errors in a row, Top 2 happened while you played a Beta game (which are not the most stable things on earth) but as you got a 3rd, something is at fault. Do you have any extra devices attached to PC?
 
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
Colif said:
Try running memtest86 on your ram stick, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

most times ram is more random and doesn't blame same process for 2 errors in a row, Top 2 happened while you played a Beta game (which are not the most stable things on earth) but as you got a 3rd, something is at fault. Do you have any extra devices attached to PC?
Click to expand...
Yeah I might just try a higher pass count if I havr time and no, I don't have another stick, just 1. I don't have any other devices either, maybe just the headset (that plugs in through USB) and my gamepad.
 
Upvote 0 Downvote
Colif said:
Try running memtest86 on your ram stick, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

most times ram is more random and doesn't blame same process for 2 errors in a row, Top 2 happened while you played a Beta game (which are not the most stable things on earth) but as you got a 3rd, something is at fault. Do you have any extra devices attached to PC?
Click to expand...
Update; I ran 8 passes overnight and it turned up 1 error in test 8, pass 7/8. What's the best course of action now?
 
Upvote 0 Downvote
finn183 said:
Update; I ran 8 passes overnight and it turned up 1 error in test 8, pass 7/8. What's the best course of action now?
Click to expand...
Replace the RAM.
A memtest with even 1 error is memory that needs replacing unfortunately.
There's a conception that only 1 error is OK, because it can't be that bad, which is incorrect. 1 error means the RAM is not functioning correctly, and therefore best course of action is to replace the RAM.

Doesn't guarantee a fix to your problem, but it's highly likely. So you'll need to eradicate the RAM being the issue. But I highly suspect it is what is causing the problem.

Colif said:
Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Click to expand...
 
Upvote 0 Downvote
PC Tailor said:
Replace the RAM.
A memtest with even 1 error is memory that needs replacing unfortunately.
There's a conception that only 1 error is OK, because it can't be that bad, which is incorrect. 1 error means the RAM is not functioning correctly, and therefore best course of action is to replace the RAM.

Doesn't guarantee a fix to your problem, but it's highly likely. So you'll need to eradicate the RAM being the issue. But I highly suspect it is what is causing the problem.
Click to expand...
Alright, I have since RMA'd the RAM stick. Hope it solves the issue.
 
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
PC Tailor said:
Replace the RAM.
A memtest with even 1 error is memory that needs replacing unfortunately.
There's a conception that only 1 error is OK, because it can't be that bad, which is incorrect. 1 error means the RAM is not functioning correctly, and therefore best course of action is to replace the RAM.

Doesn't guarantee a fix to your problem, but it's highly likely. So you'll need to eradicate the RAM being the issue. But I highly suspect it is what is causing the problem.
Click to expand...
UPDATE: Alright, it has been a while but I finally got my RAM back.
...Turns out that solved nothing and I still get the same BSOD, no changes. What now?
 
Upvote 0 Downvote
Have you set PC up for minidumps?
Can you give us any new ones you have so we can look, I get another guy to make a conversion as well, might see more

can you right click start
choose disk management
expand the window so you can see all the columns
take a screenshot, upload to an image sharing website and show a link here. Just curious what that looks like after reading your 1st post again.

unlikely to be cause of a BSOD though.
 
Upvote 0 Downvote
Colif said:
Have you set PC up for minidumps?
Can you give us any new ones you have so we can look, I get another guy to make a conversion as well, might see more

can you right click start
choose disk management
expand the window so you can see all the columns
take a screenshot, upload to an image sharing website and show a link here. Just curious what that looks like after reading your 1st post again.

unlikely to be cause of a BSOD though.
Click to expand...
Link to minidump (new one + 4 old ones for comparison). Doubt it'll help since the BSOD seems the exact same.

Compare Diskpart and This PC from inside Windows to what's seen when I open them with CMD inside preboot environment. It's odd.
 
Last edited:
Upvote 0 Downvote
you should have taken old hdd out when you installed win 10 last time, your actual boot partition is the 99mb EFI partition on the hdd, that could well slow your boot speed down a little - the partition marked SYSTEM in the CMD window. WIn 10 has a habit of trying to be helpful, it would have seen the old boot partition and just added itself to it.

the partition marked Boot is just where windows itself is (obvious) but the bios will be getting instructions on where to boot from by looking at the efi partition on hdd


tWvTCUx.png
 
Last edited:
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
Colif said:
you should have taken old hdd out when you installed win 10 last time, your actual boot partition is the 99mb EFI partition on the hdd, that could well slow your boot speed down a little - the partition marked SYSTEM in the CMD window. WIn 10 has a habit of trying to be helpful, it would have seen the old boot partition and just added itself to it.

I don't get how C is showing as 519gb total space when the ssd itself is only 223gb (the shots are all your pc, right?)
8J7deC1.jpg


tWvTCUx.png


Something's not right there?
Click to expand...
Exactly, because for some reason in the PE the 2 hard drive partitions are put above the SSD partition. No clue why.
Also of note is that for another odd reason Wjndows refused to reinstall until I plugged the hard drive back in.
 
Upvote 0 Downvote
Colif said:
which disk comes 1st is determined by where they attached on motherboard, its why hdd is still disk 0, and above the ssd in CMD

in top shot its showing D as C drive, ssd showing as E, thats what confused me.
Click to expand...
Yeah. Odd how that happens because again, Windows is showing the correct order just fine.
 
Upvote 0 Downvote
What I suggest is this.
copy anything you want to keep onto HDD
unplug PC from power
unplug hdd & ssd.
plug ssd into data cable hdd had before (this will fix the disk drive order)
leave hdd unplugged
reinstall win 10 on ssd - fresh install may also remove BSOD problem since it only started after the install

once win 10 boots fine by itself, reattach hdd and go into BIOS and make sure hdd not listed in boot order
hopefully bsod problem goes away
 
Last edited:
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/Ptyi.html
File information:080319-7718-01.dmp (Aug 3 2019 - 05:57:13)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process: Illustrator.exe)
Uptime:0 Day(s), 0 Hour(s), 55 Min(s), and 05 Sec(s)

File information:080319-11515-01.dmp (Jul 27 2019 - 23:12:11)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 38 Min(s), and 43 Sec(s)

File information:072819-7781-01.dmp (Jul 27 2019 - 15:10:39)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: Spotify.exe)
Uptime:0 Day(s), 0 Hour(s), 08 Min(s), and 38 Sec(s)

File information:072819-7671-01.dmp (Jul 27 2019 - 15:30:46)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process: MsMpEng.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 09 Sec(s)

File information:072819-7437-01.dmp (Jul 27 2019 - 15:01:26)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 2 Hour(s), 13 Min(s), and 29 Sec(s)
Possible Motherboard page: https://www.asrock.com/mb/AMD/AB350M-HDV/index.asp
It appears you have the latest BIOS installed.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
ooops, i forgot to send a message saying he is probably formatting PC so dumps not exactly helpful.

based on dumps, I still would have updated LAN drivers. Installed were
Aug 28 2018 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom