The system powers on and displays a dark background with a rotating blue cursor.
The system powers on and displays a dark background with a rotating blue cursor.
Here’s a revised version of your text:
I was using my PC for a few hours handling tasks, then playing games, and finally watching a movie before heading downstairs to prepare a meal. When I left the computer out of habit, I pressed win+L to lock it, and everything seemed normal. About 30 to 40 minutes later, the screen went black. I thought it was just sleeping, so I moved my mouse and saw the cursor spinning blue as if loading. After waiting another 10 minutes, nothing happened. Then I restarted the PC, but it still didn’t work. I tried unplugging one of my monitors, but that didn’t help. When I turned it back on, everything appeared fine—it booted to the Windows logo and spun before either opening the lock screen or showing a black screen.
I also noticed that I can’t perform any key combinations like Control+Shift+Delete. The Windows key combined with Control+Shift+B only brings the mouse back to the center, and I’m unable to boot into safe mode. This is concerning, especially since I recently downloaded the latest Nvidia drivers.
Could someone please assist me with this issue? Your help would be greatly appreciated!
Remove the newest Windows updates; revert if it was a fresh build rollout. Update the BIOS. Visit the manufacturer’s website, download the latest version. Prepare a USB using eFAT format and label it BIOS. Extract the archive into the USB drive. Restart the computer and choose M-Flash during BIOS configuration. Pick the USB device and execute the BIOS file. Enter the user account, then open an elevated command prompt and run powercfg.exe /hibernate off. Press enter.
Have you attempted to start in safe mode via the boot options? (Press F12 during startup for certain models.) Could you share the system details?
The issue recurs after installing the latest Nvidia driver and updating Windows.
Have you solved this problem? I've kept facing the same issue even after reverting to earlier updates, but it's still not working.