Enabling dump files at all times and creating frozen game dump files
-
@Bad:
That could eat lots of fps but it is by purpose
:(. Ok I see what you mean now. That is going to be a problem.
-
No you set it up once. No need to start anything. It just kicks in on application crash.
For enabling WER directly through registry editing or using PowerShell we use
https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm
Gesendet von meinem SM-G930F mit Tapatalk
WER via registry also works, please set dump-type to 2 to get a full dump (note, these are big) as minidumps don’t hold enough data.
https://docs.microsoft.com/en-us/windows/win32/wer/windows-error-reporting:(. Ok I see what you mean now. That is going to be a problem.
WER or DebugDiag won’t eat fps. Application Verifier will. But normally you don’t have to run AV as a normal user.
-
Does
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\Falcon BMS.exe]
work okay (with the space in the exe name)?I suppose I’ll try repro’ing one of the crashes to find out…
-
Does
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\Falcon BMS.exe]
work okay (with the space in the exe name)?I suppose I’ll try repro’ing one of the crashes to find out…
You can indeed set WER in registry. You can choose where you want the dumps. Don’t forget to set it to type 2 for full dumps
-
You can indeed set WER in registry. You can choose where you want the dumps. Don’t forget to set it to type 2 for full dumps
https://i.postimg.cc/xjg6Svb6/image.pngI wonder if there is a way to tweak minidumps to get more info than the standard one – there are many options.
If you guys haven’t looked into it I’ll try to research and see if I can find anything.
In your experience, what does the minidump lack that hampers debugging? Is it lack of the application heap state?
-
I wonder if there is a way to tweak minidumps to get more info than the standard one – there are many options.
If you guys haven’t looked into it I’ll try to research and see if I can find anything.
In your experience, what does the minidump lack that hampers debugging? Is it lack of the application heap state?
Seifer might fill in the blanks, but indeed amongst others the heap. I had a quick peak at custom minidump, but couldn’t see directly how to set it in WER (maybe DebugDiag can?). But if you can look into it, that would be great. Full dumps are rather large indeed.
-
Seifer might fill in the blanks, but indeed amongst others the heap. I had a quick peak at custom minidump, but couldn’t see directly how to set it in WER (maybe DebugDiag can?). But if you can look into it, that would be great. Full dumps are rather large indeed.
You can set it in WER with the CustomDumpFlags reg value. I’ll try to poke at it and see if I can find any good settings. MiniDumpWithIndirectlyReferencedMemory in particular looks useful.
-
The reason we need full dmps is that most of the times, the bug is not trivial. We need to look at other threads, or some memory area from memory areas which contains data that might be related to the CTD.
For example, the network CTD tells only a part of the story. If I had the full dmp, I would be able to reconstruct the whole message and see if it was a bug in the message parser or a network bug.
Once you add a few of those “ifs” to debugging, you are speculating too much to get something useful. Full dmps don’t have this problem.
-
For those brave enough to go into their registry or not wanting to install additional software, you can use the method below. I haven’t tested what happens with DubugDiag2 and registry(WER) enabled, but I would suggest using only one of the options.
Enable dump files even if BMS fails to - without installing additional software
Simply doubleclick the .reg file in this zipfile and reboot to enable dump files being created for the Falcon BMS executable in c:/dump. Note that the resulting .dmp files are huge, so before sharing zip them to reduce them to about 10% of their original size.Or if you want to create the regedits it yourself, follow the steps below and make sure the set DumpType to 2 to get full user dumps that hold enough info for debugging.
-
Launch regedit (start menu, type regedit)
-
navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
-
create LocalDumps keys (right click ‘Windows Error Reporting’)
-
create ‘Falcon BMS.exe’ key and fill them with the items as shown (pick your own dump folder as you like) and reboot
- DumpCount = the number of .dmp files being stored before overwriting the oldest
- DumpFolder = where you want the dump files to appear
- DumpType = set this to 2, other types don’t hold enough info
-
-
First post updated
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-