Recently, many netizens have encountered an error prompt that the memory cannot be "Read". I hope the following articles can help everyone.
When running certain programs, sometimes the memory error prompts appear, and then the program is closed.
"0x ???????" instructions "0x ?????????" instruction. The memory cannot be "Read".
The "0x ???????????" memory referenced by the "0x ????????" instructions cannot be "Written".
I believe everyone should have seen the above situation, and even say that some netizens have repeatedly reinstalled the system because they are unhappy because they are unhappy. I believe ordinary users should not understand those complicated hexadecimal code.
There are aspects of this phenomenon, one is hardware, that is, there is a problem with memory, and the other is software, which has many problems.
One: Let's talk about hardware first:
Generally speaking, computer hardware is not easy to break. The possibility of memory problems is not high (unless your memory is really a miscellaneous land), the main aspect is: 1. The memory bar is broken (second -hand memory is mostly), 2. Use memory with quality problems, 3. There are too many golden fingers inserted on the motherboard. 4. Use different brands of memory of different capacity, thereby incompatibility. 5. The heat dissipation problem brought by overclocking. You can use Memtest's software to detect memory, which can completely detect the stability of memory.
Second, if none, the failure is ruled out from the software aspect.
Let's talk about the principle first: There is a place where the memory stores the data is called a buffer. When the program places the data in the buffer, the "function function" provided by the operating system needs to apply. The area address returns to the application, and the application can use this memory through this address. This is the "dynamic memory distribution", which is the "cursor" in programming. Memory is not always recruited and endless, and sometimes memory distribution fails. When the distribution fails, the system function will return a 0 value. At this time, the return value "0" does not indicate the newly opened cursor. Instead, the system issued to the application to inform the application that an error occurs. As an application, you should check whether the return value is 0 after each application is applied. If it is, it means that if there is a failure, some measures should be taken to save, which enhances the "robustness" of the program. If the application does not check this error, it will think that this value is assigned to it according to "thinking inertia" and continue to use this memory in subsequent execution. The real 0 address memory area stores the most important "interrupt descriptor table" in the computer system, which is absolutely not allowed to use it. Under the operating system without the protection mechanism (such as DOS), writing data to this address will cause immediately as a machine. In a strong operating system, such as Windows, this operation will be captured by the system's protection mechanism immediately. Applications that are forcibly closed by the operating system to prevent their errors from expanding. At this time, the above -mentioned memory will not be "Read" errors, and it is pointed out that the referenced memory address is "0x00000000". There are many reasons for the failure failure of memory distribution. Insufficient memory, and the version of the system function may not match. Therefore, this distribution failure is more common in the operation system for a long time, and a variety of applications (including the inadvertent "installation" virus program) are installed, and a large number of system parameters and system files have been changed.
In an application using a dynamic allocation, sometimes there will be such a situation: the program tries to read and write a "available" memory, but somehow, the cursor that is expected to be invalidated is invalid. It may be "forgotten" to allocate the operating system, or it may be that the program has canceled the memory at some point and "didn't pay attention" and so on. The cancellation of memory is recycled by the system, and its access rights are no longer the application. Therefore, the reading and writing operation will also trigger the protection mechanism of the system. The only end of an attempt to "illegally" procedures is that the operation is terminated and the entire resources are recovered. The laws of the computer world are still much more effective and severe than humans! Such a situation is the BUG of the program itself, and you can often reproduce errors in a specific operation order. The invalid cursor is not necessarily 0, so the memory address in the error prompt is not necessarily "0x00000000", but other random numbers.
Suggestion first:
1. Is there a Trojan or virus in the inspection system?
> 2. Update the operating system and let the installation program of the operating system copy the correct version of the system file and correct system parameters. Sometimes the operating system itself has bugs. Pay attention to installing the officially issued upgrade procedures.
3. Try to use the latest official version of the application, the Beta version, and the trial version will have bugs.
4. Delete and re -create a file in WinntSystem32WBEMREPOSITORY folder: right -click my computer on the desktop and click Management. Under "Service and Application", click the service, and then close and stop WindowsManagementInTrumentation. Delete all files in WINTSYSTEM32WBEMREPOSITORY folder. (Please create a backup copy of these files before deleting.) Open "Service and Application", click the service, and then open and start WindowsManagementInstrumentation services. When the service is restarted, the information provided based on the information provided in the following registry will be re -created: HKEY_LOCAL_MACHINESOFTWAREMICROSOFTWBEMCIMAMAUTOROVERMOFS
Run the executable file in the compressed package to repair
Hot search words: 360 Security Guard Office365 360 browser WPS Office IQiyi Huawei Cloud Market Tencent Cloud Store
it works
it works
it works