|
|
Post by Coolverine on Feb 10, 2022 19:29:53 GMT -5
I was noticing recently that my computer would not go to sleep even though it's set to. Figured out what was going on and fixed it, just wanted to share it here in case anyone ever happens to have the same issue.
For some reason enabling Dolby/DTS encoding for my soundcard uses my microphone, even though I have my microphone disabled. This ended up being what was preventing my PC from sleeping, the microphone being in constant use as long as encoding is enabled.
Running this command "powercfg /requests" (without quotes) in a cmd prompt as admin shows anything preventing the PC from sleeping. Normally it will say "None" for everything on the list unless there's video/audio playing in a browser or there's a game or something like that running. It's not always straightforward what is causing it, but that command still gives an idea of where to look in order to fix the problem.
|
|
|
|
Post by Emig5m on Feb 22, 2022 1:07:59 GMT -5
Your PC wasn't sleeping probably because it sucks HEH-HEH-HEH-HEH...
|
|
|
|
Post by Cop on Feb 22, 2022 11:16:27 GMT -5
Sick burn...
|
|
|
|
Post by Coolverine on Feb 26, 2022 12:47:12 GMT -5
Ran into another issue today, I wanted to update my graphics drivers because I noticed my performance in Cyberpunk 2077 got worse after the new update. They would not install, was getting stuck at the system check part. All I did was sign out and back in on Windows, they installed just fine after that.
Also performance in that game seems better after updating the drivers.
|
|
|
|
Post by ForRealTho on Feb 26, 2022 17:57:15 GMT -5
|
|
|
|
Post by Coolverine on Feb 26, 2022 18:40:00 GMT -5
Might not be a bad idea, can't really remember the last time I did that.
I'm planning (hopefully) to get an RDNA 3 videocard whenever they come out this year. AMD says they're spending more money to make sure they meet the demand, I guess it remains to be seen.
|
|
|
|
Post by Coolverine on Dec 10, 2022 20:16:31 GMT -5
Found another thing, my secondary monitor is 75hz but it had a flickering issue unless I set it to 60hz. Had to go into the settings on the monitor itself and change DisplayPort from 1.1 to 1.2 and that fixed it, I can set it to 75hz just fine and there's no more flickering.  I prefer DisplayPort over HDMI, because Windows 10 has this dumbass feature where it treats the monitor connected with HDMI like it's always on if it's set to extended desktop, even when it's off. They say it's like that on purpose, but I think it's just some oversight that they are too lazy to fix. |
|
|
|
Post by Coolverine on Sept 18, 2023 1:09:10 GMT -5
Found another solution to an odd problem: Accidentally clicked "Direct Mode" setting in my sound card's software while a game was running, it didn't seem to like that and I lost all sound plus the sound control panel couldn't detect it anymore. Restarted but it was still stuck, was really afraid the soundcard was bricked. Solution was to uninstall all drivers and software, then went to device manager and saw my soundcard had the yellow warning symbol. Right clicked and scanned for hardware changes, that got it detected properly and all sound worked again. Also after re-installing the drivers/software for it, it actually sounds better than before. Not even sure I had to re-install the sound drivers/software but still did it for good measure. Have been thinking about removing the soundcard and using an HDMI audio extractor for sound though. I like my soundcard but Creative's drivers and software have been really hit or miss for a very long time now. One thing that continually messes it up is that Windows 10/11 has its own audio enhancement features and they seem to conflict with Creative/Soundblaster, even after turning them off. *edit* Also kept noticing my subwoofer was sounding pussified, turned out the crossover somehow enabled itself at some point which made the sub very quiet. I think crossover needs full range speakers, which these are 5.1 desktop speakers. |
|
