<Deleted Post>

Ok, noted. I only described what I had previously learnt. But thanks for confirming that iGPU will work too.

Even if we enable iGPU, what are we going to achieve? As there is apparently no setting in BIOS to regulate the Backlight level of the laptop display, it looks like this problem can't be solved through BIOS.

In the BIOS mod, have you disabled PEG and enabled iGPU?

Being able to use internal graphics allows you to safely test an updated vBIOS module in the BIOS, to see about better compatibility that you wanted. That way if the vBIOS module fails to be compatible with your graphics card or it's own vBIOS, then you can still see screen due to using internal graphics from the CPU to flash back to previous BIOS version without vBIOS change. With that said, what CPU do you have, so we can confirm it has onboard graphics, I assume it does but not all do so shouldn't assume

In the BIOS mod I did no changes to those settings, only disabled High Precision Timer in hidden menu as discussed, and then enabled the menus as mentioned and still those sections I showed might need further enabling anyway for you to see.
Tonight I mainly discussed my thoughts with you about that, and enabled chipset menu and showed you where in AMIBCP those settings I mentioned are located, so you can confirm if that section of the BIOS needs further enabling or not so you can access the settings.
You need to let me know if you can see that section yet or not, all setting changes will be done on your end within the BIOS.

Your first move wont be to disable the graphics card anyway, you can always leave it enabled too if you want, you only need to test enable the onboard graphics and both will show up in GPU-z (May need Intel driver installed first).
Both can be enabled at once, and once you confirm Intel GFX enabled, you can enable/disable either at will. Laptops that come with CPU with internal GFX and an external graphics card like you have, usually leave both enabled in case the external graphic card dies.
But since this is a very expensive gaming system vs OEM like Dell or HP they disabled all this to force you to either contact them to buy another $300-400 graphic card, or send it in for repairs etc.

Yay! HPET has been finally disabled. There is no HPET device in Windows Device Manager now. Thanks a lot!

The Chipset Menu has also been exposed, and looks like almost all the settings are there. There is no Recovery Menu, but I have no problem if it cannot be exposed.

Although HPET has been disabled and I wouldn't want to enable it back, but still if it is required in future, it would be great if you could expose HPET setting as well so that I have the option to enable it in case there is a need.

In CPU Configuration, I would just request you to expose C8 Report, C9 Report and C10 Report settings as well (which are currently not available), if possible. There is no problem if those can't be exposed though.

Zitat von Lost_N_BIOS im Beitrag #78

---

Being able to use internal graphics allows you to safely test an updated vBIOS module in the BIOS, to see about better compatibility that you wanted. That way if the vBIOS module fails to be compatible with your graphics card or it's own vBIOS, then you can still see screen due to using internal graphics from the CPU to flash back to previous BIOS version without vBIOS change. With that said, what CPU do you have, so we can confirm it has onboard graphics, I assume it does but not all do so shouldn't assume

---

Zitat von Lost_N_BIOS im Beitrag #78

---

Tonight I mainly discussed my thoughts with you about that, and enabled chipset menu and showed you where in AMIBCP those settings I mentioned are located, so you can confirm if that section of the BIOS needs further enabling or not so you can access the settings.
You need to let me know if you can see that section yet or not, all setting changes will be done on your end within the BIOS.

---

Sweet, NO HPET!!! That was easy I bet disabling both ways conflicted last time then, or some bug in original BIOS or maybe combo of both. So, only disable this time was that hidden folder, so thanks to you we now know those settings apply too.
High Precision Timer is still "Enabled" in the defaults actual BIOS setup module, surprised it was not that one that needed changed! the only place that setting is visible is in that hidden menu right now, I will see if I can add in another section, but not certain I can do that with the tools we the public have.

Maybe on recovery, one of the methods needs to be put back, or it's just something I can't enable. I'm sure I could get, if I had the system here and could test changes quickly, but like you said it's no big deal.
I will put these attempts on that back to original state that way they aren't causing any issues later with anything else.

I know what you mean about the heatsink, this would only be for short quick testing though so it would be OK. You could test for few minutes with it to make sure it works, if not clear CMOS to re-enable the AMD card, then if it's working you'd know it's OK to test a new vBIOS in BIOS to see if updated vBIOS changed anything for you in the BIOS for your graphics card. Thanks for those boards BIOS, I will look and see if anything needed from them or not, normally my intention would be to try the latest version.

Zitat von Lost_N_BIOS im Beitrag #81

---

You could test for few minutes with it to make sure it works, if not clear CMOS to re-enable the AMD card, then if it's working you'd know it's OK to test a new vBIOS in BIOS to see if updated vBIOS changed anything for you in the BIOS for your graphics card. Thanks for those boards BIOS, I will look and see if anything needed from them or not, normally my intention would be to try the latest version.

---

Please show me GPU-z image, is there two cards shown in the dropout menu at the bottom to choose graphics card? This is meant to be checked with Internal Graphics enabled.
https://www.techpowerup.com/download/techpowerup-gpu-z/ - standard version if fine, you can say no to "Install" and run it from the unzipped folder

It would be unknown device in device manager, until you installed first possibly INF files if not already installed, possibly Intel ME drviers if not installed, and then it would show up as a graphics device detected by windows possibly but would still need actual Intel Graphics drivers installed before you could use it in anything like you mentioned with DirectShow etc.

Yes, do not change primary display, it's never really needed even in our test we discussed. But, even if you did, and screen was blank on reboot, you can clear CMOS and it would reset that setting back to default.

It may not show up, if they removed the default vBIOS for internal GFX in the BIOS. I have not had a chance to check any of this yet, surprised you are jumping ahead and messing with things you initially deemed risky
Please wait until I've had a chance to look further into this before making anymore BIOS changes relating to this, except for the above mentioned test.

Zitat von Lost_N_BIOS im Beitrag #83

---

Please show me GPU-z image, is there two cards shown in the dropout menu at the bottom to choose graphics card? This is meant to be checked with Internal Graphics enabled.

---

Zitat von Lost_N_BIOS im Beitrag #83

---

It would be unknown device in device manager, until you installed first possibly INF files if not already installed, possibly Intel ME drviers if not installed, and then it would show up as a graphics device detected by windows possibly but would still need actual Intel Graphics drivers installed before you could use it in anything like you mentioned with DirectShow etc.

---

Zitat von Lost_N_BIOS im Beitrag #83

---

It may not show up, if they removed the default vBIOS for internal GFX in the BIOS. I have not had a chance to check any of this yet, surprised you are jumping ahead and messing with things you initially deemed risky

---

Zitat von Lost_N_BIOS im Beitrag #83

---

Please wait until I've had a chance to look further into this before making anymore BIOS changes relating to this, except for the above mentioned test.

---

I should also inform you that now AIDA64 shows the CPU Microcode as 25h (previously it was 1Eh). I have attached the screenshot here.

Thanks! I will have to check what vBIOS is included in the BIOS, not dump from your card. If they removed the stock Intel GOP/vBIOS then we know this is the issue. I can put back in as a test possibly, but I am unsure, would have to check and see how that looked post edit.
I checked, Haswell-Broadwell vBIOS version 1031 is still in the BIOS, both the 4MB and 8MB versions, so they did not remove. But no GOP version, only orom, so no EFI/UEFI booting from internal GFX only CMS legacy I think

But, due to your GPU-z image test, some other area of settings maybe disabling, I'll have to look. There is no AMD vBIOS in there though, so this is moot point.
I can't update that to try and help BIOS detect card, only you could on your end via updating the graphics card BIOS itself, via this thread AMD and Nvidia GOP update (No requests, DIY)

On microcode, both 314 and latest BIOS have revision 1D for your CPUID, so any microcode you see before or now is being replaced by windows over the BIOS installed version. I never changed those, I think you said leave as-is
Rev 32 is the latest version for your CPUID 506E3, if you update this in the BIOS it will over-ride windows version due to being newer.

Zitat von Lost_N_BIOS im Beitrag #85

---

But, due to your GPU-z image test, some other area of settings maybe disabling, I'll have to look. There is no AMD vBIOS in there though, so this is moot point.
I can't update that to try and help BIOS detect card, only you could on your end via updating the graphics card BIOS itself, via this thread AMD and Nvidia GOP update (No requests, DIY)

---

Zitat von Lost_N_BIOS im Beitrag #85

---

On microcode, both 314 and latest BIOS have revision 1D for your CPUID, so any microcode you see before or now is being replaced by windows over the BIOS installed version. I never changed those, I think you said leave as-is
Rev 32 is the latest version for your CPUID 506E3, if you update this in the BIOS it will over-ride windows version due to being newer.

---

Sorry, yes I linked confusing thread. You're card BIOS is UEFI already. Near end of the thread, is GOP updater by Sylar76, I assumed it was discussed/linked on first page too. Latest version is here, in post #503 - AMD and Nvidia GOP update (No requests, DIY) (34)

First you dump your current graphics card BIOS using GPU-z, using this button circled in red. Your graphics card BIOS is already UEFI BIOS (See arrow), so you don't have to worry about converting to that only updating if you wanted to latest version, just make sure you also leave in legacy rom too if size is an issue


As for the other BIOS from compatible laptops, I still have to check that out. They would not have AMD vBIOS in them, maybe orom, but I'll have to look when time permits.

On microcodes again, sorry I think I checked wrong file earlier when I replied Yes, I already updated to latest version in these last rounds, but now seeing that I notice I put wrong version 25 instead of 32, my microcode checker database was out of date so when I looked 25 was shown as latest.
I will fix this next round of updating, sorry! No, no issues with updating it, you already flashed one with all latest version except the ones I was slightly out of date still on (2018 version, but not quite latest revisions)

What boot logo do you see, Clevo or something else? I haven't checked, but asking for the other user that hopped in here.

It's another logo. As aram downloaded the BIOS from this thread, he would be seeing the same logo.

OK, thanks. He was asking me about putting in a Clevo logo, and I simply hadn't checked the BIOS for any logos. Maybe he has the original Clevo logo, or a backup from his original BIOS that has this logo he can upload here.
I asked him about that in PM, maybe he'll reply here with more info.

Also, I checked again, and I was sleep looking earlier when I replied about microcodes. I put latest version, it's for platform 32, but latest microcode is rev 25 (Dated 4-18-2018), already in your BIOS.
So, AIDA64 shows correct, and this is code I put, not windows update as I suspected when looking at that wrong previously.

Ok, thanks for confirming that AIDA64 shows the correct microcode (and it is the latest one).

I had this general question: if in a system, BIOS has older microcode and Windows use the same one, is it possible to update the microcode in Windows such that the OS uses the latest one (without updating the BIOS)?