Page MenuHomeFeedback Tracker

LSP on network card causing "No message recieved...", with workaround
Closed, ResolvedPublic

Description

I have been getting the message "No message recieved..." after anywhere between 2-20 minutes when playing. I then had to revert to the main screen, refresh the server list, and log back in. If I waited the full 90 seconds, the game freezes and crashes. This process repeats itself after different lengths of playtime, most often at about ten minutes. I know that the server didn't go down as others kept on playing. I have found no packet losses, though I'm not an expert on that.

My issue hasn't been fixed by any game update either, as I religously tried updates on both experimental and stable cause I really wanted to play.
I reproduced the issue just before this workaround. After doing what is described below I have been able to confirm that every time I've gotten the "No message recieved..." was due to server restart. This was not in conjunction with a game update.

I have a Gigabyte Sniper 2 motherboard with the Bigfoot Network Killer networking controller. The bundled software for the motherboard seem to do some kind of "optimization". I use a cabled connection to a router.

This issue was resolved for me during the last couple of weeks by unmapping LSP on the bundled software for that chip. Maybe more motherboards run this kind of functionality?

Here's my process for a workaround on win 8.1:

Open a command prompt, go to:
"\Program Files\Bigfoot Networks\Killer Network Manager\"
-Type killertool -lsp -unmap

Flush DNS using:
-Type ipconfig /flushdns and press Enter.
-Type ipconfig /registerdns and press Enter
-Type ipconfig /release and press Enter.
-Type ipconfig /renew and press Enter.
-Type netsh winsock reset and press Enter.

Reboot the computer.

Now I get two warnings each time I log into windows by Bigfoot Networks that says:
"LSP wasn't correctly mapped. Do you want to remap LSP?" (translated from swedish)
I click "No" on both of those, thereby not remapping the LSP again.

Now I have what appears to be crippled or maybe unsecure functionality in my networking solution but I can play DayZ without losing connection. I'm not sure to the day, but have been doing fine the last couple of weeks after months with the same problem.

I'm not sure if this constitutes a closed ticket, but at least the workaround is properly stated.

My reddit post:
http://www.reddit.com/r/dayz/comments/2e0hfm/anyone_else_getting_no_message_recieved_at/clai63e

I will attempt to remap LSP again and reproduce for a crash report as soon as I am able.

Details

Legacy ID
2327137782
Severity
None
Resolution
No Bug
Reproducibility
N/A
Category
Multiplayer
Steps To Reproduce

Launch a game.
Play on server for up to 20 minutes.
Get message "No message recieved for xx seconds."
Go back to main screen and then refresh server list or wait 90 seconds for game to freeze and crash.

Additional Information

This ticket is similar to my ticket 0021174 on the Arma 3 issue reporter.

Windows 8.1
Motherboard Gigabyte Sniper 2 1.0 with Bigfoot Networks Killer Ehternet Controller 6.0.0.24, software version 1.1.0.179

Intel i7-3770K
NVIDIA GTX 670
Router ASUS RT-AC56U wired connection
ISP: Bahnhof Sweden 100/100Mbit fibre

Same error, reproduced and fixed in the same manner for Arma 3, DayZ standalone (and similarly Battlefield 4).

Event Timeline

woofer88 edited Steps To Reproduce. (Show Details)Oct 16 2014, 1:10 AM
woofer88 edited Additional Information. (Show Details)
woofer88 set Category to Multiplayer.
woofer88 set Reproducibility to N/A.
woofer88 set Severity to None.
woofer88 set Resolution to No Bug.
woofer88 set Legacy ID to 2327137782.May 8 2016, 8:19 PM

As suggested on the Arma 3 tracker, this issue has been submitted to Qualcomm Atheros as well.

Hi woofer88,

Thanks for contacting us regarding your workaround. Unfortunately, since "Bigfoot Network Killer" is a third party software for which the game is not designed around, I wouldn't consider this a bug. However, we do appreciate that you have put in the effort of investigating the workaround as well as posting it for other users that might have similar issues :)

Regards,
JStewart