-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Audio
- Windows Volume Adjust crashes Often.

Create an account on the HP Community to personalize your profile and ask a question
12-01-2021 09:38 PM - edited 12-01-2021 09:41 PM
Windows Volume Adjust crashes Often. i thought the issue would be with the audio drivers and I uninstalled it and reinstalled in device manager. Still the Problem Exists. I tried Windows Defender Scanning, sfc /scannow, I ran HP Hardware Diagnostics. I tried downloading and installing the driver from HP driver downloads and even flashed OS thrice. The Problem still exists. The Sound from the speaker is crackled sometimes, and sound response is not immediate. If i Muted, it gets muted 30s later. I updated BIOS too.
Does anyone have solution for this?
Solved! Go to Solution.
Accepted Solutions
12-02-2021 12:22 AM - edited 12-02-2021 12:28 AM
Solution
New temporary solution that works with Realtek drivers. Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\xxxx\PowerSettings where 'xxxx' is one of keys which contains DriverDesc value 'Realtek High Definition Audio'. Note: There may be multiple ones containing PowerSettings, for example 'Nvidia High Definition Audio'. You'll find there three binary values and set them: ConservationIdleTime = ff ff ff ff; IdlePowerState = 00 00 00 00; PerformanceIdleTime = ff ff ff ff. Default values are all 00 00 00 00 which disables power settings, but driver somehow overrides it with 0a 00 00 00 which is 10 seconds (0x0a = 10) and is by default in driver. Problem shouldn't occur again after restart (or I haven't noticed). This is not solution to problem, it only prevents audio hardware going idle, but I don't see any impact on energy consumption. I'm going to send mail to Realtek support about this problem as it's clearly driver problem, and when (or if) they respond I'll post an update.
I would like to add for users not familiar with searching the registry for these settings, there is one more step.
On my Envy Laptop in the same registry file you had to:
Click on the key's actual drop down arrow
Search for the "PowerSettings" folder
For my registry key this was located under both files "0001" and "0007" AND both locations had the Idle values incorrectly stated.
thanks to @FVB-92 and @RoccoIV
12-02-2021 12:22 AM - edited 12-02-2021 12:28 AM
Solution
New temporary solution that works with Realtek drivers. Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\xxxx\PowerSettings where 'xxxx' is one of keys which contains DriverDesc value 'Realtek High Definition Audio'. Note: There may be multiple ones containing PowerSettings, for example 'Nvidia High Definition Audio'. You'll find there three binary values and set them: ConservationIdleTime = ff ff ff ff; IdlePowerState = 00 00 00 00; PerformanceIdleTime = ff ff ff ff. Default values are all 00 00 00 00 which disables power settings, but driver somehow overrides it with 0a 00 00 00 which is 10 seconds (0x0a = 10) and is by default in driver. Problem shouldn't occur again after restart (or I haven't noticed). This is not solution to problem, it only prevents audio hardware going idle, but I don't see any impact on energy consumption. I'm going to send mail to Realtek support about this problem as it's clearly driver problem, and when (or if) they respond I'll post an update.
I would like to add for users not familiar with searching the registry for these settings, there is one more step.
On my Envy Laptop in the same registry file you had to:
Click on the key's actual drop down arrow
Search for the "PowerSettings" folder
For my registry key this was located under both files "0001" and "0007" AND both locations had the Idle values incorrectly stated.
thanks to @FVB-92 and @RoccoIV