Please show me image of the boot page now so I can see.

Fan settings may rely on EC FW, and yes, EC FW will always be 0000 or N/A since the chip has been erased. Did you Enabled >> Automatic Thermal Reporting << Before setting thermal trip points and fan speeds? You must do that first

Thunderbolt, you may need to look up that exact chip model online, and see if you can find anyone discussing it's FW and how it's updated (if possible, it may not be possible for the public)
Default is enabled (For discreet), did you also test disabled? Also, for any setting I mentioned/look at, I'm only looking at optimal, so be sure you have stated after flash by loading optimal defaults (Restore Defaults) in the BIOS exit page before making any changes.

On the blinking LED, so what happened before when charging, nothing/No LED? The only thing relating to charging I touched was made those three battery options visible to you in the original Advanced page, I didn't change the default settings so same options were always what was applied.

Did you test changing the LCD panel type yet at Chipset >> LCD panel type?

On Thunderbolt, at Chipset >> PCH I/O >> PCI Express Config >> Root Port x (many numbers), each one has a setting "Disable Gen2 Pll Shutdown and L1 Controller Power gating" this mentions it needs to be enabled for TB to function (Default disabled)
I see "USB Sensor Hub" disabled at >> PCH I/) >> USB (maybe this help with USB 3/C). Also, xDCI Support = disabled by default
Also, at New Advanced >> ACPI D3Cold settings (USB #1-2 disabled), this mentions USB3 in help text

Zitat von Lost_N_BIOS im Beitrag #96

---

Generic model names don't help me in regards to what I asked, sorry for not being specific. I wanted to know if both systems use same exact graphics card chipset, for example both use 970M or 1050M etc.

Yes, all settings will be unlocked for you once I'm done! I will need a complete set of all BIOS pages, submenus, all visible settings after this, if you want me to confirm every single thing is visible.
Or you can check this yourself if you want, but you'll also need images, so you can compare side by side image with BIOS in AMIBCP

I will wrap up BIOS right now, please give me 15-20 minutes if you are reading this now, and then I should be done and have BIOS ready for you

@ket - can you look into this vBIOS, and see if you can see a way to change whatever is applied to 15" monitor, to instead be applied to 17" monitor?
I'm not sure if this is possible, but when 15" monitor is connected, system acts right, when 17" is connected info is detected wrong (wrong sys model, wrong card model) and fans spin at 100%
I think this may be controlled by the vBIOS inside main BIOS, however maybe not? I can edit/mess with that, but we planned to do later, and I just remembered you know about digging deeper than I do into actual card vBIOS
I'll follow up with a link to this in PM if you don't reply in a day or two, just in case you don't look into thread notifications - heads up
Thanks man, hope you can spare a few to check it out - http://s000.tinyupload.com/index.php?fil...327796822192791

---

Thanks for your thoughts @ket - The issue is when using 17" screen (goal), fans run at full blast and info is all wrong (Don't care really)
When using 15" screen (don't want to use) everything works properly, although card and system model ID wrong, not important really, the fans acting right with this monitor but not the other is the main thing we want to fix
This unrelated to windows, and happens at BIOS level as well, so not a windows issue.

This is ES System, so we can't use retail ME FW, or BIOS region etc. Something in the card's vBIOS is causing this, and we'd like to switch it, so that when using 17" screen it does everything it currently does on the 15" now.
He has flash programmer, so unless signature check is an issue with actual use of the vBIOS (and not just flashing), then you can mod away and he can recover if need be. Can you switch everything relating to the 15" to the 17"'s details instead (Or copy it there, less work that way)

If you think something in the BIOS vBIOS could be doing this, here is a copy of that. I also suspected this, and looked at it in Intel BMP but didn't see anything that caught my eye in regards to any of this (except neither this nor BIOS settings offer either monitors actual resolution)
BIOS defaults set to = vBIOS default, and vBIOS default set to = BIOS default
http://s000.tinyupload.com/index.php?fil...602686142951604

* Edit - @code9523 - ket made me think of something, and I found a switch off from 17 R5 and 15 R4 in setup... So... new test files for you, maybe we can make some magic happen!


Sorry, but be ready to recover from each one, unsure of outcome here, especially on the 00 edit - 75 or EB probably best outcome, one more edit is possible here (similar to 00 edit, but done differently, probably better way) but I didn't think of it until looking at these images and uploading all this, so if these fail one more to try next
http://s000.tinyupload.com/index.php?fil...688087902789429

Aside from the additional edit I mentioned above, I can also switch these (the lea {load effective address} 17 R5 for 15 R4) around too I believe. So we'll try that next too if these aren't helpful

If the hardware on that ES is the same as retail theres no reason why you can't flash to retail firmware, the ES shouldn't be locked in any way so its very unlikely you need to even override any IDs or security checks you might just have to force the flash from a DOS prompt or EFI shell but thats it. Aggressive fans will be part of the Lookup table or fuzzy logic - thats all held in the vBIOS not the main BIOS (or it should be). Incorrect info will also be part of the vBIOS so theoretically you could also rip out the vBIOS from some retail A17R5 firmware and use it to replace the vBIOS injected in the ES firmware then everything should work as intended. It would also be worth testing by using some different screens as the issue could be a compatibility problem with the current screen. If thats the case the bug may or may not have been fixed in the retail firmware no real way to know that without trying.

@ket - we've already tried that, and I've tried on a few Dell ES models for others, it's got ES PCH, so I assume other stuff not the same as retail either. He has flash programmer, and aside from that, BIOS flashing isn't an issue.
What you mention about fan profiles in vBIOS I have no clue about any of that, this is why I asked if you'd look at that vBIOS. I've never even heard those terms Well I have heard of Fuzzy Logic, but only in speaking about Alien technology or Scientific stuff, not computer/BIOS related.

We have not tested retail vBIOS (in BIOS), other than failed BIOS region swaps which contain it, but I do believe he's tested retail vBIOS on the card and it didn't help. I agree, it would be good if he could test a few other 17" screens to see if same things happen or not.

@code9523 - any testing results from the above BIOS package yet?

Ok
1. V5EB = no changes
2. V500 = 15R4 name in bios but nothing else changed.
3. V575 freezes on alienware screen no boot no bios entry.

Thanks for testing, it's useful info! So, V5EB = no change, this means that was the default thing it was doing (going to 17 R5). Does this happen with either 15 or 17" screens?
Please test that BIOS with both screens. Also, test V500 and BIOS below with both screens. Sorry, I forgot to mention this screen stuff when I posted those, but this is what I wanted to test, along with the outcome of each of these edits
on V500 - I think this may be done in a better way, but maybe test both, here is the BIOS done with better method - http://s000.tinyupload.com/index.php?fil...577869055053941

Interesting that V575 does not boot

Hello, can you please post the bios dump for this laptop again?