==> Crash/Hang/Block, please come here <==

[fred3]

The processor is an AMD 32 bit.  Something like an AMD XP 3200+ I believe.

I'm not sure what the "old interface" is.... ?

[Curson]

Hi fred3,

The old interface is not using the QT Toolkit but the Win32 API.
Could you please download this version and give it a try ?

Regards.

[fred3]

Yes.  The old one works on this computer.
Thanks.

[Curson]

Hi fred3,

I'm glad to read this.
Could you please stick to the version with the old interface until we troubleshoot the problem you encountered with the new one ?

Regards.

[fred3]

Yes.  Thank for the help!

[Curson]

Hi fred3,

You are very welcome.
I will let you know of the outcome of our investigation.

Regards.

[graphixillusion]

Hi there. I'm running the last version of roguekiller x64 under windows 8.1 pro wmc x64 and i'm receiving bsod. I always used roguekiller and i never got this stuff. I'll upload the minidump in here. Thank you!

[Curson]

Hi graphixillusion,

Welcome to Adlice.com Forum.

Thanks for bringing this problem to our attention.
We will proceed to the analysis of the minidump you provided as soon as possible.


Regards.

[Tigzy]

Hello,
Just to let you know (I'll update the main post as well) that every BSOD issue will not be fixed now, for a very good reason:
We are in the process of redoing the driver from scratch for better performance and stability.

The driver is the thing that would cause 99% of the BSOD you encounter with (and caused by) RogueKiller, so hopefully once the new version of the driver is out the problem will be gone. Please be patient.

As a workaround you can switch driver off with -nodriver command line, or for Premium users by unchecking the Kernel driver in settings.

[WD-40]

running windows 10
I can run RogueKiller_DEBUG previous version.
I can run RogueKiller newest version in 32bit
I can't run RogueKiller 64bit any version.
64bit versions crash (blue screen) within seconds of starting the app, so there is no dmp from RogueKiller.
windows minidump included

[Curson]

Hi WD-40.

Welcome to Adlice.com Forum.

According to the minidump you provided, the crash is caused by a driver issue.
However, we won't be able to correct it since we are in the process of redoing the driver from scratch for better performance and stability.

You can still use the 64-bit version of RogueKiller using the "-nodriver" switch.
If you need help with the tool, please refer to the official tutorial.

Regards.

[Ammako]

Latest version of RogueKiller

What if I am -not- getting a BSoD, but my entire computer is freezing?
Granted, I never let it sit there for several minutes before seeing if it would blue screen, but every time, it consistently freezes my entire computer when it gets to Antirootkit Scanner and I have to hit the reset button.

Scan completed fine in Safe mode, but driver was off when in safe mode.

[Curson]

Hi Ammako,

Could you please give me the name and full path of the process displayed when the system hang ?

Regards.

[rarson]

I am using the old version of Roguekiller (I don't really care for the new interface) and I'm having a problem with it on most computers. It usually gets to around 50% before the interface freezes. I can open up Task Manager and see that Roguekiller is still doing something, I can move the Roguekiller window around as well. But I can't get the Stop button to work.

If I leave it sit for a while (>10 minutes), the stop button eventually functions. If I leave it sit even longer, Roguekiller will eventually finish its scan. It usually takes longer than 30 minutes for it to "snap out of it." This happens on 32- and 64-bit versions of Windows 7, 8, and 10. Task Manager shows Roguekiller's CPU usage, RAM usage, and disk usage changing the entire time, so like I said, it still appears to be doing something even when the interface is frozen.

I never had this problem with the versions of Roguekiller prior to the interface change, nor with the new interface, but as I stated, I don't like the new interface so I switched over to using the "old" versions shortly after the new interface was released. I just updated to 12.2.0.0 and I'm still having this problem on pretty much every computer.

[Curson]

Hi rarson,

Welcome to Adlice.com Forum.

I was able to reproduce the issue on my end.
However, the old interface is not really updated anymore, so I can't promise we will be able to fix it.

Regards.