Suggestion : Collaborate To fix Qbikhkxp.sys Problem

[stuntgp2000]

As a Wingate user, I would be very happy if I could help Wingate Developers to fix Qbikhkxp.sys Problem.

Since I believe that Wingate is the most advanced proxy server, I would get very happy if it get to be stable.

As I remarked many users/customers of Wingate suffer from a strange Blue Screen Of Death (BSOD) that appears randomly, and as one of those who suffer from this BSOD. I decided to help Wingate Devs to solve this issue.

Then I decided to write this topic, in which Wingates users/customers, who face this BSOD, can give all the TECHNICAL Infos about their systems.

So people are encoureged to give their :
1) Hardware configuration (CPU, RAM, Modems, Network adapters..)
2) System & its carateristics ( i.e XP SP1, W2K SP3 ..)
3) Protection utilities (Antivirus, Firewalls ...)
4) any remarks or events about the BSOD (i.e it appears when many PCs are connected, when using a specefic program, when changing or activating certain Wingate options ...)

finaly, I ask from a Moderator to put this topic as Sticky, if he wish to

Thanks in advance.

[stuntgp2000]

The PC on which Wingate 5.2.3 is installed is running Windows XP SP1 Pro with all critical updates installed. My Hardware configuration is Celeron 2.4GHz, 128Mo RAM.

I was using wingate without having any problem (I had WinGate 5.2.3 + PureSight) till the day I went to Integrate Kaspersky Antivirus plug-in into Wingate. Then randomly I got blue screens of death.

I thought that Kaspersky plug-in is the source of the problem and I uninstalled it, then everything went OK and back to normal. The server started to work normally.

Days later, I went to do a fresh installation of Windows XP SP1, I installed Wingate, I configured It as usually. but this time I didn't install any other plug in, only Winagte.

Since downloads are forbidden, I went to configure WWW Proxy Service to block all links that has .exe, .dll, .ocx, in order to decrease the risk of getting infected by spywares, at the end. I applied it but it seems it does not work.
I read the Help and I found that in order to do that I must activate ENS & Wgic redirection in WWW Proxy Service. And Opps, 5 mins later after activating Transparent Rederection, I have got a BSOD. then deactivated the option and everything went OK, then I applied it again and I've got a BSOD again. then I realized that END & WGIC Redirection is the source of the problem, thus both Puresight & Kaspersky use Transparent Redirection in order to do their work. So I may say that something is wrong with Transparent Redirection.

I have made some research on the net and I found that this problem occurs because Wingate engine wants to write in a non allocated memory plage or an other program conflicted with Wingate Engine.

I haven't tried Wingate with Windows XP SP2, but I think both users with SP2 and/or with NX Technology in their CPUs will suffer more still use SP1.

By the way, I have looked here & there and I found that one of the solutions is to use Wingate 6.0.3 Build 1005. In fact, the use of Wingate 6.0.3 build 1005 reduce the number of BSODs. However th problem is still there. because now I am using Wingate 6.0.3 Build 1005 and the problem remains.

I hope I could help you better Identify the source of the problem.
And I will keep looking for the main reason behind this problem.

[erwin]

Hi there

Thanks for your feedback

There have been a few BSOD fixes since 5.2.3 and as you have found WinGate 6.0.3 has fixed the issues you had with XPSP1.

Unfortunately when new Service packs are released or hardware drivers (usually for network adapters) these things can often cause BSODs with the Qbikhkxp.sys (the driver used by WinGate ENS) since they operate deep in the OS just like the WinGate driver.

We always looking to improve the stability and performance and make sure the that is compatible with most situations but unfortunately sometimes BSODs will encountered.

Good feedback on these is always appreciated, so keep up the good work.

Regards
Erwin

[genie]

Hi,

Thanks for your offer. Normally, when this kind of problem occurs we ask people to provide us with the certain information, such as: operating system, network card makes/types/models and the exact information the system reported (stop code, addresses, etc). Also, it is very beneficial to supply QBIK developers with the dump file, generated by the system, even if it is only a minidump file.