Every time I try to put put my laptop to sleep, hibernate, restart it or shutdown, it stalls for about 10 minutes before giving me a Driver Power State Failure.
Having installed "WhoCrashed" and "Windbg", I was able to determine it was related to "ntkrnlmp.exe", "ndis.sys", "raspppoe.sys" and a vpn driver at one point or another. I "believe" I managed to uninstall the offending vpn driver but of course still overall have the same issue.
This appeared to occur while trying to do a windows update last week but I can't be sure. I presume, there is a out of date or corrupt driver but just can't seem to determine which one.
Here's some background; for the first few days Windows 10 was fine, no problems what so ever but then it I was just listening to music browsing the web, no games or any cpu/ram intensive stuff running and all of a sudden my music stops and then I get taken straight to my bios screen as my PC just restarts out of nowhere. As it is starting up however it shows the black screen with the Windows logo in the middle and the loading circles spinning round, then it shows a black screen and I hear the sound of Windows starting up, wait a few seconds and it says "Configuring updates" or "Configuring Windows" (can't quite remember) Anyway, as it comes back on it I get a little notification saying Windows updates were installed. Then 5 or so mintues later it does it again. Either it's coincidence or it has something to do with it but for a few hours when I was playing GTA V nothing happened for the rest of that time of my PC being loaded.
Again, I was watching an MP4 (I use VLC Player if that has anything to do with it) and it blue screens out of nowhere (I can't remember the exact reason but I've uploaded the crash dumps here [URL] .... ) dunno if the blue screen has anything to do with the random crashing
TL;DR: Windows 10 keeps randomly turning itself off without warning, sometimes going straight to the bios screen and loading back up sometimes just completely off and requires me to turn it back on.
Okay so I've upgraded and use windows 10 for about 2 weeks now. All is fine until I've experienced this random shutdown where the computer turns off completely in a splitsecond then reboots itself.No BSODs, no warnings at all. Recently, it's been shutting itself down and reboots itself but won't even make it to the login screen before it shuts itself down again and this will continue in a loop. I had to turn off the plug and turn it back on. It will prompt a system restore which the computer will work fine for a while after the system restore. I assume this problem is because of windows 10 because I have not experienced this problem when I was using windows 8.1.
URL...In control panel under windows update I click "view update history",URL...I'm assuming it has to do with my previous problem in the previous post, another problem might have been that I shut down during a restart for an update because my computer sometimes has problems starting up so I have to unplug my desktop and plug it back in for it to work. (when it restarts it says overclocking failed thought I don't overclock so I enter and exit the BIOS to get back to normal)
Win 10 Home.Upon 'restart', system freezes part way through shutdown.If I use the "Slide" feature it will shut down ok.Have already tried sfc/scannow; found corrupt files but was unable to fix. Files don't appear to be critical.
Noticed that after an update from Windows Update you "Must" do a Reboot for the installation/update to process. In prior versions of Windows when I would take an update, I might just wait until I shut the PC down for the night, and it would finish up in the morning upon startup. In Windows 10 that no longer works (for me) it MUST be a Reboot for it to process...
Device is up to date, however from either the Start menu or Command prompt Windows freezes at manufacturer splash screen on restart, requiring hard shutdown, This returns even after clean install of Windows 10....
I installed W10. This problem appears to be random and happens a couple of time a month. It is really annoying. What happens is, the WiFi appears to stop working. It can't find any available networks and won't reconnect no matter what I do. I have even tried closing/restarting explorer but that does nothing.
If I try to shut-down or restart my computer, it just hangs on the shut-down/restart screen. I have to hold down the power button to get my computer to shut-down. The weird thing is, after a restart, it works fine ...for a few weeks. It just seems very strange.
I use a WiFi dongle. I have a couple of them so I tried each one - they all eventually give me the same result . I have a HP if that works.
If I leave Western Digital My Book plugged into a usb3 port at shut down there will be a restart in a few seconds.
This has been the action through both versions of Win10. (Currently on the 2nd version as of Nov.20) At this time the only items that allow restart are mouse, keyboard and network adapter Fast Start is turned off An extra usb3 board was installed during the first Win10 but two usb3 items cannot be inserted side by side.
One will read as a usb2 if two are inserted into the new 2 ports in the rear. This My Book now is the only item plugged into that back USB3 port. The drivers for usb3 appear to be current according to the mfg site. When this external is ejected then the computer shuts down. On Win7 pro this external could be left plugged in all the time.
Is a line of attack to remove this new usb (2 on front, 2 on back) and start over with another?
I have installed W10 twice using the update feature. Everything work fine except when I want to shutdown or put the machine to sleep by clicking on those options, the machine makes noise like the HD is working. It then just shuts down and reboots again. The only way I can shut it off is by using the button on the computer.
I installed Windows 10 one week ago, but I still have issues with the sleep mode. I configured the laptop, that whenever I close the lid or I use my function key the sleep mode is started.
Unfortunately the laptop is either not entering the sleep mode correctly or is not able to restore it. Which means when I open several programs they won't open again.
If have an ASUS Transformer Book Flip TP500LA: Intel i3 4030 4 GB Ram 240 GB SSD
I tried the following so far: BIOS Update to the newest version 203Downgrade the Intel MEI driver to an older oneReinstall the graphic and touchpad driver Nothing of that was successful. Are there any logfiles to analyse?
I had recently performed a clean reinstall when I upgraded my laptop to a Samsung 850 Evo, and ever since then I've had problems with sleep. If I initiate sleep, hibernation, or shutdown then the screen goes black but the status LEDs stay on. punching all the buttons do NOTHING, with my only recourse being to press the power button until the lights go out. After which the system acts as if I woke from hibernation as normal. Restarts are unaffected, which is a good thing as having to force-restart my laptop every week will get old fast.I believe I have installed all needed drivers, and Device Manager does not show anything missing.
When I put my laptop to sleep and then attempt to wake it up, it will power on (going through the boot up screens) instead of just waking up, thus causing me to lose any information open on the computer.
I have tried a few things to try to wake it up to no avail:
sfc /scannow in cmd unplug all usb devices before going to sleep/waking up rollback graphics drivers resetting power plan settings and power button settings back to default state
My laptop, running Windows Ten from a clean install, has issues with the sleep function. About once a day, when I either put the computer to sleep or when it does it on its own, the screen will go black but the computer will not stop running. All the lights are on, the fan and disks keep running. Nothing works to turn the screen back on and my only option becomes to force a shut down.
I've tried tweaking all the power options in various ways, I've tried disabling/enabling hibernation/fast start and I've searched for an answer but I do not have one.
I had an initial fault with Windows 10 where the start button disappeared so to switch it off I used Alt/F4. That brought up a small screen that allowed me to shut down . The next time I tried it I looked at a couple of options and chose sleep mode...Big mistake. I cannot wake up the screen at all, the computor itself will switch on and off mit the power switch but nothing appears on the screen, it is blank. I have tried hitting various buttons on the keyboard to no avail.
When I put my computer in sleep mode, it won't 'wake up'. I have to manually turn off the computer and then start it up again. This has happened twice. I'm not putting it into sleep mode until I find out what's wrong and that's exasperating as I normally leave my computer on all day so I can periodically play my games.
Ive just got a new pc that roughly half the time doesn't shutdown correctly. It displays the shutdown screen, goes blank and then does nothing. It remains powered and the fan comes on and off when need. (Its only a small Atom CPU). Ive tried disabling USB selective suspend but that doesn't seem to have worked.
Prior to upgrading to Windows 10, my system was running Windows 7 Home Premium SP1. When running my previous OS (WIN 7) I rarely had errors listed in Event Viewer. Now after upgrading to Windows 10, I get errors/warnings I never used to get under Windows 7.
The error is of the "Critical" level in Event Viewer.
After doing a normal shutdown, and then booting my system, I check Event Viewer and always find the following critical error:
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
---------------------- START: Event Viewer XML error text ---------------------
I never used to get this error after doing a normal shutdown (prior to upgrade to Windows 10, when I was on Windows 7). Now it happens all the time. Why this error is occurring after doing a normal shutdown followed by a boot?
I suspect it's a glitch with the first production release of Windows 10, but I have no proof of that. My system runs fine, yet I get the above error (and a number of other errors) since I upgraded to Windows 10.