New Dell System Bios 15R2 / 17R3 1.3.6

Just saw this bios and updated from the Dell Support site (Marked as URGENT)

Fixes & Enhancements
-Caldera mode1 enter mode5 setting
-Remove TDPL method for DPT

Anyone know what this does?

Seems ok so far...

 

@Prema, any idea what this change log means?

 

So there's something involving the Graphics Amplifier (Caldera is its code-name).
The 13 R2 has no BIOS version online (yet).
Also, with every BIOS, make note of anything not highlighted in the released notes.
( Link to BIOS.)

 

Maybe some updated Sleep/Resume profiles for GA, so that it acts and feels like an internal discrete graphics chip.
Also, it could be support for upcoming pascal's that utilise the same skylake chipset.

 

i'll give it a go wtih my 1070 tonight and see if i notice any different behavior with the way they integrate

 

http://www.dell.com/support/home/us...ls?productCode=alienware-13-r2&driverId=FM3F7
It's up for the 13 R2. I'm going to flash it.
EDIT: Don't notice much of a difference from BIOS 1.2.15. The Graphics Amp performance is still the same. The Keyboard Repeat Rate Sleep Bug is still present. No RAM OC options. CPU performance is about the same too.
EDIT 2: I don't know if it was due to the BIOS update or the software update, but sleep and hibernate are present when using the GA.

 

Beware all I've suffered multiple DRIVER_POWER_STATE_FAILURE BSOD on 1.3.6. Since these dumb BSODs can happen for any reason/config YMMV, but it happens for me whenever I've put the GA into Sleep state (this is one of the new features of the BIOS). At some point in sleep state Windows BSOD and simply shuts down (instead of staying in sleep).

Turning off sleep for now with the GA attached. If it continues I'll try and roll back to 1.2.15.

 

,I have a problem since five days ago, when I try to turn off the computer takes a very long time between 5-10 minutes. and later turn on it's normal, but I check with bluescreen program and show Driver_state_power_failure and ccleaner show memory dump ... it is something related ?? as you can solve? my bios are 1.2.8 alienware 17 R3... and windows 10 aniversary update

 

It's not related. My BSOD started right after installing 1.3.6 BIOS.


Sent from my iPhone using Tapatalk

 

1.3.6 is no longer available for 13R2. There is only 1.2.15. Support could not explain me what does it mean by email. I've already flashed 1.3.6 and have no idea if it's safe to stay on this version

 

OK, I take that back, sorry. So now it seems I'm having the same exact shutdown problems and BSOD as you are. This is still on 1.3.6, same exact behavior as yours.

I'll respond to your other thread. Since we are on different BIOS, it may be video card drivers or something else. I'll post an update if I figure it out.

 

I think the driver_state_power_failure BSOD is not related to the BIOS, I'm on 1.2.8 and it happened to mine as well

currently I suspect it's something to do with the latest Killer WLAN drivers

that or it's the latest 372 Geforce driver. It only happened once I updated to both of these, but the WLAN driver is high on the suspect list

 

Ok thanks, sounds like a good place to start. There were very recent driver updates to both yah. I'm gonna roll back to 1.2.15 and monitor. If I keep getting the bsod I can rule out the bios. Then I'll try rolling back the killer and nvidia drivers one at a time.


Sent from my iPad using Tapatalk

 

So the BSOD was due to the newest Killer Networking driver (version 1.1.62.1727) and NOT the 1.3.6 BIOS. Kudos to Zenetic. Will post again if anything else comes up (and think twice and try to troubleshoot before posting!).

 

I have installed 1.3.6 and my 17R3 is working fine, and I have had no issues. I also have installed the latest GeForce driver, however I have the Intel 8260 and haven't updated the network drivers. So the issue seems to be with the Killer drivers (again).

 

Just realized HDD light actually works now with 1.3.6

 

Upgraded from 1.2.14 after an issue where I was unable to power up the laptop (only power LED would light up, no other activity). After clearing CMOS and patiently going through Fn + power button start up a few times with and without the main battery connected it finally beeped 5 times and then booted into the system diagnostics. Afterwards I was able to boot normally and flash BIOS 1.3.6. No issues since.

 

Is anyone else getting critical Kernel Power messages in Event Viewer since updating the BIOS (The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.)? Event ID 41, Task 63.

This is when shutting down or rebooting the PC with the GA attached.

Sent from my Nexus 6 using Tapatalk

 

Make sure you have unplugged the AGA before you try to flash the bios.

 

Yup, the only thing I had attached to my AW when I flashed 1.3.6 was the AC adapter.

These errors definitely started happening after installing the new bios. It isn't the killer drivers because my bsod have completely vanished since downgrading the drivers. Now all that's left are these lousy Critical events. It's also creating "Windows was not properly shut down" Critical messages in Reliability History.

Otherwise the AW+AGA behaves perfectly. Sleeps and shuts down with the AGA attached without issue. Just creates these errors.

I have a suspicion that it's related to the new sleep modes enabled for the AGA, but who knows. Could be just my AW. Anyhoo, just downgraded back to 1.2.15 and all the errors have stopped. I'm not taking any chances.

 

You all have right - Dell also updated AGA software:
http://downloads.dell.com/FOLDER03877126M/2/App_DT_Caldera3.0.7.0_W10_Setup_NX9DF_ZPE.exe

Maybe it is correlated with BIOS update.

PS - I'm waiting for an update myself - just few days more.

 

With 1.3.6 and new GA software, my computer will not shutdown. It ALWAYS restarts.

I uninstalled the newer GA software and went back to the old software. Issue resolved. Installed the new software, issue came back. Reinstalled Windows clean with new GA software, won't shut down. So the eff if I'm using this newer software, using the old software it works fine.

 

So that's the way I am always installing updates about 2-3 week delay to avoid problems.
I also noticed, that package was updated 17th of August, but probably it will not resolve your problem.

 

That's a very smart move. But the temptation can be great...

Seriously though, for BIOS updates I'm going to try to wait even longer, like a month. I waited about 2 weeks before upgrading from 1.2.8 to 1.2.13 and still ran into issues. I then updated to 1.2.14 with no problems, but will still wait for this one.

 

1.3.6 installed last week and working w/o issue. I don't have a GA and haven't updated any other drivers except nvidia. All is well.

 

I'm still on 1.2.8 because it's been the most stable for me, I'm tempted to try 1.3.6 but I'll wait a bit longer.

 

I'm still on 1.2.3 and will probably never upgrade after my past experiences. The old mantra "if it ain't broke don't try and fix it" comes to mind now.

 

I stayed on 1.2.2 with my 15R2 until last week when I went to 1.3.6

So far no issues.

 

Installed today on my 15 and its been stable so far.

 

Got my AW 15 yesterday, factory BIOS was on 1.2.8 so I am wondering if I should update from 1.2.8 to 1.3.x or stick with tried and tested quote "If ain't broke, don't fix/update it!!!"?
Or upgrade to 1.2.15 and then to latest update? NV 353.40 driver is always crashing and pc is overheating. I removed McAfee and IDPT.

 

ask to @VICKYGAMEBOY he know a lot abput your model

 

Well, 1.3.6 is safe and works fine, i recommend people to install OS using RAID instead of AHCI, seems IRST drivers are much more stable.. also stick with stock intel TDPF drivers, and IME, as well as chipset drivers, stay away from latest killer wireless suite.. apart from that Nvidia and Intel ones You can use the latest from their website without any issues..

 

Well, I uninstalled ITDPF, it was overheating my PC. I downloaded Killer 1.57 from their website and its quite stable. I prefer AHCI and SSD is way faster than HDD so RAID is somewhat kills the purpose. Now I have to download Single Language to activate my OEM license.
To @VICKYGAMEBOY: Any Idea which version of Single Language to download? Is it English US or English International?

 

Both will Work.. Just Get English US just to be on safe side.. AHCI with some SSD have issues, specially with BIOS above 1.2.2, like the Read/Write Indicator, along with some minor freeze, ive tested on 10 different setups, the reason I recomnd using RAID, it doesn't raid ur system anywys.. just installs the intel driver, which detects ur NVMe proper.. it also have negative point, when ur clearing ur cmos for somereason it deletes the RAID driver. and ull be stuck with Inaccesible device..

 

Updated today from 1.2.2 to the newest BIOS, haven't seen any problems so far.. Hopefully none will arise.

 

Sorry for replying late. I was unwell for couple of weeks. English US definitely worked and I used MS MCT to verify which ISO to download and upgraded to Anniv. Yeah you're correct RAID gives more R/W than default NVMe driver. I'll upload ATTO disk results with RAID,NVMe native and NVMe w/ IRST in a couple of days.

 

sure man, take care of urself, even I'm falling sick recently.. just post any information you have.. that would give other users some idea as well, for now me and @judal57 are testing throttling issues, both have tested.. we will make a thread soon, make sure to follow.. peace..

 

Updated my signature to include 3DM scores. Take care VickyGameBoy.

 

Are you sure TDPF is working? It only works on 1.2.8.
If in use a newer BIOS it fails to initialise on boot up as recorded in my system logs. I'm discussing this with Dell at the moment and were working on a solution but all firmware past 1.2.8. Doesn't work.

Sent from my SM-G935F using Tapatalk

 

@vickyboy why do you recommend installing using RAID and not AHCI. I don't plan to use raid, and every guide I have seen recommends using AHCI. I also intend to never install the IRST drivers.

Correct me if I am wrong

 

you can fiddle around and see whats best for u, the reason why im sticking to RAID instead of AHCI, i get microfreezes using AHCI, and also it doesnt detect my samsung NVMe PM951 properly. RAID doesnt mean its raided.. just it install proper drivers, and shows as proper drive unlike AHCI MS drivers.. also i get better read rates.. it depends on which drive ur using.. for me RAID is better, and somewhere in Intel / OEM forums they have suggested to use RAID, even though ur not gna raid..

 

@VICKYGAMEBOY : I think those glitches are fixed in latest 1.3.9 BIOS. If you stick with windows, RAID mode has the optimal/best R/W speeds. If there is need to add multiple OSes stick with AHCI to ensure wider compatibility across multitude of distros.