Instructions that appear when playing games.

Memory cannot be "read" or "written" Solution:

Some people will pop up an error message that the memory cannot be "read" when running the racing program. I hope the following article can help everyone.

People who use the Windows operating system sometimes encounter such an error message. When running some programs, sometimes there will be a memory error prompt, and then the program will automatically close or click Close, which will seriously lead to failure to close.

0x instruction refers to 0x memory. The memory cannot be read.

0x memory referenced by 0x instruction cannot be "written".

I wonder if you have ever seen such a fault. (The contents after 0x may be different. )

Generally speaking, this phenomenon has two aspects. First, there is something wrong with hardware, that is, memory. The second is software, which has many problems.

1, caused by Microsoft IE buffer overflow vulnerability.

2. The conflict in the use of memory or virtual memory address leads to the need to allocate a memory address for the operation of the program. When the program ends, it will free up space for the new program. Win is a multi-task system. Sometimes, how much memory or virtual memory do we need to ensure simultaneous tasks before the program ends and new tasks begin? Maybe win doesn't do a good job on this issue, so this error often occurs, which usually happens after running large-scale software or multimedia.

3. Inferior memory chips will also have this problem. Generally speaking, memory problems are unlikely. The main aspects are: the memory stick is broken, the memory quality is problematic, and there are two different brands of memory with different capacities, which is more likely to be incompatible. At the same time, we must pay attention to heat dissipation, especially after overclocking. You can use the software MemTest to check the memory, and you can thoroughly check the stability of the memory. This problem occurs if you have dual memory, and different brands of memory chips are mixed or you buy second-hand memory. At this time, you should check whether there is a memory problem or it is incompatible with other hardware.

4. Vulnerabilities in Microsoft Windows system. Windows specifies memory addresses 0X00000000 to 0X0000ffff as the address range for allocating null pointers. If a program tries to access this address, it is considered an error. Programs written by c/c++ usually do not carry out strict error checking. When malloc is used to allocate memory and there is not enough address space to allocate, a null pointer will be returned. However, the code does not check this error and thinks that the address allocation has been successful, so it accesses address 0X00000000, so a memory violation access occurs and the process terminates. When the pif file is filled with ascii characters, the following situations will occur: the illegal pif file (filled with ASCII characters \''x\'') must have at least 369 bytes before the system will think it is a legal pif file, and then it will be displayed as an icon of the pif, and then the program, font, memory, screen and other contents will appear in the properties. Moreover, only when the size of the non-pif file is 369 bytes, there will be no program error when viewing the "Program" page of the property, even if it is 370 bytes. When viewing the "Program" property page of an illegal pif file larger than 369 bytes, Explorer will give an error and prompt: \' * * * \' Memory referenced by the instruction. Unable to "read" memory. The problem lies in the hexadecimal addresses of 16 of the pif file: 0x00000181[0x87] 0x000000182 [0x001] and 0x00000236544. As long as the values of 0x00000 18 1 and 0x00000 182 are changed to [0xff], any change of other addresses will not cause an error.

5.apache service may not be completely installed and started correctly. Change OracleOraHomeXXHTTPServer in service to stop.

6. The application failed to check the memory allocation. When a program needs a piece of memory to save data, it needs to call the "function function" provided by the operating system to apply. If the memory allocation is successful, the function will return the address of the newly opened memory area to the application, and the application can use this memory through this address. This is "dynamic memory allocation", and the memory address is also a "pointer" in programming. Memory is not always available and inexhaustible, and sometimes memory allocation will fail. When the allocation fails, the system function will return a value of 0. At this point, the return value "0" no longer indicates the newly enabled pointer, but a notification sent by the system to the application, indicating that an error has occurred. As an application, you should check whether the return value is 0 after each memory application. If so, it means that there is a fault and some measures need to be taken to save it, which enhances the "robustness" of the program. If the application does not check this error, it will think that this value is an available pointer assigned to it according to "thinking inertia" and continue to use this memory in subsequent operations. The real 0-address storage area stores the most important "interrupt descriptor table" in the computer system, which is absolutely not allowed to be used by applications. In an unprotected operating system (such as DOS), writing data to this address will lead to an immediate crash, while in a robust operating system, such as Windows, this operation will be immediately captured by the protection mechanism of the system, and as a result, the operating system will forcibly close the wrong application to prevent its error from expanding. At this time, the above-mentioned "write memory" error will appear, indicating that the referenced memory address is "0x00000000". There are many reasons for the failure of memory allocation, such as insufficient memory and mismatched system function versions. Therefore, this distribution failure is mostly seen after the operating system has been used for a long time, a variety of applications (including virus programs installed unintentionally) have been installed, and a large number of system parameters and system files have been changed.

7. Due to the error of the application itself, it refers to an abnormal memory pointer. In an application that uses dynamic allocation, it sometimes happens that the program tries to read and write a memory that should be available, but for some reason, the expected available pointer has become invalid. It may be "forgetting" to ask the operating system for allocation, or it may be that the program itself canceled this memory at some point, "not paying attention" and so on. The logged-out memory is reclaimed by the system, and its access right no longer belongs to the application, so reading and writing operations will also trigger the protection mechanism of the system, and the only final result of the program that tries to "violate the law" is to be stopped by the operation and recover all resources. The laws of the computer world are still much more effective and severe than human beings! A situation like this is a BUG in the program itself, and you can often reproduce the error in a specific operation sequence. The invalid pointer is not always 0, so the memory address in the error prompt is not necessarily "0x00000000", but it can also be other random numbers.