Please stop changing things around while we're trying to fix this issue. Each attempt/change will change the system state - which will affect the results of what we're getting.
A memory dump is a picture of the system state at the moment in time when the crash occurred. So, if program A writes to memory owned by program B - nothing will happen until program B tries to access that memory. When program B does access the memory, that's when it'll crash. If program A has exited by this point, then there's no evidence that it caused the crash. This is why the system state is a delicate balance - and we should, at a minimum, be able to observe the same drivers
being loaded throughout the parade of dump files.
FWIW - you can generate a crash dump of a user-mode process by locating the process in Task Manager - Processes tab. Then right click on the process and select "Create Dump File".
As with BSOD's, this is a snapshot of a point in time (of this process). Unless the process has crashed (and hasn't exited yet) there's no sense in doing it. If you're able to catch the process before it exits, use the above steps to generate the dump file. Then upload it and give us the link so we can analyze it.