Server HANG/Blue Screen/Restart

[jiandc]

Wingate 6.0.3 (1005) on Windows 2003 Server (Latest SP) on HP Compaq d530CMT machine with 512MB Memory.

Windows sometimes restarts, freezes, or BSOD.

The server has 2 NICS, one facing our LAN (HP NC3120) and the other (on-board BroadCom NetExtreme GigaBit Ethernet) to the internet directly to our Router with a real IP Address(ENS, Firewall and NAT Enabled).

When Win2003 restarts, after any of the above occurs, it displays the message below (pls note that this happened several times already).

20/10/2004 0x000000c2 (0x0000000a, 0x81ae8ec8, 0x6174754d, 0x00000000)
24/10/2004 0x000000c2 (0x00000007, 0x00001153, 0x02080007, 0x817c3d88)
24/10/2004 0x000000c2 (0x00000007, 0x00001153, 0x02080007, 0x817c3d88)
24/10/2004 0x000000c2 (0x00000007, 0x00001153, 0x00020025, 0x817e5ba8)
25/10/2004 0x000000c2 (0x00000007, 0x00001153, 0x02080006, 0x817fe4d0)
01/11/2004 0x000000c2 (0x00000007, 0x00001153, 0x12080007, 0x817c6cc8)
01/11/2004 0x000000d1 (0x00000064, 0x00000002, 0x00000000, 0xf81f0392)
01/11/2004 0x000000c2 (0x00000007, 0x00001153, 0x02080025, 0x817e09f8)


I have just increased the RAM today to 1GB hoping that the problem will be solved.

jian

[genie]

Hi,

I'll send you the test driver tomorrow so you can see if it fixes your problem.

[genie]

The new driver is on the way (ZIPed sys file).

[Bob Tucker]

I have a very similar problem, but on different hardware and operating system. The system board is an Intel se7505vb2 dual Xeon with 512 MB RAM. It has two onboard network connections: One Intel PRO/100+ Network Connection (10/100 Intel 82550PM Fast Ethernet controller) - which is the external network conenction, and one Intel PRO/1000 Network Connection (10/100/1000 Intel 82540EM Gigabit Ethernet controller) in 100 MB mode - which is the internal network connection. The external NIC connects to a Cisco 810 router which, in turn, connects to DSL on a leased line. The operating system is WinXP SP2 with patched TCPIP to eliminate loopback errors (MS post XP2 TCPIP stack tcpip.sys 5.1.2600.2155).

One or twice each day, I receive a 0x02c stop. The System Error Event ID's (1001 AND 1003) suggest device drivers. Microsoft KB articles also suggest memory. Microsoft's windows memory test from Microsoft OCA seemed to rule out memory. Nonetheless, I exchanged memory and power supply. Analysis of the error codes in the 1003 Events and memory dump suggested the NIC drivers. I looked at this as a hardware problem and did not think Wingate might be involved until just very recently.

I had not correctly configured DNS in Wingate. I learned from your excellent engineer Pascal on this site of the DNS switch in the advanced options program. I now use that. The Wingate DNS is accessed as a forwarder on the network DNS, and clients access only the network DNS. I made this change a few days ago. The number of BSDs has declined to less than one per day. (The number of email messages that could not be moved has also declined to less than one per day.)

Because the frequency of BDSs is directly affected by Wingate configuration, I think it may be that Wngate is involved. Would the test driver that you are sending jiandc be appropraite for this case?

Kindest Regards,

Bob Tucker

[Bob Tucker]

I just read a post from gergoe with a similar problem. In that case, you asked for the memory dump. Should you want it, I do have the dump from the lst crash.

[jiandc]

Hi,

I forgot to mention that the server has McAfee Virus Scan Enterprise 8.0i installed.

Today, the server went to BSOD again.

I was able to copy most of the details while it was dumping memory. Pls see below:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

QBIKHKXP.SYS

Stop: 0X000000D1 (0X00000064, 0X00000002, 0X00000000, 0XF721....)

Address f7218392 base at f720b000 date stamp 41493ef6


I will check my email for the driver that you sent.

jian

[jiandc]

I just opened my email and replaced Qbikhkxp.sys.

And now, we wait and see.

[Bob Tucker]

I listed the problem I have earlier in this thread. My oproblem seems to be very similar to that of jiandc. Might the updated Qbikhkxp.sys help in this case?

Kindest Regards,

Bob Tucker

[Bob Tucker]

I have three minidumps. Each indicates that the culprit is qbikhkXP.sys. I foolishly installed the MS beta debugger and am now having trouble with symbols. However, I have cut and pasted a section from the debugger indicating to be qbikhkXP.sys from one of the minidumps. If possible, I would like to get your newer qbikhkXP.sys as soon as possible. I will be at the client site in the morning, and it would be most useful if I could have the updated qbikhkXP.sys file.

Unable to load image qbikhkXP.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for qbikhkXP.sys
*** ERROR: Module load completed but symbols could not be loaded for qbikhkXP.sys
Probably caused by : qbikhkXP.sys ( qbikhkXP+3a5 )


With Kindest Regards,

Bob Tucker

[jiandc]

I can forward to you the email with the file I received from QBik

[Bob Tucker]

Dear Jian,

Please do forward it. Thank you.

With Kindest Regards,

Bob Tucker

[Bob Tucker]

Dear Gene,

I have emailed you the three minidumps from our Wingate system. Debug in each minibug indicates the crash was probably caused by qbikhkXP.sys in each case.

Kindest Regards,

Bob Tucker

[jiandc]

i need your email addreess

[Bob Tucker]

Dear Jian,

Thank you.

Kind Regards,

Bob Tucker

[genie]

Hi, Bob

The new driver has been sent to you.

[Bob Tucker]

Thank You!

[Bob Tucker]

Dear Gene,

I installed the new Wingate qbikhkXP.sys driver. I fixed my DNS settings via the Advanced Options program. I reduced the number of entries in spoof detection to 20. And I applied the SP2 Windows XP TCP/IP hotfix. (The later alllows loopback address 127.0.0.2 to be used on XP - which Wingate email appears to be using). It is now a day and a half later, and everything is working. It is early, but so far, there is not a hint of a problem. Previously, I would have had at least one BSOD and one or more "stuck" emails in this time period.

Thank you,

Bob Tucker

[genie]

Thanks for letting know, Bob - great to hear that!

[jiandc]

Hi,

Today is the SECOND day since I installed the new qbikhkxp.sys and our Wingate Server did not have any problem.

No Hang-up, No Restart and No BSOD.


jian

[Bob Tucker]

Dear Gene,

It has been four days. No BSODs no OxO2c stops. The "stuck mail problem stille xists, but at a low level when compared to what I had been seeing. The reconfiguration of DNS and reduction of the number of spoof rules may have contributed to that reduction.

[stuntgp2000]

I suffer from the same problem, please can anyone send me qbikhkxp.sys. I am using Wingate 6.03 B1005.

you can send me this file to my e-mail stuntgp2000@yahoo.fr

thanks in advance

[genie]

Good to hear the fix helped.
2Stuntgp2000: the new driver has been sent to you.

[stuntgp2000]

Thanks.

however, there is still no improvment, I have got 3 BSODs this afternoon.
I am doing my best to find the cause of this problem.

[genie]

Ok, can you send me the minidump file?
What did your system reported (module name, addresses, stop code)?

[stuntgp2000]

The minidump files is sent to you

[genie]

Hi,
I sent you the new driver. The crash that you observed is quite interesting. What I mean is that it looked like the hardware driver behaved in non-standard way, being unfair to our driver, so to speak. What kind of network hardware you have on your Wingate machine?

[stuntgp2000]

Hi,

Sorry I am not at work now, so I can't give you the exact reference of my hardware; but all I remember is that my network adapter is a built in network adapter with a VIA chipset. Monday, I will give you the exact info.

For now, It's not final because I need some time to proove it, but I suspect that this BSOD is due to Pc-cillin 2004 Firewall.

During the last three days I had no BSOD, because I disabled Pc-cillin 2004 Firewall.

Please can you tell me what is the role of Qbikhkxp.sys in Wingate ?

[genie]

QBIK driver plugs itself into the system between the drivers that do the hardware-related stuff and the higher-level protocol drivers. Therefore it relies on both parties to play fair.

[stuntgp2000]

As far as I know, Pc-cillin Firewall strats working since windows boot time. I think it interfers with Wingate.

Anyway I am going to proove this, if pc-cillin is behind this BSOD or not

thanks for your reply

[Bob Tucker]

Je suis sûr que vous avez raison. Wingate contient un excellent "firewall". Wingate ne devrait pas être employé avec d'autres. <<Je ne sais pas le mot pour "firewall" en français. C'a été beaucoup d'années depuis que je suis en France, et j'ai oublié presque tout.>>