Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Black screen after login, random shut downs, update may be the problem?


  • Please log in to reply
3 replies to this topic

#1 CrystalIce

CrystalIce

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:09:43 AM

Posted 17 February 2016 - 11:01 PM

Hi guys, I really could use some help here.

 

I'm currently running Windows 8 on my acer laptop which I've had for many years.

 

A few days ago the laptop decided to randomly restart itself (I believe after getting a blue screen error saying there has been a problem and the system needs to restart) and ever since then I've had nothing but problems, and I think it was after my computer updated itself to 8.1.

 

The first problem was after logging in, I could see my desktop background but none of my icons. I solved this by right clicking and selecting view icons but they kept appearing huge and then disappearing again. Then after restarting again and after logging in, the screen would just go black. Sometimes I was able to see the mouse and start the task manager, sometimes I couldn't do anything. 

 

So after trying multiple times of restarting, I restarted in safe mode and uninstalled all of the previous windows updates that had been installed on the day that the problems started and stopped it from automatically updating itself, this reverted it back to windows 8. After that the laptop was fine for a day, but again, after restarting, it's going crazy again. Sometimes I get the black screen, sometimes the system restarts itself randomly.

 

I've tried everything from disabling the display adapter and generic non-pnp monitor thinking it was a graphics issue (the monitor had a triangle with an exclamation point in it next to it) but this only worked for a short time before the black screen came back so I've enabled the display adapter back but not the monitor. Both have the latest versions installed.

 

I ran the sfc/ scannow prompt and looked at the log, this is what stood out to me:

 

2016-02-17 19:17:44, Info                  CSI    00000163 [SR] Verify complete
2016-02-17 19:17:44, Info                  CSI    00000164 [SR] Verifying 100 (0x0000000000000064) components
2016-02-17 19:17:44, Info                  CSI    00000165 [SR] Beginning Verify and Repair transaction
2016-02-17 19:17:46, Info                  CSI    00000166 [SR] Cannot repair member file [l:38{19}]"ActionCenterCPL.dll" of Microsoft-Windows-HealthCenterCPL, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-02-17 19:17:46, Info                  CSI    00000167 [SR] Cannot repair member file [l:32{16}]"ActionCenter.dll" of Microsoft-Windows-HealthCenter, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-02-17 19:17:46, Info                  CSI    00000168 [DIRSD OWNER WARNING] Directory [ml:520{260},l:98{49}]"\??\C:\WINDOWS\diagnostics\system\HomeGroup\en-GB" is not owned but specifies SDDL in component Microsoft-Windows-HomeGroupDiagnostic.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 
2016-02-17 19:17:46, Info                  CSI    00000169 [SR] Cannot repair member file [l:38{19}]"ActionCenterCPL.dll" of Microsoft-Windows-HealthCenterCPL, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-02-17 19:17:46, Info                  CSI    0000016a [SR] This component was referenced by [l:268{134}]"Microsoft-Windows-Client-Features-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.Microsoft-Windows-Client-Features-Package-shell"
2016-02-17 19:17:46, Info                  CSI    0000016b [DIRSD OWNER WARNING] Directory [ml:520{260},l:86{43}]"\??\C:\WINDOWS\diagnostics\system\HomeGroup" is not owned but specifies SDDL in component Microsoft-Windows-HomeGroupDiagnostic.Interop, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 
2016-02-17 19:17:46, Info                  CSI    0000016c Ignoring duplicate ownership for directory [l:86{43}]"\??\C:\WINDOWS\diagnostics\system\HomeGroup" in component Microsoft-Windows-HomeGroupDiagnostic.Interop, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 
2016-02-17 19:17:47, Info                  CSI    0000016d [SR] Cannot repair member file [l:32{16}]"ActionCenter.dll" of Microsoft-Windows-HealthCenter, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-02-17 19:17:47, Info                  CSI    0000016e [SR] This component was referenced by [l:268{134}]"Microsoft-Windows-Client-Features-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.Microsoft-Windows-Client-Features-Package-shell"
2016-02-17 19:17:48, Info                  CSI    0000016f [SR] Verify complete
 
I have no idea what that means though or how to fix it. I've also done a system refresh which seemed to work for a while but again, the black screen comes back. I can only start the computer in safe mode now so I really need help.
 
Should I reinstall the windows updates? Or was that the issue? I'm really stuck here. 
 
Thanks for any help you guys can give me. Much appreciated.
 
Quick edit: Just opened windows action center because it was mentioned in the log, windows security center service was turned off, tried to turn it on and got a message saying "windows security center service can't be started". I'm currently running my laptop in safe mode with networking. 
 
Anything to do with it maybe?

Edited by Orange Blossom, 18 February 2016 - 07:02 AM.
Moved to Windows 8. ~ OB


BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,264 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:43 AM

Posted 19 February 2016 - 09:53 AM

Press the Windows key windowskey_zps092d5c75.png
 and the X key, in the menu that opens click or tap on Command Prompt (Admin).  This will open the Elevated Command prompt.
 
Copy and paste the command below, then press Enter.
 
dism /online /cleanup-image /restorehealth
 
Restart the computer to complete the repair.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 CrystalIce

CrystalIce
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:09:43 AM

Posted 19 February 2016 - 04:36 PM

 

Press the Windows key windowskey_zps092d5c75.png
 and the X key, in the menu that opens click or tap on Command Prompt (Admin).  This will open the Elevated Command prompt.
 
Copy and paste the command below, then press Enter.
 
dism /online /cleanup-image /restorehealth
 
Restart the computer to complete the repair.

 

 

Thanks for the reply dc3. I ran the command but it's giving me an error 87 message which is saying that the command dism /online /cleanup-image /restorehealth is unknown.

 

I'm tearing my hair out with this. It won't go to desktop after the login screen. It either goes to a black screen or it doesn't even get that far, the little loading icon just freezes. This seems to happen every time after I shut down or restart my laptop.

 

Any other help please? I really think the stupid 8.1 update started all of this > :(

 

EDIT:

 

After uninstalling the generic non-pnp monitor (that had an exclamation point next to it) and the laptop working, I kept my laptop in hibernation or sleep mode, afraid that shutting it down would cause the problems again. All was going well but then I noticed that some applications like skype etc weren't opening and I couldn't update adobe flash player for some reason. So I shut down my computer and restarted. I logged in fine and my applications worked (flash player still wouldn't download though) so I shut down my laptop again last night before going to bed.

 

It wouldn't work today and I've just discovered that the generic non-pnp monitor that I had previously uninstalled is back again. Could this be causing all of the problems? I'm going to uninstall it now and see if that makes a difference.

 

EDIT AGAIN:

 

I just restarted my laptop after uninstalling generic non-pnp monitor and it's working fine now so that must have been the problem. My monitor now is generic pnp monitor in device manager. This was previously hidden when the non generic one was installed but it's unhidden now.

 

Will this non generic pnp monitor come back after retarting though? How do I make sure it's gone for good?

 

Thanks guys!


Edited by CrystalIce, 19 February 2016 - 05:04 PM.


#4 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,264 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:43 AM

Posted 20 February 2016 - 09:50 AM

Thanks for the reply dc3. I ran the command but it's giving me an error 87 message which is saying that the command dism /online /cleanup-image /restorehealth is unknown.

 

Did you copy and paste the command in the Command Prompt, or did you just type it in.  The error 87 is usually caused by a lack of the space between the dism and the /online.

 

If there is an yellow exclamation point next to the Generic Non-PnP Monitor this usually is an indication that the driver for the monitor is corrupted.  If you deleted this driver and then restart the computer the installation wizard will install a new driver for the monitor.  The Generic Non-PnP Monitor is the setting you want.


Edited by dc3, 20 February 2016 - 09:51 AM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users