johnbl :
cool, if you have your system to save the crash dump and it does not save it. I would suspect that the OS lost access to your drive. on a mostly working system this can happen if a drive does not respond in a certain timeout value (30 seconds). Pretty common issue with certain firmware conditions on solid state drives. The device takes too long to respond, windows resets the SATA port and forces a disconnect but the drive never reconnects and later a critical process needs access to the drive and bugcheck is called. no drive access= no memory dump file and the error logs will also not have been created. (I have seen a system with plenty of memory go for 4 hours before a critical process called a bug check)
Work around for this would be to make sure that hotswapping is enabled for the SATA port that the drive is connected to. this way if windows resets your sata port it will auto reconnect and there will be a event log to show for it. (later you have to figure out why the drive did not respond in time, bad cables connections (thermal issues with cable) , need updated chipset drivers, firmware issues in SSD, these type of things )
after you get your system to bugcheck and make a memory dump. let me know and I will look at it.
Two problems:
1. My motherboard doesn't support hotswapping.
2. I'm not using an SSD.
My system is kind of outdated and a lot of BIOS setting are off limits, because Dell.
If I had the money I would build a new computer, but I have like $4.16 to my name, and at the moment I'm not making any money.