Question New build: monitor keeps losing input. Is it a problem with my 4090?

[JPrug]

All parts are brand new.

CPU: AMD Ryzen 7 7800X3D 4.2 GHz 8-Core Processor
CPU cooler: Thermalright Peerless Assassin 120 SE 66.17 CFM CPU Cooler
Motherboard: Gigabyte B650 AORUS ELITE AX ATX AM5 Motherboard
Ram: G.Skill Flare X5 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory
SSD/HDD: Western Digital Black SN850X 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
GPU: Zotac GAMING Trinity OC GeForce RTX 4090 24 GB Video Card
PSU: Thermaltake Toughpower GF3 TT Premium 1000 W 80+ Gold Certified Fully Modular ATX Power Supply
Chassis: Lian Li LANCOOL 216 ATX Mid Tower Case
OS: Windows 11
Monitor: Gigabyte M32U 31.5" 3840 x 2160 144 Hz Monitor

My experienced friend helped me put the actual tower together. The build has run successfully for hours at a time, including when it was first built. However, after I moved the build to another location, problems started.

The main issue that I am experiencing is that sometimes the monitor will stop receiving input. This most often happens when I restart the system. The motherboard splash screen shows up and then it fades and I hear the Windows 11 log-in jingle, but then nothing appears on screen. Sometimes the monitor does receive input after a long time of waiting (5+ minutes) and then it can be successfully used but not always. The monitor remains powered even though it does not display anything (it has a flashing idle light).

For a while I thought that it was related to updating the GeForce 4090 GPU to the latest drivers. Whenever I did that, the very next time without fail the next restart would have the aforementioned issue of the monitor not receiving input after BIOS but before Windows (but the Windows sound does play). I'm not sure if Windows is not loading or if Windows had loaded but my graphics card isn't showing me it.

When the monitor loses input, I try holding down the power button, then turning it back on. Usually it continues to fail to get to Windows. I am always able to get to BIOS and have done many (5+) clean Windows re-installations via USB. The boot order is always correct (SSD first) The monitor has lost input a couple of times during Windows re-installations. I have been able to fully update Windows but that has not solved the issue.

I was able to install the second-most recent GPU driver and survive a few restarts.

I found a suggestion to re-seat my GPU, and after I did I was able to survive a restart after fully updating my GPU driver for the first time since the very first build. But then a few restarts later, the monitor losing input issue happened again.

I have tried Windows' Startup Repair and Automatic Repair features and they did not work. Usually I was able to use the USB to system restore to a point before I fully updated my GPU monitor and that would work, but most recently the system restore gave me a warning that "You must always restore the drive that contains Windows. Restoring other drives is optional" but then the drive was greyed out so I couldn't continue and had to do another fresh re-install.

I have had a few Windows blue screens. I think one of them said Critical Process died.

From trying some other suggestions, I verified that secure boot was disabled and that CSM Support is disabled.

Here are some pictures of my BIOS settings:

https://imgur.com/ZHGBURN

View: https://imgur.com/ZHGBURN

https://imgur.com/K2Jaicz

View: https://imgur.com/K2Jaicz


Since those pictures (taken after the issues already started), I was able to successfully fully update the BIOS via Flash to version F8a but the monitor issue has persisted.

Any help would be greatly appreciated.

 

[Lutfij]

Welcome to the forums, newcomer!

However, after I moved the build to another location, problems started.
Could you elaborate on how you moved the system? I'd try and look at the connectors in your build and see if they're all secure.

have done many (5+) clean Windows re-installations via USB
Where did you source the installer for the OS?

For the sake of relevance, did you flash the CMOS after you'd verified that you updated to the latest BIOS version?

 

[JPrug]

Thanks for the welcome!

The build was put together in an open area about 10 feet away from my desk in the corner of the room. I turned off the computer, switched off the power supply, unplugged the power supply, then physically carried everything to the new location. I plugged the power supply back in, switched it on, then powered on the computer. I'll go ahead and turn off my computer and double check all the connectors after posting this reply.

I got the OS from this page on the Microsoft website: https://www.microsoft.com/en-us/software-download/windows11/

I'm not sure what flashing the CMOS means, could you please let me know?

 

[JPrug]

Welcome to the forums, newcomer!

However, after I moved the build to another location, problems started.
Could you elaborate on how you moved the system? I'd try and look at the connectors in your build and see if they're all secure.

have done many (5+) clean Windows re-installations via USB
Where did you source the installer for the OS?

For the sake of relevance, did you flash the CMOS after you'd verified that you updated to the latest BIOS version?

Hi again, I wanted to provide an update on the situation.

I tried installing Windows 10 instead of Windows 11 and that did not resolve the issue.

What does seem to be working is connecting my GPU to the monitor via DisplayPort instead of HDMI. The DisplayPort has worked without issue. To test, I then went back to the HDMI and the lack of monitor input happened again on a restart. When this happened, I then plugged the DisplayPort cable back in and it worked. I then tried a different HDMI cable by itself and the lack of monitor input occurred.

It seems to me like the 4090 is having a problem with its HDMI output.

Edit: I was able to connect my 4090 to an old monitor flawlessly via HDMI. It seems to be a specific interaction between the 4090 and my M32U. One theory is that it's because the M32U has an unusual 144 hz refresh rate. In any case, I don't feel like troubleshooting further and will stick to using DisplayPort.