Computer tips

Computer startup failure stop: 0X00000050 solution There are aspects of this phenomenon, one is the hardware, that is, memory problems, the second is the software, which has many problems.

First, hardware In general, computer hardware is not easily broken. It is unlikely that there will be a memory problem (unless your memory is really a no-ticidation), the main aspects are:

1, the memory is broken (most of the used memory situation)

2, the use of a memory problem with quality problems 3, memory is inserted in the gold finger on the motherboard part too much dust.

4. Use different brands of memory with different capacities, resulting in incompatible situations.

5, the issue of heat in the hyperband. You can use MemTest this software to detect memory, it can completely detect the stability of the memory.

Second, the software principle: memory there is a place to store data called the buffer, when the program puts the data in the buffer, you need the operating system to provide "functional function" to apply, if the memory allocation is successful, the function will be opened up by the new The address of the memory area is returned to the application, and the application can use this memory through this address. This is "dynamic memory allocation" and the memory address is the "cursor" in programming. Memory is not always available and inexhaustible. Sometimes memory allocation fails. When the allocation fails, the system function will return a 0 value. At this time, the return value "0" does not indicate the newly enabled cursor, but the system sends a notification to the application, indicating that an error has occurred. As an application, after each application for memory, it should check whether the return value is 0. If it is, it means that there is a failure, and some measures should be taken to save it, which enhances the "robustness" of the program. If the application does not check for this error, it will continue to use this memory in subsequent executions, as "thinking inertia" considers the value to be the available cursor for it. The true 0-address memory area stores the most important "disruption descriptor table" in the computer system and is absolutely not allowed to be used by the application program. 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. The result is that The application is forcibly closed by the operating system to prevent its error from expanding. At this time, the above-mentioned memory can not be "read" error, and the referenced memory address is "0x00000000". There are many reasons for memory allocation failures, such as insufficient memory and mismatched versions of system functions. Therefore, this allocation failure is more common after the operating system has been used for a long time, after installing a variety of applications (including inadvertently "installed" virus programs), after a large number of system parameters and system files have been changed. In applications that use dynamic allocation, sometimes this happens when the program tries to read or write a piece of memory that should be "available," but for some reason, the expected cursor is invalid. It may be that "forget it" requires distribution to the operating system, or it may be that the program has already logged out of this memory at some point and "not noticed" and so on. The logged-out memory is reclaimed by the system, and its access rights do not belong to the application. Therefore, the read-write operation also triggers the protection mechanism of the system. The only end result of an attempt to “illegal” the program is to terminate the execution and recover all the resources. The laws of the computer world are still more effective and harsh than humans! Cases like this are bugs in the program itself, and you can often reproduce the errors in a specific sequence of operations. The invalid cursor is not always 0, so the memory address in the error message is not necessarily "0x00000000" but other random numbers.

First suggestion:

1. Check if there are Trojans or viruses in the system. Such a program often irresponsibly modifies the system in order to control the system, resulting in an abnormal operating system. In general, information security awareness should be strengthened, and no curiosity should be found on executable programs from unknown sources.

2, update the operating system, so that the operating system installer to re-copy the correct version of the system file, modify the system parameters. Sometimes the operating system itself will also have BUG, ​​pay attention to install the official release of the upgrade program.

3, try to use the latest official version of the application, Beta, trial version will have BUG.

4. Delete and then recreate the files in the Winnt\System32\Wbem\Repository folder: Right-click My Computer on the desktop and click Manage. Under Services and Applications, click Services, and then close and stop the Windows Management Instrumentation service. Delete all files in the Winnt\System32\Wbem\Repository folder. (Create a backup copy of these files before deleting.) Open Services and Applications, click Services, and then open and start the Windows Management Instrumentation service. When the service is restarted, these files are re-created based on the information provided in the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Autorecover MOFs.