I ran a diagnostic scan the day after I received my new XPS 15 Kaby Lake laptop and noticed the battery health is at 90%. I think it it should be 100% for a new computer. However the BIOS says the battery health is excellent. Which do I believe and has anyone else experienced this? I'm ready to return it. Thank you.

I searched and can't find an answer. I have an older Inspiron 1545 and it won't restart or shut down normally. I am only able to shut the laptop off using the power button. 

Many thanks if anyone can shed some light on this problem. Thanks.

Ever since I loaded W 10, this Dell laptop has been very disappointing. Won't sync with my contacts list on my iPhone. Won't go to "sleep" mode and reactivate correctly - have to fully power down and up (regardless of power settings), half the time won't add excel spreadsheet changes to the C:\file, only to the file on the desktop, won't recognize the 5 GB band in a dual band wi-fi router, etc., etc.   I give up.  Buying the Apple soon.

I recently purchased a dell XPS 13 2 in 1 and it worked fine. I updated the latest version of all drivers from the Dell site and also updated windows 10.  Now the laptop intermittently freezes for 1-2 seconds often. This happens in general browing, typing and watching you tube videos.

I am not able to understand what is causing the issue as it worked fine before updating the drivers. Any help would be appreciated.

Neither of the driver packages for the Realtek IR webcam work. One just gives me a "Device cannot start 10" error and the other starts but doesn't function and causes a BSOD on shutdown/reboot.

I'm using an Inspiron 13 5368 2-in-1 with Windows 10 home and the drivers in question are listed in the drivers page for my specific service tag. The generic drivers do work, but do not support Windows Hello as the IR functionality is needed.

Hello,

I am having extreme issues with my SSD speed. It has gotten quite bad. The SSD was a user-upgrade over the HDD that came with the Dell M4800 on the date of purchase. Initially the SSD upgrade worked well (Samsung EVO 850 500 GB). Recently, performance has taken a nose-dive. I have looked for solutions online and come up short and also failed to see any case as bad as my own.

Current Random Write IOPS - 1,144

Current Random Read IOPS - 12,752

Current Sequential Read (MB/s) - 547

Current Sequential Write (MB/s) - 103

OS - Windows 8.1,  64-bit  x64-based processor  - i7-4700MQ

SSD - 211 GB free of 420 GB

RAM - 32 GB

Some of the solutions I've attempted:

Enabling AHCI  (uses an auto-installed Intel driver, which seems funny)

Verified TRIM is enabled

Turning off system restore

Disabling drive indexing

Turning of defragmenting

Turning off paging file

Disabling hibernation

Disable Write-Caching

Turning off superfetch and windows search

Installing my discrete video card drivers again (Intel HD drivers had been updated, and the result was screwing with the usability of the device)

updating Samsung Magician (appears to have made sequential writing and random writing worse)

A lot of the above corresponding to this site: www.computing.net/.../552.html

This all started with updating the drivers for the device for the bios and etc. A number of the updates were marked as urgent, so would prefer not to roll back (security and what not).

Please help. This ***.

Simon

Hi Experts,

I have a Dell Inspiron laptop that won't start anymore. It had been working fine, but does not boot now. I do not see the light on as well that indicates that the laptop is charging. I have tried putting the battery in a friend's laptop of the same model and that seems to be working. Also, the battery adapter works with the other laptop.

Any pointers on what other steps I can do to fix this problem are greatly appreciated.

Laptop model: Dell Inspiron 15 i15547-5033sLV Signature Edition Laptop

I recently bought a brand new Dell Inspiron 13 7000 series off the dell website. After about 4 to 5 weeks of use, I notice that the screen had a couple of really prominent white spots and I know that I was not the cause as it has only been used at home. So, I contacted dell and after 2 hours on the phone, they sent a technician over. The guy came and replaced my screen with a refurbished screen and I thought all the problems would go away.

Well after about 30 minutes after he left, I noticed that the screen was bleeding light from the backlight like there was no tomorrow! Now the screen would glow white light everywhere when it's on a black screen! NOT ONLY THAT but as you may know, the inspiron 13 is a 2-in-1 tablet/laptop and I noticed that the laptop does not detect that it is in tablet mode anymore!!! Now whenever I try to use it as a table, the keyboard and trackpad do NOT disable and tablet mode is basically useless! I also noticed that the screen touch sensitivity is horrible now, sometimes it doesn't even register my finger! The last thing that I noticed is that the IR light for windows hello takes FOREVER to work while before the repair it was almost instantaneous!

Dell really needs to have better technicians or check their parts before sending them out! The original white dots were a "screen defect from factory" according to the technician. 

I have a dell xps L502X service tag no: <Service tag removed>, my hard drive has crashed. So I want to upgrade my hard drive to ssd. But even after contacting service centre and dell exclusive store no one could exactly tell me which ssd will fit into my laptop. Can anyone tell me which ssd will fit into my laptop and which is the best one?

Recently purchased Dell XPS 13 9360(2016 model) at Dubai and using it in India. AC Power Adapter 45 W is getting over hot while charging. Is it normal or need to replace AC power adapter under warranty.

Hi, my laptop is a dell Precision M6600 with Nvidia quadro 4000m and 16GB Ram. Since one month now I have a problem with the CPU that after a while start to work at 90%-100%, even without any program active. Then it start to freeze or working very very slowly. Naturally I checked processes, virus, and finally I re-formatted the HD. No way, the problem comes back again. So I started to think to a HW problem: MOBO, video card, RAM. The Dell diagnostic online finds every thing ok, but the battery. 

Indeed the battery is out of his lifetime since long time and I get always the message to replace it. 

Now,  what I discovered, and I 'm asking help and an explanation for it, is that during the CPU 100% busy the icon of the power, on the right lower side of the display, it change: from plugged in/charging   to  battery with a cross. Then, if I unplug and re-plug the power supply it go back again to  plugged in/charging and CPU return to work fine.

Don't tell me that I have to just to replace the battery becouse it should work fine eben without it.

Thanks for your help.

Hi,

How do i enable chiral/circular scroll in XPS 13 2-in-1 9365 ?

Couldn't find it in windows mouse options. Also "mouse properties" screen does not have "synaptics" tab either, as I've seen on other laptops.

Thank you

I need to restore the Bios password. How do i do that?
My laptop: Dell Vostro 5460 
Service Tag: <Service tag removed>

I bought in Vietnam.

Thanks for reading my post!.

I recently bought

Pwr+ 65W Laptop 12V Auto Car Charger for Dell-Inspiron
www.amazon.com/.../ref=cm_sw_r_cp_apa_FkXRybS50X242

 I get the standard "unrecognized charging adapter" message.  And no charging. My ACCOUNT charger works fine.  Can someone recommend a DC charger that will work?  This laptop is for a boat and 110 is not available.

Hi I recently got a no battery detected message on my Dell Inspiron 17 5000 (5759)  also dell power manager lite started telling me "system will power down when ac adapter is unplugged" the battery charger light started flashing an orange light aswell but when I unplug the AC power the battery seems to work perfectly however the charging light still flashes orange I ran diagnostics from bios and other tools on dells website they all said that there is no problem.

Can someone identify what this icon is in the taskbar? Thank You in advance for any help.

E6440 – unable to update control vault firmware

Hi, I am unable to update the control vault firmware on my e6440

The update program appears to work ok. But on reboot the update dose not complete

how can I fix this?

here is the contents of C:\Windows\System32\CVFirmwareUpgradeLog.txt

Thursday December 29, 2016 17:47:17: Command - FWUpgrade
Thursday December 29, 2016 17:47:17: There is no FW upgrade count reg key
Thursday December 29, 2016 17:47:17: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 17:47:17: Event: eventIndx: 0, Handle: 248
Thursday December 29, 2016 17:47:17: Event: eventIndx: 1, Handle: 5c
Thursday December 29, 2016 17:47:17: Event: eventIndx: 2, Handle: 6c
Thursday December 29, 2016 17:47:17: Event: eventIndx: 3, Handle: 70
Thursday December 29, 2016 17:47:17: Event: eventIndx: 4, Handle: 60
Thursday December 29, 2016 17:47:22: cvif_IsUsh (0x0)
Thursday December 29, 2016 17:47:22: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 17:47:22: Event: FwUpgradeStarted: 1, Handle: 5c
Thursday December 29, 2016 17:47:22: Control Vault getting chip type
Thursday December 29, 2016 17:47:22: Could not determine chip type
Thursday December 29, 2016 17:47:22: Failed. Return code: 15 Set number of failed FW upgrades to 1

Thursday December 29, 2016 17:47:22: Event: FwUpgradeError: 4, Handle: 60

Thursday December 29, 2016 17:54:46: Command - FWUpgrade
Thursday December 29, 2016 17:54:46: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 17:54:46: Event: eventIndx: 0, Handle: 4e0
Thursday December 29, 2016 17:54:46: Event: eventIndx: 1, Handle: 468
Thursday December 29, 2016 17:54:46: Event: eventIndx: 2, Handle: 1f4
Thursday December 29, 2016 17:54:46: Event: eventIndx: 3, Handle: 4e8
Thursday December 29, 2016 17:54:46: Event: eventIndx: 4, Handle: 4e4
Thursday December 29, 2016 17:54:51: cvif_IsUsh (0x0)
Thursday December 29, 2016 17:54:51: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 17:54:51: Event: FwUpgradeStarted: 1, Handle: 468
Thursday December 29, 2016 17:54:51: Control Vault getting chip type
Thursday December 29, 2016 17:54:51: Could not determine chip type
Thursday December 29, 2016 17:54:51: Failed. Return code: 15 Set number of failed FW upgrades to 2

Thursday December 29, 2016 17:54:51: Event: FwUpgradeError: 4, Handle: 4e4

Thursday December 29, 2016 17:54:54: Command - FWUpgrade
Thursday December 29, 2016 17:54:54: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 17:54:54: Event: eventIndx: 0, Handle: 520
Thursday December 29, 2016 17:54:54: Event: eventIndx: 1, Handle: 524
Thursday December 29, 2016 17:54:54: Event: eventIndx: 2, Handle: 528
Thursday December 29, 2016 17:54:54: Event: eventIndx: 3, Handle: 52c
Thursday December 29, 2016 17:54:54: Event: eventIndx: 4, Handle: 530
Thursday December 29, 2016 17:55:00: cvif_IsUsh (0x0)
Thursday December 29, 2016 17:55:00: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 17:55:00: Event: FwUpgradeStarted: 1, Handle: 524
Thursday December 29, 2016 17:55:00: Control Vault getting chip type
Thursday December 29, 2016 17:55:00: Could not determine chip type
Thursday December 29, 2016 17:55:00: Failed. Return code: 15 Set number of failed FW upgrades to 3

Thursday December 29, 2016 17:55:00: Event: FwUpgradeError: 4, Handle: 530

Thursday December 29, 2016 18:09:43: Command - FWUpgrade
Thursday December 29, 2016 18:09:43: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 18:09:43: Event: eventIndx: 0, Handle: 208
Thursday December 29, 2016 18:09:43: Event: eventIndx: 1, Handle: 1c4
Thursday December 29, 2016 18:09:43: Event: eventIndx: 2, Handle: 1c8
Thursday December 29, 2016 18:09:43: Event: eventIndx: 3, Handle: 1dc
Thursday December 29, 2016 18:09:43: Event: eventIndx: 4, Handle: 20c
Thursday December 29, 2016 18:09:49: cvif_IsUsh (0x0)
Thursday December 29, 2016 18:09:49: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 18:09:49: Event: FwUpgradeStarted: 1, Handle: 1c4
Thursday December 29, 2016 18:09:49: Control Vault getting chip type
Thursday December 29, 2016 18:09:49: Could not determine chip type
Thursday December 29, 2016 18:09:49: Failed. Return code: 15 Set number of failed FW upgrades to 4

Thursday December 29, 2016 18:09:49: Event: FwUpgradeError: 4, Handle: 20c

Sunday February 12, 2017 15:22:11: Command - FWUpgrade
Sunday February 12, 2017 15:22:11: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 15:22:11: Event: eventIndx: 0, Handle: 50
Sunday February 12, 2017 15:22:11: Event: eventIndx: 1, Handle: 54
Sunday February 12, 2017 15:22:11: Event: eventIndx: 2, Handle: 44
Sunday February 12, 2017 15:22:11: Event: eventIndx: 3, Handle: 20c
Sunday February 12, 2017 15:22:11: Event: eventIndx: 4, Handle: 1ec
Sunday February 12, 2017 15:22:16: cvif_IsUsh (0x0)
Sunday February 12, 2017 15:22:16: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 15:22:16: Event: FwUpgradeStarted: 1, Handle: 54
Sunday February 12, 2017 15:22:16: Control Vault getting chip type
Sunday February 12, 2017 15:22:16: Could not determine chip type
Sunday February 12, 2017 15:22:16: Failed. Return code: 15 Set number of failed FW upgrades to 5

Sunday February 12, 2017 15:22:16: Event: FwUpgradeError: 4, Handle: 1ec

Sunday February 12, 2017 15:45:51: Command - FWUpgrade
Sunday February 12, 2017 15:45:51: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 15:45:51: Event: eventIndx: 0, Handle: 214
Sunday February 12, 2017 15:45:51: Event: eventIndx: 1, Handle: 21c
Sunday February 12, 2017 15:45:51: Event: eventIndx: 2, Handle: 220
Sunday February 12, 2017 15:45:51: Event: eventIndx: 3, Handle: 224
Sunday February 12, 2017 15:45:51: Event: eventIndx: 4, Handle: 228
Sunday February 12, 2017 15:45:57: cvif_IsUsh (0x0)
Sunday February 12, 2017 15:45:57: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 15:45:57: Event: FwUpgradeStarted: 1, Handle: 21c
Sunday February 12, 2017 15:45:57: Control Vault getting chip type
Sunday February 12, 2017 15:45:57: Could not determine chip type
Sunday February 12, 2017 15:45:57: Failed. Return code: 15 Set number of failed FW upgrades to 6

Sunday February 12, 2017 15:45:57: Event: FwUpgradeError: 4, Handle: 228

Sunday February 12, 2017 15:51:28: Command - FWUpgrade
Sunday February 12, 2017 15:51:28: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 15:51:28: Event: eventIndx: 0, Handle: 1dc
Sunday February 12, 2017 15:51:28: Event: eventIndx: 1, Handle: 1e0
Sunday February 12, 2017 15:51:28: Event: eventIndx: 2, Handle: 204
Sunday February 12, 2017 15:51:28: Event: eventIndx: 3, Handle: 218
Sunday February 12, 2017 15:51:28: Event: eventIndx: 4, Handle: 21c
Sunday February 12, 2017 15:51:33: cvif_IsUsh (0x0)
Sunday February 12, 2017 15:51:33: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 15:51:33: Event: FwUpgradeStarted: 1, Handle: 1e0
Sunday February 12, 2017 15:51:33: Control Vault getting chip type
Sunday February 12, 2017 15:51:34: Could not determine chip type
Sunday February 12, 2017 15:51:34: Failed. Return code: 15 Set number of failed FW upgrades to 7

Sunday February 12, 2017 15:51:34: Event: FwUpgradeError: 4, Handle: 21c

Sunday February 12, 2017 16:20:48: Command - FWUpgrade
Sunday February 12, 2017 16:20:48: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 16:20:48: Event: eventIndx: 0, Handle: 1c4
Sunday February 12, 2017 16:20:48: Event: eventIndx: 1, Handle: 1c8
Sunday February 12, 2017 16:20:48: Event: eventIndx: 2, Handle: 1e4
Sunday February 12, 2017 16:20:48: Event: eventIndx: 3, Handle: 210
Sunday February 12, 2017 16:20:48: Event: eventIndx: 4, Handle: 214
Sunday February 12, 2017 16:20:53: cvif_IsUsh (0x0)
Sunday February 12, 2017 16:20:53: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 16:20:53: Event: FwUpgradeStarted: 1, Handle: 1c8
Sunday February 12, 2017 16:20:53: Control Vault getting chip type
Sunday February 12, 2017 16:20:53: Could not determine chip type
Sunday February 12, 2017 16:20:53: Failed. Return code: 15 Set number of failed FW upgrades to 8

Sunday February 12, 2017 16:20:53: Event: FwUpgradeError: 4, Handle: 214

Sunday February 12, 2017 16:31:23: Command - FWUpgrade
Sunday February 12, 2017 16:31:23: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 16:31:23: Event: eventIndx: 0, Handle: 210
Sunday February 12, 2017 16:31:23: Event: eventIndx: 1, Handle: 214
Sunday February 12, 2017 16:31:23: Event: eventIndx: 2, Handle: 218
Sunday February 12, 2017 16:31:23: Event: eventIndx: 3, Handle: 21c
Sunday February 12, 2017 16:31:23: Event: eventIndx: 4, Handle: 220
Sunday February 12, 2017 16:31:28: cvif_IsUsh (0x0)
Sunday February 12, 2017 16:31:28: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 16:31:28: Event: FwUpgradeStarted: 1, Handle: 214
Sunday February 12, 2017 16:31:28: Control Vault getting chip type
Sunday February 12, 2017 16:31:28: Could not determine chip type
Sunday February 12, 2017 16:31:28: Failed. Return code: 15 Set number of failed FW upgrades to 9

Sunday February 12, 2017 16:31:28: Event: FwUpgradeError: 4, Handle: 220

Saturday February 18, 2017 10:09:12: Command - FWUpgrade
Saturday February 18, 2017 10:09:12: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 18, 2017 10:09:12: Event: eventIndx: 0, Handle: 4c
Saturday February 18, 2017 10:09:12: Event: eventIndx: 1, Handle: 50
Saturday February 18, 2017 10:09:12: Event: eventIndx: 2, Handle: 48
Saturday February 18, 2017 10:09:12: Event: eventIndx: 3, Handle: 204
Saturday February 18, 2017 10:09:12: Event: eventIndx: 4, Handle: 1fc
Saturday February 18, 2017 10:09:17: cvif_IsUsh (0x0)
Saturday February 18, 2017 10:09:17: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 18, 2017 10:09:17: Event: FwUpgradeStarted: 1, Handle: 50
Saturday February 18, 2017 10:09:18: Control Vault getting chip type
Saturday February 18, 2017 10:09:18: Could not determine chip type
Saturday February 18, 2017 10:09:18: Failed. Return code: 15 Set number of failed FW upgrades to 10

Saturday February 18, 2017 10:09:18: Event: FwUpgradeError: 4, Handle: 1fc

Tuesday February 21, 2017 18:32:25: Command - FWUpgrade
Tuesday February 21, 2017 18:32:25: Event: SUCCESS creating FW Upgrade events. Return code: 0
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 0, Handle: 210
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 1, Handle: 218
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 2, Handle: 1c4
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 3, Handle: 1c8
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 4, Handle: 208
Tuesday February 21, 2017 18:32:30: cvif_IsUsh (0x0)
Tuesday February 21, 2017 18:32:30: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Tuesday February 21, 2017 18:32:30: Event: FwUpgradeStarted: 1, Handle: 218
Tuesday February 21, 2017 18:32:30: Control Vault getting chip type
Tuesday February 21, 2017 18:32:30: Could not determine chip type
Tuesday February 21, 2017 18:32:30: Failed. Return code: 15 Set number of failed FW upgrades to 11

Tuesday February 21, 2017 18:32:30: Event: FwUpgradeError: 4, Handle: 208

Tuesday February 21, 2017 20:36:12: Command - FWUpgrade
Tuesday February 21, 2017 20:36:12: Event: SUCCESS creating FW Upgrade events. Return code: 0
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 0, Handle: 1d8
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 1, Handle: 1dc
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 2, Handle: 220
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 3, Handle: 228
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 4, Handle: 22c
Tuesday February 21, 2017 20:36:17: cvif_IsUsh (0x0)
Tuesday February 21, 2017 20:36:17: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Tuesday February 21, 2017 20:36:17: Event: FwUpgradeStarted: 1, Handle: 1dc
Tuesday February 21, 2017 20:36:17: Control Vault getting chip type
Tuesday February 21, 2017 20:36:17: Could not determine chip type
Tuesday February 21, 2017 20:36:17: Failed. Return code: 15 Set number of failed FW upgrades to 12

Tuesday February 21, 2017 20:36:17: Event: FwUpgradeError: 4, Handle: 22c

Tuesday February 21, 2017 21:53:18: Command - FWUpgrade
Tuesday February 21, 2017 21:53:18: Event: SUCCESS creating FW Upgrade events. Return code: 0
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 0, Handle: 210
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 1, Handle: 214
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 2, Handle: 218
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 3, Handle: 21c
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 4, Handle: 220
Tuesday February 21, 2017 21:53:23: cvif_IsUsh (0x0)
Tuesday February 21, 2017 21:53:23: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Tuesday February 21, 2017 21:53:23: Event: FwUpgradeStarted: 1, Handle: 214
Tuesday February 21, 2017 21:53:23: Control Vault getting chip type
Tuesday February 21, 2017 21:53:23: Could not determine chip type
Tuesday February 21, 2017 21:53:23: Failed. Return code: 15 Set number of failed FW upgrades to 13

Tuesday February 21, 2017 21:53:23: Event: FwUpgradeError: 4, Handle: 220

Saturday February 25, 2017 11:04:00: Command - FWUpgrade
Saturday February 25, 2017 11:04:00: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 25, 2017 11:04:00: Event: eventIndx: 0, Handle: 210
Saturday February 25, 2017 11:04:00: Event: eventIndx: 1, Handle: 214
Saturday February 25, 2017 11:04:00: Event: eventIndx: 2, Handle: 218
Saturday February 25, 2017 11:04:00: Event: eventIndx: 3, Handle: 21c
Saturday February 25, 2017 11:04:00: Event: eventIndx: 4, Handle: 220
Saturday February 25, 2017 11:04:05: cvif_IsUsh (0x0)
Saturday February 25, 2017 11:04:05: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 25, 2017 11:04:05: Event: FwUpgradeStarted: 1, Handle: 214
Saturday February 25, 2017 11:04:05: Control Vault getting chip type
Saturday February 25, 2017 11:04:05: Could not determine chip type
Saturday February 25, 2017 11:04:05: Failed. Return code: 15 Set number of failed FW upgrades to 14

Saturday February 25, 2017 11:04:05: Event: FwUpgradeError: 4, Handle: 220

Saturday February 25, 2017 15:44:15: Command - FWUpgrade
Saturday February 25, 2017 15:44:15: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 25, 2017 15:44:15: Event: eventIndx: 0, Handle: 210
Saturday February 25, 2017 15:44:15: Event: eventIndx: 1, Handle: 214
Saturday February 25, 2017 15:44:15: Event: eventIndx: 2, Handle: 218
Saturday February 25, 2017 15:44:15: Event: eventIndx: 3, Handle: 21c
Saturday February 25, 2017 15:44:15: Event: eventIndx: 4, Handle: 220
Saturday February 25, 2017 15:44:20: cvif_IsUsh (0x0)
Saturday February 25, 2017 15:44:20: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 25, 2017 15:44:20: Event: FwUpgradeStarted: 1, Handle: 214
Saturday February 25, 2017 15:44:20: Control Vault getting chip type
Saturday February 25, 2017 15:44:20: Could not determine chip type
Saturday February 25, 2017 15:44:20: Failed. Return code: 15 Set number of failed FW upgrades to 15

Saturday February 25, 2017 15:44:20: Event: FwUpgradeError: 4, Handle: 220

Saturday February 25, 2017 17:56:37: Command - FWUpgrade
Saturday February 25, 2017 17:56:37: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 25, 2017 17:56:37: Event: eventIndx: 0, Handle: 1f0
Saturday February 25, 2017 17:56:37: Event: eventIndx: 1, Handle: 218
Saturday February 25, 2017 17:56:37: Event: eventIndx: 2, Handle: 21c
Saturday February 25, 2017 17:56:37: Event: eventIndx: 3, Handle: 220
Saturday February 25, 2017 17:56:37: Event: eventIndx: 4, Handle: 224
Saturday February 25, 2017 17:56:43: cvif_IsUsh (0x0)
Saturday February 25, 2017 17:56:43: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 25, 2017 17:56:43: Event: FwUpgradeStarted: 1, Handle: 218
Saturday February 25, 2017 17:56:43: Control Vault getting chip type
Saturday February 25, 2017 17:56:43: Could not determine chip type
Saturday February 25, 2017 17:56:43: Failed. Return code: 15 Set number of failed FW upgrades to 16

Saturday February 25, 2017 17:56:43: Event: FwUpgradeError: 4, Handle: 224

Sunday February 26, 2017 15:15:48: Command - FWUpgrade
Sunday February 26, 2017 15:15:48: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 26, 2017 15:15:48: Event: eventIndx: 0, Handle: 1dc
Sunday February 26, 2017 15:15:48: Event: eventIndx: 1, Handle: 208
Sunday February 26, 2017 15:15:48: Event: eventIndx: 2, Handle: 1c0
Sunday February 26, 2017 15:15:48: Event: eventIndx: 3, Handle: 1c4
Sunday February 26, 2017 15:15:48: Event: eventIndx: 4, Handle: 1e8

Sunday February 26, 2017 15:16:43: Command - FWUpgrade
Sunday February 26, 2017 15:16:43: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 26, 2017 15:16:43: Event: eventIndx: 0, Handle: 210
Sunday February 26, 2017 15:16:43: Event: eventIndx: 1, Handle: 54
Sunday February 26, 2017 15:16:43: Event: eventIndx: 2, Handle: 48
Sunday February 26, 2017 15:16:43: Event: eventIndx: 3, Handle: 20c
Sunday February 26, 2017 15:16:43: Event: eventIndx: 4, Handle: 220
Sunday February 26, 2017 15:16:48: cvif_IsUsh (0x0)
Sunday February 26, 2017 15:16:48: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 26, 2017 15:16:48: Event: FwUpgradeStarted: 1, Handle: 54
Sunday February 26, 2017 15:16:48: Control Vault getting chip type
Sunday February 26, 2017 15:16:49: Could not determine chip type
Sunday February 26, 2017 15:16:49: Failed. Return code: 15 Set number of failed FW upgrades to 17

Sunday February 26, 2017 15:16:49: Event: FwUpgradeError: 4, Handle: 220

Sunday February 26, 2017 16:48:10: Command - FWUpgrade
Sunday February 26, 2017 16:48:10: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 26, 2017 16:48:10: Event: eventIndx: 0, Handle: 44
Sunday February 26, 2017 16:48:10: Event: eventIndx: 1, Handle: 1fc
Sunday February 26, 2017 16:48:10: Event: eventIndx: 2, Handle: 1f8
Sunday February 26, 2017 16:48:10: Event: eventIndx: 3, Handle: 200
Sunday February 26, 2017 16:48:10: Event: eventIndx: 4, Handle: 204
Sunday February 26, 2017 16:48:15: cvif_IsUsh (0x0)
Sunday February 26, 2017 16:48:15: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 26, 2017 16:48:15: Event: FwUpgradeStarted: 1, Handle: 1fc
Sunday February 26, 2017 16:48:15: Control Vault getting chip type
Sunday February 26, 2017 16:48:16: Could not determine chip type
Sunday February 26, 2017 16:48:16: Failed. Return code: 15 Set number of failed FW upgrades to 18

Sunday February 26, 2017 16:48:16: Event: FwUpgradeError: 4, Handle: 204

After 2 years of usage, my Alienware 17 R2 battery just stopped working. I get a a "battery failure, replace now message" every time the laptop boots. I tried all the fixes, except removing the battery thanks to the wonderful design of the laptop which requires taking apart everything to get to the battery. 

I have given up fixing it but now that i am searching for a new replacement battery, I just cant find one for this model. I have scoured the net in search for the battery and have come up with nothing except a replacement from a Chinese vendor. Dell apparently doesn't carry it and I have read in various forums that if i install a non oem battery, the system might not recognize it.

Have been using the laptop as a desktop for the past couple of months. I did not pay more than 2 grand for a such a sub par quality product.  

My webcam does not work, and it only shows a black screen. in addition, it does not display on the device manager -> imaging devices, but sometimes it does.

Trying to fix this problem, I have diagnosed my device using the pre-boot tool, the PSA diagnostic, and USB controller error occurs(see attachment below).

USB controller error suggests that I should  do this steps to solve the error, but my webcam problem is still there:

• Please update BIOS.
• Turn off the computer and reseat the USB device.
• Try a different working USB device and check if the error is still seen.
• Restart your computer and rerun the PSA diagnostics.

Although The PSA diagnostics does not detect the **USB controller error** is not showed anymore, my webcam is still showing the black screen.