Unable to debug dmp files created in Windows 10

We have replicated the issue listed in this forum post and have been unable to debug crashes on Windows 10 systems with the Fall Creator’s update. We have also verified that we are able to debug crashes created with the same executable on a system that does not have the Fall Creator’s update.

Steps to reproduce:

  1. Create a C++ project

  2. Add a class with a method that causes a crash. The following snippet will cause a memory exception:

    *((int *)0) = 0;

  3. File > Package Project > Packaging Settings. Ensure “Include Debug Files” is enabled.

  4. Build and run your game. Trigger the crash on a system with the Windows Fall Creator’s update.

  5. Open the dmp file with Visual Studio. The dmp file can be found at “[buildDir]/WindowsNoEditor/[yourGame]/Saved/Crashes/…”.

  6. Click “Set Symbol Paths”. Provide the path to the pdb file created in step 4. This can be found next to your exe in “[buildDir]/WindowsNoEditor/[yourGame]/Binaries/Win64”. Then click “Debug Native Only”.

  7. Notice you get an error loading the executable for your game and can not debug the dmp file. If you generate the dmp file on a system without the Fall Creator’s update you can debug it no problem.

We are not having trouble generating good dmp files with other Windows Native applications therefore there is reason to believe that this is a bug in the Unreal Engine.



PS if this is not the correct place to report a bug, can someone please point me to the correct location?

1 Like

We’re having the same issue, we’re getting crash dumps sent to us automatically by customers and we’re not able to open any of the .dmp files in Visual Studio if the customer is running the Fall Creator’s update.

Hey everyone,

We’ve actually just switched over to a new bug reporting method using a form that contains a template of necessary info, which you can read more about here: Unreal Engine Bug Submission Form - Announcements - Unreal Engine Forums

However, in this particular case, I’d like to attach files that are publicly available. We ran into this issue internally, and one of our developers was able to work around the issue, which Microsoft are currently looking into as it seems to be a regression on their end.

Attached are the necessary Pre-FCU debug dll’s. Copying them alongside your executable should allow the minidumps to work again.

link text

Hey Sean, thanks for the reply!

The problem with the workaround of using these pre-FCU DLLs is that the game will no longer run on Windows 7 or, presumably, on Windows 8 machines. It definitely doesn’t run on Windows 7 until we remove those DLLs.

There may be an older version of those DLLs that works on all platforms (I’m investigating now), but I wanted to let you know that, unfortunately, using these DLLs only works if you’re on a Windows 10 machine.

Sorry for the extended delay on this. Could you try placing Windows SDK versions of the dbghelp dll’s alongside executables to see if that fixes it on Win7?

One of our developers has tested these on Win10 & Win7 and this appears to resolve the issue in the meantime until a fix is available from Microsoft.

link text

Hi, any news on this problem? Several months seem an awful long time for microsoft to fix such a severe bug…

f your pc crashes, how can you discover what took place, fix the difficulty and it save you it from happening again? you can discover the small memory sell off file beneficial in this situation. The small memory sell off file carries the smallest quantity of beneficial information that might assist you pick out why your laptop crashed. The reminiscence unload file contains the subsequent statistics:
The prevent message, its parameters and other records
A listing of loaded drivers
The processor context (p.c.) for the processor that stopped
The technique records and kernel context (EPROCESS) for the technique that stopped
The system facts and kernel context (ETHREAD) for the thread that stopped
The Kernel-mode name stack for the thread that stopped
To create a memory unload file, home windows calls for a paging document on the boot quantity this i

To configure startup and recuperation alternatives to apply the small reminiscence dump record, observe these steps.

information icon observe because there are several versions of Microsoft windows, the following steps can be distinctive on your pc. If they’re, see your product documentation to finish those steps.
click start, and then click on control Panel.
Double-click system, and then click on advanced machine settings.
click on the superior tab, after which click Settings underneath Startup and recuperation.
in the Write debugging information listing, click on Small reminiscence unload (64k).
Startup and healing - Small memory dump dialog container
To change the folder place for the small memory unload files, kind a new route within the dump file box (or in the Small sell off listing field, relying for your model of home windows).
Bluestacks TextNow Photomath

So which dlls are we supposed to ship with?

I want to be able to debug dmp files generated on windows 7, 8, and 10 machines.

If I ship with the dbgeng.dll and dbghelp.dll from the win7-sdk zip will I be able to debug crashes from windows 10 too?

Do I have to ship with different dlls depending on which version of windows they are on? This seems very sloppy, can someone clarify this for me?

Thank you!

Download both of the zips posted above, then put the 2 dlls from the win 7 version and the missing one from the other. So far it is working perfectly for win 7-10.

Thank you Zeblote!

Hi Sean, do you have news on this ? It’s been quite some time and this is quite a big issue.

Hi, I’m encountering the described issue and would like to try your workaround but the attached files are no longer available. Where can I find the pre-FCU dlls now?