Yeah, the logs haven't been super useful and the Windows Diagnostic Report Viewer also keeps crashing, seperate software issue I think, so I can't even see what errors that's showing fpr AAPG.exe
I'm on an early R5 1600 with 16GB, 3000MHz Corsair RAM, QVL'd for the MoBo... but yeah I think their were memory issues at launch, but again I haven't seen any before and had this system running 18 months or so before any issues in AAPG. Maybe related to the update/memleak, I'll take a look at the event viewer over the weekend. Right now, back to Witcher3 for a bit.
Ye, think there is your issue.. Same as me, the R5 series has chipset issues with the corsair and pushes the 3000Mhz back to (guessing the number here) around 2666Mhz or even lower depending on the kit which causes horrible performance. Which you can see in Task Manager > Performance > Memory and there you see bottom right your speed.
My guess you will see a lot of Kernell32.dll crashes in event viewer because of this.
The way I fixed it is by going into Bios and load a preset XMP profile, and increase my DRAM VBoot voltage from 1.2 (which is what my kit uses standard) and increased it to 1.3.
WARNING: Going higher then .1 increase can cause hardware damages never go for 1.4.. NOTE: DRAM VBoot comes only with motherboards that support it.
Same for my DRAM Voltage, increased it from 1.2 to 1.25. Than in your case, you could also drop your Memory Frequency from DDR4-2666Mhz to DDR4-2400Mhz. Normally the Bios also come with preset timings like 16-16-16-36, but that should not make a difference, I personally used the first preset to test and since then I had one or two more crashes and it started to work with out crashes.
If you are not sure how to do this all, there are some good tutorials on youtube to watch.
And I cannot stress enough, DRAM VBoot not higher then .1 and DRAM Voltage not higher then .05, going higher can cause boot failures and worse case scenario hardware damage. So be careful with that.
This issue can also be resolved with money by going for a single rank stick kit for the best results which is 2x8GB, anything else will require manual clocking like dual rank kits and 4 stick kits.
Comments
I'm on an early R5 1600 with 16GB, 3000MHz Corsair RAM, QVL'd for the MoBo... but yeah I think their were memory issues at launch, but again I haven't seen any before and had this system running 18 months or so before any issues in AAPG. Maybe related to the update/memleak, I'll take a look at the event viewer over the weekend. Right now, back to Witcher3 for a bit.
Thx for the replies.
My guess you will see a lot of Kernell32.dll crashes in event viewer because of this.
The way I fixed it is by going into Bios and load a preset XMP profile, and increase my DRAM VBoot voltage from 1.2 (which is what my kit uses standard) and increased it to 1.3.
WARNING: Going higher then .1 increase can cause hardware damages never go for 1.4..
NOTE: DRAM VBoot comes only with motherboards that support it.
Same for my DRAM Voltage, increased it from 1.2 to 1.25. Than in your case, you could also drop your Memory Frequency from DDR4-2666Mhz to DDR4-2400Mhz. Normally the Bios also come with preset timings like 16-16-16-36, but that should not make a difference, I personally used the first preset to test and since then I had one or two more crashes and it started to work with out crashes.
If you are not sure how to do this all, there are some good tutorials on youtube to watch.
And I cannot stress enough, DRAM VBoot not higher then .1 and DRAM Voltage not higher then .05, going higher can cause boot failures and worse case scenario hardware damage. So be careful with that.
This issue can also be resolved with money by going for a single rank stick kit for the best results which is 2x8GB, anything else will require manual clocking like dual rank kits and 4 stick kits.