Problems with new Ryzen build

[Shark5060]

Hi,

I've just switched to team Red from my old system (i7 6850K, MSI X99 Godlike) and have problems getting it to run.

Let's start with the hardware:

 

Mainboard: ASUS RoG Strix X570-F Gaming

CPU: AMD Ryzen 7 5800X

RAM: Corsair Vengeance Pro (CMW32GX4M4C3000C15 - using only 2 sticks of this kit - so 16GB total)

Cooler: Fractal Design Celsius S36

PSU: Corsair AX860i

GPU: Nvidia GeForce RTX3080 FE

SSD: Samsung 960 EVO 250GB M.2

Other SSD/HDD: Samsung 850 Evo 500GB, Samsung 860 Evo 1TB, Western Digital WD20EZRZ 2TB

OS: Windows 10 Pro, 64Bit (20H2, 19042.844)

 

I have updated the BIOS of the Mainboard to 3405, which is the most current version available to download.

Currently the CPU is running at 4.3GHz and the memory at "stock" 3GHz (ODCP) - but I've tried running everything on stock as well.

 

Now for my problem:

I've installed everything, and booted up my old windows which worked and installed a bunch of drivers and whatever.

After installing the chipset drivers and rebooting the system my GPU driver was constantly crashing. Windows was giving me a notification saying "forcing to reinstall GPU driver" or something similar (it was in German, so don't know the exact translation). The screen was flashing black every ~30 secs due to the constant driver crashes.

I've then booted into safe mode and used DDU to remove the driver. But after reinstalling it and rebooting the problem was back.

 

I've then installed windows on top of the old version - same issue

Then I've wiped the drive and installed windows fresh. Same problem after installing Chipset and GPU drivers (Nvidia: 461.72).

 

Last I've downloaded the newest chipset drivers from AMD directly (Asus: 2.11.26.106 vs. AMD: 2.13.27.501) but that also did not help.

 

Things to note:

- I've bought the mainboard as "outlet" (meaning it was sent back from another customer for some reason) - so this could be DOA.

-> I have ordered a new board from Amazon, which will arrive on monday for testing, but I wanted to make sure I didn't fck something else up ... I know Ryzen can be a bit picky.

 

- I have not tried installing windows with ONLY the M.2 SSD installed without the other drives attached

-> is this something I should try?

 

- I have not tried different RAM, mainly because I don't have any at hand.

-> Does someone know if the RAM mentioned above is incompatible? The 16GB Version with 3600 is listed on the QVL, but not my specific version/speed.

 

If anyone has anything I can try in the meantime - or if the new board doesn't fix my issue - please let me know.

 

Thank you.

[Skiiwee29]

Try moving the card to the 2nd PCIE slot and see if the crashing continues there. 

[Shark5060]

Oh I actually tried that. Sorry, forgot to mention it.

The crashing stopped for a while, but after 3-4 reboots (installing other drivers, like Sound, LAN, etc) and setting up Office365 the crashing started anew.

 

Also the 2nd PCIE Slot only runs at 8x speed - not sure if this detail matters.

[Shark5060]

Reddit suggested installing a previous GPU driver version and uninstalling chipset drivers. Tried both with no difference.

I could try reinstalling windows without ever installing chipset, but I'll do that anyways once the new board arrives.

[Random_Animator]

I'm having a similar issue, switched from intel 5820k to amd 5950x and my gpu drivers have been crashing constantly, i also tried a DDU, fresh windows install, updating the BIOS. Every time i did one of these changes, it was stable for a day or two but then starts crashing again.

[Shark5060]

I have just re-plugged the PCIE Power cables on both my PSU and GPU (and the shitty adapter cable that NVIDIA uses) and also removed the Riser cable from the case ... it's working for now. I don't say that fixed it yet, because I had similar behaviour before and it crashed after a couple reboots again.

[Shark5060]

okay, calling it done. It was the PCIE Riser cable.

Got the new mainboard today and tested it with and without the cable - and yeah, even the new one doens't like to play nicely with the cable ... so it's probably shot.

 

Thanks y'all for your help.