EP_X0FF wrote:\Device\Ptilink is driver object of PTILINK.SYS which is related to Parallel Technologies DirectParallel IO Library.
What about second one, I'm not sure what is this. If you interested then can you attach it here for further analysis (or upload somewhere to free file hoster)?
NOD32 v4? I've tried rku before together with NOD without any problems. Did you tried running full scan of chkdsk for your system disk?
Im gonna post all things i find that might be related to my problem with RKu, so sorry if i get to much offtopic, but i figure its best to post all i found.
First, those two hidden drivers didnt show up after reboot, havnt seen them again
I uploaded them both to:
http://rapidshare.com/files/368404568/drivers.rar.html
PW: kernelmode
MD5: E4A26610E59854FBBE407F01D71B350B
Secondly, I was wrong, in rootrepeal the hooks i though was from nod32 was from outpost.
I dont have it active but apparently it had a driver running which did those hooks, so i uninstaled it and disabled nod (to be sure)
Now after reboot (without outpost or nod running) i have some new results from rootrepeal (still the same with RKu, it hangs on the same place as before),
Rootrepeal shows some weird hooks (they werent shown before, maybe cus outpost hooks was shown instead, i dont know)
http://img411.imageshack.us/img411/534/hooks.png
And this is the log file:
http://rapidshare.com/files/368408426/rep.txt.htm
log from stealth objects:
http://rapidshare.com/files/368415011/s ... s.txt.html
(Also i think its a bug in rootrepeal, when sorting the hooks like in the left window in the image and then saving a log file, the log file is different
http://rapidshare.com/files/368409417/rep2.txt.html )
edit: I run chkdsk and it reported 0 damaged sectors