High CPU usage with Firefox (also, freeze issues)

[avatar]

I will be able to sign the new driver version only at the office (EV certificate token is there).

Here is a new build with an old signature:
https://www.dropbox.com/s/i14waabp05nr847/drivers.bin?dl=0

It works for me, but I am not sure if windows allow you to use it. It is easy to check though.

How to use it:
1. Replace "drivers.bin" in Adguard folder with this new file (better backup the previous version just in case).
2. Restart Adguard Service
3. Check %windir%\System32\drivers\adgnetworkwfpdrv.sys file details. Version should be 6.0.0.20.

 

[randomusername]

I updated the file and restarted the service. Which options do I have to set?

 

[avatar]

I updated the file and restarted the service. Which options do I have to set?

So it works?

Just leave the WFP driver checked and let's wait for some time. I hope that bluescreen issue is fixed in this new version.

 

[randomusername]

I don't know if it works yet ...

Checked. Waiting ... Wish me luck.
(So do I!)

 

[avatar]

Fingers crossed

 

[randomusername]

Are you still investigating the High CPU issue by the way? Or are you focussing on "just use the other driver"?
(J4I, no High CPU problems over the weekend.)

 

[avatar]

Are you still investigating the High CPU issue by the way? Or are you focussing on "just use the other driver"?
(J4I, no High CPU problems over the weekend.)

I am out of ideas so the other driver is my best bet now

However now I learned about EagleGet, maybe we have a compatibility issue here?

 

[randomusername]

I don't know. Have you tried installing EagleGet?

 

[avatar]

I don't know. Have you tried installing EagleGet?

No, I asked @George to test AG with it.

 

[randomusername]

Thanks.

I'll report tomorrow if there's another BSOD with the new driver.

 

[randomusername]

BSOD after 20 minutes.

---------- Post added at 07:33 PM ---------- Previous post was at 07:25 PM ----------

I uninstalled EagleGet now...

 

[avatar]

How is it without EagleGet?

 

[randomusername]

No new bluescreen yet. However, I can safely say that it's not EagleGet which caused the BSOD as it had been installed for a couple of weeks without a problem.

 

[avatar]

No new bluescreen yet. However, I can safely say that it's not EagleGet which caused the BSOD as it had been installed for a couple of weeks without a problem.

Then this is a compatibility issue, but I doubt we can handle it on our side.

I see eagleget driver in the error stack trace, no sign of our driver. This means EagleGet just does not handle some cases properly (when there're more than one WFP driver in the system).

 

[randomusername]

I'll better let them know then, thanks.

Up to now, no High CPU issue either ...
How does the driver work?

 

[avatar]

Up to now, no High CPU issue either ...
How does the driver work?

Roughly:
1. It intercepts TCP/UDP packets and sends them to user mode (AdguardSvc) which decides what to do with it.
2. Adguard service sends back modified packets which are injected into the TCP/UDP flow.

 

[randomusername]

Sweet. Looks like I'll keep that one. Why isn't it the default one?

 

[Boo Berry]

The WFP driver? Likely because of potential incompatibilities, e.g. Kaspersky.

 

[randomusername]

Ah, OK.

So ... not sure if this topic is irrelevant now.

 

[avatar]

In fact WFP driver is default for Windows 8 and newer.
The only exception is when KIS or ESET is detected.

So I don't know why it wasn't turned on in your case.