Ryzen 2700X, Asus Crosshair VI Hero build post issues

[beezischillin]

Dear LTT forums,

I am turning to you because I haven’t exactly found any solution to my problem online.

I have a relatively decent build with a very strange issue.

 

I’m running an Asus Crosshair VI Hero Wifi board with a Ryzen 2700X, two sticks of 16 gig G Skill 3200mhz 14-14-14-34 ram, an Asus Vega64 and a 250 gig Samsung m.2 nVME ssd.

Now this set-up has been more than wonderful for the most part, however ever since Sekiro came out I’ve discovered a pretty serious issue. Towards the end of the game inevitably around the same part my system would hang, throwing up a colored screen and then promply turning off. When I try and turn it on I either a) no video output or b) I get past the ROG logo, wherein a stretched American Megatrends logo appears without any prompt or other text related to bootup. I don’t remember off the top of my head what diagnostic code the motherboard throws, however I know that it’s not in the manual and it’s not an error code, it’s simply supposed to be a bootup step to be passed.  I’m running the latest drivers and BIOS and Windows Update.

 

It’s not necessarily a gaming-related issue but Sekiro’s been the one use case to reliably reproduce this issue.

 

The only solution to passing this screen and ending up with a working computer seems to be to remove all USB devices, press the CMOS Reset button and then plug them all back in. It’s not related to overheating as I have an NH15D keeping the CPU under control while the GPU doesn’t seem to have any issues with heat either. I’ve left a game like Dark Souls 3 to idle for a few hour without any stability issues (thinking that being a predecessor it’s pretty close engine-wise). Windows also idles without issues for days when I normally use this computer as a network storage. I’ve just encountered this issue again while trying to boot memtest86 to try and figure out if it’s a ram issue or not. Under windows 10 everything works perfectly, even a Prime95 and Furmark combination runs perfectly fine for hours.

 

I tried disabling XMP, with the ram running at 2100mhz the same thing happens so it doesn’t seem to be related to any Ryzen platform stability so far. Tried various slots on the motherboard and a combination of either and both sticks.

 

I’m currently booted into memtest86 and running the test to see if I can gleam any useful information out of this.

 

Please tell me that there’s still something to do that I haven’t thought of to figure this out because I’m pretty close to just returning the components and going with an iMac for a desktop just to rid myself of having to deal with this forever.

Thank you and I’m in your debt!

[Turtle Rig]

2 hours ago, beezischillin said:

Dear LTT forums,

I am turning to you because I haven’t exactly found any solution to my problem online.

I have a relatively decent build with a very strange issue.

 

I’m running an Asus Crosshair VI Hero Wifi board with a Ryzen 2700X, two sticks of 16 gig G Skill 3200mhz 14-14-14-34 ram, an Asus Vega64 and a 250 gig Samsung m.2 nVME ssd.

Now this set-up has been more than wonderful for the most part, however ever since Sekiro came out I’ve discovered a pretty serious issue. Towards the end of the game inevitably around the same part my system would hang, throwing up a colored screen and then promply turning off. When I try and turn it on I either a) no video output or b) I get past the ROG logo, wherein a stretched American Megatrends logo appears without any prompt or other text related to bootup. I don’t remember off the top of my head what diagnostic code the motherboard throws, however I know that it’s not in the manual and it’s not an error code, it’s simply supposed to be a bootup step to be passed.  I’m running the latest drivers and BIOS and Windows Update.

 

It’s not necessarily a gaming-related issue but Sekiro’s been the one use case to reliably reproduce this issue.

 

The only solution to passing this screen and ending up with a working computer seems to be to remove all USB devices, press the CMOS Reset button and then plug them all back in. It’s not related to overheating as I have an NH15D keeping the CPU under control while the GPU doesn’t seem to have any issues with heat either. I’ve left a game like Dark Souls 3 to idle for a few hour without any stability issues (thinking that being a predecessor it’s pretty close engine-wise). Windows also idles without issues for days when I normally use this computer as a network storage. I’ve just encountered this issue again while trying to boot memtest86 to try and figure out if it’s a ram issue or not. Under windows 10 everything works perfectly, even a Prime95 and Furmark combination runs perfectly fine for hours.

 

I tried disabling XMP, with the ram running at 2100mhz the same thing happens so it doesn’t seem to be related to any Ryzen platform stability so far. Tried various slots on the motherboard and a combination of either and both sticks.

 

I’m currently booted into memtest86 and running the test to see if I can gleam any useful information out of this.

 

Please tell me that there’s still something to do that I haven’t thought of to figure this out because I’m pretty close to just returning the components and going with an iMac for a desktop just to rid myself of having to deal with this forever.

Thank you and I’m in your debt!

It sounds like a game / video driver issue.  Run DDU "Display Driver Uninstaller" in safe mode and do a clean and reboot.  Then your back up.. Now install latest nvidia WHQL drivers then run the game and see what happens.

[beezischillin]

1 hour ago, Turtle Rig said:

It sounds like a game / video driver issue.  Run DDU "Display Driver Uninstaller" in safe mode and do a clean and reboot.  Then your back up.. Now install latest nvidia WHQL drivers then run the game and see what happens.

Thank you for getting back to me. Installing nvidia drivers will not do anything for me as I own a Vega64. It’s also not a GPU / driver issue from what I can tell as memtest86 crashed the same way (sans colored screen) after trying to boot it during POST.