Help me, brothers. The instruction "0x7c80a332" refers to "0x0535 1000 memory. Unable to read.

Unable to read (or write) the memory error details.

People who use the Windows operating system sometimes encounter the following error message: "The memory 0X00000000 referenced by the 0x instruction cannot be read or written", and then close the application. If you ask some "experts", the answer you get is often indignation and disdain like "Windows is so unstable". In fact, this error is not necessarily caused by the instability of Windows. This paper will briefly analyze the common causes of this error.

First, the application cannot check the memory allocation.

When a program needs a piece of memory to store 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.

Second, the application refers to an abnormal memory pointer due to its own BUG.

In applications that use 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 failed. 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.

If the above error prompt appears frequently, the following suggestions may be helpful:

1. Check the system for Trojan virus. In order to control the system, such programs often modify the system irresponsibly, resulting in abnormal operating system. We should strengthen our awareness of information security at ordinary times, and never be curious about executable programs with unknown sources.

2. Update the operating system, so that the installation program of the operating system can copy the correct version of the system files and correct the system parameters. Sometimes there are bugs in the operating system itself, so pay attention to installing the officially released upgrade program.

3. Try a new version of the application.

This is caused by a program error. You can change the program settings or reinstall the program.

I believe everyone should have seen it, and even said that some netizens repeatedly reinstalled the system because they were dissatisfied with this frequent error prompt. I believe that ordinary users like us should not understand those complicated hexadecimal codes. Those are just for researchers at Microsoft Research Asia (just kidding).

Third, software or hardware?

When running some programs, sometimes there will be a memory error prompt, and then the program will 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. )

Look carefully at the contents after 0x. Is everyone's error code different? But their problems may be the same. There are two reasons for this error prompt. First, there is something wrong with the hardware, that is, there is something wrong with the memory. Second, the software has many problems.

1, let's talk about hardware first:

Generally speaking, computer hardware is not easy to break down. Memory problems are unlikely (unless your memory is really a bunch of miscellaneous brands), and the main aspects are: 1. Memory is broken (mostly second-hand memory), 2. Using memory with quality problems, 3. There is too much dust in the golden finger of the memory inserted in the motherboard. 4。 Using different brands and capacities of memory leads to incompatibility. 5。 Heat dissipation caused by 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.

2. If none of the above conditions exist, then solve the problem from the software aspect.

Let's talk briefly about the principle first: there is a place in memory called buffer for storing data. If the program puts the data in one place, it will overflow because of insufficient space. For example, a bucket can only hold one catty of water. If you put two Jin of water in it, it will overflow. The system is displayed on the screen. This problem often appears in windows2000 and XP systems. Windows2000/XP has very strict requirements on hardware. In the case of deadlock, overflow or illegal operation of resources similar to Windows98, the above situation will occur in order to keep the system stable. In addition, it may also be caused by poor compatibility between hardware devices.

At the same time, because the system runs to protect a section of memory, other user programs cannot access the memory, and this error will also occur when user programs illegally read these memory spaces.

Fourth, give a few examples:

(1) q: The "0x003713644" memory referenced by the "08ba9ef" instruction cannot be read. To terminate the program, click OK.

A: There is an error in IE. You need to reset IE:

1 Open the "Run" window in the "Start" menu, enter "regsvr32actxprxy.dll" in it, and then click "OK", and an information dialog box "dllregisterserveractivexprxy" will appear. Dll successful "will appear, and click" ok "again.

2 Open the Run window again and enter "regsvr32shdocvw.dll"

3 Open the Run window again and enter "regsvr 32 ole out 32. dll"

4 Open the Run window again and enter "regsvr32actxprxy.dll"

5 Open the Run window again and enter "regsvr32mshtml.dll"

6 Open the Run window again and enter "regsvr32msjava.dll"

7 Open the Run window again and enter "regsvr32browseui.dll"

8 Open the Run window again and enter "regsvr32urlmon.dll"

(2) Ask the "0x00000000" memory referenced by the "0x70dcf39f" instruction. The memory cannot be read. To terminate the program, click OK.

A: After the prompt message is closed, IE browser is also closed. Solution: Repair or upgrade IE browser and patch the system at the same time. Make sure your IE is upgraded to 6.0.

(3) Q: There was an error when RealOneGold was closed. It used to be normal, but recently, "0x ffffff" memory referenced by the "0xffffffff" command will appear every time it is turned off. This kind of memory can't be a hint of "read".

A: When the input method used is Microsoft Pinyin Input Method 2003, and the language bar is hidden (there is no problem if it is not hidden), this problem will occur when closing RealOne, so you can display the language bar before closing RealOne or use any other input method as the current input method to solve this problem.

(4) Q: The "OX77F5CDO" instruction refers to the "Oxffffffff" memory and cannot be read. To terminate the program, click OK.

Answer: Double-click the shortcut of a game to prompt that the Client.dat program is wrong. Solution: Reinstall the latest driver of graphics card, and then download and install DirectX9.0.

(5) Q: The "0x00303033" memory referenced by the "0x772b548f" instruction cannot be "written". To terminate the program, click OK.

A: QQ automatically goes offline. When I opened QQ again, I found that there were more than a dozen messages. Solution: This is because the other party uses QQ BUG to send special code. If QQ is wrong, just patch or upgrade to the latest version.

(6) Q: Open IE browser or the "0x00000000" memory referenced by the "0x70dcf39f" instruction will appear in a few minutes. The memory cannot be read. To terminate the program, click OK. After clicking OK, the message box "An internal error has occurred and a window you are using will be closed soon" will appear. After closing this prompt message, IE browser is also closed.

Answer: Repair or upgrade IE browser and patch it at the same time. I see that there is a repair method that Win2000 is self-upgrading, that is, Win2000 is upgraded to Win2000. In fact, this method is to restore the system to the initial state. For example, if your IE is upgraded to 6.0, it will be changed to IE5.0 after the upgrade.

(7) Q: Double-click the "AutoRun.exe" file in the CD under windowsxp to display the "0x00000078" memory referenced by the "0x77f745cc" instruction. Memory cannot be "written". To terminate the program, click OK, but it works normally in Windows98.

Answer: This may be a compatibility problem of the system. For winXP system, right-click the AutoRun.exe file, properties and compatibility, and select "Run this program in compatibility mode" and "Windows98/Me". Win2000, if the SP is patched, just start running, and enter: regsvr32c: \ winnt \ apppatch \ Slayer ui.dll. Right-click and the properties and compatibility options will also appear.

(8) Q: My hero, Super Jieba, has been unable to play since he got online. Every time you are prompted that the "0xff000 1 1" memory referenced by the "0x060692f6" command cannot be read, press OK to terminate the program.

A: Try reloading Hero Super Jieba. If it will be reinstalled, you can try to download the corresponding version of the patch from official website. Not yet, so I have to try another player.