R0Nav 1.0
I am writing to confirm that this works great! Although I was having a few problems at the start, PiOjO helped me fix all of them and was very patient. Many thanks!
When does a public version comes out?
How much gold to become a VIP?
Have sent you a message on Skype 

Darn I have x64 bit comp, I'd be happy too test for a x64 Bit if you are making.
I will help you test it! I have a couple of keys so I don't mind.
Tested the 32-bit version, works great been using it for the last couple of days! The only problem i have had, is that recently its stated telling me that my key was in use or that the amount of users for that key have been reached???
well i had 2h using it, till my pc crashed (dont know why normaly never crashes),and now since 2days im trying get in again
...no matter when i try it all the time sireal in use 
...no matter when i try it all the time sireal in use 
pi0j0, glad to hear that this works on 32 bit.
Is it possible for you to kernel patch on 64 bit, but determine the interval at which windows scans, and discontinue the kernel right before it scans it, and then re-enable after it scans through the clean code?
Is it possible for you to kernel patch on 64 bit, but determine the interval at which windows scans, and discontinue the kernel right before it scans it, and then re-enable after it scans through the clean code?
Information
It works by periodically checking to make sure that protected system structures in the kernel have not been modified. If a modification is detected, then Windows will initiate a bug check and shut down the system, with a blue screen and/or reboot. The corresponding bugcheck number is 0x109, the bugcheck code is CRITICAL_STRUCTURE_CORRUPTION. Prohibited modifications include:
Modifying system service tables
Modifying the interrupt descriptor table
Modifying the global descriptor table
Using kernel stacks not allocated by the kernel
Modifying or patching code contained within the kernel itself, or the HAL or NDIS kernel libraries
It should be noted that Kernel Patch Protection only defends against device drivers modifying the kernel. It does not offer any protection against one device driver patching another.
Modifying system service tables
Modifying the interrupt descriptor table
Modifying the global descriptor table
Using kernel stacks not allocated by the kernel
Modifying or patching code contained within the kernel itself, or the HAL or NDIS kernel libraries
It should be noted that Kernel Patch Protection only defends against device drivers modifying the kernel. It does not offer any protection against one device driver patching another.
This thread is closed for replies.


