How to get the program to catch the dump file, MiniDumpWriteDump

Debugging the dump file is simple, double-click to automatically open the vc and then f7 runs.

But there are a lot of things to pay attention to in between.

The file is placed in **.

The dump file doesn't have to be in the location where you compiled it, you can create a new folder to put it.

2。To restore the scene at that time.

You may have to ask, how is it possible, this dump file was sent to me by the user, I can't go to the user's home to debug it, right?

This recovery site does not mean that you have to go to that machine, but that you have to get the binary file corresponding to the dump file.

But the recovery site requires all the binaries to correspond, and you must have those exes and dlls that cause the user to crash. Since it's a program you publish, of course you will have an exe file. So just consider the dll here.

The dump file contains the version numbers and timestamps of all the dll files, so you can be sure to get them somehow. If you can get the best from the user, if it is not convenient, the user will not be able to use the operating system that we usually don't use, so find a machine with a corresponding system will generally have it. But remember not only to keep the file name consistent, but also to check the version and timestamp, if it is different, there is no way to use it.

crashdump:

Restart the computer - press the F8 key, when the boot menu appears, select, set it correctly for the last time, press enter to try.

Or enter safe mode, and then disinfect and restart.

If you can't solve it, reinstall the system.

The dump file is a memory image of the process. You can save the execution status of the program to a dump file through the debugger. The dump file is used by the driver writer to debug the driver, and this file must be opened with a special tool software, such as windbg.

In windbg it can be passed. The dump command saves the dump file of the process. For example, the following command saves the image of the current process as a c: file:dump /ma c:\

The ma parameter indicates that the dump file should contain the complete information of the process, including the memory of the entire user mode, so that the dump file size will be relatively large and the information is very comprehensive. If you don't use the ma parameter, the saved dump file will only contain some important data, such as registers and thread stack space, and the file size will be relatively small, and it will not be able to analyze all the data.

In WindBG, you can open a dump file for analysis via the File Open Crash Dump menu. After opening the dump file, the information and status that you see when you run the debugging command are the status of the process when the dump file is saved. The dump file can be used to easily save the status of the process when the problem occurs, which is convenient for post-event analysis.

Dump is also a data file exported from Oracle and SQL databases. Data can be backed up and later imported.

**BlueScreenView, running it will automatically read C: Windows Minidump *DMP operating system BSOD record dump file.

windbg is a tool that can manually grab dump files, if you want your program to be smarter, when you encounter a crash of your program, you want the program to catch the dump file by itself, and then you can analyze it. Recently, I happened to encounter such a thing, so I looked for it, and with the help of friends on the Internet and forums, I completed such a thing. minidumpwritedump is a win32 api that can accomplish such a thing.

Because I'm using C now, I'm encapsulating it, and I don't know much about hosting ** calling those win apis. So I took the help of some friends.

I'll just post it directly.,Run it and you'll know.,But so far, I've analyzed the dumps caught by this test program.。 In the future, let's analyze it, there is no environment on the machine now.

Reason why dynamic link libraries cannot be targeted1Virus Trojan causes, the more typical virus is the kidnapping Trojan, it is a new type of highly destructive Trojan is different from the traditional virus, it is by kidnapping the system file dll to achieve boot start, the Trojan is mainly manifested, 2

Caused by upgrading a piece of software. Reinstalling the software will resolve the issue. 3.Caused by one's own misoperation.

Repair solution for unable to locate program input points: Software repair: **Install Kingsoft Guard, enter the main interface, enter [Kill Trojan] and then click [Quick Scan] to manually fix the unable to locate program input points.

Method 1 on the Dynamic Link LibrarySearch for the dll you need on the Internet, enter the dll you want into the search box, and pay attention to the safe browsing function of Kingsoft Guardian when searching, so as not to enter the trojan or phishing site due to the problem of not being able to locate the program input point. 2.

Restart the computer shortcut F2 or F8 to enter safe modePut the missing dll to C: Windows System32

You can follow my method to solve the problem, and if it doesn't work, ask me again.

If I don't know if I can enter safe mode? If you can get in, copy it from another normal computer""to your own computer"system32"directory, and then register the file:

Run, cmd

regsvr32 C: Windows sysytem32 (i.e. open a command prompt and enter a command).

Or use the system disc to boot into the installation interface and press the R key to enter"Restore the faulty table", and then enter the command at the command prompt:

cd x:\i386

Expand C: Windows sysytem32 (X-ray drive is on the disk, enter a command and press enter, pay attention to the space) copy is completed, then reboot the system, change to hard disk boot, log in normally.

If you can't do it, you can ask, thank you.

Reason why dynamic link libraries cannot be targeted1Virus Trojan causes, the more typical virus is the kidnapping Trojan, it is a new type of highly destructive Trojan is different from the traditional virus, it is by kidnapping the system file dll to achieve boot start, the Trojan is mainly manifested, 2Caused by upgrading a piece of software.

Reinstalling the software will resolve the issue. 3.Caused by one's own misoperation.

Unable to locate the program input point repair solution: Software repair:**Install Kingsoft Guard, enter the main interface and enter the [Kill Trojan] and then click [Quick Scan] to manually fix the unable to locate the program input point on the dynamic link library Method 1

Search for the dll you need on the Internet, enter the dll you want into the search box, and pay attention to the safe browsing function of Kingsoft Guardian when searching, so as not to enter the trojan or phishing site due to the problem of not being able to locate the program input point. 2.Restart the computer shortcut F2 or F8 to enter safe mode

Put the missing DLLs in C: Windows System32.

Hello landlord, please take a look at this solution.

Hope it helps.

It is a debug tracking related module, which is used to track the work of the process, and collect the stack information when the program produces an exception when the process crashes, so that the developer can analyze it, so as to quickly find out the cause of the program abnormality. Program exceptions are the most frustrating thing for every C++ program, because of their accidental nature, it is difficult to find out the cause of the error. This library can greatly reduce the burden on developers.

Copy the file directly to the system directory

1. Windows 95 98 ME system, copy to the C: Windows System directory.

2. Windows NT 2000 system, copy to C: Winnt System32 directory.

3. Windows XP system, copy to C: Windows System32 directory.

Then turn on "Start-Run-Enter" and press Enter to resolve the error prompt.

For the program, try to run the game with compatibility mode and administrator privileges, operation: Properties Compatibility on the program Check on Run with administrator privileges and use the compatibility mode of XP SP3.

Win2000 is my favorite. However, since entering the dual-core era, win2000 has a lot of problems. For example, the program cannot be located. Wait a minute.

You can consider playing a dual-core patch (but some programs still have problems),It is recommended to change win2003.

Reason why dynamic link libraries cannot be targeted1Virus Trojan causes, the more typical virus is the kidnapping Trojan, it is a new type of highly destructive Trojan is different from the traditional virus, it is by kidnapping the system file dll to achieve boot start, the Trojan is mainly manifested, 2Caused by upgrading a piece of software.

Reinstalling the software will resolve the issue. 3.Caused by one's own misoperation.

Unable to locate the program input point repair solution: Software repair:**Install Kingsoft Guard, enter the main interface and enter the [Kill Trojan] and then click [Quick Scan] to manually fix the unable to locate the program input point on the dynamic link library Method 1

Search for the dll you need on the Internet, enter the dll you want into the search box, and pay attention to the safe browsing function of Kingsoft Guardian when searching, so as not to enter the trojan or phishing site due to the problem of not being able to locate the program input point. 2.Restart the computer shortcut F2 or F8 to enter safe mode

Put the missing DLLs in C: Windows System32.

Exactly the same question as you.

I'm also win10

Also this game.