New Build - Weird Issue

[Broth3rz]

Everything seems to have been running good but I have this one issue...and it seems pretty serious.

So I'll be doing whatever, whenever, then everything locks up for 1 second, my screen goes black, for 1-3 seconds, screen comes back on like it the input was just switched because it says Displayport 1 at the top, then all seems good.. but then my sound doesn't work until I restart, only after this issue. I don't know how MUCH locks up, I know I can't move the mouse when it starts to happen. I haven't had any audio playing when it does it to see what it does with that. But audio is gone after it does it anyway.. I guess it cuts out?

 

I thought maybe it was the display cable before I noticed it would lock up, and so I have a new one, still have the issue. It seems to be completely random..

I have 2 Logitech speakers plugged into my green port on my motherboard, but I do also have a Motu M4 audio interface that is connected through USB Type-C for my 2 other studio speakers.

 

I heard Windows does black screen stuff?

Since it is locking up that rules out the monitor, and the display cable. It seems to be loosing signal, but what signal I'm not sure. Could RAM do this? I did notice 1 stick had the heatsink kinda pulling off some, but that shouldn't do this?

There was a bent pin on my motherboard for the USB 3 slot, I bent it back and all was good, plus I'm not using the front I/O ports for anything, let alone my mouse or anything that locks up... I don't know what this is.

 

Specs:
ASUS Dark Hero

WD 850 1TB, WD 850 2TB, 4TB WD Black HHD

RTX 3070 Aorus

AMD 5900x

128GB G.Skill Trident Z Neo.

Seasonic PRIME TX-850

SAMSUNG 49-Inch CRG9

Windows 10 Enterprise LTSC

Any ideas?

[TylerDurden!]

3 minutes ago, Broth3rz said:

ideas

is the windows install NEW too?

[RONOTHAN##]

3 minutes ago, Broth3rz said:

Everything seems to have been running good but I have this one issue...and it seems pretty serious.

So I'll be doing whatever, whenever, then everything locks up for 1 second, my screen goes black, for 1-3 seconds, screen comes back on like it the input was just switched because it says Displayport 1 at the top, then all seems good.. but then my sound doesn't work until I restart, only after this issue. I don't know how MUCH locks up, I know I can't move the mouse when it starts to happen. I haven't had any audio playing when it does it to see what it does with that. But audio is gone after it does it anyway.. I guess it cuts out?

 

I thought maybe it was the display cable before I noticed it would lock up, and so I have a new one, still have the issue. It seems to be completely random..

I have 2 Logitech speakers plugged into my green port on my motherboard, but I do also have a Motu M4 audio interface that is connected through USB Type-C for my 2 other studio speakers.

 

I heard Windows does black screen stuff?

Since it is locking up that rules out the monitor, and the display cable. It seems to be loosing signal, but what signal I'm not sure. Could RAM do this? I did notice 1 stick had the heatsink kinda pulling off some, but that shouldn't do this?

There was a bent pin on my motherboard for the USB 3 slot, I bent it back and all was good, plus I'm not using the front I/O ports for anything, let alone my mouse or anything that locks up... I don't know what this is.

 

Specs:
ASUS Dark Hero

WD 850 1TB, WD 850 2TB, 4TB WD Black HHD

RTX 3070 Aorus

AMD 5900x

128GB G.Skill Trident Z Neo.

Seasonic PRIME TX-850

SAMSUNG 49-Inch CRG9

Windows 10 Enterprise LTSC

Any ideas?

Try running DDU, weird black screens are usually a GPU issues, and driver issues are the easiest thing to diagnose with GPUs

[Broth3rz]

6 minutes ago, TylerDurden! said:

is the windows install NEW too?

Everything is new so the install is new. First time on W10 really.

6 minutes ago, RONOTHAN## said:

Try running DDU, weird black screens are usually a GPU issues, and driver issues are the easiest thing to diagnose with GPUs

I guess I could get rid of the driver and reinstall, I think I used the Studio Driver since I'm not really into gaming. Do you think the driver could be the issue? Should I get the Game Ready driver?

 

But remember it's not just a black screen, it seems to completely lock up FIRST, for a second or so before the black screen. That would lead me to it not being the GPU unless the driver is locking up my Windows, is that a thing?

[RONOTHAN##]

4 minutes ago, Broth3rz said:

Everything is new so the install is new. First time on W10 really.

I guess I could get rid of the driver and reinstall, I think I used the Studio Driver since I'm not really into gaming. Do you think the driver could be the issue? Should I get the Game Ready driver?

 

But remember it's not just a black screen, it seems to completely lock up FIRST, for a second or so before the black screen.

The game ready and studio drivers are basically the same thing, with the studio drivers basically just not getting day 1 compatibility with new games, so the only way this would really cause an issue is if you had issues playing Cyberpunk. It could very easily be a driver issue, as they can cause some really funky problems. Besides, its a lot easier to test a driver issue than it is to check if your graphics card is bad

[Broth3rz]

Just now, RONOTHAN## said:

The game ready and studio drivers are basically the same thing, with the studio drivers basically just not getting day 1 compatibility with new games, so the only way this would really cause an issue is if you had issues playing Cyberpunk.

I don't game at all apart from Path of Exile and I haven't even played since I got the PC, I don't play it much. So no gaming honestly. So do you think I should still try the reinstall of the driver?

[RONOTHAN##]

Just now, Broth3rz said:

I don't game at all apart from Path of Exile and I haven't even played since I got the PC, I don't play it much. So no gaming honestly. So do you think I should still try the reinstall of the driver?

Yes, with DDU. You want to hope its a driver issue, because otherwise it would mean you have a hardware issue, and getting new hardware now is extremely difficult.

[RONOTHAN##]

After you try drivers, run memtest to see if maybe one of your Ram sticks is bad, as a failing ram stick can also cause weird hardware issues.

[Broth3rz]

1 hour ago, RONOTHAN## said:

Yes, with DDU. You want to hope its a driver issue, because otherwise it would mean you have a hardware issue, and getting new hardware now is extremely difficult.

I reinstalled the NVIDIA Studio Drivers. We will see if that changing anything.

1 hour ago, RONOTHAN## said:

After you try drivers, run memtest to see if maybe one of your Ram sticks is bad, as a failing ram stick can also cause weird hardware issues.

I ran 1 pass of memtest86 and it had no errors, but I wasn't about to sit there another 3-4 hours to do the other passes.

 

Now when I do memtest86, should I run with only 1 RAM stick in, or all 4? I will run it again and let it do ALL 4 passes later today, but as far as I can see it had no errors on 1 pass, so it's most likely okay?

I will see if the driver does anything in the meantime. But if it's not the drivers or RAM, what else could it be? The motherboard? Because I do lock up before the black screen.

[RONOTHAN##]

1 minute ago, Broth3rz said:

I reinstalled the NVIDIA Studio Drivers. We will see if that changing anything.

I ran 1 pass of memtest86 and it had no errors, but I wasn't about to sit there another 3-4 hours to do the other passes.

 

Now when I do memtest86, should I run with only 1 RAM stick in, or all 4? I will run it again and let it do ALL 4 passes later today, but as far as I can see it had no errors on 1 pass, so it's most likely okay?

I will see if the driver does anything in the meantime. But if it's not the drivers or RAM, what else could it be? The motherboard? Because I do lock up before the black screen.

I would run it with all 4 stick, so if there is an issue with your ram, it'll show up and you can then go stick by stick to find it. A motherboard issue is the next most likely. Try updating the bios, or just reflashing the current bios if it is the newest version. 

[Mark Kaine]

most likely motherboard or display cables... 

 

 

you can try to remove *everything* the pc does not need to run, that means mostly all you weird speakers and adapters you might have etc... and see if the issue persists. 

 

Also, obviously, different cables. Preferably HDMI. 

 

 

[Broth3rz]

Alright, so, I ended up returning half my RAM because 1 stick would always stay orange and not match the other 3 RGB wise, and on another stick the heatsink was pulling off. So I'm at 64GB right now, I ran the memtest86, took 8 hours and 31 minutes. It couldn't have had better results because EVERYTHING was 0. No errors or anything.

 

Now after removing half the RAM the issue did happen 2 times quite close to each other, lock up, black screen, comes back, no sound, have to restart for sound to come back.

 

So my RAM is rated to run at 3600Mhz... but I just dropped it down to the default 2666Mhz to see maybe even though they show no errors, they are running unstable because of the Mhz? Or would memtest86 show me if they had no errors but were unstable?

 

I just dropped the RAM so I will update if the issue happens again. So its not the monitor, DP cable, drivers and it seems likely its not the RAM, will update on that part.

 

But I guess it could be anything? Spike in the PSU? Video Card? I'm not sure. But if the lockup problem persist what should I try next? Switch out the GPU?

 

NOTE: When I did BIOS flash in the beginning it got to the 'don't turn the PC off' screen and it automatically shut off getting half way through that line reading wise and ALL my RGB was on, 4 fans, RAM, CPU, motherboard, etc, but the PC was making NO SOUND, the fans weren't running even though the RGB was on, it was very weird. I let it sit for quite some time then used the power button to shut it down and it was fine. So I'm scared to re-flash the BIOS, but it says the version is up to date, don't know if that would case this lockup issue? I don't know anymore..