BIOS update (1.4.4) messed up my laptop

Vasudev, please stop responding, you are not even answering the questions asked.

To 0lok, the answer is no, there is no increased risk of bricking. The issue comes down to the fact that if 1.4.4 includes the updated ME firmware, and if 1.4.4 was not flawed (which it is), then Dell would not have necessarily included a new ME firmware in a future BIOS update.

But considering that people are having problems with 1.4.4, I think it is safe to assume that Dell will be releasing a new BIOS with a ME Firmware image as part of it and they will make sure it updates everything properly.

In any case, to answer your question, I do not think having a improperly flashed BIOS without the ME firmware as part of the process will change (or shall I say increase) your chances of a brick on a future flash.

The risk comes in based upon the entire process in and of itself, not necessarily because of one component or another, but most certainly, more components included in the BIOS update increases the risk of any one component failing to update properly.

 

Thank you very much.. I am learning here..

 

If you can get Dell vendor unique ID, then I think you can flash MEFW even though its disabled. But, I haven't tested it or able to get it.
Good thing why you can apply 15r3 or 17 r4 MEFW because it has 6700HQ and 6820HK chips.

 

MEFW update from 15R3 might work on our systems only if u have BIOS 1.4.4.. for me i have tried.. it shows i cannot downgrade ME.. since im on PT 3448 version.. official dell ones is 3426

 

Never downgrade MEFW or even try to. According to Win-raid, Intel employed a code that bricks PC when downgrading.
I was able to run it and FW didn't flash since, ME flashing was disabled as i said before.

 

Im hoping for a newer version of ME firmware from official DELL ones.. lets see.. its stil under suspended release.. they might take quite sometime

 

No problem! This was one of the reasons I first posted here.
I do not have a AGA so cant test that. But I use my AW as a working station and it is attached to a dell dock D3100 and no issues there with an external monitor and various devices. HDMI works as expected just to add.

Strange. I have done it straight forward as recommended from dell/AW. I have since day one flashed bios from within windows. I copy the installer for the bios to my desktop and run it from there. I think I can recall the firmware screen when flashed the bios.. But I did not study it exact. It flashed just like all the other bios'es I have done. So I cant say other than it was flashed properly. Like I have said before, just flashed bios, no standalone updater. Followed Dell's recommended prosess. I have all my system components and values stock as it was from the box.

 

Now I use Dell GSet which is safest and fastest way to flash BIOS. Copy the EXE to root of ur flash drive and use F12 to choose Dell Flash Update utility and use Tab keys for navigating between options.

 

Based on Dell's site: http://www.dell.com/support/article...intel-me-txe-advisory-intel-sa-00086-?lang=en this is the bois og ME firmware release. The AW17R3 was labeled with suspended release for some time, but was updated some days ago. It was then I updated the Intel(R) Management Engine Components Installer. MY ME firmware was not changed and stayed on 11.8.50.3426
Sorry in advance if I misunderstood you.

 

Never try to downgrade again. Its blocked by Intel. There will be incoming MEI FW for most models.

 

No, I used the one on the dell page ThomasAAT posted http://www.dell.com/support/article...intel-me-txe-advisory-intel-sa-00086-?lang=en
Alienware 17 R3 1.4.4 7CDG2_11.7.0.1054

I got an AGA and have no problems with it.

This could be the reason I get crackling static noise with the logitech G933 adapter plugged into the hub that's plugged into the USB-C port so does anyone know if it's the Bios or Intel Management Engine Interface Driver causing it.
The hub I got is this one http://www.belkin.com/au/p/P-F4U090/

 

Is it me you are referering to? I dont say anything about downgrade and it is the last thing I would recommend doing.

 

I thought you were downgrading.

 

Vasudev, maybe that is why you didn't get the MEFW because you used the GSet utility to flash ONLY the BIOS and the Dell windows installer actually does both???

Again, why not use the utility provided by the manufacturer (regardless if firmware update is a BIOS startup option)???

If you guys hate Windows 10 so much, you do realize that these laptops are only offered with Windows 10.

After doing a ton of reading all over the place, it would seem that the majority of those having problems are those not following the simple "download and run the app" install. Or, even those that have done that and failed are running modified nVidia vBIOSes and mucking around with forced ME firmware updates that are not Dell supplied for that model.

 

Ah, okay. No harm done
I upgraded from the version provided 2015 on dell's driverpage.

 

I have gathered the same image... I have always used the Dell windows bios installer and run it from windows. Easy and straight forward. Never had a problem. Flashed from 1.2.8 to 1.3.9 and then up to 1.3.10, 1.3.12 and finally 1.4.4

 

Same here.. I flash in windows as well.. flashed from bios 1.3.6 to 1.3.9 to 1.3.10 to 1.3.12 and 1.4.4.. NO ME FIRMWARE UPDATE.. Bios 1.4.4 is really the problem.. someone in this forum brick jis laptop because of the bios.. http://forum.notebookreview.com/threads/alienware-15r2-7-beeps-of-death.797563/page-7

Who ever created bios 1.4.4 should be fired.. tsk tsk tsk..

 

I can only speak for my self. My flashing to 1.4.4 went smooth with the ME firmware update. So there is variations out there. Like I said before all my clocks and bios values is stock. I add this due what @95TA mentions about modifying the system and maybe results in problems some are experiencing.

 

0lok, that is exactly it. So many people use throttlestop and tons of other utilities to boost performance, just about anything that messes with the system on a low-level can be at fault in causing a BIOS load/MEFW flash to fail...

I mean there is little doubt that 1.4.4 has issues though... Dell/Alienware know this and have admitted it is flawed, it is just that they are developing and thoroughly testing a new update to make sure those same problems don't exist in a new release. We just have to be patient.

Who knows, maybe they didn't setup certain things in the system to allow the flash to happen properly all the time. Maybe you have to do it directly after a fresh reboot with no external peripherals attached at all and on the built-in display with no AGA hooked up. Who knows. All that is known is that it is a bad release and they are working on a new one.

 

Agree.
But since they have re-released the 1.4.4 bios, they must have ensured that it not bricks motherboards (like version 1.2.12 did and as a results was pulled for good). A tek I spoken to told me that the bios was tested before the re-release to ensure minimal issues. But it is good to see that they are working on a new update that rules out flaws that users have. I guess I am one of the lucky ones.
By the way; Is it confirmed by dell/aw that they will release a new bios that replace the 1.4.4?

Regards the last here, I always unplug all external devices with only the AC adapter plugged in. This after recommendations from a Alienware tek I spoken to during my first bios flash.

 

The Old and New re-released BIOS update EXE contain the same exact hashes which only means they didn't change anything.

 

I am aware of that. But my point is that they wouldn't re-publish the bios if they know the issues was bricking motherboards and/or give major issues for most users.

 

if you check dell alienware forum bios 1.4.4 is bricking alot of laptop.. very sad..

 

Sad yes... But then the question is; what kind of modifications and flash methods are they using. And is there any devices plugged in during the flash etc. So many variables.
I just cant belive that dell/aw wold post and keep the bios available for download if they know there is more likely to brick mb than other bios'es.
There is always a risk for bricking, but it tends to be more focus and posts if some are experiencing problems. Like fire in dry grass...

And a side note; they who dont have any issues tend to not post or comment on these kind of forum treads...

 

Even too much temp files creates a problem during flashing, when some BIOS contents are unpacked there. Lenovo always extracts driver/BIOS/FW to C:\drivers\Lenovo\ which ensures everything goes smoothly. Dell used to do this earlier but now they unpack FW,BIOS to temp and drivers are copied to C:\Program Data\Dell\

 

as for me no modification at all.. I used TS but restored my undervolt back to default and uninstalled TS.. I even Uninstalled my Antivirus just to reduce risk of bricking but sadly it didnt update my ME Firmware.. still a reason why this bios would indicate it has a problem.. your right for those who bricked there laptop we dont know what condition or modifications they dis before flashing.. my only concern is why it didnt flash ME Firmware when we basically did the same.. no modification and run on windows desktop with very minimal programs running at background.. also we are still here and dell haven't release a new bios fix.. sad again..

edit:
to add i even delete all stuff in temp folder on safe mode before flashing.. lol

 

True. If there was any such a thing that ruled out all potential risks during flashing bios.
What @Vasudev mentions had been a good start to go back to and build upon.

 

0lok, I am wondering if in your playing around with performance utilities if it didn't change some flags somewhere or caused a system "hack" that changed something in the OS that ended up preventing the ME FW to be updated.

Per your own admission, you played around with your setup as well. That means you fall into the same category as everyone else with flashing issues where the ME FW didn't update.

Just because you uninstalled everything does NOT mean the people that wrote that software ended up reverting every and all settings in the underlying OS back to "stock". On the contrary, lazy developers are usually the ones that develop those tools and leave things in a "far from original" state.

I started out as a "hacker" back in the day, and ended up one of the most anal-retentive developers to make sure changes are tracked and reverted on the uninstall of packages.

I do appreciate your candor, but unless you did the flash from a "virgin" OS without the possibility of underlying changes that somehow affects the machine on a lower level, then you just proved the point made.

 

I may add, that none of the above in any way lets Dell/Alienware "off the hook" for not developing a more robust updating process. On the contrary I think it showed a complete lack of "fore-thought" on their part to develop a tool that does not work under more severe and less "ideal" system configurations.

 

I dont know man.. But I believe on @unclewebb and @Prema compare to the incompetent dell engr.. also I am more leaning to people like them due to the fact that OEM wants to cripple old units so that we have to buy a new one.. I might just be speculating.. hahjahaha.. but for me its quite logical that OEM for laptop are now like mobile phones.. after 2 yrs your mobile phone will be rubbish.. But you might be right.. I dont know.. hahahhahahha.. anyways youve been very informative and I am learning.. thanks.. also from the way you sound man your like a dell representative.. anyways.. tough luck for me.. have to wait for the new bios..
edit: TS is just for undervolt for better temps..

 

@Vasudev @Papusan new windows update for spectre.. i just updated.. still waiting for a new bios from dell

https://blogs.windows.com/windowsex...eltdown-security-updates-for-windows-devices/

https://support.microsoft.com/en-us/help/4090007/intel-microcode-updates

 

@judal57 @Vasudev there is also a new bios for Haswell models a.k.a Alienware 15R1 / 17 R2

http://www.dell.com/support/article...cve-2017-5754-impact-on-dell-products?lang=en

http://www.dell.com/support/home/in/en/inbsd1/Drivers/DriversDetails?driverId=RTRRK

 

Just applied the WU update my self. The build number stays unchanged and I do not notice any performanceloss. Testet with the Intel-SA-00086 and InSpectre tools and the results is the same as before (all green).

 

i updated to A10, i will check performance

 

Why did you applied the WU update through Microsoft Update Catalog if you have already updated it through latest bios?

 

Well windows update is still broken for me but now it's showing an error code 0x80080005 and nothing seems to fix it the only thing that I haven't tried is the last fix which is Download the Windows 10 Media Creation Tool (MCT) and use it to perform an “in-place upgrade” of Windows 10 and I need to find out if it will deactivate a couple of programs that can only be activated once as when I upgraded the SSD it deactivated them and had to get them reactivated and was a once off reactivation.

 

There's no need to apply that updates because W10 will simply ignore them since you have uCode already! Sometimes it will slowdown things.

You should have waited for some weeks especially because we updated MEIFW couple of days and how was the perf. after FW update.
I talked to Prema regarding MEI FW and he said he freezed MEI 9 since MEI 9.1.x disables BCLK Overclocking.

 

askwoody.com/tag/windows-update-troubleshooter/
Download link to the New version of the Windows Update troubleshooter

 

Also add Dism++ to clean Wu cache, install history, Sxs cleanup and SxS temp files.

 

I did some research before I applied the update. And found out that:

"There’s nothing wrong with installing both the firmware-based microcode update and the OS microcode update (as opposed to only doing one or the other). They won’t conflict.​

When you first turn on the PC, it will load the appropriate microcode into the CPU before it boots the OS. Once control is passed to the OS during the boot process, the OS will check the microcode loaded into the CPU against that in the OS update. If the microcode in the OS update is newer, the OS will unload the firmware-based microcode from the CPU and replace it with what is in the update."​

Source:
www.askwoody.com/2018/microsoft-helps-intel-by-releasing-kb-4090007-a-spectre-2-firmware-update-for-win10-1709-skylake-processors-only/

www.tenforums.com/windows-10-news/105244-kb4090007-intel-microcode-cumulative-update-windows-10-v1709-2.html

Double protected

Some users have uninstalled this kb update with no issues. So if I feel something is off, I will uninstall it.

Do you have both the bios and wu update @VICKYGAMEBOY ?

 

If you did your research you would find... “if your system is working normally, don’t bother downloading this patch“

Double protected

 

Yes i have windows update + catalog update + bios 1.4.4 + 11.8 ME firmware manual flash

 

Cant be protected enough
After reading trough dell's recommendations, this is in fact the right thing to do:

There are two essential components that need to be applied to mitigate the above-mentioned vulnerabilities:

1. Apply the processor microcode update via BIOS update listed in the Dell Products Affected section below.
2. Apply the applicable operating system patch. See the OS Patch Guidance section below.

http://www.dell.com/support/article...cve-2017-5754-impact-on-dell-products?lang=en

This is a bit older post (JAN 28, 2018) and does not apply to KB4090007: Intel microcode updates, but rather (KB4078130):

This patch allows people with affected systems to download the patch via the Microsoft Update Catalog, which disables the mitigations for the “Spectre variant 2.”

Note that the patch notes specifically state that you should run this patch “ ifyou are running an impacted device” (emphasis ours). In other words, if your system is working normally, don’t bother downloading this patch*. This is what Microsoft calls an “out of band” patch, and it doesn’t appear that it will be made available via Windows Update, either.​

I guess this is where you quote from and as you see, this is about a different update.​

 

i downgraded to A09. i have seen cpu performance drop :/ maybe the next time DELL hahahaha

 

I never heard of this.
This was only some sort of unconfirmed rumor.
Can you cite sources for this?

My ME was downgraded by Svet from 1425 to 1399 successfully without any problems.

 

Check Win-raid, there was new MEI FW 3448. I really meant 3448 was new version when Dell only posted update for 3425/3426.
Its nice to hear Svet actually Joined MSI and providing his experience for better OC and all goodies.
Maybe Svet did use a older version of Tool that bypass the lockdowns?

 

Looks like there will be a new NVIDIA GPU update to address the Meltdown and Spectre:

Link

It is in progress at the moment....



I am a bit hesitated to jump on this update when it comes. That said I recently updated the intel graphic driver without issues​

 

Yeah, see I have ZERO trust in nVidia, so I know for fact that any excuse they can have to reduce performance on older GPUs they take as just another marketing way to push the newer products...

Plus, if you aren't doing crypto-activities, who cares about any info they might be able to steal in regards to graphics rendering/gaming...

Just wait until people start complaining that the "fix" killed performance... Bound to happen with a company like nVidia...

 

And what’s the problem use newer Nvidia Drivers from Nvidia’s own download site?
Who say you have to use old Nvidia Drivers in new glossy Package from Dell?

 

They invest time and money in unwanted things when, any user can download from nvidia site to get them protected with worse performance.
They need to fix MEIFW and fix bricked motherboards.