Turbo
New Member
- Joined
- Aug 20, 2018
- Messages
- 4 (0.00/day)
| Processor | I5-3470 |
|---|---|
| Motherboard | GA-H61M-D2P-B3 |
| Memory | Unifosa 1333>1600 9-9-9-24 1.6v |
| Video Card(s) | Windforce R9-290 |
| Storage | WD 1TB 7.2k |
| Case | Cougar Archon |
| Power Supply | EVGA SuperNova 750 G2 |
| Mouse | Etekcity Scroll T-142 4000dpi |
| Software | Win10 Pro |
So I had the chance to borrow my brothers 290 and play with crossfire. I was benching and it got hot a lot faster than anticipated, and by the time i was thinking about temps it was already 95C (only a min or two at most though)
I thought, eh, reference cards hit that all the time (my pair are windforce cards), should be fine right? nope
After taking out the second card almost all games had crashing issues upon launch (especially EA games, for whatever reason?)
At first I thought it was an OS or driver issue, but I tried a fresh install of 1703 and 1806 win10, as well as many amd drivers from 14.4 to 18.8.1.
I narrowed it down to it crashing whenever the Vram clocks changed, tried clock blocker and that helped confirm it, everything was fine if the clocks were help up.
So at that point it was either the core or the memory... I remembered multi monitor setups hold the card at full ram clock (at least with the 290s) and so I plugged in a second monitor, and everything started working great...
This pointed towards a memory issue
I edited the bios so the min ram speed was 300mhz, this also failed to remain stable.
Then I threw an extra 50mv at the memory controller, that didnt help either.
So I started thinking about ram timing straps... apparently the first strap is 150-400. So I raised it to 401mhz, just enough to get it to the next strap..
Sure enough, that fixed it! Does anyone have any guesses as to what went wrong? did the MC just decide it doesn't like the tight timing of the low frequency strap?
I thought, eh, reference cards hit that all the time (my pair are windforce cards), should be fine right? nope
After taking out the second card almost all games had crashing issues upon launch (especially EA games, for whatever reason?)
At first I thought it was an OS or driver issue, but I tried a fresh install of 1703 and 1806 win10, as well as many amd drivers from 14.4 to 18.8.1.
I narrowed it down to it crashing whenever the Vram clocks changed, tried clock blocker and that helped confirm it, everything was fine if the clocks were help up.
So at that point it was either the core or the memory... I remembered multi monitor setups hold the card at full ram clock (at least with the 290s) and so I plugged in a second monitor, and everything started working great...
This pointed towards a memory issue
I edited the bios so the min ram speed was 300mhz, this also failed to remain stable.
Then I threw an extra 50mv at the memory controller, that didnt help either.
So I started thinking about ram timing straps... apparently the first strap is 150-400. So I raised it to 401mhz, just enough to get it to the next strap..
Sure enough, that fixed it! Does anyone have any guesses as to what went wrong? did the MC just decide it doesn't like the tight timing of the low frequency strap?
Last edited:
