![]() ![]() If the problem persists after these steps, you may have a faulty cooler or flawed video card and/or processor. ![]() Also, check that all fans are still working and replace any that aren't. A can of compressed air can dislodge stubborn dirt. Use a vacuum to suck up obvious dust (avoiding internal cables, of course). Overheating can often be solved by opening your PC and cleaning out the cobwebs. If the processor has overheated, the black screen will usually prompt a reboot or automatic shutdown of the PC. As noted, you should suspect the video card if you receive a black screen when the computer otherwise appears to be working (the fans are on, the hard drive light is active, etc). In many cases, overheating is caused by the video card or the processor. Overheating will usually result in a featureless black computer screen, which may or may not be followed by a restart. Fortunately, computers are built to shut down before that occurs. This heat must be removed to keep the system running high temperatures can cause components to lock up and become damaged. Your Windows black screen error could be down to the motherboard, the power supply, or the hard drive.Īll computers generate heat. If the monitor does work with another PC, but not with yours, then you're probably looking at a hardware fault elsewhere that impacts the video card's ability to work. Check it by connecting to another computer. Should the monitor not work when connected to integrated graphics, however, you may have a monitor issue. Also check the video card for obvious signs of defect, like a broken cooling fan or charred electronics. If you recently did that, revert to an old driver. Try updating to the latest video driver on Windows. If you have a discrete video card, try removing your card and switching to your motherboard's integrated video.ĭoes your monitor work? Then the video card is the problem. If these easy solutions don't work, you're likely dealing with video adapter issues. Some versions of DVI and HDMI can't handle resolutions above 1080p. ![]() I have an idea to hide all windows before launching a screensaver to prevent reading information during switching to the lock screen.Did you just upgrade your monitor? If so, make sure your connection can handle the resolution. To access the settings for your lock screen in Windows 10, navigate to Settings > Personalization > Lock screen.The first thing you can change is the lock-screen image. You can use "rundll32 user32.dll,LockWorkStation" instead of "tsdiscon", but I prefer the second way. You can configure screensaver settings here (press Win+R, enter text below and press OK): control.exe can reach the screensaver settings via GUI. That's why it works only after configuring a screensaver in Windows. The script takes a key value for the screensaver from the windows registry and use it to start a pre-configured screensaver. Therefore I decided to follow the way from the screensaver settings: to lock session as continuation of the screensaver. I wanted to do smth described in the title, but didn't find a way to do it (I hope, yet). bat file with the next content: for /f "tokens=3" %%a in ('reg query "hkey_current_user\control panel\desktop" /v scrnsave.exe') do start "" /wait /d "%%~dpa" "%%~nxa" /sĪnd launch it when you want to lock the session. Just think of it as shell scripting in a more pythonic environment and it's not terrible. Having a 1/4 century of bash experience, powershell is very strange, but also a bit refreshing to work with. ( Learn more here.) A slightly less convenient alternative is Get-Member. Unfortunately, installing it now requires the -AllowClobber option. (I have to admit that even though I can write sed directly into a script without testing it at the CLI, this IS better.) There is a useful tool for exploring objects that is recommended by a Microsoft technet blogger. We access a single property with the convenient dot notation. ![]() Here, the Get-ItemProperty returns an object that has many properties. This is a pretty succinct demonstration of how powershell returns objects (complete with methods, accessors, etc.) rather than streams of text like bash. That value just happens to be a complete path to a *.scr file, and therefore you can (and I do) tell powershell to run it as a command. This will get the value of the SCRNSAVE.EXE property from the registry. Powershell.exe -command "& (Get-ItemProperty 'HKCU:Control Panel\Desktop')." # This works from both WSL/bash and powershell! To make this a legitimate SO answer, I'll include the simpler one: #!/bin/bash ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |