I've forwarded your ID and MAC addresses to the creator of STOPDecrypter so that he can archive them in case he is able to figure out your decryption key at some point in the future.
I've forwarded your ID and MAC addresses to the creator of STOPDecrypter so that he can archive them in case he is able to figure out your decryption key at some point in the future.

You may have already seen this, but Demonslay335 on the BleepingComputer forums said that this is JSWorm 2.0, and that our decrypter for it has been updated: https://www.bleepingcomputer.com/forums/t/698141/jsworm-ransomware-jsworm-jurasik;-jsworm-decrypttxt-support/#entry4792780
You can find the decrypter here: https://www.emsisoft.com/decrypter/jsworm-20

A lot of the things I saw in the log were missing when the fix was run. There are two likely explanations. Either another tool removed them before the fix was run, or there are infections on the system that keep changing their file names and load points in order to make removal more difficult.
For now, run a Malware Scan with Emsisoft Emergency Kit (EEK) and quarantine anything it finds (do not click "Delete"), and be sure to save the report (you can view it after the scan and then save it from there) when it's done and attach it to a reply. You can download it at the following link: https://www.emsisoft.com/en/home/emergencykit/download/
After running the scan with EEK, please run another scan with FRST and post the new logs in a reply so that I can make sure that everything was taken care of.
Note that if EEK wants to restart your computer after scanning that you should do so before running FRST again.

The dump needs to be saved when the crash happens. If it needs to be caught automatically, then this is the easiest way: https://help.emsisoft.com/en/1772/how-do-i-configure-automatic-crash-dumps-in-case-of-application-failures/

[!] No keys were found for the following IDs:
[*] ID: bwVJLrUFtzutHXui1MCvtQw7baY8jcfIt3avTOVz (.radman )
Please archive these IDs and the following MAC addresses in case of future decryption:
[*] MACs: 82:C5:F2:71:83:C3, 80:C5:F2:71:83:C3, 80:C5:F2:71:83:C2
This info has also been logged to STOPDecrypter-log.txt

Thanks GT500. I followed your advice.
[!] No keys were found for the following IDs:
[*] ID: bwVJLrUFtzutHXui1MCvtQw7baY8jcfIt3avTOVz (.radman )
Please archive these IDs and the following MAC addresses in case of future decryption:
[*] MACs: 82:C5:F2:71:83:C3, 80:C5:F2:71:83:C3, 80:C5:F2:71:83:C2
This info has also been logged to STOPDecrypter-log.txt

Do you mean a pre-emptive dump, when I dump a perfectly working Firefox on the off-chance that something in its dump will show a potential problem, or do you mean doing something (to Windows?) to make sure that next time this happens a full dump is taken? As I said before I'm unaware of these crashes when they happen & there's no dump, that I'm aware of. Even if I monitor the arrival of 'pending' dump submission info in the relevant FF folder, I'm quite likely going to have no idea of even which tab in FF was the problem.