I get Attempted to Write to Read-Only Memory almost every time I use my computer (deleted)

Question

I get Attempted to Write to Read-Only Memory almost every time I use my computer (deleted)

Anonymous

* * Duplicate of: I get Attempted to Write to Read-Only Memory almost every time I use my computer ****

For some reason my post got deleted and I don't understand the reason behind it

https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/i-get-attempted-to-write-to-read-only-memory/3f8db31b-d5f3-4b77-bf5b-9b9ba9998f6f

I'm having serious problems with my Windows and I need to know what to do, unfortunately, I can't go to that post nor can I create a new one (I get an error)

would appreciate any help.

here is a link to my latest minidumb files

https://jumbomail.me/j/URFVl8j6TUSJ9bt

And following is my msinfo

OS Name Microsoft Windows 10 Pro

Version 10.0.19045 Build 19045

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name USER-PC

System Manufacturer Gigabyte Technology Co., Ltd.

System Model G1.Sniper 5

System Type x64-based PC

System SKU To be filled by O.E.M.

Processor Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. F10, 25.08.2014

SMBIOS Version 2.7

Embedded Controller Version 255.255

BIOS Mode Legacy

BaseBoard Manufacturer Gigabyte Technology Co., Ltd.

BaseBoard Product G1.Sniper 5

BaseBoard Version To be filled by O.E.M.

Platform Role Desktop

Secure Boot State Unsupported

PCR7 Configuration Binding Not Possible

Windows Directory C:\WINDOWS

System Directory C:\WINDOWS\system32

Boot Device \Device\HarddiskVolume3

Locale United States

Hardware Abstraction Layer Version = "10.0.19041.3636"

Installed Physical Memory (RAM) 16,0 GB

Total Physical Memory 15,9 GB

Available Physical Memory 7,43 GB

Total Virtual Memory 35,9 GB

Available Virtual Memory 22,6 GB

Page File Space 20,0 GB

Page File C:\pagefile.sys

Kernel DMA Protection Off

Virtualization-based security Not enabled

Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable

Hyper-V - VM Monitor Mode Extensions Yes

Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes

Hyper-V - Data Execution Protection Yes

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Answer 1

Three of the minidumps indicate that the crash was caused by "bflwfx64.sys" which is the Qualcomm Atheros network driver. Downloading and installing the latest version of the LAN driver from the Gigabyte website at this link should fix this problem.

https://download.gigabyte.com/FileList/Driver/m...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Answer 2

Anonymous

Yes, I've checked it again and now it works. Have no idea what the problem was. However I still have issues with my Windows and keep getting Attempted to Write to Read-Only Memory

0 comments

Answer 3

For some reason my post got deleted and I don't understand the reason behind it

https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/i-get-attempted-to-write-to-read-only-memory/3f8db31b-d5f3-4b77-bf5b-9b9ba9998f6f

<snip>

Evidently you used another profile - KonRud . - to create multiple same topic threads.

The one you mentioned, does not look deleted to me...

I get Attempted to Write to Read-Only Memory almost every time I use my computer Last reply 43 minutes ago](https://answers.microsoft.com/en-us/windows/forum/all/i-get-attempted-to-write-to-read-only-memory/3f8db31b-d5f3-4b77-bf5b-9b9ba9998f6f?LastReply=true#LastReply "answers.microsoft.com") by [KonRud . | Created 18 hours 21 minutes ago by KonRud .

Answer 4

Anonymous

Here are all of my minidump files for the month: https://jumbomail.me/j/8U6bJJ7pTkqqEy6Will it help?

0 comments

Answer 5

Hi, Rudnok. I'm Robinson, and I’m happy to help you today.

The minidumps indicate that the crash was caused by a driver issue, but could not identify which driver had caused the problem.

You can use the Driver Verifier to gather more information about which driver is causing the problem.

Step 1: Create a system restore point. in case anything goes wrong you will be able to restore your computer. You can see how to do it at this link.

https://support.microsoft.com/en-us/windows/cre...

Step 2: Enable the Diver Verifier

1-Right-click on Start then click on Windows Terminal (admin)

2-Type this command and press Enter:

Verifier

3-Select "Create custom settings (for code developers)" and click Next

4-In the "Select individual settings from a full list", select everything except "Low Resource Simulation", "and "Force Pending I/O Requests" and click Next

5-Select "Select driver names from a list" and click Next

6-Select everything except the driver provided by Microsoft and click on Finished

7-Reboot your computer and use it normally until your computer crashes again

8-Compact and share the new minidump

Step 3:Disable the Driver Verifier

1-Right-click on Start then click on Windows Terminal (admin)

2-Type this command and press Enter:

Verifier

3-Select "Delete existing settings" and click on Finish

Share via

I get Attempted to Write to Read-Only Memory almost every time I use my computer (deleted)

5 answers