Traditional Culture Encyclopedia - Almanac inquiry - Why does EXCEL automatically close after it is opened?
Why does EXCEL automatically close after it is opened?
The keyboard is locked.
solution
First, the recharge system
Secondly, turn on F8 to enter safe mode to prevent viruses and kill Trojan horses.
Kaspersky and 360 security guards are best together.
Why does proe automatically close after it is opened? In most cases, the proe in normal use will suddenly jump out, which is usually related to memory, such as too little memory.
If the license pops up incorrectly after startup, and then exits, it is caused by incorrect cracking. What used to be normal is not normal now, so it's because the network card has changed. Crack the license file again.
There are also some special cases caused by the problem of starting the page. In this case, you can modify the configuration options and try to set the startup page to blank.
Finally, it is possible that you have loaded an incorrect configuration file, which is usually found by directly using someone else's config.pro You can change the name of config.pro to start without using configuration.
For more questions and solutions, please refer to here: hi.baidu./icefai/blog/item/47F6b262ed25fde0e6113a4d.
I hope I can help you ~
Why does the Eternal Tower automatically close when it is opened Dear player:
Today, we received feedback from some players. After executing the game "Eternal Tower", clicking the "Enter Game" button on the startup interface will abnormally exit to the pop-up page, and the game will not run normally. After emergency inspection by several technicians, it is found that the problem may be caused by installing the latest Microsoft patch but not restarting the computer. In this regard, we suggest that players who exit abnormally, please restart their computers and try to log in to the game again.
Thank you for your understanding and support of our work. I wish you all a happy Spring Festival!
Eternal Tower Operation Team
2011February 9
Shengda official website
Why does QQ chat room automatically close after opening? 1: Brother, if you can't clean up the redo system, kill your computer and poison it.
2. The next latest version, some old ones are not supported.
3. Your computer is out of memory, so I suggest you tidy up the virtual memory.
Common reasons why this memory cannot be read or written.
People who use the Windows operating system sometimes encounter the following error message: "The 0X00000000 memory referenced by the 0x instruction cannot be written", and then the application closes. If you ask some "experts", the answer you get is often indignation and disdain such as "Windows is too unstable". In fact, this error is not necessarily caused by the instability of Windows. This article will briefly analyze the common causes of this error.
1. The application could not check the memory allocation.
When a program needs memory to store data, it needs to call the "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 the 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 the system sends an error notification to the application. 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 should be taken to save it, which enhances the "robustness" of the program.
If the application does not check this error, it will regard this value as an available indicator allocated to it according to "thinking inertia" and continue to use this memory in subsequent executions. 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 operating system without protection mechanism (such as DOS), writing data to this address will lead to immediate shutdown, 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 "write memory" error mentioned above will appear, and it is pointed out that the referenced memory address is "0x00000000".
There are many reasons for memory allocation failure, such as insufficient memory and system function version mismatch. Therefore, after the operating system has been used for a long time, after installing various applications (including virus programs installed unintentionally) and changing a large number of system parameters and system files, this allocation failure is more common.
Second, the application refers to an abnormal memory pointer because of its own BUG.
In applications that use dynamic allocation, it sometimes happens that the program tries to read and write "should be available" memory, but somehow this expected availability indicator becomes invalid. Maybe you "forgot" to ask the operating system for allocation, or the program itself cancelled the memory at some point and "didn't pay attention" and so on. The logged-out memory is reclaimed by the system, and its access rights no longer belong to this application. Therefore, reading and writing operations will also trigger the protection mechanism of the system. The only final result of the program that tries to "violate the law" is * * * to stop execution 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 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 irresponsibly modify the system, 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 installer of the operating system can copy the correct version of the system file again 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.
When executing some programs, sometimes a memory error prompt appears, and then the program closes.
0x instruction refers to 0x memory. Unable to "read" memory.
The "0x" memory referenced by the "0x" instruction cannot be "written".
I wonder if you have made such a mistake? (The contents after 0x may be different. )
Generally speaking, this phenomenon has many aspects, one is hardware, that is, memory, and the other is software, which has many problems.
Let's talk about hardware first:
Generally speaking, memory problems are unlikely. The main aspects are: the memory stick is broken, the memory quality is problematic, and the memory of two different brands with different capacities is mixed, which is also prone to incompatibility. At the same time, pay attention to heat dissipation, especially after overclocking. You can use MemTest software to check the memory, which can thoroughly check the stability of the memory.
If you have dual memory, and this problem will occur when different brands of memory sticks are mixed or you buy second-hand memory, you should check whether there is a problem with the memory or whether it is incompatible with other hardware. If not, please troubleshoot the software.
Let's talk briefly about the principle: there is a place in memory for storing data called buffer. When a program puts data in one place, it will overflow because there is not enough space. For example, a bucket can only hold one catty of water. When you put in two Jin of water, the water will overflow. The system is displayed on the screen. This problem often appears in windows2000 and XP systems. Windows 2000/XP has very strict requirements on hardware. When encountering deadlock, overflow or illegal operation of resources similar to Windows 98, the above situation will occur in order to keep the system stable. In addition, it may be caused by poor compatibility between hardware devices.
Let me analyze it for you from a few examples:
Example 1: Opening IE browser or "0x00000000" memory referenced by "0x70dcf39f" command will appear in a few minutes. Unable to "read" memory. To terminate the program, click OK in the message box. 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 the prompt message, IE browser also closes. Solution: 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 replaced by IE5.0.
Example 2: Double-click the "AutoRun.exe" file in the CD under windows xp to display the "0x00000078" memory referenced by the "0x77f745" command. Memory cannot be "written". To terminate the program, click OK, but it can run normally in Windows 98. Solution: This may be a compatibility problem of the system. For winXP systems, right-click the AutoRun.exe file, properties and compatibility, select Run this program in compatibility mode, and then select Windows 98/Me. Win2000, if the SP is patched, just start and execute it, and then enter: regsvr32c: \ \ winnt \ \ apppatch \ \ slayeui.dll. Right-click and the properties and compatibility options will also appear.
Example 3: An error occurred when closing RealOne Gold. It used to be normal, but recently, the "0xffffffff" memory referenced by the "0xffffffff" command appears every time it is closed. Memory cannot be a "read" hint. Solution: When the input method used is Microsoft Pinyin Input Method 2003 and the language bar is hidden (there is no problem when it is not hidden), this problem will appear when RealOne is closed, 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.
Example 4: My Hero Super Jieba has been unable to play since surfing the Internet. Every time I am prompted that the "Oxff0000 1 1" memory referenced by the "Ox060692f6" command cannot be "read", please press "OK" to terminate the program. Solution: try to make up for the hero's super solution. If it will be refilled, please try to download the corresponding version of the patch from the official website. Not yet, so I have to try another player.
Example 5: Double-click the shortcut of a game, and the command "Ox77f5cdO" points to the memory "Oxffffffff", which cannot be read, prompting that the Client.dat program is wrong. Solution: Recharge the latest driver of graphics card, and then download and install DirectX9.0.
Example 6: When a friend sent me a message, my computer received an error message: the "0*00303033" memory referenced by the "0*772b548f" command could not be "written", and then QQ automatically went offline. I started QQ again and found that he had sent more than a dozen messages. Solution: This is that the other party uses the QQ BUG to send special code, and there is an error in QQ. Just patch or upgrade to the latest version, and it will be fine.
From the above example, we can see that there are many reasons for failure. Here, we list the mentioned and possible reasons for your reference.
solution
1. If the memory stick is damaged, please replace it.
2. Dual memory is not compatible with using the same brand of memory or only using one memory.
3. Replace the memory stick due to memory quality problems.
4. Heat dissipation problem Strengthen the heat dissipation inside the chassis.
5. Memory and motherboard are not inserted correctly or are incompatible with other hardware. Reinsert the memory or replace it.
6. If there is something wrong with the hard disk, please replace it.
7. Driving problem: Recharge driving. If it is a new system, the motherboard driver should be installed first.
8. Recharge when the software is damaged
9. The software is defective and needs to be repaired or the latest version is used.
10. Software and system are incompatible. Patch the software or try the compatibility mode of the system.
1 1. There is a conflict between software and software. If you have installed any new software recently, please uninstall it and try it out.
12. If the software needs to be used in other related software, please refill the related software. For example, there is an error when playing a file in a certain format, which may be a problem with the decoder of the file.
13 virus protection
14. Antivirus software conflicts with system or software. Because antivirus software enters the bottom monitoring system, it may conflict with some software. Please uninstall it and try again.
15, there is something wrong with the system itself. Sometimes the operating system itself has bugs. Pay attention to install the official upgrade program, such as SP patch, and it is best to install it. If it doesn't work, please refill the system or replace it with another version.
It is very common to have a blue screen when using Windows, and because the source of the error is not clear, it is laborious and time-consuming to reinstall the system frequently. Some windows downtime passwords are collected below for your reference.
Digital narration
0 0x0000 job completed.
1 0x000 1 invalid 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 bank control block has been corrupted.
8 0x0008 There is not enough storage space to process this command.
9 0x0009 The address of the storage control block is invalid.
10 0x000a environment is incorrect.
1 1 0x000b tried to load a malformed program.
Error in 12 0x000c access code.
13 0x000d data error.
14 0x000e does not have enough storage space to complete this operation.
15 0x000f The system cannot find the specified drive.
16 0x00 10 cannot delete the directory.
17 0x00 1 1 The system cannot move files to other drives.
18 0x00 12 has no file.
19 0x00 13 storage media is write-protected.
20 0x00 14 system cannot find the specified device.
2 1 0x00 15 device is not ready.
22 0x00 16 device cannot recognize this instruction.
23 0x00 17 data error (cyclic redundancy check)
24 0x00 18 program issued a long error instruction.
The 25 0x00 19 drive cannot find a fixed sector or track on the disk.
26 0x00 1a cannot access the specified disk or floppy disk.
27 0x00 1b drive cannot find the required volume.
28 0x00 1c printer has no paper.
29 0x00 1d system cannot write data to the specified drive.
30 0x00 1e system cannot read the specified device.
3 1 0x00 1f connected to the equipment in the system has no influence.
32 0x0020 The process cannot access the file because it is being used by another process.
Part of the file 33 0x002 1 is locked and cannot be accessed now.
The floppy disk of drive 34 0x0022 is incorrect. Please insert %2 (volume serial number: %3) into drive% 1.
36 0x0024 There are too many open shared files.
38 0x0026 has reached the end of the file.
39 0x0027 Disk is full.
50 0x0032 This network request is not supported.
5 1 0x0033 The remote computer cannot be used.
52 0x0034 Duplicate network name.
53 0x0035 The network path cannot be found.
54 0x0036 The network is busy.
55 0x0037 The specified neork resource or device is no longer available.
56 0x0038 The command limit of neork bios has been reached.
57 0x0039 There is something wrong with the network adapter.
The server specified by 58 0x003a cannot perform the requested operation.
An unexpected error occurred in the 59 0x003b network.
The 60 0x003c remote adapter is not compatible.
6 1 0x003d printer queue is full.
The space of the 62 0x003e server cannot store the 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 0x004 1 Access to the network is denied.
66 0x0042 The network resource type is wrong.
67 0x0043 The network name cannot be found.
68 0x0044 exceeds the name limit of LAN adapter.
69 0x0045 exceeds the limit of network bios session.
70 0x0046 The remote server is paused or starting.
7 1 0x0047 cannot connect to this remote computer at this time because the number of connections has reached the maximum.
72 0x0048 The specified printer or disk device has been paused.
80 0x0050 file already exists.
82 0x0052 Unable to create directory or file.
83 0x0053 int 24 failed
84 0x0054 The storage used to process this request cannot be used.
85 0x0055 The name of the near-end device has already been used.
86 0x0056 The specified network password is incorrect.
87 0x0057 parameter error.
88 0x0058 A data write error occurred in the network.
89 0x0059 The system cannot perform other trips at this time.
100 0x0064 Unable to create other system signals.
10 1 0x0065 belongs to the semaphore dedicated to other trips.
102 0x0066 semaphore has been set and cannot be closed.
103 0x0067 Unable to specify semaphore.
104 0x0068 Unable to request a dedicated semaphore during the interrupt.
105 0x0069 The previous ownership of this semaphore has ended.
106 0x006a Please insert the floppy disk into% 1.
107 0x006b The program stopped because the replacement disk was not inserted.
108 0x006c disk is in use or locked.
109 0x006d pipeline has been aborted.
1 10 0x006e The system cannot open the specified device or file.
The file name of 65438+110x006f is too long.
1 12 0x0070 Insufficient disk space.
1 13 0x007 1 No internal file identifier is available.
1 14 0x0072 The target internal file identifier is incorrect.
1 17 0x0075 The ioctl call issued by the application is incorrect.
1 18 0x0076 The value of the write verification parameter is incorrect.
1 19 0x0077 The requested command is not supported by the system.
120 0x0078 This function is only valid in win32 mode.
12 1 0x0079 semaphore exceeded the timeout period.
122 0x007a The data area passed to the system call is too small.
123 0x007b file name, directory name or storage label syntax error.
124 0x007c system call hierarchy is incorrect.
125 0x007d disk is not marked.
126 0x007e cannot find the specified module.
127 0x007f cannot find the specified program.
128 0x0080 has no waiting sub-trip.
129 0x0081%1This application cannot run in win32 mode.
130 0x0082 attempted to use the file handle of the open disk partition.
Operations other than original disk I/O.
13 1 0x0083 tried to move the file pointer before the beginning of the file.
132 0x0084 Unable to set the file pointer on the specified device or file.
133 0x0085 join or subst command cannot be used for previously bound disk drives.
134 0x0086 Try to use the join or subst command on a combined disk drive.
135 0x0087 Try to use the join or subst command on the replaced disk drive.
136 0x0088 The system tried to delete the link relationship of the unlinked drive.
137 0x0089 The system tried to delete the replacement relationship of the unreplaced drive.
138 0x008a The system tried to add the drive to the directory where the drive has been added.
139 0x008b The system tried to replace the drive with the directory of the replaced drive.
140 0x008c system tried to replace the drive with the directory of the replaced drive.
14 1 0x008d The system tried to replace the drive with a combined drive directory.
142 0x008e system cannot perform join or subst at this time.
143 0x008f system cannot merge drives or replace directories under the same drive.
144 0x0090 This directory is not a subdirectory of the root directory.
There is still data in the 145 0x009 1 directory.
The path specified by 146 0x0092 has been replaced.
147 0x0093 Insufficient resources to process this instruction.
The path specified by 148 0x0094 cannot be used at this time.
149 0x0095 The drive directory you are trying to merge or replace is the target that has already been replaced.
150 0x0096 config.sys file did not specify system tracking information, or the tracking function was cancelled.
15 1 0x0097 specifies an incorrect number of semaphore events.
152 0x0098 do *** uxsemwait not executed; Too many semaphores are set.
153 0x0099 do *** uxsemwait list is incorrect.
154 0x009a The storage medium symbol length limit you entered.
155 0x009b Unable to create another thread.
156 0x009c receives the trip rejection signal.
157 0x009d has been discarded and cannot be locked.
158 0x009e sector has been unlocked.
The address of 159 0x009f thread ID is incorrect.
160 0x00a0 The quoted numeric string passed to dosexecpgm is incorrect.
16 1 0x00a 1 The specified path is incorrect.
162 0x00a2 signal waiting to be processed.
164 0x00a4 system failed to create thread.
167 0x00a7 failed to lock some files.
The resource requested by 170 0x00aa is in use.
173 0x 0ad The locking requirement of the cancellation range is not obvious.
174 0x00ae file system does not support automatic change of lock type.
180 0x00b4 system found an incorrect section number.
182 0x00b6 The operating system cannot execute% 1.
The file 183 0x00b7 already exists. Cannot create the same file.
The flag sent by 186 0x00ba is wrong.
The system flag specified by 187 0x00bb cannot be found.
The operating system of 188 0x00bc cannot execute% 1.
189 0x00bd operating system cannot execute% 1.
The operating system of 190 0x00be cannot execute% 1.
19 1 0x00bf cannot execute% 1 in win32 mode.
The operating system of 192 0x00c0 cannot execute% 1.
193 0x00c1%1is not a correct win32 application.
The operating system of 194 0x00c2 cannot execute% 1.
The operating system of 195 0x00c3 cannot execute% 1.
196 0x00c4 operating system cannot run this application.
The 197 0x00c5 operating system cannot run this application at present.
The operating system of 198 0x00c6 cannot execute% 1.
199 0x00c7 operating system cannot run this application.
200 0x00c8 code segment cannot be greater than or equal to 64kb.
20 1 0x00c9 operating system cannot execute% 1.
202 0x00ca operating system cannot execute% 1.
The 203 0x00cb system cannot find the entered environment option. \r
205 0x00cd is in the instruction subdirectory, and there is no signal sub-processor for any trip.
206 0x00ce file name or extension is too long.
207 0x00cf Ring 2 stack is in use.
People who use the Windows operating system sometimes encounter the following error message: "The 0X00000000 memory referenced by the 0x instruction cannot be written", and then the application closes. If you ask some "experts", the answer you get is often indignation and disdain such as "Windows is too unstable". In fact, this error is not necessarily caused by the instability of Windows. This article will briefly analyze the common causes of this error.
1. The application could not check the memory allocation.
When a program needs memory to store data, it needs to call the "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 the 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 the system sends an error notification to the application. 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 should be taken to save it, which enhances the "robustness" of the program.
If the application does not check this error, it will regard this value as an available indicator allocated to it according to "thinking inertia" and continue to use this memory in subsequent executions. 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 operating system without protection mechanism (such as DOS), writing data to this address will lead to immediate shutdown, 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 "write memory" error mentioned above will appear, and it is pointed out that the referenced memory address is "0x00000000".
There are many reasons for memory allocation failure, such as insufficient memory and system function version mismatch. Therefore, after the operating system has been used for a long time, after installing various applications (including virus programs installed unintentionally) and changing a large number of system parameters and system files, this allocation failure is more common.
Second, the application refers to an abnormal memory pointer because of its own BUG.
In applications that use dynamic allocation, it sometimes happens that the program tries to read and write "should be available" memory, but somehow this expected availability indicator becomes invalid. Maybe you "forgot" to ask the operating system for allocation, or the program itself cancelled the memory at some point and "didn't pay attention" and so on. The logged-out memory is reclaimed by the system, and its access rights no longer belong to this application. Therefore, reading and writing operations will also trigger the protection mechanism of the system. The only final result of the program that tries to "violate the law" is * * * to stop execution 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 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 irresponsibly modify the system, 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 installer of the operating system can copy the correct version of the system file again 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.
When executing some programs, sometimes a memory error prompt appears, and then the program closes.
0x instruction refers to 0x memory. Unable to "read" memory.
The "0x" memory referenced by the "0x" instruction cannot be "written".
I wonder if you have made such a mistake? (The contents after 0x may be different. )
Generally speaking, this phenomenon has many aspects, one is hardware, that is, memory, and the other is software, which has many problems.
Have you installed some software, such as Internet assistant?
I also installed the magic rabbit's internet assistant.
Sometimes it automatically blocks some web pages or something.
It closed as soon as it was opened.
You turn it off and have a try.
Or you have the problem of setting fire to the wall, usually these two problems.
If not, you might as well consider deleting QQ and reinstalling it.
No, it can only be the system, but the possibility that the system is incompatible with QQ is really low.
Why does the perpetual calendar automatically close after it is opened? I use a life calendar with a yellow calendar.
This problem has never occurred, so you can find out.
Why does my firewall automatically close after it is opened? Generally speaking, this is because some programs end anti-virus software programs, especially some viruses and Trojan horses, which will automatically stop the execution of anti-virus software, and some can destroy your anti-virus software. If you don't upgrade frequently, you may be infected with a virus.
Why does Rising Firewall automatically close after it is opened? Probably infected with a virus like AV Terminator. Go to: shadow.baidu./juansha/index.jsp to download a special killing. In addition, try to download tools such as Rising Kaka Assistant Security Guard 360, close unfamiliar programs in the program bar, and kill them. You can also inquire in 360 to install patches for the system. You can also use the above software in safe mode. Clean up your system.
- Previous article:Huang Li's signature.
- Next article:In February 2022, can dragons look up and travel far? What do you mean, the dragon looks up?
- Related articles
- 2002 old almanac query
- Check the moving date in the old calendar.
- Gregorian calendar may 0
- Gregorian calendar 199 1 June 18 night 2 1:47, what are the birthday moon constellations and rising constellations in Deyang, Sichuan?
- 20 16 has a year of the monkey. When is the next year of the monkey?
- lucky day
- Modern yearbook
- Gregorian calendar query1April, 996
- Which version of Gregorian calendar is accurate?
- Can I worship the Bodhisattva with this Buddha?