well lets say this:
my good old GA-AX370-Gaming 5 doesnt worked nice with Ripjaws V - but work totally fine with Trident-Z RGB (with same latency etc)
so changing RAM can help
well it comes in saturday I will update if I crash still, if I am still crashing do you have any recommendations for a mobo I should swap to, I cant rma because I gave my old parts to a buddy so I cant sit without a pc for 1-2 months.
So weird thing I was playing path of exile for literally like a week straight no crashes but as soon as I went to go play warcraft 3 my crashing problem is back. Idk if this helps
The system was running 'stable' with the new RAM until you changed to a different game.
Check your RAM timings in BIOS, to see if the system has determined the correct timings, research the correct timings and update them, although be careful while changing these, as setting the wrong timings, 'can and will lock you out of your system' with a black screen on Bootup!
\*Backup your BIOS to a USB flash drive before making any changes, and use it to flash back to your previous 'stable' timing settings.*\
Also the fact that there is a 'sync' in timings between the RAM and CPU, may be the major issue here. 'Older games', may have an issue to update? I'm not sure?
Good luck with this, as it can be tedious!
I would advise to go to the forums of your RAM manufacturer and seek the correct info from there, usually the correct timings will be on their website.
About every time I crash I can find this error in my Event Viewer
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 0
The details view of this entry contains further information.
Do a surface scan on the system to check for corrupt files:
1. Open a command prompt as Admin.
2 Type SFC /Scannow, then press enter.
If this does not fix the issue, try to re-flash your BIOS. These are the only things I can think to do. Have you reported this issue to Microsoft, I think you should. I found this in Microsoft error reporting forums:
I think you should refer to Microsoft Feedback hub as they will likely have the answer.