New
#61
I'm trying think if i installed something like that.
Going into Safe Mode now.
I'm trying think if i installed something like that.
Going into Safe Mode now.
Unfortunately, I dont have anything like that installed. I dont have an Ipad as well.
Here are the logs.
Still looking for something close to the auxiliary screens.
According to the logs, Windows managed to install a number of updates during that 'rest' period!
Please boot back to normal mode again, and leave the system for 30 minutes - see what happens.
If there's no change after 30 minutes, reboot it again back to Safe Mode.
Nothing changed.
I included new logs.
Did you find anything in the logs?
I knoiw this is a bit leftfield, but do you have an external USB hard drive plugged in when you boot up?
Try unplugging it if yes.
Nope. I dont have anything plugged in.
UPDATE:
The Black screen is now gone. Because I uninstalled the Service Pack 1. Maybe that will give you guys a clue to what happened. I know it will ask me to install it again in the future.
I dunno if this falls under resolved.
There's no significant errors in the System log.
The Application log shows these errors....
Code:Activation context generation failed for "c:\program files (x86)\windows live\photo gallery\MovieMaker.Exe".Error in manifest or policy file "c:\program files (x86)\windows live\photo gallery\WLMFDS.DLL" on line 8. Component identity found in manifest does not match the identity of the component requested. Reference is WLMFDS,processorArchitecture="AMD64",type="win32",version="1.0.0.1". Definition is WLMFDS,processorArchitecture="x86",type="win32",version="1.0.0.1". Please use sxstrace.exe for detailed diagnosis.
This one is interesting, and could indicate a problem with the service - or possibly a corrupt user profileCode:The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
Please run the following commands, and post the results..
SC QC SESSIONENV
SC QUERYEX SESSIONENV
SC SDSHOW SESSIONENV
... I've just seen your update!
Please run CheckSUR and SFC /SCANNOW and post the result - and we'll see if that throws anything up at us.