Wireshark-bugs: [Wireshark-bugs] [Bug 4549] Error while capturing packets: read error: PacketRec
Date: Mon, 6 Dec 2010 12:03:57 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4549

--- Comment #6 from Chris Maynard <[email protected]> 2010-12-06 12:03:49 PST ---
(In reply to comment #5)
> the router. (Cat-5, RJ45, about 150cm). A newer Packard Bell iXtreme Windows 7
> (where the failure happens) having an USB WiFi stick: Gigabyte GN-WB32L
> 802.11n
OK, well your hardware is sure to be different than the OP's, but at least we
have some information to go by.

> Problem: There are three interfaces listed, "Microsoft", "Microsoft", and
> "Realtek PCIe GBE Family Controller". How do I know the difference between the
> two "Microsoft" entries?

You can try searching for the service name,
438FF13A-C854-4688-A525-59F9F7D8CD65, in the registry to find other information
about the interfaces.

> Possibly related: I never bothered with the CD that came with the USB WiFi
> stick. Perhaps if I find that CD somewhere in the pile, the interface will get
> a distinct name, and perhaps even the error will disappear.

Possibly.

> I forgot to stop the capture, so  left Wireshark running overnight and found
> the error dialog next morning.

To me this smells of a potential memory exhaustion problem and might very well
be the root cause of the failure.  (See
http://wiki.wireshark.org/KnownBugs/OutOfMemory).  How much memory does your
Packard Bell PC have?  If you want to perform long-term capturing, then I would
highly recommend using dumpcap instead with ring buffers and max file size
settings.

> I just downloaded windump and will try it out later this evening if my better
> half allows. What else would be useful to you?

If it is a memory exhaustion problem, then you might not see it with windump
because there's no way windump will use as much memory as Wireshark does. 
Still, you can repeat the test anyway, just in case it's not a memory related
issue.  If you don't have a problem with windump, then you should repeat the
test with dumpcap.  Dumpcap won't use very much memory and can essentially run
forever.  These 2 tools, windump and dumpcap, will help rule out or confirm
memory exhaustion as the cause.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.