14

The adventure (how it all started)

Exactly as in the title, whenever I lock the screen (by pressing Windows + L or Ctrl + Alt + Del -> Lock) audio stops working. Well, partially, since speakers still work perfectly but headphones (line out) don't! Same thing does NOT happen when the PC wakes up after sleep mode. It seems like the only thing killing the line out is locking the damn screen.

This is by far the weirdest bug I have ever encountered.

System

-Sager NP7338 / CLEVO W230SS
-Sound card: VIA High Definition Audio (HD Audio) 1802p
-Windows: 8.1 x64 Pro

Initially I thought that the problem was audiodg.exe crashing because of faulty drivers but after some tests I noticed the process was simply restarted and the audio services (WindowsAudio and WindowsEndpointBuilder) were never stopped (in fact speakers keep working).

I tried the following drivers: - 10.0500d - 10.1200a - 11.0100a - 11.0300a

Have you got any idea? Any other driver I might try? As long as it's compatible with my 1802p (I tried a Realtek driver out of desperation and I got BSOD).

A possible cause...

My hypothesis is that locking the screen triggers some event that makes some critical process crash. The problem is I have no idea which process this might be. Plus the event viewer doesn't give any useful information in regard. I'm going to test Windows 7 but it's absurd because this laptop is supposed to be compatible with Windows 8.1 (yes, it's still in warranty and if I can't find a solution I will return it).

Thank you in advance for your help.

UPDATE 1

I have literally compared the list of processes running BEFORE locking the screen and the list of processes running after. Apart from a couple of non-related processes everything is exactly the same. I'm desperate... Plus I couldn't test Windows 7 since I can't boot it in UEFI mode (and I don't want to erase the current Windows partition in case I have to show the problem to someone.

Another thing: I tried to disable all the startup items (including VIA VDeck) and magically the problem seemed fixed. I could lock the screen and the headphones would keep working but once I triggered sleep mode PUF, audio was gone again. I am quite sure it's a software problem.

2
  • 2
    Thanks for your answer! Running initHeadphones.exe also worked with my Clevo P170SM-A with a Realtek. Renaming hp.dll didn't work as a permanent workaround, but I managed to create a Windows task to run initHeadphones.exe "On workstation unlock of any user" Commented Apr 7, 2015 at 3:37
  • 1
    Can you post the actual answer as an answer?
    – Burgi
    Commented Dec 6, 2016 at 21:19

2 Answers 2

3

Since this topic is over two years old and no 'answer' has been provided, I'm happy to collect the points. Here is the answer that the author found, his/her self (moved here from the question).

This is the weirdest thing ever happened to me. Here's what I found out:

  • By itself the audio driver (be it the default "High Definition Audio" from Microsoft or "VIA HD Audio(Win8.1)" from VIA) stops sending the sound to line-out after waking up from sleep mode

  • If I also execute the hot keys manager from CLEVO (HkeyTray.exe) audio works through suspend/wakeup but doesn't work after locking the screen

  • Now the best! Inside the hot keys manager's folder (in my case C:\Program Files (x86)\Hotkey) there is a small .exe file called InitHeadphone.exe. As you can guess running it re-enables audio from line-out/headphones no matter what you did (sleep, lock, whatever). It seems to have some dependencies so it must be run inside the folder.

What an adventure folks! I'll try to investigate more and understand why there is such a connection between two pieces of software of two different producers (CLEVO and VIA). It's almost like they are in a symbiotic relationship! I hope this will help somebody. Please let me know if so. :)

Temporary Workaround

If your headphones/Line-out don't work after sleep mode or locking the screen and you have a VIA sound card just download CLEVO's hot keys manager and run the file initHeadphones.exe. I still have to figure out why though...

Stable Solution

wspawn from the forum of Notebook Review (thank you! You are still welcome to post an answer yourself) found the following solution:

To prevent the hotkey software from messing with the audio controls / headphones rename the following file: C:\Program Files (x86)\Hotkey\hp.dll to C:\Program Files (x86)\Hotkey\hp_DISABLED.dll.

FINAL SOLUTION

Apparently installing the Hotkey utility from CLEVO (which can be also found on Sager's drivers page) is enough. Latest version is 8.0100. I still have to find a way to fix the problem without installing this stupid program.

1
  • Thanks for taking the initiative on cleaning this up. I moved more of the solution information here.
    – fixer1234
    Commented Apr 15, 2017 at 16:58
1

As an addition to Reeves's answer, it is possible to solve this problem without having Clevo's hotkey program running.

Note that, as far as I'm aware, this problem is unique to Clevo laptops, but affects a huge number of them. It is a bit annoying that this problem has existed for years, but Clevo seems perfectly happy with their software hack to fix the (presumably) hardware bug.

On Windows

What we need to do is run the InitHeadphones program every time the computer wakes from sleep.

First, one does unfortunately have to first install Clevo's Hotkey program, as explained in Reeves's answer to get the InitHeadphones program. If there is an easier way, please correct me!

Second, disable the Hotkey program from autostarting.

Finally, open Windows's Task Scheduler application. Set the action to run InitHeadphones.exe (By default, C:\Program Files (x86)\Hotkey\InitHeadphones.exe) and the trigger to be:

Begin the task: On an event
Log: System
Source: Power-Troubleshooter
Event ID: 1

On Linux

There exists a project called init-headphones on Linux, which provides a Python program which talks directly to the amplifier and tells it to behave.

Link to repository: https://github.com/Unrud/init-headphone

This program does exactly what it says on the box with no hassle after being set up

1
  • As of now, it looks like my clever method using Windows Task Scheduler no longer works, even if I run the task manually :( - The Linux method is still working fine!
    – Sompom
    Commented Dec 9, 2017 at 17:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .