Windows 10: Dell Inspiron 3135 does not sleep/shutdown/hibernate

I'm running Windows 10 build 9926 on an Inspiron 3135 from 2013. I made a clean installation from the Microsoft ISO on a 120GB Kingston SSDNow V300 SSD. Prior to that it was running the original HDD with its 8.0 distribution upgraded to 8.1 via the Windows Store.
I have the latest BIOS available for this computer.

Other than the webcam which I did not test, everything works. Except proper shutdown stuff.

When I select shutdown from the interface, the system sits there for a quite a while with the hard drive LED blinking briefly every 2-6 seconds. I did not try with a stopwatch, but that remains the behavior for well over 3 minutes. This time I happened to notice that after quite some time I saw a longer amount of time with the LED on, then another brief blink, then it went dark.

After turning on, I looked at the System Event log. Here are some interesting entries:
4:17:19 The process ... has initiated the power off ...
4:17:25 The system is entering sleep.
4:24:18 The boot type was 0x0.
4:24:18 The last shutdown's success status was false. The last boot's success status was false.
...
4:24:18 Windows failed fast startup with error status 0cC0000001.
...
4:24:19 The system watchdog timer was triggered.
4:24:21 The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
4:24:21 The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

I checked the Kingston site for firmware. I'm not sure whether there is better than what the SSD contains. The SSD is new from NewEgg. The Kingston firmware app says there is no newer firmware.
(There is a notice on the app screen to run the app in AHCI mode, but I confirmed that the BIOS is set to AHCI.)
I did not try this SSD on Windows 8; I guess I could and see whether it behaves the same.

I now tried to reboot instead of shutdown and the system again went into this period of blinking. I held the power button because I wanted to check the BIOS.

Any ideas?

J

:)

 

Occasional BSOD in Windows 10, and wake from Sleep issues

Yes. Now I recall the Intel Management Engine Interface Driver on my own Dell Inspiron 3542 has been blamed for that. I never personally suffered it, but here is the article...

Inspiron 15 (3542), 14(3442), 17(5748) Running Windows 10 may not Shutdown, Resume From Hibernate, Sleep or not Power on | Dell Deutschland

Inspiron 15 (3542), 14(3442), 17(5748) Running Windows 10 may not Shutdown, Resume From Hibernate, Sleep or not Power on

I took the fix (in the course of updating all drivers), even never having suffered the issue, & still was fine.

 

No sleep option in Windows 10

Dell Inspiron 570 desktop 1TB HD upgraded to Windows 10. No Sleep Option. Dont want to use Hibernation. Want to get sleep option back please.

 

Update drivers - chipset, storage, Intel devices (RST, ISCT, IME, etc), video
Disable Fast Startup (this was an issue with earlier versions of Windows)

Even though you're not experiencing BSOD's, please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):
Solved BSOD - Posting Instructions - Windows 10 Forums

 

As a working Computer builder and tech for the past 35 years, I've had to build a list of Brand names, of unacceptable quality.
At the top of my list of "Never, ever, buy one of these" is 'Kingston'. They buy a lot of ram, rejected by the original manufacturer.
Some of that may work initially, but fail later. Nuff said on that.

I have Windows 10 running without issue on a Dell Inspiron E1405, with NO issues at all.
I'd NEVER buy a Dell, but that little laptop was given to me, so I use it for experimental purposes only.

Both Hibernate and Sleep are still troublesome, like from day one. So I totally disable both!

As for shutdown, I use only a Quick Shutdown shortcut, on my desktop or Quick Launch toolbar.

If you'd like to at least try the Quick Shutdown shortcut, here's the syntax for it.
It's the same shortcut I use for Windows 7, 8, 8.1 and 10.

%windir%\System32\shutdown.exe /s /t 0

Copy and paste this shortcut, because every space is important.
When I use this shortcut to shutdown, my PC's usually shut down in anywhere from five to eight seconds.

I started using a Quick Shutdown shortcut with Windows 98. Over the years the syntax for the shortcut has changed some, but the result is still the same.
The shortcut for Windows XP is:
%windir%\System32\shutdown.exe -s -t 00 -f

My Windows XP PC shuts down in just five seconds.

It's my hope that the above information will help someone, somewhere, someday.

Cheers Mates and happy computing!

*Cool

 

35 years, that sure is a great deal of experience. . .sure glad you are around to help us out. . .*Smile

 

I used the shortcut (cut & paste into an elevated command window). Unfortunately I see the same behavior - the system blinked the disc LED for a while. After many minutes I turned it on an I see the events for watchdog timer.

 

I do not know how to update drivers other than let Windows do its thing. The computer is AMD, so no Intel in sight.


I disabled Fast Startup, did not make a difference.


Here is the report.


J

 

I had remembered that the system did succeed in restarting quite a few times during the initial installation and updates, so i wiped it and performed a clean install.
I see a couple of failures to install updates, but so far no issue with restart.

I installed all the drivers and applications I had before the wiping and the system does sleep, hibernate and restart as expected.

One noted difference: I installed FastAccess Anywhere Face Recognition (login via webcam), which I harvested from my Dell Inspiron 11 3147. In the first installation this facility worked but I had the shutdown issues. After the wiping I am not sure that this facility works - it keeps claiming that it sees a face and asks for the password associated with the face (rather than recognizing the face and using the already associated password).
I also recall that on the 3147 as well as the initial installation on the 3135, FastAccess updated itself from the distributed 4.1.201 to a slightly higher version number. After the wiping I have not yet seen the update notice. SensibleVision's web site says "FastAccess 2.x, 3.x and 4.x are no longer receiving minor updates. Users can purchase an upgrade to 5.x at a discount."

 

To update drivers you start at the Dell support website and enter your service tag number to find the latest updates available for your system. If the drivers aren't available there, then we can look in other locations (such as the Intel Download Center, located here: Intel Download Center )

 

I had installed Windows 8.1 drivers as were available for hardware not assigned a driver by Windows 10 - those were the WiFi DW1705 and the touchpad. I also installed the chipset driver package but I have no direct indication that it changed anything.

Other drivers on the Dell site seem older than Windows 10's own choice: Realtek Audio 6.0.1.7195,A02 (Windows 10 installed its own 6.0.1.7446), Realtek Gb Ethernet 2.1.2013.528,A00 (Windows 10 installed its own 8.1.1110.2014), AMD Chipset and Radeon HD 8250 Graphics 13.152.1.1,A00 (Windows 10 installed a Radeon HD 8250 driver 15.200.1006.0).

As I wrote above this machine is AMD and has no Intel components.

 

The Windows Update drivers are preferable to the drivers from Dell in most cases (as these are specifically targeted at Win10).
And Dell was just a starting point for drivers, after that it's a hunt for the original driver maker and hoping that Dell hasn't added something to the drivers that the system requires (if so, then using the original driver maker's drivers may result in problems).

Under ordinary circumstances finding suitable drivers that have been updated is a frustrating chore. Figuring out if the Windows Update drivers, the PC manufacturer's drivers, the motherboard drivers, or the original device manufacturer's drivers (along with other driver makers) are more suitable is very frustrating (and not always possible to do).

Now add to that a beta OS that doesn't have many sources for updated drivers - but it does take drivers designed for older versions of the OS - and it's surprising that things work as well as they do.

Good luck!

 

After a wipe and reinstalling Windows 10, including the same drivers and applications as before, the system does behave correctly. It hibernates, sleeps, restarts and shuts down.