Re: GreySynth
Posted: Sun Aug 18, 2019 8:29 am
Don't forget, those are just typical causes, not the only possible causes. So, if they can be eliminated, the real work can be done. Since your PC is pretty advanced, it may be overclocked. Do you know about that? It is also a possible cause for such behaviour.
As far as I understand, you took care of everything but RAM testing. The quasi industry standard for testing RAM is MemTest86. You download an image that you can prepare a USB stick with, then you start from that stick (alternatively you can also burn a CD and start from that CD).
Here's the link to the website of MemTest86: https://www.memtest86.com/
(And don't feel intimidated. I checked your mainboard, and its UEFI Bios is just fine to use with v5.x)
Windows comes with its own tool as well, but it isn't nearly as precise. However, for completeness I mention it. You would open the start menu then type "mdsched.exe". It wants you to reboot, which you should do. After the test (its just a short one) your PC boots back to Windows. If you couldn't see exactly what the diagnosis concluded, you can view the results by checking the "event viewer".
When RAM is just fine, you culd try to remove parts of the schematic, until it doesn't crash anymore. This way you can isolate the issue. if there is any. But do those tests with 3.0.6, please.
As far as I understand, you took care of everything but RAM testing. The quasi industry standard for testing RAM is MemTest86. You download an image that you can prepare a USB stick with, then you start from that stick (alternatively you can also burn a CD and start from that CD).
Here's the link to the website of MemTest86: https://www.memtest86.com/
(And don't feel intimidated. I checked your mainboard, and its UEFI Bios is just fine to use with v5.x)
Windows comes with its own tool as well, but it isn't nearly as precise. However, for completeness I mention it. You would open the start menu then type "mdsched.exe". It wants you to reboot, which you should do. After the test (its just a short one) your PC boots back to Windows. If you couldn't see exactly what the diagnosis concluded, you can view the results by checking the "event viewer".
When RAM is just fine, you culd try to remove parts of the schematic, until it doesn't crash anymore. This way you can isolate the issue. if there is any. But do those tests with 3.0.6, please.