All geek questions in one place

Killing processes in Windows 7

I am debugging plugins in Windows 7, and, of course, the host plugin (Cubase5.exe) sometimes crashes due to errors in the plugin. In XP or Vista, I could always restart it immediately and continue. But on Windows 7, although Cubase seems to close, it still appears in the task manager, and I can't kill it in any way. After a minute or two, it disappears on its own. At the same time, I cannot work because the plugin DLL is still blocked by the process.

Does anyone know why this is happening on Windows 7? I already tried to turn off automatic error reporting, but this did not help. I tried connecting 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 to follow the instructions here , but it seems that this is possible only if I connect the second machine to the computer to debug it remotely.

+3
source share
5 answers

Finally, I found a solution using this article:

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

This required the installation of Windows debugging tools for Windows (a nice name) and LiveKd, but by following the steps I was able to track which driver caused the process to freeze: it turned out to be a 64-bit driver for the M-Audio Oxygen 8 V2 controller that I use . Unfortunately, there is no driver update.

, - , .

+4

Process Explorer ? "":)

+1

, , werfault.exe Cubase open minidump .

, .

+1

, - Process Monitor, Cubase. , , "", . , , Cubase .

0

, . , "" , " " ( " ".). , (, svchost.exe), . , , () , .

, , .

0

Source: https://habr.com/ru/post/1761472/

More articles:


All Articles