The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Clevo Hotkey app is no longer working

    Discussion in 'Sager and Clevo' started by 0x2501, Oct 17, 2012.

  1. 0x2501

    0x2501 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Hi guys,

    Hope you can help me out. I just reinstalled Windows because the Hotkey application suddenly stopped working, and well, I have no bloody idea what is going on as it just stopped working yet again.

    Since the Hotkey app stops working, I'm unable to change the screen brightness, turn on/off Wifi+BT, or basically, do quite a lot of basic things. I got a P150EM, and I'm running Hotkey 6.0056.

    Here's the error message I get:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
    at HotKey.ControlCenter.GetBrightness()
    at HotKey.ControlCenter.Form1_Load(Object sender, EventArgs e)
    at System.Windows.Forms.Form.OnLoad(EventArgs e)
    at System.Windows.Forms.Form.OnCreateControl()
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmShowWindow(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ----------------------------------------
    HotKey
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Hotkey/Hotkey.exe
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
    ----------------------------------------
    Audiodll
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Hotkey/Audiodll.DLL
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Any ideas?
     
  2. mattcheau

    mattcheau Notebook Deity

    Reputations:
    1,041
    Messages:
    1,246
    Likes Received:
    74
    Trophy Points:
    66
    did you try reverting back to 6.0045?
     
  3. 0x2501

    0x2501 Newbie

    Reputations:
    0
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    Yeah, I did try 6.0045, but well, I found the answer to this problem.

    TeamViewer 7 Monitor Driver.

    I had to roll-back to a previous version (System Restore) before that specific driver was installed, and problem solved
     
  4. kong

    kong Notebook Consultant

    Reputations:
    24
    Messages:
    119
    Likes Received:
    11
    Trophy Points:
    31
    I didn't install the hotkey app, and I can do all basic functions e.g. adjusting brightness, volumes, toggle keyboard light, etc. :\
     
  5. jaug1337

    jaug1337 de_dust2

    Reputations:
    2,135
    Messages:
    4,862
    Likes Received:
    1,031
    Trophy Points:
    231
    That's probably because Windows Update did it for you.... what the hell :D
     
  6. studmuffin

    studmuffin Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5

    I also have the P170EM. After about a week of having it the hotkey program stopped working. Was really bugging me! A few weeks later I got a second hard drive and reinstalled my computer into a raid 0. I was also hoping a clean reinstall would fix the hot keys. and it did! for a week.... I couldn't figure it out. The debugging I did made it sound like .NET issues. I had to install older versions of .Net for my some of programs and thought one of those was the problem. Still couldn't figure it out for the longest time.

    2 months later. Here this post here... after reading it I went into my Team viewer settings, uninstalled the monitor driver. Tada! The hotkey program started working again (after I started the program again, I've kept a shortcut on my desktop. It would run just long enough for me to turn the keyboard backlight on) without a computer reboot. Darn program conflict. The monitor driver is a minor thing at least.

    But yay! Hotkeys again!

    and indeed. Windows has some basic hotkey functionality it will do automatically if a 3rd party program isn't running that overrides it. Most I got it to do was volume controls and put the computer to sleep. Which is actually kind of annoying the sleep hotkey is inbetween the Mute and Reduce volume hotkeys... Eh. I'll deal with it. The laptop is boss
     
  7. theriko

    theriko Ronin

    Reputations:
    1,303
    Messages:
    2,923
    Likes Received:
    4
    Trophy Points:
    56
    If you have trouble with the sleep button just tell windows to do nothing when it's pressed (in power options)
     
  8. phrozact

    phrozact Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Just wanted to say thanks for posting this. Saved me the trouble of re-installing the operating system!