Latitude 5400 Sleep Issues

Have you looked at any of the BIOS settings, specifically Block Sleep and Wake On Lan? This support page has more information.

Hi,

I faced a same problem. The BIOS settings, Block Sleep and Wake On Lan both disabled.

Any updates?  I'm having the same problem with a bunch of 5400 and 5500s.  vPro won't even work when they do this.

Thanks

I am having the same issue. I am trying to configure machines at a remote location and I have to keep getting someone onsite to wake up the machines. 
They are plugged in and set to not sleep on AC power, and connected via LAN.
I have had success in disabling the EEE (energy efficient ethernet) setting in the NIC configuration, but it seems to be happening again.
Dell Latitude 5400. 

Has anyone figured this out yet?  We've deployed quite a few of these now and they all have this issue.  In some cases the laptop will no longer ping just after about 30 minutes, or it randomly responds, if no one has logged on to it.  If the network cable is unplugged and reconnected the connection stays normal again for a while, but then stops again.  Also, this is occurring either with the network cable directly connected to the laptop or while connected to the WD19 dock.

Looks like our shipment of laptops are also exhibiting this behavior. Will report back if we find any leads!

Same here. Our IT department says this is a "new feature". When I hit the power button the fan stops momentarily, but then resumes. The light on the power button turns off (IT says it is to conserve power, but how much power does one LED really consume?), but if I touch the keyboard or move my external mouse the screen immediately comes back on. If I pick up my mouse to turn the power button off, then the laptop comes back on and I have to put it to "sleep" again.

So annoying because there's times I've put it in my backpack and hours later I pull it out and the fan is running because it got hot and now the battery is almost dead. Also when it was new, it would not recognize any headphones plugged in after it was already powered up. IT finally fixed that issue.

I wish Dell would fix this "new power feature". Really wish I had my old 7480 back.

We also have the same issue with all of the Latitude 5400's we purchased and it would drive me crazy because it would prevent us from accessing the laptops remotely. I believe I have figured out what is causing it however. Even with sleep disabled, Windows 10 has a feature called "Connected Standby". It's only supported if the device itself supports it (which the Latitude 5400 does). This mode basically replaces normal sleep mode altogether. What Connected Standby does is it puts the computers into a low power state but still allows it to be waken up for any Windows Updates that need to be installed. We used Lenovo computers prior to switching to Dell and I noticed that the Lenovo's we bought did not have this feature which is why we never experienced it until switching over to Dell.

In order to disable this, open up regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power and the set the key "CsEnabled" to 0 and then reboot. This will disable connected standby mode and enable normal sleep mode on the laptop itself. Since the normal sleep mode is now enabled, you can control if the computer goes to sleep as you normally would through the Windows Power settings in Control Panel. I hope this helps.

The trick that seems to have been working on one machine was Disabling the "C-states" located in the BIOS. This was suggested in another thread on Dell forums. We did also make sure that sleep states for Windows was disabled and that the green low-power modes for the ethernet was also disabled.

We've had one computer that we noticed was having issues dropping network connections and 'resume' once keyboard or mouse was moved. After disabling "C-States", things seem to work as expected.

Unfortunately I am also reporting my 4 of 4 my Latitude 5400 are exhibiting poor sleep behaviour and more often than not they are not resuming from sleep cleanly, and may not turn back on, or after some delay will BSOD and reboot. The computer reports entering into connected standby prior to the BSODs.

This is what I am using:

• Dell factory Windows 1909 image
• Upgraded to Windows 2004 update
• Upgraded all drivers and BIOS to current as of June 2020 using Dell Command
• BIOS v 1.7.4

BSOD Details:

This was probably caused by the following module: pdc.sys (0xFFFFF8041829E5D0)
Bugcheck code: 0x14F (0x4, 0x2, 0xFFFFF8041829E5D0, 0xFFFF9D8FD66E5A50)
Error: PDC_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\drivers\pdc.sys
description: Power Dependency Coordinator Driver
Bug check description: This indicates that a system component failed to respond within the allocated time period, preventing the system from exiting connected standby.
This is likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Notes:

• 2004 no longer supports Connected Standby alterations via Registry. Its also called Modern Standby now in Microsoft literature... but not in the OS itself.
• I have removed Sleep modes for users and added Hibernate instead... not too many complaints yet but its early days.

Here is System Information XML from Dell Command for anyone else interested in software versions

http://www.w3.org/2001/XMLSchema" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance">

Operating System
Microsoft Windows 10 Pro (x64)
10.0.19041


BIOS
BIOS
1.7.4


Driver
Realtek(R) Audio
6.0.8940.1
0236


Driver
Intel(R) Host Bridge/DRAM Registers - 3E34
10.1.14.7
3E34


Driver
Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft)
10.0.19041.329
9DED


Driver
PCI standard RAM Controller
10.0.19041.1
9DEF


Driver
Intel(R) SPI (flash) Controller - 9DA4
10.1.15.6
9DA4


Driver
Intel(R) Gaussian Mixture Model - 1911
10.1.7.3
1911


Driver
Intel(R) Thermal Subsystem - 9DF9
10.1.15.6
9DF9


Driver
I/O LPC Controller - 9D84 for Intel(R) 300 Series Chipset Family On-Package Platform Controller Hub
10.1.15.6
9D84


Driver
Intel(R) Smart Sound Technology (Intel(R) SST) OED
10.23.3349.218
0222


Driver
Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller
10.23.0.3349
9DC8


Driver
Intel(R) PCI Express Root Port #8 - 9DBF
10.1.15.6
9DBF


Driver
Realtek PCIE CardReader
10.0.18362.21317
525A


Driver
Intel(R) SMBus - 9DA3
10.1.15.6
9DA3


Driver
Intel(R) Wireless-AC 9560 160MHz
21.70.0.6
9DF0


Driver
Intel(R) Chipset SATA/PCIe RST Premium Controller
17.5.3.1026
282A


Driver
Alps Pointing-device Driver
10.3201.101.312


Driver
Intel 825xx 10/100/1000 Ethernet Network Drivers
25.0.1.0


Driver
Realtek USB Audio
6.3.9600.2215


Driver
Intel(R) HID Event Filter
2.2.1.377


Driver
Intel(R) Wireless Bluetooth(R)
21.80.0.3


Driver
Intel(R) Serial IO GPIO Host Controller - INT34BB
30.100.1915.1


Driver
Intel(R) Management Engine Components
1938.12.0.1317


Application
Dell Power Manager Service
3.6.0


Application
Dell Update - SupportAssist Update Plugin
5.1.0.11858


Application
Dell Command | Update for Windows 10
3.1.2


FRMW
PM981a NVMe Samsung 256GB
1530.2029


Application
Dell Digital Delivery Services
4.0.52.0


Driver
Graphics
26.20.100.8141


Driver
Intel Software Installer
21.70.0.6


Driver
Intel(R) Dynamic Tuning
8.6.10401.9906

I am having similar issues, although may be different

https://www.dell.com/community/Latitude/Latitude-5400-Sleep-Crashes-in-Windows-10-2004/m-p/7637112#M23531

Microsoft Windows 10 uses Modern Standby instead of S3 and problems are here.

https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby-vs-s3

I switched to old S3 power mode and all works fine as usual.

How to do it?! Just change the CsEnabled to 0.

You can use ready ".reg" file, download and open it.

http://notebookcheck.com/fileadmin/Notebooks/Sonstiges/connected-standby-disable.reg

or you can manually create ".reg" file, save and run or edit Windows Registry directly

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power]
"CsEnabled"=dword:00000000

You need restart your laptop after it.

If you want to restore the default mode - Modern Standby, you need change CsEnabled to 1.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power]
"CsEnabled"=dword:00000001

Sorry @PiT13 that is no longer applicable to Windows 10 2004. It works in 1909 and 1903, but not 2004.

my 5400 also has such an error, it is very bad that dell allows such an error. I hope it will be improved. currently the button and cover turn off the machine