With my new build computer, I am having serious problems with the sleep function. This was an upgrade from 8.1.
After attempting to wake up from sleep with an input, either a) the screen remains black, or b) the desktop is visible but soon after, everything freezes and no input is possible at all requiring a manual reset. The computer turns on and wakes up (fan and light).
Right now I've turned sleep off, but I'd like to have it working properly.
I have downloaded all the latest drivers from Asus and Nvidia, including chipset, LAN, Video, latest Bios, etc.
Xeon 1650 v3 Asus X99 WS-E motherboard 32GB ECC RAM Nvidia GTX 950 Intel 750 SSD M.2 Nvme 450gb Samsung 850 Pro 1 TB Logitech wireless mouse and keyboard Asus 4k HDMI 2.0 monitor
ASUS UX303LN user. Before 3 days, my laptop started refusing to wake up from sleep properly, instead it reboots from a clean state, It is as if I am pressing an invisible reset button that starts the computer from scratch.
The first time this occured, I managed to catch a glimpse of a BSOD with a sad face, followed by a restart (unfortunately I have not managed to note down the message). After that every time I do the same there is no BSOD, the laptop just shows the BIOS posting and then it loads Windows. Event Viewer shows the same Error 41 after every reboot. Note that before this problem started to occur, my laptop barely had to start from scratch (every time I was done with working I was just closing the lid, returning in a functioning environment) for a good 2 years. I had to reboot maybe once/twice a month for the necessary updates.
Some more info:
-After crashing, the computer does NOT generate a memory dump, no matter what. I know how to setup a memory dump, however for the last 50 crashes it does not. I have tried selecting minidump instead of automatic dump without a result (the last dump was 3 weeks back for another reason). Disabling automatic restart after crash does not work either. -The problem started 2 days after receiving the notorious KB3140743 update (that came together with KB3139907). Uninstalling the first did not work, the second cannot be uninstalled. -Trying to alleviate the problem, I thought of changing to hibernate instead of sleep when I close the lid/ the system goes idle. For that I had to reenable hibernation (powercfg /h on) which I had disabled because I have not used it. It worked ONCE, just the first time, every other time the result is the same as with sleeping (reboot and error 41). Enabling/disabling Hybrid Sleep did not work either) -Windows memory diagnostics shows no errors, SMART also shows no errors for the SSD
What I have tried (and failed) so far:
-Reverting KB3140743 -Updating/reverting display drivers for the 2 GPUs (intel 4400/geforce 840m) -Updating/reverting/completely disabling intel 7260 wifi/bluetooth drivers (which are known to be problematic) -Changing network card's "keep device awake" options -Updating intel DPTF drivers (after seeing that they post some not critical errors in the event viewer) -Disabling Throttlestop (a tool to manage the CPU's behaviour) -Changing power schemes -Tinkering with different SSD options (indexing/virtual memory etc)
a few days ago I updated my 64 bit windows 7 ultimate to windows 10 pro, and ever since then whenever I put the PC to sleep and try to wake it the PC tries to start but the screen remains black and after a while a BSOD will appear (now with a sad face on it... amusing...) stating driver_power_state_failure, it happens consistently and only under those circumstances (at least for now) I tried running the driver verifier (as explained on other posts BSOD on sleep, DRIVER_POWER_STATE_FAILURE - Windows 10 Forums) and followed the tenforums tutorial, but nothing in particular happened
I use the sleep function a lot and I cant have it like this.
Recently, whenever I wake my laptop up from sleep (from closing the lid and then opening it again), sometimes I get a BSOD.
I think it started when I updated the Intel graphics driver, so I've booted into safe mode, uninstalled and reinstalled the driver, and I still get an issue.
I've attached the debug files, there was a previous BSOD a few months ago that I was getting due to a Nvidia driver issue, but I downgraded to an earlier version and it's stopped it, so I don't think the issue is there.
So upgraded from 8.1 Pro. I never had any problems with 8.1 other than the occasional crash here and there, but nothing exceptional. Now every time that I try to wake the computer from sleep I get a stop message that states that it tried to write to read only memory.
I have run memtest86 overnight with 7 iterations and it passed them with no errors. I ran a burn test on my CPU to see if it was overheating, with it never going above 63 degrees Celsius even on the most extreme test.
The crashes are not random. They only happen when I try to wake the computer from sleep. However, it looks like what is causing them is random.
I have never overclocked my computer and I have never touched the frequencies with the memory.
while trying to wake up my PC from sleep mode. I have had this configuration for 3-4 weeks and it's been 100% stable. I am just wondering if there is some driver that caused this BSOD to pop up when I was trying to wake up my PC. Hardware-wise, I only installed a new fan 3-4 days ago, and that is pretty much it. The blue screen message stated that it was caused by MEMORY_MANAGEMENT, Error number 0x0000001a. It seems that it was caused by driver ntoskrnl.exe +14e2e0.
I installed new Geforce Drivers yesterday as well as some Logitech drivers for their GT steering wheel dated 2010. Perhaps they are causing a conflict with something.
I have recently completed a new home build with the following specs:
Processor: i7-6700k Motherboard: Gigabyte GA Z170X Gaming GT Memory: Corsair Vengence LPX DDR4, 2666 GPU: Sapphire Radeon R9 Fury SSD: Intel 750 Series, 1.2 TB PSU: Corsair RM Series 750 Watt Case: Corsair Carbide Series Air 540 OS: Windows 10 Home
The build went fairly well and the computer seems rather stable (and very, very quiet). But the main problem I am having is that after the computer wakes up from sleep mode, it crashes a few seconds later and re-boots. The event log will be riddled with entries upon reboot, but one critical event in particular catches my attention:
Event ID: 41, Kernel-Power
There are also a number of Errors that show up; not sure if they are normal or not but I suspect errors should not typically occur. I've updated all of my device drives but that didn't really seem to solve the issue. I also tried changing the power settings and un-selecting "Fast Startup" as per a recommendation I read on a different forum but that had no effect. To prevent the system crash, I've simply been shutting down my computer after I am done using it which isn't a bad thing, but I'd like to have the option of using sleep mode.
Also, for what it's worth, I remember having a bitch of a time with sleep mode with RAID 0 on my old computer, so perhaps Windows does not yet adequately support "sleep mode" with PCI-E controllers.
Ever since updating to Windows 10 I have periodically had a problem with my computer when I wake it from sleep. The symptoms of this are as follows:
The machine will wake from sleep fine and I'm able to put in my password etc. After 30s to a minute, the machine will give me a BSOD citing Driver_Power_State_Failure (occasionally it has been something else but this is the main culprit.) It then collects data cycling up to 100% but does not reboot automatically. I need to do this manually. When I do so, the machine will reboot normally.On a couple of occasions in the last month, the machine will simply not wake from sleep at all and neither does it respond when I press the power or reset buttons. The only way I can get it to start again is by manually turning off the power supply and then turning it on again. I am not sure if this is related to the BSOD issue or whether it is a separate issue.I have previously had an issue where the machine would appear to wake from sleep but the screen would remain dead and the keyboard was unresponsive (though the num lock light was showing.) I can't recall having this issue recently and am unsure whether this is a separate issue.It normally seems to occur after the machine has been asleep (hybrid sleep) for some time.Of late I've noticed that it often seems to coincide with me opening a new program or file immediately after waking the machine from sleep.
I have tried several things to fix the issue as follows:
I've tried to run Driver Verifier but have never managed to get the machine to start up successfully even with only one driver selected. (In fact I have to manually import the original registry settings to turn off Driver Verifier again in order to get my machine going again.)I have uninstalled and unplugged a USB video capture device but that has made no difference.I have completely uninstalled the drivers for my graphics card and then reinstalled using Microsoft's default drivers. No difference. I've made sure that I am running the latest drivers, have checked Windows update etc.
It's tricky to pin things down to a particular driver without using Driver Verifier and I'm not sure how to decipher the dump files and error logs generated each time this happens.
I randomly received a "Kernal Security Check," with no code associated with it. I'm thinking it could be this Corsair K70 RGB I just installed. If it is, I'm just going to send this thing back. I know people have had tons of problems with it; however, I thought I'd give it another whirl since its firmware has been updated.
After upgrading to W10 my pc keeps waking up from sleep mode. I've disables the reboot and scan in to wake the pc in task scheduler, I removed the wake on lan, mouse and keyboard from waking it in device manager, and I've disabled what I can in power management. It still wakes up a few minutes after going into sleep mode..
Since I upgraded to windows 10 from windows 7 my pc every night wakes its self from sleep mode. I did the command prompt and it said a wake timer was waking my pc, I have been unable to find a wake timer. How to fix this?
i am having a strange issue with my windows 10 pro version, It was working fine until the 3rd cumulative update. Now my lap never goes to sleep. When i sleep the laptop it goes to sleep and then automatically wake after 30 to 40 sec, and sometimes even 4 to 5 minutes. I have troubleshooted the power option, removed all the scheduled events but nothing works. On searching the command prompt with powercfg lastwake command it shows The POWER BUTTON.
I have windows 10 pro 64 bit. I am running a 120gb SSD for my OS and a 1.5TB HDD for media and games. Whenever I put the computer in standby or sleep mode the HDD is not recognized when the computer wakes up. Upon restart the HDD is recognized and everything is groovy.
Recently I have been finding my PC powered up when it should be sleeping. Using powercfg -lastwake does not show a cause but looking at system events I can that there are a series of events each day starting at 08:59:31. One of these is a Power - Troubleshooter event which says that the system has returned from a low power state but Wake Source is unknown. This and the other messages are ones that normally appear if I wake up the PC manually. There are subsequent events from Windows Update so I thought that might be the cause but it does not run immediately and I now believe that it is running because the PC has woken up and is not causing it to wake.
I have checked in Power Options Advanced Settings/Sleep and Allow wake timers is set to disabled.i have checked that on my network adaptor, 'Allow this device to wake the computer' is not checked.I have checked Control Panel/Security and Maintenance/Automatic Maintenance and Allow scheduled maintenance to wake my computer at the scheduled time is unchecked.
I had also checked in Task Scheduler and under WindowsUpdate there are 4 tasks but under Conditions, none are set to 'Wake the computer to run this task'.Checking back through the event logs it seems that this problem first happened on 27th Sep and always happens at 08:59:31. I have looked at the event log for the previous day and can see some events relating to the installation or update of a device driver although I haven't made changes to the hardware for a long time. It is followed by an event relating to Disk 3 which I don't normally have so I assume these were as a result of plugging in a USB device. There are also events relating to a windows update of VCLibs 12. how I can track down the culprit?