• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

AM4 B350/X370 black screen crash thread

The only time my PC has a Black screen crash is when I try to run the MS Android EMU, it Black screen crashes every time as it uses Intel HAXM. It’s a real pain as it means I cannot use my AMD PC for some of my work.
Hope MS patch the EMU so it works on AMD PC's or make is so it can be run across a network.
 
Got my new CPU from RMA. Unfortunately (all stock settings) black screen issue is not a plug and play fix. Also swapped to new RAM G.Skill Samsung so my setup should work together as confirmed by many.

Will sit down and tweak tomorrow and this weekend when I have more time. Hope I don't have to replace my motherboard, but it's the only thing I haven't replaced yet....
 
Got my new CPU from RMA. Unfortunately (all stock settings) black screen issue is not a plug and play fix. Also swapped to new RAM G.Skill Samsung so my setup should work together as confirmed by many.

Will sit down and tweak tomorrow and this weekend when I have more time. Hope I don't have to replace my motherboard, but it's the only thing I haven't replaced yet....

What are you typically doing when you get black screen?
 
Had a black screen issue the other day whilst sat on the desktop. Well it was a code 8 hard crash. Only thing I changed was the performance bias from auto/none to Aida.
Disabled that again andhas been on for 48 hours without a hiccup.
 
Had a black screen issue the other day whilst sat on the desktop. Well it was a code 8 hard crash. Only thing I changed was the performance bias from auto/none to Aida.
Disabled that again andhas been on for 48 hours without a hiccup.

It's like a game of some kind :D

Makes me think, I tend to leave it on auto. Maybe should just leave it properly disabled... I can still replicate the display cut-out under occt linpack avx, but as that apppears to be the only thing that causes it, am not too bothered, but will try disabling this and see what happens.
 
It's like a game of some kind :D

Makes me think, I tend to leave it on auto. Maybe should just leave it properly disabled... I can still replicate the display cut-out under occt linpack avx, but as that apppears to be the only thing that causes it, am not too bothered, but will try disabling this and see what happens.

Worth a shot. I'm happy to call mine stable now. It passes everything I can throw at it and apart from that performance bias crash things have been just fine.
 
What are you typically doing when you get black screen?

AVX stress is the fastest way for it to occur (Linpack or ycruncher).

On the new chip/ram, the only setting tested was 3.6 CPU and 2133 ram with all voltages/other settings on auto, so I have some tinkering to do, but it's ridiculous to have to fiddle with it this much out of the box. Won't have time to really sit down with it until Saturday.
 
AVX stress is the fastest way for it to occur (Linpack or ycruncher).

On the new chip/ram, the only setting tested was 3.6 CPU and 2133 ram with all voltages/other settings on auto, so I have some tinkering to do, but it's ridiculous to have to fiddle with it this much out of the box. Won't have time to really sit down with it until Saturday.

Is it just the display cutting out, or a hard crash?

If you are not sure, when you get it, if you unplug display connector and reconnect it, does it come back?

Or, if you can see your board when this happens, do you get a q code error?

If it's just display cutting out, what monitoring software for you have installed?
 
Is it just the display cutting out, or a hard crash?

If you are not sure, when you get it, if you unplug display connector and reconnect it, does it come back?

Or, if you can see your board when this happens, do you get a q code error?

If it's just display cutting out, what monitoring software for you have installed?

Always hard crash, code 8.

I believe I just have the portable installation of HWInfo, and it's not running on startup. Not running HWInfo and Linpack at the same time just to eliminate possibilities. Linpack is running by itself, but Linpack does have a monitor. Ycruncher doesn't have monitoring. No afterburner or other software running at startup.

I'm inclined to think that crashing at default or crashing at a set reduced clock is because of over volting, but can't really test until I start tweaking.

I honestly might just try to get stable for gaming. New game coming out on the 16th so I'm getting down to the wire for what I can actually do to make this thing 'stable'.
 
Yeah, have found overvoltage can be just as much an issue as undervoltage.

If it's hard crash code 8, it's not likely monitoring.

But one thing that oddly caused the most occurrences of code 8 crash for me was moving to a cryorig r1 air cooler.

Went back to my water cooling in the end for my cpu.
 
Yea, it's kind of silly.

I've kept up on your adventures :) it's been a crazy ride for you as well.

I'm on the C6H monoblock from EK. Made sure not to tighten too hard this time around either.
 
Yea, it's kind of silly.

I've kept up on your adventures :) it's been a crazy ride for you as well.

I'm on the C6H monoblock from EK. Made sure not to tighten too hard this time around either.

I know there were issues with EK and backplates - have you investigated that? Something to do with the gasket. They caused this exact issue.
 
I know there were issues with EK and backplates - have you investigated that? Something to do with the gasket. They caused this exact issue.

EK had rubber gaskets on some products back in March, but the issues have been resolved. The gasket that was shipped with my product is a blue paper film material. I believe the original gaskets caused people to not be able to boot at all.
 
Think I'm just going back to stock for a while.

Find settings that pass stress testing, runs fine for a few days, then starts giving crap all over again.

Boards not worth th PCB it's printed on currently in my opinion.
 
Yeah, but now getting black screens with cpu at stock and trying to run ram at rated settings k2933 rather than previous 3066), when just testing with memtest...

It's just ******* ******** at this point.

Was running fine for days at 3. 975ghz and ram at 3066, and the only thing that would cause black screen was occt.

I'm just tired of it.
 
Has anyone tried a board RMA or a different AM4 board recently?

I did some testing last night and have some weird settings 3.7ghz and 3200 ram. 5 hour memtest to 2000% coverage 0 errors. 20 back to back runs of cinebench and instant crashes occt. Still more tweaking to do...
 
It does sound like RAM instability mate. I know you've had it running at 3000 and it might have tested ok at first but I'm sure you aware they need to be left overnight tbh.
I can do 3600 and its gaming/bench stable but it will not pass memory tests.
Give this a go, get your final mem speed and then increase your CPU. Many users are finding that their CPU cannot do both a max OC's at the same time.

https://www.techpowerup.com/memtest64/
 
Back
Top Bottom