[Winpcap-users] PC rebooting phenomenon in winpcap application

[Cholmin Kim]

I'm appreciate for your help~
I have installed the newest version of WinPcap, and the blue screen has not
been shown at least on several trails!
It was really helpful~

Cholmin Kim


-----Original Message-----
From: winpcap-users-bounces at winpcap.org [mailto:winpcap-users-
bounces at winpcap.org] On Behalf Of Gianluca Varenni
Sent: Wednesday, November 01, 2006 1:12 AM
To: winpcap-users at winpcap.org
Subject: Re: [Winpcap-users] PC rebooting phenomenon in winpcap application

I think you obtain that crash information using windbg and the crash dump
or 
minidump.
First of all, I suggest you to migrate to winpcap 3.1 or better winpcap 4.0 
beta2. We cannot provide any support for 3.1beta4 (which is really old).

If you still experience such crashes, please post a zipped copy of the
crash 
dump or minidump to ftp://www.winpcap.org/pub/incoming (and send me a mail 
after uploading it).

Hope it helps
GV

----- Original Message ----- 
From: "김철민" <cmkim at sysonchip.co.kr>
To: <winpcap-users at winpcap.org>
Sent: Tuesday, October 31, 2006 4:57 AM
Subject: [Winpcap-users] PC rebooting phenomenon in winpcap application


> Hello Everyone~
>
> I’m a beginner of the Winpcap and had made an application with it.
> It has been built on Visual Studio .NET 2003 on Windows XP Service pack 2.
> Its function is to capture every packet from an Ethernet device to bypass 
> it to opposite side Ethernet device and vice versa. (Like a GW function)
> Its throughput is reach to 30Mbps.
> The problem is that in every try, the application makes the PC to reboot 
> after some running (about 5 to 20 minutes)
> Here is the blue screen dump of my situation
>
> --------------------------------------------------------------------------
----------------
> DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
> An attempt was made to access a pageable (or completely invalid) address 
> at an
> interrupt request level (IRQL) that is too high.  This is usually
> caused by drivers using improper addresses.
> If kernel debugger is available get stack backtrace.
> Arguments:
> Arg1: 7c82deea, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 7c82deea, address which referenced memory
> --------------------------------------------------------------------------
----------------
>
> Some window driver guy said that it looks like a problem of winpcap
driver 
> (.sys)
> But he can not explain further because he doesn’t know about winpcap 
> well……
>
> So are there any comments?
> Any comment will be welcome ^^
>
> I’m using winpcap 3.1 beta 4
>
> Have a nice day~
>
> PS : Sorry for my terrible English…… ^^
>
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users 

_______________________________________________
Winpcap-users mailing list
Winpcap-users at winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20061101/e4ff12c9/attachment-0001.htm