The memory cannot be & quot; read & quot; command 00000000*0.

Memory cannot be "read" command 00000000*0 problem "0x ????????" Command reference "0x ????????" Memory. The memory cannot be "read ". This problem occurs in a variety of ways: hardware, memory, and software. I. First talk about hardware: Generally, computer hardware is very bad. The possibility of memory problems is not high (unless your memory is really a mess), the main aspects are:
1. Memory stick is broken (mostly used memory), 2. Memory with quality problems, 3. There is too much dust in the golden finger part of the memory inserted on the motherboard. 4. Use different brands of memory with different capacities, resulting in incompatibility. 5. Heat Dissipation caused by overclocking. You can use the MemTest software to check the memory, which can thoroughly detect the memory stability.
2. If none of them exist, the software should be able to resolve the fault. Principle 1: the memory has a buffer where data is stored. When the program puts the data in the buffer zone, the "function" provided by the operating system is required to apply. If the memory is allocated successfully, the function will return the newly opened memory zone address to the application, and the application can use this memory address. Www.2cto.com is "dynamic memory allocation", and the memory address is also the "cursor" in programming ". The memory is not always used, and sometimes the memory allocation fails. When the allocation fails, the system function returns a value of 0. The returned value "0" does not indicate a new enabled cursor. Instead, the system sends a notification to the application notifying you of an error. As an application, check whether the returned value is 0 after each memory application. If yes, it means that a fault has occurred and some measures should be taken to save the problem, this enhances the robustness of the program ".
If the application does not check this error, it determines that this value is the available cursor assigned to it according to "thinking inertia" and continues to use this memory in subsequent execution. The real 0-address memory zone stores the most important "Interrupt Descriptor Table" in computer systems and is definitely not allowed by applications. In an operating system without a protection mechanism (such as DOS), writing data to this address will immediately become a machine, while in a robust operating system, such as Windows, this operation will be immediately captured by the system's protection mechanism. The result is that the operating system forces the application that fails to be closed to prevent the error from expanding. At this time, the above memory cannot be "read" error occurs, and the referenced memory address is "0x00000000". There are many causes of memory allocation failure, such as insufficient memory and mismatched system function versions. Therefore, this allocation failure is often seen after the operating system has been in use for a long time, installed a variety of applications (including inadvertently "installed" virus programs ), after a large number of system parameters and system files are changed. In applications that use dynamic allocation, sometimes the program tries to read and write a piece of memory that should be available, but somehow, the expected available cursor has expired. It may be that the system requires allocation "forgot", or that the program has logged out the memory at some time and "did not pay attention. The logged-out memory is reclaimed by the system and its access rights do not belong to this application. Therefore, read/write operations also trigger the system's protection mechanism, the only end of an "illegal" program is to be terminated and all resources are recycled. Laws in the computer world are much more effective and harsh than humans! Such cases all belong to the bugs of the program. You can often reproduce errors in a specific operation order.
Invalid cursor may not always be www.2cto.com 0. Therefore, the memory address in the error message is not set to "0x00000000", but other random numbers. First, we recommend that you: 1. check whether there are Trojans or viruses in the system? > 2. Update the operating system so that the operating system installer can copy the system file of the correct version and correct system parameters. Sometimes the operating system itself also has bugs. You must install the officially released upgrade program. 3. Try to use the latest official version of the application, Beta, trial version will have bugs.
4. Delete and recreate the file in the WinntSystem32WbemRepository folder. Right-click my computer on the desktop and Click Manage. Under "services and applications", click Services, and then close and stop the WindowsManagementInstrumentation service. Delete all files in the WinntSystem32WbemRepository folder. (Create backup copies of these files before deletion .) Open "services and applications", click Services, and then start the WindowsManagementInstrumentation service. When the service is restarted, the files are re-created based on the information provided in the following registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWBEMCIMOMAutorecoverMOFs
Author THISISPAN