Share via

server 2016 black screen

Tool Shed 1 Reputation point
2020-09-18T05:55:22.127+00:00

I'm facing an issue with black screen right after successfully login through RDP. I cant launch task manager, or use powershell or psexec remotely to connect to the server. I dont have audio process running, appreadiness is set to manual. If i console into the server instead of black screen it's either gets frozen right after ctrl-alt-del before credential screen or on welcome screen right after entering credentials. It's happening on both physical and virtual servers. The only thing i am able to do is to reboot which fixes the issue for a few days. Nothing on event logs and users have interactive setup in the group. It's running 14393.3866 build

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,436 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-18T13:15:59.847+00:00

    Lockups are almost always caused by hardware issues. I'd check here and with manufacturer that the hardware has support.
    https://www.windowsservercatalog.com/
    Also check the manufacturer site for the latest ROM bios, firmware, chipset, and driver support pack.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  2. Tool Shed 1 Reputation point
    2020-09-18T21:23:06.877+00:00

    Looks like hardware is supported.

    I should clarify a bit. i can do unc to the server and still able to browse folders and files. i can also do Enter-pssesion and connect and run few command like list processes or netstat. However if i try to list services it just sits there. It's across multiple platforms and hardware. Almost feels like a patch issue

    If i reboot servers go back to normal. Some dont get issue again but some get it a week or so later

    0 comments
  3. Anonymous
    2020-09-18T21:50:59.007+00:00

    Also check the manufacturer site for the latest ROM bios, firmware, chipset, and driver support pack. Some things to try;

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  4. Molly Lu 766 Reputation points Microsoft Vendor
    2020-09-28T06:33:01.717+00:00

    Hi,

    Welcome to Microsoft Q&A.
    Check if there is a memory.dmp under C:\Windows folder.
    If there is a dump file, you can download the WinDbg Preview from Microsoft Store for dump analysis.
    Reference link —— Analyzing a Kernel-Mode Dump File with WinDbg
    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/analyzing-a-kernel-mode-dump-file-with-windbg

    Best regards,
    Molly

    --------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  5. Tool Shed 1 Reputation point
    2020-09-28T20:06:42.897+00:00

    Hi,

    I was able to trace it to Symantec locking out processes.

    I un-installed Symantec and monitoring.