Windows 10 startup issue resolved. Black screen observed upon booting.
Windows 10 startup issue resolved. Black screen observed upon booting.
Hello, my workstation functions properly without Hyperthreading enabled. When I attempt to start with it running Hyperthreading, the display goes dark right after the Windows 10 loading screen appears. I've updated the BIOS and drivers for the graphics card, turned off CSM in BIOS settings, and completed a full RAM test—no issues found. I've looked everywhere for a fix but haven't succeeded so far. System specs: Fractal Define 7 XL CPU (2 x Intel Xeon Silver 4216, 32 cores, 64 threads, 3.2GHz), motherboard from ASUS WS C621E SAGE, RAM type DDR4 ECC 192GB, sound card RME HDSPe AIO Pro, graphics card 2GB PNY NVIDIA T400 GDDR6 (80GB/s, 3x mDP DSP), storage setup includes multiple SSDs and a Windows 10 Pro for workstations. Power supply: Corsair RM1000x, modular design, silent operation, 80PLUS GOLD rating. Monitor: LG Ultrafine 31.5 inch 4K.
You've attempted to run "sfc /scannow". It seems this command isn't connected to your current task, but it's a good precaution.
Thank you for your input. The scan detected and fixed the problem, but it didn't fully resolve the issue.
Overclocking then return to Default settings. Update the Firmware and BIOS at the provided link. Launch a Command Prompt with administrative privileges, enter the following command: DISM /Online /CLEANUP-IMAGE /RestoreHealth. After completion, run SFC /scannow and press Enter. If the message indicates no Integrity Violation, all files should be fixed.
Hi, I noticed dropouts and clicks while using Cubase. Someone suggested hyperthreading might be the issue. I disabled it and realized the computer runs much slower afterward. Now I’ve turned it back on, but the screen shows black.
These commands and cleanup options don't actually work. They seem to be ineffective, having never assisted anyone before. Consider using system restore to revert to an earlier state if possible.
I've completed a system restore about a few months back and the issue persists.