If the crashes doesn't create any logs, it just means windows can't create them. Usually means hardware problems, something in the computer stopped working to an extent where Windows couldn't collect error info.
The error codes is quite vague, as it can be both the CPU, RAM or the motherboard in need of help.
There is a couple of things you can try, if you haven't done so already:
Update BIOS on the motherboard
Check the XMP profile is loaded correctly in BIOS
Update Chipset drivers for your motherboard
Re-seat the memory
Try to run with one stick of RAM at time, to rule out a stick gone bad
Check Temps on your CPU, maybe it is running too hot, and needs some new thermal paste
Unless you have taken your computer apart recently, no need to check for broken pins on the motherboard
If any CPU or GPU overclocks have been applied, return the values to stock
If none of this yields any results, there is a couple of things you can try to start figuring out if it is hardware of software related.
You could either create Hirens Boot CD, or some other form of Linux Live environment (Like Ubuntu). You could even try to just leave the PC in the BIOS, if the crashes happen when the system is idle. If the crash happens while running in the live OS/BIOS, we can rule out software bugs, and need to focus 100% on hardware problems.
If you changed anything, hardware wise, shortly before this behavior started, maybe that could have been the trigger?
SEISM1C reacted to Tea-Sir in bdos Code: UNEXPECTED_STORE_EXCEPTION
