Error encountered during startup: GPU not detected.
Error encountered during startup: GPU not detected.
Hi!
I just built a pc...
The specs:
GPU: MSI 4070 Super Ventus 3x
CPU: Ryzen 5 7600x
MoBo: B650 Eagle
RAM: 2x16 DDR5 Corsair Vengenace ram 6000hz
SSD: nvme wd_black 1tb
PSU: MSI A750GF
CASE: MSI Gungnir 110R
SO: W11 Pro
I also have 2 monitors connected to my GPU, one via HDMI/HDMI cable, the other one via HDMI/DISPLAY PORT cable.
The issue:
In a total random way, at boot, sometimes (let's say 1 over 6-7 boots) the GPU is not recognized.
The rgb on my peripherals (mouse/keyboard) are on, fans are spinning (GPU fans as well), but nothing is shown on the monitors.
I can hear the windows sound from my speakers tho.
The red led on my mobo shows "VGA".
The issue goes away if I restart the pc via reset button on my case. Never happened to have a black screen if I reset the pc that way.
What I tried:
- updated MoBo BIOS (F3)
- cleaned drivers with DDU in safe mode and installed both older and latest drivers again
- reinstalled W11 from scratch
- checked cable connections on GPU (the GPU is connected using 2 8 pin cable -no daisy- to the adapter I found in the box)
- unplug (when black screen happens) one or both the HDMI cables
- plugging one cable to the MoBo directly (and in that case I can see everything but the GPU is then not recognized by any program I have like HWinfo/Monitor)
- install some drivers from the MoBo page like the AMD chipset one
- unplug all the USB peripheral when the issue appears
What I think:
I will exclude a power issue, since the PSU is new (all pieces are brand new from Amazon) and I tested a lot the GPU during those days not only running benchmarks like Cinebench 2024, but also by playing demanding games like Cyberpunk 2077 with Path Tracing on, Dragon's Dogma 2 maxed out, etc. I played for hours with no issues at all, not a single crash or weird temp value (always monitoring).
The only weird response I had from a program was from OBS. Sometimes the GPU usage, normally around 10% (I do use Nvidia Broadcast mostly for the "background blur" feature), goes up to 60-70% in IDLE for no reason.
It only goes away if I restart the pc, going back to a normal value, but then when I again shut it down and boot then there is a high chance I get the "black screen" issue. I don't really understand if those are related somehow.
I also noticed a weird thing. The first thing I do in every pc is to turn off fast boot from OS settings, because I had issues with my old pc. Even both the fast boot and hybernation are off sometimes the pc stays "on" even after shutting it down (it do it very rarely, but it happened). I also noticed that it kept (randomly) rebooting itself after shutting it down. I think I solved this issue by changing a value in the registry editor that was set on "0" (about power at shut down), maybe something changed after the latest W11 update, idk.
Anyway, the random black screen(s) at boot still persist. I can shut it down/reboot like 6-7 times without any issue, or I can have like it happing twice in a row.
Then I noticed something related to Razer Synapse: sometimes when the pc "rebooted" itself after a shut down, or after staying "on" even if I shut it down, the Synapse program had an update. Didn't notice if it was always the case, but surely it did it 2-3 times. Now I stopped the automatic updates tho.
Also, when the pc boots up it usually gives power to my peripherals first (mouse/keyboard/mouse charger/hub) and then to the first monitor where the BIOS splashpage should be visible. Like in a chain. If it doesn't turn on immediately after my keyboard then it won't at all.
The bad thing is that this issue doesn't happen every time, so I can't check properly if there is a conflict between hardware or not (like, idk, trying to boot it with only m/k). It seems totally random (the only thing that seems to have a "regularity" is the OBS issue with the GPU usage, that seems to appear close to the moment I will receive a black screen at boot).
I also had some BSOD (didn't have time to read the error...) before reinstalling W11. Like 2 of them, right after some of the "I turned off the pc but it is still powered" moments.
p.s. about the BIOS setting I didn't touch anything BUT the XMP profile. The first time I used that, then I updated the BIOS again (the first time I installed F2 since F3 was in beta) and since it reverted it to no XMP I then chose the other one (the AMD one, don't remember the name now... anyway, same result).
What I think could be the culprit (but I will be too upset to find...):
- faulty GPU: it works like a charm with every demanding task, it would be absurd to fail at boot...
- faulty PSU: should be powerful enough (also Gold+ certified...) so, idk...
- incompatibilty to XMP/theotherone profile: then I will have my RAM not at its best...
- faulty MoBo: I don't really know how to test it
- maaaaybe the DISPLAY PORT cable? Since the BIOS splashpage is shown on that monitor (I switched the cables, the BIOS switched as well ofc)... but isn't it weird that nothing is shown on the HDMI one (like the windows login screen, that was shown on the other monitor usually)?
- the one cable I didn't connect from the case: the case comes with some rgb fans, and has a board on the back to control them. The board also has a sata port to connecto to the PSU for the power and another cable that I left out, that should be connected to the MoBo in order to controll the rgb via software (and not only via the case front panel like I am doing now). I don't really think this could be the culprit but I prefer to be clear about what I have done with my build...
Thanks
š
Edit1:
Right now again it stayed āonā (lights on, fans spinning, etc) after shut down. I hade to reboot it and then shut down again.
This is getting ridicolous.
The motherboard in question?
https://download.gigabyte.com/FileL...10...ff09835a5c
[Confirm that the user manual is available.]
= = = =
My thoughts and suggestions (in any order):
1) The PSU, simply because it's new, should not be ruled out, as should any other part.
2) PSUs offer three voltage levels (3, 5, and 12) for different system parts. If some components or LEDs seem to work, it doesn't necessarily mean the PSU is working properly.
3) Drivers: Download them directly from the manufacturer's official site. Reinstall and adjust settings. Avoid third-party tools or installers. Make sure you're using the genuine websiteājust because the name appears in the URL doesn't guarantee it's the real manufacturer's site.
4) Intermittent or random issues usually stem from a loose connection. These can appear and disappear due to expansion, movement, or vibrations. Check all connections carefullyācards, RAM, jumpers, and case parts. Case connections can be tricky and often get mixed up.
5) Test with only one monitor for a short period. See if the issue persists. Then try using another monitor to see if it resolves.
6) Be aware that during shutdown Windows might perform updates or other maintenance tasks. This could delay shutdowns and cause problems. If you force a shutdown, it risks data loss.
7) Avoid editing the registry unless you're certain it will fix the problem. Only do this after backing up the entire system, including the registry.
8) Inspect Reliability History/Monitor for any error codes, warnings, or messages recorded just before or during the monitor failures (such as random crashes).
9) Ignore past problems. Many components have changed since then, so issues that were before should now work. Also, ensure all settings and options are properly enabled.
10) Revisit the instructions: "The board also includes a SATA port to connect to the PSU for power and another cable I omitted, which should link to the motherboard to control RGB via software (instead of just using the front panel). I donāt think this is the main cause, but itās good to be clear about what Iāve done with my build..."
Hi.
Yes, this is the motherboard.
1-2) how do I know if the psu is funcional? Under huge stress everything works well, I don't think that the gpu need more power to boot than to run games like Cyberpunk with path tracing on.
3) I installed every driver directly by the official site (nvidia and the mobo ones).
4) I tried to reseat the gpu and looked like it was the issue until the black screen appeared again. Also it was pretty straigthforward to connect everything else tbh, even the front panel cables went ready to connection (no single cables, just one big chunk for audio and another one for the buttons/leds). I will re-check them if other software-related solutions will be non useful...
5) tomorrow I will try that
6) I know that but I think I waited a fair ammount of time. But I have to say that sometimes I got some BSOD (last one said "critical_process_died", but let me reboot and sing in as always). I also did a sfc /scannow and the health check as well, no results
7) the value I edited didn't seem to did anything tho. It was the "powerdownaftershutdown" value, but I got another random reboot-after-shutdown once after that... and that will lead me to another idea: what if is a MoBo issue? In one of the threads I have read about that registry edit a user said that, among other issues, the MoBo was the culprit for the reboots. Could it be my case? I am reading a lot of stuff about the B650 MoBo (not necesarry my model that it is pretty recent) that concerns me.
8) in reliability history there are some critical errors (even hardware ones) but those are not related to every black screen issue I had. What do you mean with "Monitor"?
10) tomorrow I will try to plug it in
-------------
Meanwhile I tried to disable XMP, no effects. Disable synapse on startup and deleting nvidia broadcast. Nothing happened.
I am starting to wonder if this is a true issue... I mean, I can still use my pc I just have to reboot when the screen are blacks... I just don't know if it can be "harmful" for the pc itself.
Maybe I could try to send back both the GPU and the MoBo but I am also strating to think that maybe those two are not compatible? (I am reading that the MSI version of the B650 has an issue with the BIOS with some 4070 cards... maybe it is the same for the Gigabyte ._.). And without knowing if could be the PSU I don't really know if it is a good move... (I bought the parts one week ago, I should have 3 more weeks to send them back to amazon).
The PSU needs to be a reliable one based on reviews, considering the brand and gold certification. At least thatās my hope lol.
I also ran some tests with the PC-monitor cables today.
I performed 10 boot cycles for each test until I encountered an error.
1) With only an HDMI cable connected to one monitor: 10 boot cycles, all successful, no black screen.
2) With two monitors and two cablesāone HDMI and another HDMI/D port cable (different from the previous one). At the second boot, I saw a black screen and the PC stayed "alive" during shutdown.
3) With two monitors and two cables, using the same cables I usually use (switched the D port once). However, I changed the GPU port (there are three, I used the middle one). Again, 10 boot cycles, no black screen at all, but I experienced "PC alive at shutdown" and "auto reboot at shutdown."
I ran an integrity check using DSIM.exe (etc.), which took a few seconds and confirmed: "the operation completed successfully. sfc /scannow found nothing."
As you mentioned, I was careful with the process this time and recorded the boot times for each cycle so I can review them later in an even viewer. Iām not sure where to look now, but if you can help, Iāll share the results.
Now, if I managed to fix the black screen problem, my main goal is to eliminate those odd PC behaviors when it doesnāt shut down properly despite my commands.
Nope, it did it again. Iām getting really frustrated.
On another forum someone claimed I picked the worst 4070 super and that my monitors (C27F390FHU and S24D300H) are unsuitable for my GPU.
They also suggested buying a 460 Ti and two 144Hz monitors, but I donāt need thoseājust a 4060 Ti would be enough to run Cyberpunk with path tracing at 1080p, honestly.
Iām not sure why downgrading is necessary.
Could it really be that an old monitor is the problem? I could keep using the 4070 and switch monitors later if I want.
In any case, could an outdated monitor be the root of my problems?
Identify a consistent testing routine where only the old monitor is changed, or use another functional monitor that can be replaced.
= = = =
Regarding the "worst" scenario, seek out reliable sources, references, reviews to back up strong claims like "this is too bad" or "you absolutely must."
This is particularly relevant if downgrading is being suggested or considered. Downgrading might work only when there are clear reasons for it, such as a temporary workaround until a problematic or corrupted code is resolved.
The person on another forum keeps saying I'm "dumb" because I have a 60hz monitor and should either downgrade or get new ones. They mention needing gsync and that if the GPU reports something like "300," it might mean I'm causing a total desync or something similar. But shouldn't this happen every time I turn on the PC? I don't have a good monitor to swap, not even a 4K model, all my things are from over ten years ago. What I did was remove the "Resizable bar" in BIOS, as it could cause stability problems. I think it might be worth trying.
If the other person in the forum is criticizing you and suggesting things without any solid reasons, Iāll let you decide or consider the worth of those comments.
= = = =
Iām not sure whatās going on. It could be a mistake on my end or something I missed.
Iāll keep trying to figure it out.
= = =
What I understand is that changing the Resizeable Bar might help, but it could also not work.
People might share different ideas about how to proceed.
Search for more details on removing the Resizeable Bar.
Check this link: https://www.nvidia.com/en-us/geforce/new...r-support/
It might be useful, though it could not apply in all cases.
I did not respond to any previous actions. The following points were made: the resizable bar did nothing, and Iām leaving out other matters. Iāve looked into setting a "legacy" status for the PCIe slot, but Iām not really comfortable with that right now.
I also checked the reliability monitor during the time of the black screen. Besides some critical errors like "Windows not shutting down properly," there were no other issues (though some problems appeared with the Cyberpunk 2077 launcherāprobably because I had to restart). In the Windows Event Viewer under "windows logs - system," nothing red or critical was visible for those timings.
Would you suggest checking other tabs in the Event Viewer?
p.s.
The person didnāt really insult me, just said my actions were kind of foolish (maybe a small jab...).
Anyway, he was certain that if Windows is running, the problem isnāt with the GPU but likely with the cable or monitor. It seems like the driver might not recognize the monitors I have, which makes sense since the fans are spinning and the software is running. It looks like a GPU-to-monitor communication issue.
I can understand thisāthereās definitely something about the GPU talking to the monitor(s). If the problem were with my hardware, the OS shouldnāt even start up. That would mean changing my monitor could fix it.
And since I havenāt found anything related to PCs in the logs, itās possible the issue is tied to the monitors themselves.