Bandwidth Control Causes Crash (BSOD)

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Bandwidth Control Causes Crash (BSOD)

Postby ibraheems » Oct 31 14 1:23 pm


We have been pleased with the standard version of WinGate so we purchased an Enterprise license and enabled Bandwidth Control for the Dropbox clients connecting through the proxy. To test, we set the limit to 25 KBps (200 kbps), the source IP to a Dropbox Client and the Destination IP to the WinGate Server. We ticked the "Apply to Traffic to/from the Local Machine" and the "Rule is bi-directional" option because it's a proxy connection and not a NAT.

For the 10 or so seconds that it worked, we didn't see the client exceed 25 KBps, however, after that, the server rebooted with a BSOD.

This is a 2008 R2 X64 VM on a Hyper-V Host that has been 100% stable with WinGate otherwise. Also, we are on the latest version of WinGate Proxy.

We haven't analyzed the dump files yet... Any pointers/knowledge about whats going on?

Posts: 6
Joined: Jul 04 14 7:06 am

Re: Bandwidth Control Causes Crash (BSOD)

Postby ibraheems » Nov 04 14 7:51 am

Here are the results of debugging the dump files ... They are all pretty much the same so I'll only post one. It seems to be a clear conflict with the QbikHkVistaamd64 driver...

I can't imagine that I'm the first one to install this software on a 2008R2 x64 VM :) ... Does anyone know of a workaround for this or what exactly causes the conflict?

Dump File Analysis:

* *
* Bugcheck Analysis *
* *

This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000f8c420, The address that the exception occurred at
Arg3: fffff88002770908, Exception Record Address
Arg4: fffff88002770160, Context Record Address

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

fffff880`00f8c420 488938 mov qword ptr [rax],rdi

EXCEPTION_RECORD: fffff88002770908 -- (.exr 0xfffff88002770908)
ExceptionAddress: fffff88000f8c420 (NDIS!ndisMSendCompleteNetBufferListsInternal+0x00000000000001c0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT: fffff88002770160 -- (.cxr 0xfffff88002770160)
rax=0000000000000000 rbx=fffffa80031471a0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80038368d0 rdi=fffffa80039d29e0
rip=fffff88000f8c420 rsp=fffff88002770b40 rbp=fffffa8003a07d30
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa8003618048 r12=0000000000000000 r13=fffffa80039f34d0
r14=0000000000000000 r15=fffffa80039d0960
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffff880`00f8c420 488938 mov qword ptr [rax],rdi ds:002b:00000000`00000000=????????????????
Resetting default scope




ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

WRITE_ADDRESS: 0000000000000000

fffff880`029565fa 488b5c2448 mov rbx,qword ptr [rsp+48h]


LAST_CONTROL_TRANSFER: from fffff880029565fa to fffff88000f8c420

fffff880`02770b40 fffff880`029565fa : fffffa80`00000000 fffffa80`039f34d0 fffff880`00000000 00000000`00000000 : NDIS!ndisMSendCompleteNetBufferListsInternal+0x1c0
fffff880`02770be0 fffff880`02974428 : fffffa80`03618048 fffffa80`036d4194 00000000`00000000 00000000`000005dc : QbikHkVistaamd64+0x65fa
fffff880`02770c20 fffff880`0297519b : fffffa80`03b924a0 00000000`00000000 fffffa80`042cc2c0 fffffa80`03618048 : QbikHkVistaamd64+0x24428
fffff880`02770c60 fffff880`02974647 : 00000000`00000000 fffffa80`03b924a0 00000000`00000080 fffffa80`0319c890 : QbikHkVistaamd64+0x2519b
fffff880`02770d10 fffff800`0172573a : fffffa80`03d22b50 00000000`00001000 00000000`00000000 fffff880`01065866 : QbikHkVistaamd64+0x24647
fffff880`02770d40 fffff800`0147a8e6 : fffff880`01edd180 fffffa80`03d22b50 fffff880`01ee7fc0 fffff880`01958445 : nt!PspSystemThreadStartup+0x5a
fffff880`02770d80 00000000`00000000 : fffff880`02771000 fffff880`0276b000 fffff880`02770930 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME: QbikHkVistaamd64+65fa


MODULE_NAME: QbikHkVistaamd64

IMAGE_NAME: QbikHkVistaamd64.sys


STACK_COMMAND: .cxr 0xfffff88002770160 ; kb

FAILURE_BUCKET_ID: X64_0x7E_QbikHkVistaamd64+65fa

BUCKET_ID: X64_0x7E_QbikHkVistaamd64+65fa

Posts: 6
Joined: Jul 04 14 7:06 am

Re: Bandwidth Control Causes Crash (BSOD)

Postby Aaron Koolen-Bourke » Nov 05 14 8:40 am

Hi Ibraheems. I am very sorry for the problems you are having. Could you submit a support ticket at please. We should be able to better assist you via that support channel.

Aaron Koolen-Bourke
Qbik Staff
Posts: 56
Joined: Dec 01 10 2:48 pm

Re: Bandwidth Control Causes Crash (BSOD)

Postby nasrzg » Jan 03 20 1:21 am

I'm facing the same problem
Whenever i activate bandwidth control the server crashes
Any solution?
Posts: 7
Joined: Dec 20 16 1:05 am

Return to WinGate

Who is online

Users browsing this forum: No registered users and 6 guests