Black Screen on Boot When Enabling UEFI Mode – GTX 1650 + MSI B360M Bazooka

[albertcou]

Hi everyone,

I'm running into a strange issue and would really appreciate any insights or suggestions.
System Specs:

• GPU: GALAX GeForce GTX 1650 4GB GDDR6 EX (1-Click OC) Dual Fan
• CPU: Intel Core i5-9400F
• Motherboard: MSI B360M Bazooka (BIOS version 7B24v2D)
• Display Output: HDMI (connected to the GPU)
• RAM & other components: Functioning properly

The Problem:
When I switch the BIOS from Legacy to UEFI mode, the display goes completely black during boot. I don’t get a POST screen or BIOS splash — it stays black until Windows finishes loading, at which point everything displays normally.
If I reset the BIOS to default (Legacy mode), everything works again, and the display during boot returns. The issue occurs whether Secure Boot is enabled or disabled.
To summarize:

• Legacy BIOS mode: Everything works normally, including boot display
• UEFI mode (with/without Secure Boot): Black screen during boot; no POST or BIOS screen
• Once Windows loads: Display is normal

Troubleshooting Done:

• Updated BIOS to the latest version available from MSI
• Tried different HDMI cables
• Followed NVIDIA’s firmware update instructions, but the firmware tool reports no compatible firmware found for my GTX 1650
• Cleared and reset BIOS settings

Additional Note:
While using UEFI mode and booted into Windows 11, the BIOS displays a message saying "No driver found" under the iGPU section — not sure if it's relevant since the i5-9400F lacks integrated graphics.

---

Questions:

1. Has anyone experienced a similar issue with this motherboard or GPU?
2. Are there any BIOS settings I may have overlooked that affect UEFI display output?
3. Could this be a compatibility issue between the GTX 1650 and UEFI on the B360M Bazooka?

Any help or advice would be greatly appreciated. Thanks in advance!

 

[StViolenceDay]

Have you another decrete GPU to test if the problem is GPU-specific or not?

Maybe motherboard somwhow thinks that a display is also attached to intergated GPU and thinks it outputs picture there.
Try to disable some iGPU-related functions in the BIOS to make it auto-disabling when descrete GPU is connected (setting may be named like Hybrid mode when both GPUs are active)

 

[albertcou]

Have you another decrete GPU to test if the problem is GPU-specific or not?

Maybe motherboard somwhow thinks that a display is also attached to intergated GPU and thinks it outputs picture there.
Try to disable some iGPU-related functions in the BIOS to make it auto-disabling when descrete GPU is connected (setting may be named like Hybrid mode when both GPUs are active)

Thanks for your response,
Unfortunately, I don’t have another GPU at the moment besides the one I’m currently using, and right now there’s only one GPU installed on the motherboard.

Just a bit of extra info (probably not too important) — I used to run an RX 570 or 580 (I kinda forgot which one), and back then, when the GPU was still working fine, UEFI seemed to run normally without any issues. But that card is already broken now, and I’ve replaced it with a GTX 1650. Also, I’ve already removed the old AMD drivers using DDU to make sure there are no leftovers from the previous GPU.

 

[_roman_]

It may be graphic card related - i think they call it uefi - gop.
... Graphics Output Protocol (GOP) mode protocol in accordance with the Windows HLK requirements.

I think the graphic card is too old

my msi mainbaord gives a warning for a unsupported not gop capeable graphic card according to the manual.

 

[r.h.p]

maybe you need to convert the drive to GPT before you can change to UEFI ...

 

[Vincero]

What is your monitor resolution (natively - not what you run it as - outside of the OS where you can set whatever resolution you want, at POST time the graphics card will only see the native resolution)?

Some early graphics cards with UEFI GOP support struggle to work properly with monitors using resolutions that are seemingly in excess of their capability. E.g. some Kepler cards with UEFI support can't handle 1440P displays properly when using GOP for POST/BIOS/Setup routines - outright refusing to work with it on DisplayPort and only with HDMI and what seems like badly scaled screen output.

If you have a dumber / crappier monitor to hand, try that out.

 

[albertcou]

It may be graphic card related - i think they call it uefi - gop.
... Graphics Output Protocol (GOP) mode protocol in accordance with the Windows HLK requirements.

I think the graphic card is too old

my msi mainbaord gives a warning for a unsupported not gop capeable graphic card according to the manual.

Hmm, interesting. From what I’ve seen on most forums, the GTX 1650 should support UEFI by default.

maybe you need to convert the drive to GPT before you can change to UEFI ...

I’m not on my personal PC right now, but I can guarantee all my drives—both HDDs and SSDs—are using GPT partitions.

What is your monitor resolution (natively - not what you run it as - outside of the OS where you can set whatever resolution you want, at POST time the graphics card will only see the native resolution)?

Some early graphics cards with UEFI GOP support struggle to work properly with monitors using resolutions that are seemingly in excess of their capability. E.g. some Kepler cards with UEFI support can't handle 1440P displays properly when using GOP for POST/BIOS/Setup routines - outright refusing to work with it on DisplayPort and only with HDMI and what seems like badly scaled screen output.

If you have a dumber / crappier monitor to hand, try that out.

I'm currently using a Samsung 24" Curved Monitor (C24F390FHE), and according to the official Samsung website, it supports a resolution of 1920 x 1080 (Full HD). So I believe the monitor itself should be fine.

At the moment, I don't have an additional monitor to test with, but I don't think the issue is with the monitor. The reason is that, in the BIOS menu, the integrated GPU (iGPU) is showing a message like "No driver found" or something similar. That makes me suspect the problem might be related to the iGPU or its drivers, not the monitor.

 

[Vincero]

Hmm, interesting. From what I’ve seen on most forums, the GTX 1650 should support UEFI by default.


I’m not on my personal PC right now, but I can guarantee all my drives—both HDDs and SSDs—are using GPT partitions.


I'm currently using a Samsung 24" Curved Monitor (C24F390FHE), and according to the official Samsung website, it supports a resolution of 1920 x 1080 (Full HD). So I believe the monitor itself should be fine.

At the moment, I don't have an additional monitor to test with, but I don't think the issue is with the monitor. The reason is that, in the BIOS menu, the integrated GPU (iGPU) is showing a message like "No driver found" or something similar. That makes me suspect the problem might be related to the iGPU or its drivers, not the monitor.

Well, if the monitor is connected via the Geforce card, it matters not if the iGPU UEFI GOP software is present or not. In theory the BIOS should load the Geforce GOP module.

One other thing to check is that the primary graphics adapter is set to the PCIe slot instead of IGP in the BIOS settings.

I mean it's a CPU without functioning IGP so the BIOS should essentially treat the IGP as a null device..... But it's not like there isn't a potential flaw in the software.

 

[_roman_]

Hmm, interesting. From what I’ve seen on most forums, the GTX 1650 should support UEFI by default.

Igorslab Igor had a german text ages ago about graphic cards not working on intel.

I tested a MSI 960 GTX 4GB card early 2023. I was selling my am4 to switch in may 2023 to am5. 960 GTX had issues in windows 10 pro. Double or three time display initialisation in windows. I flashed form nvidia the update. did not work. gnu userspace required a recompile on every update. I doubt this has changed in past two years.

I would get something newer or equal, not older, as the date of introduction and technology as a Radeon 6600XT.

-- It has a reason why MSI has half a page in the manual of my fresh purchased maninboard from last week. MSI has no paper manual, that mainboard manual is poor.
They only do that to point their low paid, low knowledgabe customers and support stuff to that section of the mainboard manual. It seems much more common as expected.

I suggest you may try to borrow RAdeon 6600XT or newer from someone and try again.

Note:
[ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.B0 04/24/2025


Post could be fine. Post has nothing to do if graphic output does not work because of faulty firmware of the grapic card, firmware of the monitor, firmware of the mainboard, display cable - type and qualiity
It's easier for myself to determine post, as i still use old samsung hdd for trash file. It's easier to determine when the box starts with post during boots.

 

[eidairaman1]

Igorslab Igor had a german text ages ago about graphic cards not working on intel.

I tested a MSI 960 GTX 4GB card early 2023. I was selling my am4 to switch in may 2023 to am5. 960 GTX had issues in windows 10 pro. Double or three time display initialisation in windows. I flashed form nvidia the update. did not work. gnu userspace required a recompile on every update. I doubt this has changed in past two years.

I would get something newer or equal, not older, as the date of introduction and technology as a Radeon 6600XT.

-- It has a reason why MSI has half a page in the manual of my fresh purchased maninboard from last week. MSI has no paper manual, that mainboard manual is poor.
They only do that to point their low paid, low knowledgabe customers and support stuff to that section of the mainboard manual. It seems much more common as expected.

I suggest you may try to borrow RAdeon 6600XT or newer from someone and try again.

Note:
[ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.B0 04/24/2025


Post could be fine. Post has nothing to do if graphic output does not work because of faulty firmware of the grapic card, firmware of the monitor, firmware of the mainboard, display cable - type and qualiity
It's easier for myself to determine post, as i still use old samsung hdd for trash file. It's easier to determine when the box starts with post during boots.

Pretty strange, i used a XFX Radeon R7 250X Ghost in the Ryzen 7 5800 Rig i built in 21, Steel Legend Mobo

 

[albertcou]

Well, if the monitor is connected via the Geforce card, it matters not if the iGPU UEFI GOP software is present or not. In theory the BIOS should load the Geforce GOP module.

One other thing to check is that the primary graphics adapter is set to the PCIe slot instead of IGP in the BIOS settings.

I mean it's a CPU without functioning IGP so the BIOS should essentially treat the IGP as a null device..... But it's not like there isn't a potential flaw in the software.

Hmm, are you referring to the fact that I’m using an Intel i5-9400F? But the thing is, I was using an RX 580 before and everything worked just fine.

Igorslab Igor had a german text ages ago about graphic cards not working on intel.

I tested a MSI 960 GTX 4GB card early 2023. I was selling my am4 to switch in may 2023 to am5. 960 GTX had issues in windows 10 pro. Double or three time display initialisation in windows. I flashed form nvidia the update. did not work. gnu userspace required a recompile on every update. I doubt this has changed in past two years.

I would get something newer or equal, not older, as the date of introduction and technology as a Radeon 6600XT.

-- It has a reason why MSI has half a page in the manual of my fresh purchased maninboard from last week. MSI has no paper manual, that mainboard manual is poor.
They only do that to point their low paid, low knowledgabe customers and support stuff to that section of the mainboard manual. It seems much more common as expected.

I suggest you may try to borrow RAdeon 6600XT or newer from someone and try again.

Note:
[ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.B0 04/24/2025


Post could be fine. Post has nothing to do if graphic output does not work because of faulty firmware of the grapic card, firmware of the monitor, firmware of the mainboard, display cable - type and qualiity
It's easier for myself to determine post, as i still use old samsung hdd for trash file. It's easier to determine when the box starts with post during boots.

Hmm, unfortunately at the moment I don’t have any friends who can lend me a GPU for testing — most of them only have one GPU and are using it in their own systems. Is there any other solution I could try in the meantime?

Pretty strange, i used a XFX Radeon R7 250X Ghost in the Ryzen 7 5800 Rig i built in 21, Steel Legend Mobo

Yeah, I find it strange too, because previously I was using an RX 570/580, which is technically below the 6600XT — and it worked just fine.

 

[Vincero]

You can keep UEFI but probably not secure boot by enabling CSM mode. This boots UEFI but falls back to old BIOS module initialisation - card should output something then. Technically secure boot requires CSM being disabled.

Yeah the BIOS reporting no video software for the missing iGPU is not really an issue. It's more of an issue if the BIOS was say mistakingly blocking GOP functioning in that scenario. Unlikely but silly bugs like this happen all the time.

Looking online, there does appear to be some people who have hacked GOP updates to their Turing based graphics cards so this is likely a VBIOS issue over at the win-raid forums - I'd be more inclined to contact info@galaxytech.com first and see if they have an update / fix available.

Really another modern (well, at least less than 10 years old) graphics card to test with would be handy.
UEFI support is unlikely to be guaranteed on anything older than Nvidia Kepler or ATI GCN cards.
Even then, for example, cards up to Pascal (GTX 1000 series) still got some fixes to their implementation.

 

[albertcou]

You can keep UEFI but probably not secure boot by enabling CSM mode. This boots UEFI but falls back to old BIOS module initialisation - card should output something then. Technically secure boot requires CSM being disabled.

Yeah the BIOS reporting no video software for the missing iGPU is not really an issue. It's more of an issue if the BIOS was say mistakingly blocking GOP functioning in that scenario. Unlikely but silly bugs like this happen all the time.

Looking online, there does appear to be some people who have hacked GOP updates to their Turing based graphics cards so this is likely a VBIOS issue over at the win-raid forums - I'd be more inclined to contact info@galaxytech.com first and see if they have an update / fix available.

Really another modern (well, at least less than 10 years old) graphics card to test with would be handy.
UEFI support is unlikely to be guaranteed on anything older than Nvidia Kepler or ATI GCN cards.
Even then, for example, cards up to Pascal (GTX 1000 series) still got some fixes to their implementation.

Hmm, maybe I’ll try contacting them first, but honestly I’m not too sure they’ll give a proper solution hahaha. Still, it’s worth a shot I guess. In the meantime, I’ll just wait and see if anyone else has any solutions here (hopefully) while I wait for a reply from that contact. Thanks, Appreciate it, thanks bro @Vincero !

 

[Vincero]

Again, I expect it'll make no difference but, check what this option (or it's equivalent on your board) is set to - option called 'Initiate Graphic Adapter':

(sorry, couldn't find an MSI BIOS screenshot from your board - so this'll have to do)

A proper functioning BIOS *should* just init the first display if the chosen option isn't available... but I make no assumption that everything is always implemented properly.
In your scenario PEG should be the option it's set as.

 

[Youseethis]

Can you do a simple test? Before you start the computer, turn on the monitor but do not let it go into stand by. Fiddle with the menu of the monitor so the panel remains on even without a signal from the pc. Then turn on the pc. (obviously have the pc in uefi mode for the test). There is a chance that you will see the post and boot normally.

 

[albertcou]

Here’s the current setup on my BIOS: I’ve set it to UEFI mode, but under Settings > Advanced > Windows OS Configuration, it’s still showing CSM as enabled. I think that’s why, even though Secure Boot is enabled in the BIOS, Windows still shows it as off.

Also, as I mentioned earlier, the iGPU is showing up as “unknown driver,” not sure if that’s related or just a separate issue.

Oh, and for what it’s worth, my drive is already using GPT partitioning.

One more thing I noticed—when CSM is enabled, the GOP Information doesn’t show up in the BIOS. It only becomes accessible when the system is in full UEFI mode. Not sure if that’s relevant, but figured I’d mention it just in case.

Can you do a simple test? Before you start the computer, turn on the monitor but do not let it go into stand by. Fiddle with the menu of the monitor so the panel remains on even without a signal from the pc. Then turn on the pc. (obviously have the pc in uefi mode for the test). There is a chance that you will see the post and boot normally.

Yeah, I tried that—turned on the monitor first and kept it active by using the menu so it wouldn’t go into standby. Then powered on the PC while in UEFI mode.

Unfortunately, it didn’t seem to solve the main issue, but still, I really appreciate the suggestion. Thanks a lot!

 

[Vincero]

Well, re-flashing the VBIOS for the GPU might be hard if it isn't available - also probably risky without a proper vendor supplied package.

Have you tried flashing to a / the previous version of the motherboard BIOS (assuming that the last update doesn't change some firmware that can't be rolled back)?
Technically I'm not sure if the GOP message 'unknown driver' is technically referring to the IGP (missing in this case) or the BIOS literally saying it can't figure out what the GOP software on the graphics card is.

In theory this should all be standard but incompatibilities can always randomly exist - I'll be honest this is a bit of a shot in the dark move - I doubt it'll make a difference.
Otherwise, another different graphics card is needed to see if this is just a glitch with the one you have.
Nvidia may have (comparatively) solid drivers but, outside of the Quadro cards, their VBIOS implementation and how it handles monitors and different interfaces + GOP+UEFI is not quite as good. Sure some of this may be down to the vendors, but it all comes from one source to begin with....

 

[Caring1]

At the moment, I don't have an additional monitor to test with, but I don't think the issue is with the monitor. The reason is that, in the BIOS menu, the integrated GPU (iGPU) is showing a message like "No driver found" or something similar. That makes me suspect the problem might be related to the iGPU or its drivers, not the monitor.

Did you ignore where HDMI was mentioned instead of Displayport?
Use a HDMI cable to connect to the Monitor.

 

[Vincero]

Did you ignore where HDMI was mentioned instead of Displayport?
Use a HDMI cable to connect to the Monitor.

Re-read the first post

 

[albertcou]

Well, re-flashing the VBIOS for the GPU might be hard if it isn't available - also probably risky without a proper vendor supplied package.

Have you tried flashing to a / the previous version of the motherboard BIOS (assuming that the last update doesn't change some firmware that can't be rolled back)?
Technically I'm not sure if the GOP message 'unknown driver' is technically referring to the IGP (missing in this case) or the BIOS literally saying it can't figure out what the GOP software on the graphics card is.

In theory this should all be standard but incompatibilities can always randomly exist - I'll be honest this is a bit of a shot in the dark move - I doubt it'll make a difference.
Otherwise, another different graphics card is needed to see if this is just a glitch with the one you have.
Nvidia may have (comparatively) solid drivers but, outside of the Quadro cards, their VBIOS implementation and how it handles monitors and different interfaces + GOP+UEFI is not quite as good. Sure some of this may be down to the vendors, but it all comes from one source to begin with....

Hey there!
Looks like I’ve been away from this forum for quite a while—work’s been keeping me super busy.

Anyway, I finally had a chance to try your suggestion about flashing an older BIOS version using the support page from MSI (https://id.msi.com/Motherboard/B360M-BAZOOKA/support#cpu). I tried going back to the version shown in image 1, but ran into an issue: that version doesn’t seem to have the “Windows 10 WHQL support” setting, which is needed to enable UEFI mode for Secure Boot. So, Secure Boot can’t be activated with that older BIOS version.

At this point, I’m honestly starting to suspect it might just be a hardware defect or some other flaw with the product. Feels like there’s no fix that really works here.