Joke Collection Website - Mood Talk - Why can’t I use Landlords (character version)? Urgent~~~

Why can’t I use Landlords (character version)? Urgent~~~

Common reasons why the memory cannot be read or written

People who use the Windows operating system sometimes encounter such error messages: "The memory 0x00000000 referenced by the 0X instruction cannot be written", Then the application is closed. If you ask some "experts" for advice, the answer you get is often indignation and disdain such as "Windows is so unstable." In fact, this error is not necessarily caused by Windows instability. This article will briefly analyze the common causes of this error.

1. The application did not check the memory allocation failure

When the 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 If successful, the function will return the address of the newly opened memory area to the application program, and the application program can use this memory through this address. This is "dynamic memory allocation", and the memory address is also the "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 0 value. At this time, the return value "0" no longer represents the newly enabled pointer, but a notification sent by the system to the application, informing the application that an error has occurred. As an application, you should check whether the return value is 0 after each application for memory. If it is, it means that a fault has occurred and some measures should be taken to save it. This enhances the "robustness" of the program.

If the application does not check this error, it will think that this value is a usable pointer allocated to it according to "thinking inertia", and continue to use this memory in subsequent runs. The real memory area at address 0 stores the most important "interrupt descriptor table" in the computer system, and applications are absolutely not allowed to use it. In an operating system without a protection mechanism (such as DOS), writing data to this address will cause an immediate crash. In a robust operating system, such as Windows, this operation will be immediately captured by the system's protection mechanism, and the result is The operating system forcibly closes the errant application to prevent its error from spreading. At this time, the above-mentioned "write memory" error will appear, pointing out that the referenced memory address is "0x00000000".

There are many reasons for memory allocation failure. Insufficient memory, mismatched versions of system functions, etc. may have an impact. Therefore, this kind of allocation failure is more common after the operating system has been used for a long time, after a variety of applications have been installed (including virus programs that were inadvertently "installed"), and a large number of system parameters and system files have been changed.

2. The application references an abnormal memory pointer due to its own bug

In applications that use dynamic allocation, sometimes there will be a situation like this: the program tries to read and write a block "Should be available" memory, but for some reason, the expected available pointer has expired. It may be that it "forgot" to request allocation from the operating system, or it may be that the program itself has logged off this memory at some point without "paying attention", etc. The unregistered memory is reclaimed by the system, and its access rights no longer belong to the application. Therefore, read and write operations will also trigger the system's protection mechanism. The only fate of a program that attempts to "illegal" is to be terminated by the operation and all resources will be reclaimed. The laws in the computer world are still much more effective and stricter than those of humans! Situations like this are all bugs in the program itself, and you can often reproduce the error in a specific sequence of operations. Invalid pointers are not always 0, so the memory address in the error message is not necessarily "0x00000000", but other random numbers.

If the system often has the error message mentioned, the following suggestions may be helpful:

1. Check whether there are Trojans or viruses in the system. Such programs often irresponsibly modify the system in order to control the system, causing operating system abnormalities. You should always strengthen your information security awareness and never be curious about executable programs of unknown origin.

2. Update the operating system and let the installation program of the operating system re-copy the correct version of the system files and correct the system parameters. Sometimes the operating system itself may have bugs, so be sure to install the official upgrade program.

3. Try the new version of the application.

When running some programs, sometimes a memory error message will appear, and then the program will close.

The "0x" memory referenced by the "0x" instruction. This memory cannot be "read".

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

Have you ever experienced a similar failure? (The content after 0x may be different.)

Generally, this phenomenon occurs for several reasons. One is hardware, that is, memory problems, and the other is software, which has many problems.

Let’s talk about the hardware first:

Generally speaking, the possibility of memory problems is not high. The main aspects are: the memory module is broken, the memory quality is problematic, and Even if two different brands of memory with different capacities are mixed, it is easy to be incompatible. At the same time, you must also pay attention to heat dissipation issues, especially after overclocking. You can use the MemTest software to test the memory, which can thoroughly detect the stability of the memory.

If you have dual memory and mixed memory modules of different brands or bought second-hand memory, and this problem occurs, then you need to check whether there is a problem with the memory or other hardware. Not compatible. If not, then troubleshoot the software.

First let’s briefly talk about the principle: There is a place in the memory to store data called a buffer. When the program places data in one of the locations, overflow will occur because there is not enough space. For example: a bucket can only hold one kilogram of water. When you put two kilograms of water in, it will overflow. The system is represented on the screen. This problem often occurs on windows 2000 and the above situation. In addition, it may also be caused by poor compatibility between hardware devices.

Let me analyze it from a few examples:

Example 1: Open the IE browser or within a few minutes, the "0x00000000" memory referenced by the "0x70dcf39f" instruction will appear. This memory cannot be "read". To terminate the program, click the "OK" message box. After clicking "OK", the message box "An internal error has occurred and one of the windows you are using is about to close" appears. After closing the prompt message, IE browser The device is also turned off. Solution: Repair or upgrade the IE browser and apply a patch. One of the repair methods I have seen is Win2000 self-upgrade, that is, upgrading from Win2000 to Win2000. In fact, this method is to restore the system to its initial state. For example, if your IE is upgraded to 6.0, it will be replaced by IE5.0 after the upgrade.

Example 2: Double-click the "AutoRun.exe" file in the CD under Windows XP, and the "0x00000078" memory referenced by the "0x77f745cc" command is displayed. The memory cannot be "written". To terminate the program, please click "OK", but it runs normally in Windows 98. Solution: This may be a system compatibility issue. For winXP systems, right-click the "AutoRun.exe" file, properties, compatibility, select the "Run this program in compatibility mode" item, and select "Windows 98/Me" . If win2000 is patched with SP, just start and run, enter: regsvr32 c:\\winnt\\apppatch\\slayerui.dll. Right click, properties, and compatibility options will also appear.

Example 3: An error occurred when closing RealOne Gold. It had been used normally before, but recently the "0xffffffff" memory referenced by the "0xffffffff" command appeared every time it was closed. This memory cannot be "read".

Solution: This problem will occur when RealOne is closed when the input method used is Microsoft Pinyin Input Method 2003 and the language bar is hidden (no problem when not hidden). Therefore, the language bar can be displayed or any other input method can be displayed before closing RealOne. as the current input method to solve this problem.

Example 4: My Hero Super Jieba can no longer be played since it went online. Every time it prompts "Ox060692f6" (each change), the "Oxff000011" memory referenced by the command cannot be "read" and terminated. Please click OK to proceed. Solution: Try reinstalling Hero Super Jieba. If the problem persists after reinstalling, go to the official website to download the corresponding version of the patch and try. If it still doesn't work, I have to try another player.

Example 5: Double-click a game shortcut, the "Ox77f5cdO" command refers to the "Oxffffffff" memory, the memory cannot be "read", and a Client.dat program error is prompted. Solution: Reinstall the latest driver for the graphics card, then download and install DirectX9.0.

Example 6: A friend sent a message, and an error message appeared on my computer: the "0*00303033" memory referenced by the "0*772b548f" command cannot be "written", and then QQ Automatically logged out, and then opened QQ, and found more than a dozen messages sent by him. Solution: This is a BUG of the other party using QQ, sending special codes, and making QQ errors. As long as you apply a patch or upgrade to the latest version, it will be fine.

Through the above examples, we can see that there are many reasons for failure. Here is a list of the mentioned and possible reasons for easy reference.

Solution

1. If the memory module is broken, replace it

2. If the dual memory is incompatible, use the same brand of memory or only use one memory module

p>

3. For memory quality problems, replace the memory module

4. For heat dissipation issues, strengthen the heat dissipation inside the chassis

5. The memory and motherboard are not plugged in properly or are incompatible with other hardware Wait for the memory to be re-inserted or change the socket

6. If there is a problem with the hard disk, replace the hard disk

7. If there is a driver problem, reinstall the driver. If it is a new system, you must first install the motherboard driver

8. If the software is damaged, reinstall the software

9. If the software has BUG, ??patch it or use the latest version.

10. If the software is not compatible with the system, patch the software or try the compatibility mode of the system.

11. If there is a conflict between the software and the software, if any new software has been installed recently, uninstall it. Give it a try

12. The software needs to use other related software and if there is a problem, reinstall the related software. For example, when an error occurs when playing a file of a certain format, there may be a problem with the decoder of this file

13. Virus problem anti-virus

14. Anti-virus software conflicts with the system or software due to anti-virus software It enters the underlying monitoring system. It may conflict with some software. Try uninstalling it.

15. There are problems with the system itself. Sometimes the operating system itself will have BUGs. Pay attention to installing the official upgrade program, such as It is best to apply the SP patch. If that still doesn't work, reinstall the system or change to another version of the system.

It is common for a blue screen to appear when using Windows, and often the system is frequently reinstalled because the source of the error is not clear, which is time-consuming and laborious. The following has collected some Windows crash passwords for your reference.

Value Description

0 0x0000 Job completed.

1 0x0001 Incorrect function.

2 0x0002 The system cannot find the specified file.

3 0x0003 The system cannot find the specified path.

4 0x0004 The system cannot open the file.

5 0x0005 Access denied.

6 0x0006 Invalid code.

7 0x0007 The storage control block is destroyed.

8 0x0008 There is insufficient storage space to process this command.

9 0x0009 The storage control block address is invalid.

10 0x000a The environment is incorrect.

11 0x000b An attempt was made to load a malformed program.

12 0x000c Access code error.

13 0x000d Data error.

14 0x000e There is insufficient storage space to complete this operation.

15 0x000f The system cannot find the specified disk drive.

16 0x0010 Unable to remove directory.

17 0x0011 The system cannot move the file to another drive.

18 0x0012 No files.

19 0x0013 The storage medium is write-protected.

20 0x0014 The system cannot find the specified device.

21 0x0015 The device is not ready yet.

22 0x0016 The device cannot recognize the command.

23 0x0017 Data error (cyclic redundancy check)

24 0x0018 The program issued a command with the wrong length.

25 0x0019 The disk drive cannot find the fixed sector or track on the disk.

26 0x001a The specified disk or disk cannot be accessed.

27 0x001b The disk drive cannot find the required sector.

28 0x001c The printer is out of paper.

29 0x001d The system cannot write data to the specified disk drive.

30 0x001e The system cannot read the specified device.

31 0x001f A device connected to the system is not functioning.

32 0x0020 the process cannot access the file because it is being used by another process.

33 0x0021 Part of the file is locked and cannot be accessed now.

34 0x0022 The disk drive disk is incorrect. Please insert %2 (volume serial number: %3) into drive %1.

36 0x0024 There are too many open shared files.

38 0x0026 End of file reached.

39 0x0027 The disk is full.

50 0x0032 This network requirement is not supported.

51 0x0033 The remote computer cannot be used.

52 0x0034 The network name is duplicated.

53 0x0035 The network path cannot be found.

54 0x0036 The network is busy.

55 0x0037 the specified network resource or device is no longer available.

56 0x0038 the network bios command limit has been reached.

57 0x0039 Network configuration There was a problem receiving the card.

58 0x003a The specified server cannot perform the requested operation.

59 0x003b An unexpected network error occurred.

60 0x003c The remote adapter card is incompatible.

61 0x003d The printer queue is full.

62 0x003e The server has insufficient space to store files waiting to be printed.

63 0x003f The file waiting to be printed has been deleted.

64 0x0040 The specified network name cannot be used.

65 0x0041 Network access denied.

66 0x0042 The network resource type is wrong.

67 0x0043 The network name cannot be found.

68 0x0044 The name limit of the regional computer network adapter card is exceeded.

69 0x0045 Network bios session limit exceeded.

70 0x0046 The remote server has been suspended or is starting.

71 0x0047 No more connections can be made to this remote computer at this time because the number of connections has reached the upper limit.

72 0x0048 The specified printer or disk device has been suspended.

80 0x0050 The file already exists.

82 0x0052 Unable to create directory or file.

83 0x0053 int 24 failed

84 0x0054 The storage to handle this request cannot be used.

85 0x0055 The local device name is already in use.

86 0x0056 The specified network password is incorrect.

87 0x0057 Parameter error.

88 0x0058 A data writing error occurred on the network.

89 0x0059 The system cannot execute other trips at this time.

100 0x0064 Unable to establish other system semaphore.

101 0x0065 belongs to the semaphore dedicated to other trips.

102 0x0066 The semaphore has been set and cannot be closed.

103 0x0067 Unable to specify semaphore.

104 0x0068 Unable to request dedicated semaphore at break time.

105 0x0069 The previous ownership of this semaphore has ended.

106 0x006a Please insert the disk into %1.

107 0x006b The program has stopped because the substitute disk has not been inserted.

108 0x006c The disk is in use or locked.

109 0x006d pipe has been aborted.

110 0x006e The system cannot open the specified device or file.

111 0x006f The file name is too long.

112 0x0070 Insufficient disk space.

113 0x0071 No internal file identifier available.

114 0x0072 The target internal file identifier is incorrect.

117 0x0075 The ioctl call performed by the application is incorrect.

118 0x0076 The write verification parameter value is incorrect.

119 0x0077 The system does not support the requested command.

120 0x0078 This function is only valid in win32 mode.

121 0x0079 semaphore timeout period exceeded.

122 0x007a The data area passed to the system call is too small.

123 0x007b Syntax error in file name, directory name or storage label.

124 0x007c The system call level is incorrect.

125 0x007d The disk has no label set.

126 0x007e The specified module cannot be found.

127 0x007f The specified program cannot be found.

128 0x0080 There are no sub-trips to wait for.

129 0x0081 %1 This application cannot be executed in win32 mode.

130 0x0082 attempt to use a file handle to an open disk partition for an

operation other than raw disk i/o.

131 0x0083 attempt to use the file The indicator moves before the beginning of the archive.

132 0x0084 Unable to set file index on the specified device or file.

133 0x0085 The join or subst command cannot be used with a drive that has been previously joined.

134 0x0086 Try to use the join or subst command on the disk drive that has been combined.

135 0x0087 Try to use the join or subst command on the replaced disk drive.

136 0x0088 The system attempts to delete the link relationship of an unlinked disk.

137 0x0089 The system attempts to delete the replacement relationship of the disk drive that has not been replaced.

138 0x008a The system attempts to combine the disk drive to the directory of the drive that has already been combined.

139 0x008b The system attempts to replace the disk drive with the directory of the disk drive that has been replaced.

140 0x008c The system attempts to replace the disk drive with the directory of the disk drive that has been replaced.

141 0x008d The system attempted to subst the drive into a combined drive directory.

142 0x008e The system cannot execute join or subst at this time.

143 0x008f The system cannot combine disk drives or replace directories under the same disk drive.

144 0x0090 This directory is not a subdirectory of the root directory.

145 0x0091 The directory still has data.

146 0x0092 The specified path has been replaced.

147 0x0093 Insufficient resources to process this command.

148 0x0094 The specified path cannot be used at this time.

149 0x0095 The disk drive directory trying to be combined or replaced is an already replaced target.

150 0x0096 The config.sys file does not specify system tracking information, or the tracking function is canceled.

151 0x0097 The number of specified semaphore event dosmuxsemwait is incorrect.

152 0x0098 dosmuxsemwait is not executed; too many semaphore are set.

153 0x0099 dosmuxsemwait list is incorrect.

154 0x009a The storage media identifier you entered has a length limit.

155 0x009b Unable to create other execution threads.

156 0x009c The receiving trip refused to accept the signal.

157 0x009d The section has been abandoned and cannot be locked.

158 0x009e The section has been unlocked.

159 0x009f The address of the thread identifier is incorrect.

160 0x00a0 The argument string passed to dosexecpgm is incorrect.

161 0x00a1 The specified path is incorrect.

162 0x00a2 signal is waiting for processing.

164 0x00a4 The system cannot create an execution thread.

167 0x00a7 Unable to lock part of the file.

170 0x00aa The requested resource is in use.

173 0x00ad The lock requirement for canceling the range is not obvious.

174 0x00ae The file system does not support automatic change of lock type.

180 0x00b4 The system found an incorrect section number.

182 0x00b6 The operating system cannot execute %1.

183 0x00b7 The file already exists and the same file cannot be created.

186 0x00ba The transmitted flag is incorrect.

187 0x00bb The specified system flag cannot be found.

188 0x00bc The operating system cannot execute %1.

189 0x00bd The operating system cannot execute %1.

190 0x00be The operating system cannot execute %1.

191 0x00bf Unable to execute %1 in win32 mode.

192 0x00c0 The operating system cannot execute %1.

193 0x00c1 %1 is not a correct win32 application.

194 0x00c2 The operating system cannot execute %1.

195 0x00c3 The operating system cannot execute %1.

196 0x00c4 The operating system cannot execute this application.

197 0x00c5 The operating system is currently unable to execute this application.

198 0x00c6 The operating system cannot execute %1.

199 0x00c7 The operating system cannot execute this application.

200 0x00c8 The section of code cannot be larger than or equal to 64kb.

201 0x00c9 The operating system cannot execute %1.

202 0x00ca The operating system cannot execute %1.

203 0x00cb The system cannot find the entered environment option. \r

205 0x00cd There is no signal sub-processor for any process in the command subdirectory.

206 0x00ce The file name or file extension is too long.

207 0x00cf ring 2 stack is in use.

In short, it is actually not difficult to find an expert who knows how to do it for you