I don't know what a "standard registered mailer" is, but I can't see how that would determine whether a dump gets taken or not.
A while back, in Windows 8.1, I went through the process described at
https://docs.microsoft.com/en-us/window ... mode-dumps
to ensure that any application that crashes here will generate a dump (and not a mini one, either). The notes I have say that
these days the default (since normal users will have no idea what to do with a dump) is that none are taken.
You can define all-application defaults, in
HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps
or application-specific settings (eg for "pqr.exe") in
HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\pqr.exe
One of the settings is the location into which the dumps will be written. The default is %LOCALAPPDATA%\CrashDumps
but on my system I have changed that to %PUBLIC%\CrashDumps so that dumps taken by either my day-to-day userid
or my admin id will end up in the same place. Provided one isn't worried (eg on a multi-user system) by having dumps
from different users in a place where anyone can read them, the public location is (I think) a better idea.
Note that dumping system processes place their dumps, by design, elsewhere:
- system services' dumps end up in: %WINDIR%\System32\Config\SystemProfile
- network and local services end up in:
%WINDIR%\ServiceProfiles\LocalService and %WINDIR%\ServiceProfiles\NetworkService
Several times per day I scan the whole of %WINDIR% looking for any unexpected dumps - of course I only expect them
to be in these specific locations (plus the system dump location) but not-altogether trusting MS I prefer to look in the
whole of %WINDIR%.
The process where Windows sometimes tells you that something has crashed and that it's "checking for solutions" is
also configurable, in broad terms. Application developers can also use an API to have information from their apps
sent to MS who then collate it (ie from all the people whose app is crashing) and pass it back to the developers.
More info on that at:
https://docs.microsoft.com/en-us/window ... -reporting
Also ...
Whether whole-system dumps (ie after a BSOD) get created is controlled (at least in Win 8.1) from Control Panel -
System - Advanced System Settings - Startup-and-recovery - Settings. Apart from always wrting an eventlog record,
I have "Write debugging information" set to "Complete memory dump" and the location is the default one, ie:
"%SystemRoot%\MEMORY.DMP".
This is what one needs if a BSOD dump is to be any use (eg to an anti-malware vendor). When the dump is taken,
Windows puts data into the pagefile (and for that those MUST be on the %WINDIR% drive), then next time one
boots the system that data is copied out of the pagefile into the MEMORY.DMP file. It follows that for this to work
one's pagefile needs to be big enough - in fact it needs to be bigger than the amount of RAM in your machine. More
info on that at:
https://support.microsoft.com/en-gb/kb/969028