We can't reproduce this here. What version of TurboActivate are you using? Also what bitness is it (x86/x64)? And what version of Windows are you running on?
It almost sounds like an overclocked CPU problem.
Privileged Instruction exception on startup [Not a bug]
ChristophHi,
I noticed that my application that is using TurboActivate is throwing an Privileged Instruction exception. The code adress is pointing to:
IsInsideVMWare_(void)
defined in this file:
C:\Users\Wyatt\Documents\Visual Studio 2005\Projects\TurboActivate\Library\IsInsideVMWare_.asm
(I am not Wyatt, so I don't think this is a real location but rather the hardcoded path from the lib).
Is this something to worry about? I don't notice any weird behaviour, but that might be misleading
Assembly dump:
--- C:\Users\Wyatt\Documents\Visual Studio 2005\Projects\TurboActivate\Library\IsInsideVMWare_.asm 000000014059EF70 mov eax,564D5868h 000000014059EF75 mov ecx,14h 000000014059EF7A mov dx,5658h 000000014059EF7E in eax,dx <- This line is throwing the exception000000014059EF7F ret
ChristophWin 7 x64 on a Macbook Pro Late 2012 i7/2,6Ghz running Bootcamp. I am not overclocking anything. I am using the latest TurboActivate version
If you have a debugger attached to your process, and you have specific debugger options checked (i.e. break at any exception, etc.), then you will get this error. Under normal operation you will never get this exception (because we trap all exception, even privileged instruction exceptions, for this particular function call).
Long story short: in real-world usage this is not a problem.
If you want to continue attaching a debugger to your app and *not* get spurious exceptions then you need to either use (a) a well-configured debugger (good ones by-default only halt on uncaught exceptions) or (b) fix the config of your current debugger (tell it to only halt on uncaught exceptions).