Last edited by NCguy; 14 Jan 2014 at 19:18.
Latest updates that were installed today 2014-01-14:
KB2904440 Service stack update.
Consider the following scenario:
- You enable a Windows feature.
- You install an update for the feature.
- You optimize Windows either by using Windows Maintenance to perform the optimization automatically, or by using the dism /startcomponentcleanup command to perform the optimization manually.
- You disable the feature.
- You try to install a later update for the feature.
In this scenario, the installation fails, and you receive the ERROR_INVALID_PARAMETER error code.Issue 2
Assume that you install a driver update from Windows Update for a device that uses third-party drivers. After the update is installed, only some files for the device are updated.Issue 3
Assume that an unanticipated power loss occurs while you are using the dism /startcomponentcleanup command to optimize Windows. After you restore power to the computer, some files become invalid. Issue 4
Assume that you install a servicing stack update that requires you to restart the computer. Before you restart it, you may find multiple install attempts for the servicing stack update in the Windows Update history.
KB2912370 Issues with MS Store
- Faster Windows Store launch time on Surface RT.
- Fixes an issue in which the fresh apps in the Windows Store Live Tile do not match the apps in the Spotlight.
- Fixes an access violation in Windows Store.
- Fixes an issue in which Windows Store crashes when you change the text or font size from default to larger, or from larger to default.
- Fixes an "Access Denied" error when you try to access Windows Store.
- Fixes an issue in which Windows Store crashes when you change the background color.
- Fixes an issue in which Developer license acquisition fails with a 0xC03F1014 error code.
KB2917993 (x64) Screen turns black.
Consider the following scenario:
- You have a Windows 8.1-based device that has update 2883200 installed.
- You rotate the device to change the screen orientation to portrait orientation.
- You put the device horizontally.
- You restart the device.
- The screen rotates to landscape orientation when you log on to Windows.
In this scenario, the screen of the device turns black.
The rest of the updates are for security or for my Outlook 2013.
1. Cleared the system log
2. Let computer sleep naturally
3. woke computer
4. refreshed log
5. snapped log and posted here
Notice similarities with yours. just missing kernel power and power-troubleshooter posts to the log. It entered sleep so they had to have occurred, just didn't post. Wonder if I'm facing a re-install?
NC, Sooo, your computer sleeps OK and the only trouble is that you don't have the Power troubleshooter? that is for USB 3.0 devices!
I don't think you have to do a complete install for this, especially if you do not have USB 3 ports or use them! I am completely flummoxed why the fascination with system logs, heh. I have these errors all over them and I don't care a wit:
Not sure what you mean power-troubleshooter is for USB 3.0 devices? Do you mean that it won't post to the log when it enters sleep unless the machine has an active USB 3.0 device attached at the time it enters sleep? I actually didn't have any attached so I just plugged one in and its still not making log entries when it enters sleep. So I guess I'm unclear about the USB 3.0 thing?
NC, Yeah, I was confused. You said your computer fell asleep and that you took the snapshot after. I took that to mean that it always slept when it should!
When I expanded the power troubleshooter line in the system logs, it only says that the USB 3.0 port has woken from sleep. My ASUS Z87 Pro has special ports and apps for USB 3 including a charging port, so I doubt that you missing that particular log line means anything.
As far as I can remember, no one found anything of use in the system logs except one guy who thought 10100 meant something. I played around with it and damn near fatally crashed my computer and, in the end, did not fix sleep.
You can continue to play with the logs trying to tease out anything useful. You can do what I did and search each line on the web but it led to nothing useful for me.
I will no longer post in reply to any questions you have about the system logs as I have reached the limit of my knowledge of them and found them to be a dead end. Good luck!
Thanks for the welcome, John!
I have already tried the things you suggested, and I am aware of the different power profiles available on a laptop as opposed to a desktop (I've used nothing but laptops since 2005, and I just got a new one because I'm anticipating another overseas move later this year). The problem doesn't appear to be correlated with the method used to shut down/hibernate or put the computer into sleep mode (S3), because as long as the computer is plugged in, it won't allow me to put it into sleep mode manually no matter whether I close the lid, select Sleep from the start menu (I use a third-party Start menu, perhaps that contributes to it? But it worked fine with Windows 8... then again, I guess a lot of other things did too!), or set the main power button function to put the computer to sleep. I have tried disabling both hybrid sleep and hibernate, to no avail. Also the behaviour is the same whether I'm logged in to Windows or not. I don't think there's anything I'm missing. I had a look at the BIOS settings and couldn't find anything that appeared to pertain to the issue. At any rate, I'll keep working on it...
If you run the tool that Brink shows here (even if you have never had a bsod before) - and post the results here - it wouldn't be the most surprising thing ever if I'm able to get you on the right track.