When the computer is in the initialization process, for Windows 2000,2008, Vista and Windows 7, and 8 sudden closure "attempt to write to read-only memory" error Blue Screen of Death (BSOD) may occur. Computer suddenly shut down due to being classified by the driver attempted to write to read-only memory segment. PC Auto Shutdown enforced to protect the system from data loss.
In most cases, this blue screen error is caused by faulty memory hardware by a faulty device driver or hardware failure, sometimes. Incorrect operating conditions such as high memory and overclocking frequency settings may cause this error.
Some users have reported that Windows blue screen error is also known as "ATTEMPTED_WRITE_TO_READONLY_MEMORY" and "Stop 0x000000BE" of this error, it is usually the system initialization process appears on the screen:
Attempt to write to read-only memory
To solve the "attempt to write to read-only memory" blue screen error, check whether the system is overclocked. You can disable all overclocking or use based on specified by CPU, GPU manufacturers and other equipment installed clock frequency lower setting.
To determine if the problem is due to a blue screen memory problems, Windows 7 provides a memory diagnostic tool can be used. To do this, click the Start button, type in the search window memory. From the search results, click Windows Memory Diagnostic Tool, and then click the option to restart and check for problems. The computer will automatically restart to check for memory problems, all you need to do is follow the instructions on the screen to operate.
You can also use the Last Known Good Configuration feature that allows you to set up and configure the latest efforts to start the computer to solve this problem. To do this, you must restart your computer, press the F8 key when the character-based menu options displayed on the screen, and then click the Windows Advanced Options. Use the arrow keys to highlight Last Known Good Configuration, and then press Enter. This process will undo the blue screen error registry and driver changes may cause.
0 komentar