什么会使PrimeCeCueTrime.存在无限期悬空?

我有一个使用性能计数器的应用程序,已经工作了几个月。现在,在我的DEV机器和另一个开发机器上,当我调用PrimeCeCuthRealSype时,它已经开始挂起。据我所知,它是无限期的。我使用哪个类别作为输入并不重要,使用API的其他应用程序也表现出相同的行为。

调试(使用MS符号服务器)表明,挂起的是对Microsoft.Win32.RegistryKey的调用。进一步调查显示,正是这条线悬挂着:

while (Win32Native.ERROR_MORE_DATA == (r = Win32Native.RegQueryValueEx(hkey, name, null, ref type, blob, ref sizeInput))) { 

这基本上是一个试图为性能计数器数据分配足够内存的循环。开始于 size = 65000 做一些迭代。在第四次通话中,当 size = 520000 , Win32Native.RegQueryValueEx 挂起。

此外,相当令人担忧的是,我在PerformanceCounterLib.GetData的参考源中发现了以下注释:

    // Win32 RegQueryValueEx for perf data could deadlock (for a Mutex) up to 2mins in some 
    // scenarios before they detect it and exit gracefully. In the mean time, ERROR_BUSY,
    // ERROR_NOT_READY etc can be seen by other concurrent calls (which is the reason for the 
    // wait loop and switch case below). We want to wait most certainly more than a 2min window. 
    // The curent wait time of up to 10mins takes care of the known stress deadlock issues. In most
    // cases we wouldn't wait for more than 2mins anyways but in worst cases how much ever time 
    // we wait may not be sufficient if the Win32 code keeps running into this deadlock again
    // and again. A condition very rare but possible in theory. We would get back to the user
    // in this case with InvalidOperationException after the wait time expires.

以前有人见过这种行为吗?我能做些什么来解决这个问题?