Home/ Questions/Q 5943987
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T16:28:26+00:00

I’m debugging plugins on Windows 7 and of course the plugin host (Cubase5.exe) occasionally

  • 0

I’m debugging plugins on Windows 7 and of course the plugin host (Cubase5.exe) occasionally crashes because of errors in the plugin. On XP or Vista, I could always restart it immediately and continue working. But on Windows 7, even though Cubase appears to close, it is still visible in Task Manager and I cannot kill it by any means. After a minute or two, it disappears by itself. In the mean time, I can’t work because the plugin DLL is still locked by the process.

Does anyone know why this happens on Windows 7? I’ve already tried disabling Automatic Error Reporting but that didn’t help. I’ve tried attaching cdb to Cubase, but I get:

Cannot debug pid 5252, NTSTATUS 0xC0000001
    "{Operation Failed}  The requested operation was unsuccessful."
Debuggee initialization failed, NTSTATUS 0xC0000001
    "{Operation Failed}  The requested operation was unsuccessful."

I tried following the instructions here but it appears this is only possible if I connect a second machine to my computer to debug it remotely.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I finally found the solution, using this article:

    http://blogs.technet.com/b/markrussinovich/archive/2005/08/17/unkillable-processes.aspx

    This required installing the Windows Debugging Tools for Windows (nice name) and LiveKd, but by following the steps outlined I was able to track which driver was causing the process to hang: it turned out to be the 64-bit driver for the M-Audio Oxygen 8 V2 controller I’m using. Unfortunately no driver update is available.

    Anyway, if anyone encounters a similar problem, this is the way to solve it.

    • 0