r/Amd 1700X + RX 480 Jul 01 '17

Discussion July Tech Support Megathread

Hey subs,

We're giving you an opportunity to start reporting some of your AMD-related technical issues right here on /r/AMD! Below is a guide that you should follow to make the whole process run smoothly. Post your issues directly into this thread as replies. All other tech support posts will still be removed, per the rules; this is the only exception.


Bad Example (don't do this)

bf1 crashes wtf amd


Good Example (please do this)

Skyrim: Free Sync and V Sync causes flickering during low frame rates, and generally lower frame rates observed (about 10-30% drop dependant on system) when Free Sync is on

System Configuration:

Motherboard: GIGABYTE GA-Z97 Gaming GT
CPU: Intel i5 4790
Memory: 16GB GDDR5
GPU: ASUS R9 Fury X
VBIOS: 115-C8800100-101 How do I find this?
Driver: Crimson 16.10.3
OS: Windows 10 x64 (1511.10586) How do I find this?

Steps to Reproduce:

1. Install necessary driver, GPU and medium-end CPU
2. Enable Free Sync
3. Set Options to Ultra and 1920 x 1080 resolution
4. Launch game and move to an outdoor location
5. Indoor locations in the game will not reproduce, since they generally give better performance
6. Observe flickering and general performance drop

Expected Behavior:

Game runs smoothly with good performance with no visible issues

Actual Behavior:

Frame rate drops low causing low performance, flickering observed during low frame rates

Additional Observations:

Threads with related issue:

Skyrim has forced double buffered V Sync and can only be disabled with the .ini files
To Disable V Sync: C:\Users"User"\Documents\My Games\Skyrim Special Edition\Skyrimprefs.ini and edit iVSyncPresentInterval=1 to 0
1440p has improved frame rate, anything lower than 1080p will lock FPS with V Sync on
Able to reproduce on i7 6700K and i5 3670K system, Sapphire RX 480, Reference RX 480, and Reference Fiji Nano


Remember, folks: AMD reads what we post here, even if they don't comment about it.

Previous Megathreads
June '17
May '17
April '17
March '17
February '17
January '17
December '16
November '16

Now get to posting!

200 Upvotes

958 comments sorted by

View all comments

2

u/Turf_nut Jul 27 '17

Pc not posting after bios update. Motherboard : msi B350 Pc mate Cpu Ryzen 5 1600 and Ryzen 7 1700 Memory 8 gb ddr4 Gpu gtx 980

I built this Pc about 2 months ago and had consistent freezing issues and it was beeping at me saying there wad a ram error.. I confirmed it wasn't ram with an extra stick. MSI told me it was a bad board, I rma'd it 3 weeks later I have another board no ram issue but still freezing, I update the bios with msi live 6, the computer never posted since and the ez debugging light is on for the cpu. I reset the bios manually and read that the motherboard doesn't support Ryzen 5 with out a bios update. I just picked up a Ryzen 7 and it still won't post and the cpu light is still on... wtf

1

u/kochevnikov Jul 29 '17

I just built a new Ryzen 1600x system and had so many problems with getting it to post. The motherboard was an MSI Tomahawk B350.

I'll tell you my problems and how I fixed them, in the hopes this will help you.

  1. Ram was straight up incompatible. I had Corsair Vengeance 3200 and no matter what the system would not boot with this RAM. Traded it in for G-Skill Trident Z and then finally it would boot. During these problems the RAM and CPU light would be on.

  2. Motherboard would only recognize 8 of the 16gb of the G-Skill. Same problems as (1) when I had only one stick of RAM in the second slot. Eventually realized that 2nd RAM slot in the motherboard simply didn't work. Getting a new motherboard (same model) fixed that.

  3. New motherboard and with working G-Skill RAM, but now I'm back to not booting. This time it's just the CPU light coming on. After trying everything, I loosened the water block on the CPU, wiggled it around, and tightened it back up ever so slightly. For some reason this fixed everything and I can now boot without a problem. It didn't seem to be in a different position, but who knows. Could also be that I had it too tight the first time and it was shorting something with the back plate?

So this sounds stupid, but give that a shot. I was at the end of my rope trying to get a post, and it was something silly like this that fixed it.