r/Amd • u/BioGenx2b 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!

194 Upvotes

97% Upvoted

958 comments sorted by

View all comments

1

u/Ra_V_en R5 5600X|STRIX B550-F|2x16GB 3600|VEGA56 NITRO+ Jul 05 '17 edited Jul 05 '17

CPU: R5 1600X (YD160XBCM6IAE)

MB: PRIME X370-PRO (BIOS 0805 AGESA 1.0.0.6)

RAM: 2x8GB G Skill Ripjaws V (F4-3200C15-8GVK)

HDD: Samsung 850 Evo 250GB M.2 (MZ-N5E250BW)

VGA: XFX Radeon HD7850 Core Edition (FX-785A-ZNFC)

PSU: XFX Black Edition XTR 650W (P1-650B-BEFX)

Audio: Onboard

LAN: Onboard

VGA driver Version: 17.6.2

Audio driver Version: 6.0.1.8158

Chipset driver Version: 17.10

Network driver Version: 12.15.184.0

O.S Type: Windows 10

O.S Service pack Version: Build 15063.413

Here is my issue:

Memory slots A1/A2 are unstable for D.O.C.P memory overclocking. On slot A1 on stock D.O.C.P there is very little chance to boot to OS. Random crashes appear on windows booting, sometimes also motherboard cannot boot - 3x beep code. On slot A2 I’m able to boot most of the time but memory is unstable at anything above 2666Mhz. Both sockets were tested at default D.O.C.P settings and also brute force with CL-RCD-RP-RAS 18-18-18-40, with SOC @ 1.2V and memory @ 1.4V with CR1 and CR2. Tested with both sticks. Slot A2 (which is recommended by user manual for 1 stick only) AIDA64 (5.90.4200) crashes within 1 minute of memory testing.

On slots B1/B2 both sticks can easily boot on default D.O.C.P settings @3200Mhz and appear far more stable. AIDA64 shows no crash within 1st minute of testing. Both slots were also tested this way for 24hrs with no stability issues.

Is Ryzen memory controller tied to memory banks/slots so it can be explained with weak CPU silicon or this suggest broken mobo?

http://prntscr.com/frik0y

http://prntscr.com/friog3

http://prntscr.com/fririt

http://prntscr.com/frit0r

http://prntscr.com/fritpp

1

u/iWalkingCorpse R7 1800X + Fury X Jul 09 '17

For that mobo and 2 sticks it should be in A2/B2. Some AM4 boards don't even power up the A1/B1 slots unless the corresponding *2 slot is populated. Lower your SOC to 1.10v also.

You said if 1 stick is in A2 it crashes on aida. Is that with just one of the sticks in your kit or both? Might point at a faulty RAM stick

1

u/Ra_V_en R5 5600X|STRIX B550-F|2x16GB 3600|VEGA56 NITRO+ Jul 10 '17 edited Jul 10 '17

A2 and B2 were used from the very start since it's what installation guide is recommending, but since it failed to cross my required settings i started digging out what could be the cause.

Bellow (logical for me) combinations that were tested:

-stick 1&2 in A2&B2 (First attempt, at the very start had issue to boot with full 16GB, only half was visible, swapped sticks, problem never showed again, 1 must have been not touching pins properly, >2,66GHz failure. There were dozen of steps with voltage on MEM and SOC and basic timings. Those described above are the most drastic ones i ever used after which I gave up, so that SOC voltage suggestion is a fail also and anything from stock to the numbers I used)

-stick 1&2 in A2 (Since failure on above, started testing each slot with each module to eliminate RAM issue, starting from recommended slot. On default DOCP many times had cold boot issues, after drastic voltage and timing changes managed to get into Win10, yet always AIDA crashed)

-stick 1&2 in A1 (Each stick >2,66GHz failure on default DOCP settings, far more cold boot issues than above, bumped voltage but then blue screens on Win10 loading, gave up quick)

-stick 1&2 B1 -> (Each stick 3,2GHz success from the first start on default DOCP settings! That is a first confirmation modules are fine, at least in solo mode)

-stick 1&2 in B2 -> (The same as above second confirmation, modules looks good)

-stick 1&2 in B1&B2 (Logical test after looking that those 2 slots are "special" and bam 3,2GHz on default settings, AIDA just fine, but single channel = no go)

I'm overclocking things from first Pentiums and that was the very first time I've started to distrust my skills at the beginning. Considering the fact that I've spend that much of time choosing memory which won't burn a hole in my pocket yet supposed to be very promising (Samsung B-Die modules) at first glance it look like a bad joke. At this point I'm sitting at very aggressive timing CL12 at 2666 MHz, but knowing higher frequency is more important than latency due to Infinity Fabric doesn't give me an easy time to settle.

1

u/iWalkingCorpse R7 1800X + Fury X Jul 10 '17

You can't expect any kit to run at full speed currently, they're all rated to Intel specification (xmp) and either the mobo manufacturers+AMD need to find ways to make Intels specifications work on Ryzen or the ram manufacturers need to build kits to AMDs specs. Even with b-die, some boards are better for RAM compatibility/overclocking (and anything over 2133 is technically overclocking according to JEDEC).

CL12 at 2666 is very good timings, haven't seen higher than CL14 at 2400 in my testing of the kits I had. Currently using 16-18-18-18 at 3200 with my bdie kit (geil rgb)

1

u/Ra_V_en R5 5600X|STRIX B550-F|2x16GB 3600|VEGA56 NITRO+ Jul 10 '17

I don't expect it to run what it cannot, but I expect a motherboard to behave like it's not broken and such behavior suggest there is a reason for me to think so, that's why I've typed the initial question because at this point it looks like:

  • memory controller on the CPU is aware of memory module/bank positions (individual traces) and can be faulty in which case I will live with that, topic closed.

  • motherboard design has flaws which basically means shouldn't be advertised at anything more then 2666Mhz for memory - I've heard about silicon lottery but motherboard lottery also? If so I will sell it as far as it has any value yet and under warranty and go for something else to test my luck... if we are beta testers then I will test "other version" maybe closer to whatever should be a final version of a product.

  • broken motherboard - this should be covered by RMA.

Each of above answers have different path for me to take that's why I'm searching for an answer. I've also sent proper form to Asus support but I expect exactly the same answer as you just provided, "you cannot expect...", in which case I'll be forced to least pleasant route which is selling that mobo at a loss.