To be clear, I didn't type all of this up because I expect someone to help me. To the contrary, this is a hobby to me, and I will work through it. However, it seems like the 300/300 problem has reared its ugly head multiple times without a decisive resolution of the underlying cause. I'm just hoping that the info I provided will help tytanick diagnose the problem.
Ok, so changing to gen1 still didnt fixed the problem?
Personally on asrock i see this from time to time but reboot fixes it.
Anyway if you have this problem ober and over then may i ask you to write me a email to [email protected]
It will be easy to debug something that doest work all the time rather tan sometimes
Can you also put in core clock value 5 mem 0 and tell me if that will help? If you put such values then it will be used old script which sets only dpm state and not specific clocjs.
Tell me if it will fix 300 mhz problem
Anyway after that may i please to contact me?
Its also my hobby to fix things