I just updated my first bios, actually two computer updates

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. :-) I'm on a laptop tonight.
I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.
What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)
Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(
Not expecting help.

Verification.
Are you on build 26120.2200?
Nope, not a Dev build.

26100.2161. Available to non-Insiders.
So any verification would be questionable, but I fixed the Dev drive's shutdown problem quickly, so I had a chance to install DisplayCAL from curiosity. So, FWIW, here's what DisplayCAL said in Profile info: I don't understand it, but perhaps you will. :-)

Too long for one screenshot; does this tell you anything?
Too long for one screenshot; does this tell you anything?

Also:

ba614d286c134e76942e4293874ea38a.jpg
That looks like it's profiling pretty much like the monitor is sRGB.
Yes, the monitor's gamut is only slightly larger than sRGB; it's not a full AdobeRGB monitor by any means. More P3, which I'm fine with.
For comparison, this is the profile provided by Philips, compared to Adobe RGB:

6b4afb97f0964d618f1f13f05d9d04d3.jpg.png

This is what I get from my most recent Calibrite Profiler run:

a0a7022f8bca45cf8b238eddd0214887.jpg.png

Not exactly a lethal bug, but it's annoying.
Now I see what you mean; I was looking at the wrong profile when I first posted.

Looking at my own screenshot, the faint dotted reference comparison sRGB profile looks to me to be well inside the actual measured profile; if I have a profiling problem, I don't see it. Am I missing something?
 
I don't understand any of your concerns -- please explain.

I do all the BIOS updates that are suggested by my PC manufacturer. A good opportunity to get a cup of coffee downstairs. What's the big deal?

I also bring my car in for servicing when the manufacturer suggests.

Maybe I just like a simple life without causing myself unnecessary problems.
I only do BIOS updates if absolutely necessary. Over the years, I have had 2 updates go south on me.
I only wear my seat belt if absolutely necessary.
 
Now I see what you mean; I was looking at the wrong profile when I first posted.

Looking at my own screenshot, the faint dotted reference comparison sRGB profile looks to me to be well inside the actual measured profile; if I have a profiling problem, I don't see it. Am I missing something?
Depends.

If your monitor has a wider gamut than sRGB, and it's not limited to sRGB by its settings, the software (either Profiler or Displaycal/Argyll CMS) should profile to that.

Pre-bug Displaycal profiles for my OLED display show a wider gamut than Adobe RGB.

To repeat myself: I believe there's a bug in 24H2 that prevents profiling software from detecting the monitor's gamut properly. It defaults to sRGB.

Maybe most people would treat that with a resounding "so what?".
 
This was in preparation for going to Windows 11. My other two already had what was needed in their bios to qualify

So, first time. I did a bunch of researching and slogged through the endless tales of bricked mobos, user error after user error sprinkled with the occasional "it was easy, no problem". I chose to believe those who had no problems

These were both on MSI desktops using the "M-Flash" utility in the existing bios

And both went smoothly, though not without a lot of angst concerning "am I doing this correctly??" Turns out I did and it was indeed "easy". There are a lot of steps along the way that a guy could mess up but I did my due diligence and it worked

OTOH, now that I do have four computers Windows 11 ready I'm still not going to update from W10 on any of them. Gonna wait till I have to, next year
I don't understand any of your concerns -- please explain.

I do all the BIOS updates that are suggested by my PC manufacturer. A good opportunity to get a cup of coffee downstairs. What's the big deal?

I also bring my car in for servicing when the manufacturer suggests.

Maybe I just like a simple life without causing myself unnecessary problems.
Same! My greatest fear is missing a BIOS update then wondering whether I should sequentially update or just go straight to the latest.

What worries me though is that MSI recommend not updating unless one has problems. That's dumb. I'm not waiting till there are problems. In any case, how do I know there is a problem till something doesn't work as it should, and I realise there should have been an update 5 updates ago that may or might not now work.
 
Now I see what you mean; I was looking at the wrong profile when I first posted.

Looking at my own screenshot, the faint dotted reference comparison sRGB profile looks to me to be well inside the actual measured profile; if I have a profiling problem, I don't see it. Am I missing something?
Depends.

If your monitor has a wider gamut than sRGB, and it's not limited to sRGB by its settings, the software (either Profiler or Displaycal/Argyll CMS) should profile to that.

Pre-bug Displaycal profiles for my OLED display show a wider gamut than Adobe RGB.

To repeat myself: I believe there's a bug in 24H2 that prevents profiling software from detecting the monitor's gamut properly. It defaults to sRGB.
If I had that bug in 26120.2200, and the profiling defaulted to sRGB, wouldn't the screenshot of my monitor's gamut profile be congruent with the faint, dotted, reference comparison sRGB profile instead of being outside of it most places?
 
.... snnipped ....
Same! My greatest fear is missing a BIOS update then wondering whether I should sequentially update or just go straight to the latest.

What worries me though is that MSI recommend not updating unless one has problems.
That's dumb. I'm not waiting till there are problems. In any case, how do I know there is a problem till something doesn't work as it should, and I realise there should have been an update 5 updates ago that may or might not now work.
From what I've gleaned BIOS updates are cumulative so the latest update should incorporate any that you missed.

Gigabyte also has a prominent scary warning at the bottom of the BIOS download page for my motherboard that recommends not updating if you are not having problems. I guess that is over-ruled if they post a later BIOS update which they recommend "customers are strongly encouraged to update to this release at the earliest.".
 
.... snnipped ....
Same! My greatest fear is missing a BIOS update then wondering whether I should sequentially update or just go straight to the latest.

What worries me though is that MSI recommend not updating unless one has problems.
That's dumb. I'm not waiting till there are problems. In any case, how do I know there is a problem till something doesn't work as it should, and I realise there should have been an update 5 updates ago that may or might not now work.
From what I've gleaned BIOS updates are cumulative so the latest update should incorporate any that you missed.

Gigabyte also has a prominent scary warning at the bottom of the BIOS download page for my motherboard that recommends not updating if you are not having problems. I guess that is over-ruled if they post a later BIOS update which they recommend "customers are strongly encouraged to update to this release at the earliest.".
Gigabyte is based in Taiwan, but is majority-controlled by Xiwei, a subsidiary of China Investment Corporation, which in turn is wholly-owned by the Chinese government.

To each their own, but I would not trust access to my data to a Chinese PC. Chinese companies are required by law to obey requests from the Chinese government, without the legal right to disclose what those requests are.
 
.... snnipped ....
Same! My greatest fear is missing a BIOS update then wondering whether I should sequentially update or just go straight to the latest.

What worries me though is that MSI recommend not updating unless one has problems.
That's dumb. I'm not waiting till there are problems. In any case, how do I know there is a problem till something doesn't work as it should, and I realise there should have been an update 5 updates ago that may or might not now work.
From what I've gleaned BIOS updates are cumulative so the latest update should incorporate any that you missed.

Gigabyte also has a prominent scary warning at the bottom of the BIOS download page for my motherboard that recommends not updating if you are not having problems. I guess that is over-ruled if they post a later BIOS update which they recommend "customers are strongly encouraged to update to this release at the earliest.".
Firmware updates are cumulative, except when they're not.

I've seen some that required a previous version to have been installed. (It's unusual.)

I've had a couple of P67 boards bricked by firmware updates. That was back in 2011.

In my inexpert opinions, BIOS updates are pretty safe in 2024. If you want to reduce the risk further, only buy motherboards that have a built-in BIOS recovery utility, or a dual BIOS (with a physical switch to invoke the backup BIOS).
 
Now I see what you mean; I was looking at the wrong profile when I first posted.

Looking at my own screenshot, the faint dotted reference comparison sRGB profile looks to me to be well inside the actual measured profile; if I have a profiling problem, I don't see it. Am I missing something?
Depends.

If your monitor has a wider gamut than sRGB, and it's not limited to sRGB by its settings, the software (either Profiler or Displaycal/Argyll CMS) should profile to that.

Pre-bug Displaycal profiles for my OLED display show a wider gamut than Adobe RGB.

To repeat myself: I believe there's a bug in 24H2 that prevents profiling software from detecting the monitor's gamut properly. It defaults to sRGB.

Maybe most people would treat that with a resounding "so what?".
I don't think it's a bug. You may have calibrated to the native profile of your monitor which maybe more or less than Adobe RGB. The pundits say that gives more accurate colours than specifying exactly Adobe RGB. Anyway, there is no colour space name for your native profile so Windows defaults to calling the colour space RGB. However, the monitor profile should remain as the native profile. You could perhaps force the calibration to Adobe RGB then Windows may well recognise the colour space name.
 
Same! My greatest fear is missing a BIOS update then wondering whether I should sequentially update or just go straight to the latest.
Every BIOS update I've ever done (hundreds) has been straight to the latest version. Most of mine were on older hardware though. Have you seen any that recommend incremental updates?
 
Now I see what you mean; I was looking at the wrong profile when I first posted.

Looking at my own screenshot, the faint dotted reference comparison sRGB profile looks to me to be well inside the actual measured profile; if I have a profiling problem, I don't see it. Am I missing something?
Depends.

If your monitor has a wider gamut than sRGB, and it's not limited to sRGB by its settings, the software (either Profiler or Displaycal/Argyll CMS) should profile to that.

Pre-bug Displaycal profiles for my OLED display show a wider gamut than Adobe RGB.

To repeat myself: I believe there's a bug in 24H2 that prevents profiling software from detecting the monitor's gamut properly. It defaults to sRGB.

Maybe most people would treat that with a resounding "so what?".
I don't think it's a bug. You may have calibrated to the native profile of your monitor which maybe more or less than Adobe RGB. The pundits say that gives more accurate colours than specifying exactly Adobe RGB. Anyway, there is no colour space name for your native profile so Windows defaults to calling the colour space RGB. However, the monitor profile should remain as the native profile. You could perhaps force the calibration to Adobe RGB then Windows may well recognise the colour space name.
It's a bug.

In the past, I've profiled using both Calibrite Profiler and Displaycal/Argyll CMS, and gotten a wide gamut result. I wouldn't be chasing this if I hadn't gotten different results before, using the same hardware. (Different Windows 11 build, and different nVidia drivers. I reverted the GPU drivers, which changed nothing.)

The monitor has no "native" gamut setting, so I set it to Rec 2020. That's a wider gamut than the monitor can actually display. The profile ended up as a bit wider than Adobe RGB.
 
I consider myself a computer building enthusiast. Maintaining the latest bios on my systems is standard practice. Most times I don’t even read what was updated. The process of updating the bios is nearly trivial when you perform this task once or twice a year.
Do you find substantial improvements from these BIOS updates?
Most of what the BIOS does is unrelated to "improvements" that the user would notice. BIOS updates address security issues among many others.

Waiting until a problem is visible to you before doing a BIOS update is like waiting until you have a health problem before going for a checkup.
 

Keyboard shortcuts

Back
Top