Protection ID info thread - v6.4.0 (build 08.07.2010)

[Bigeagle]

I have the same problem as mentioned in Post 496

Protection ID crashes instantly after starting the program
but as far as i know there is no program called unlocker installed on my pc

in a winXP vm the tool seem to run fine, even the scan over network works
but a sector scan for example would be difficult, even if the drive is provided to the vm the access is not direct, or am i wrong?

maybe there is another reason
my OS: Win 7 Professional x64

Protection ID v0.6.4.0 JULY has crashed...
Build 07/08/10-17:57:05

Welcome to the scene of the crash.... take me to the hospital

EAX = 000000030h, EBX = 00000000Ah, ECX = 000000030h, EDX = 000000000h
ESI = 0004F8510h, EDI = 000000031h, ESP = 00028BF4Ch, EBP = 00028BF94h

DS = 0002Bh, ES = 0002Bh, FS = 00053h, GS = 0002Bh, SS = 0002Bh
DR0 = 000000000h, DR1 = 000000000h, DR2 = 000000000h, DR3 = 000000000h
DR6 = 000000000h, DR7 = 000000000h

CCW = 00000037Fh, CSW = 000004020h, CTW = 00000FFFFh, CEO = 076907F6Ch
CES = 002E90023h, CDO = 000000000h, CDS = 00000002Bh, CR0NPX = 004000001h

Crash @ CS:EIP -> 00023h:0752C990Bh, EFlags : 000010206h
Stack @ SS:ESP -> 0002Bh:00028BF4Ch

Crash Code : 0C0000005h
Crash Report : In Page Error

ThreadID : 0984h / 02436
ThreadName : PiD Core Thread (thread 1)
Crash Happened in Scan File -> Unknown
Procedure Name : N/A
Crash File Line Range (low) -> 00
Crash File Line Range (high) -> 00
ProtectionID was scanning ->
Last Scan was -> Crash did NOT happen in scan thread
Scan was N/A
Next Scan is -> Crash did NOT happen in scan thread

Thread Start Va / Tag : 0x00409241

Pid executable range 0x00400000 -> 0x0057B000 (0x0017B000 bytes)

Crash address is NOT within pid's image