K1/m1 4.1.0.144

[fac51]

Well all my problems are solved, took the card out and stuck it on eBay (which I do feel guilty about). Fast, stable net connection now achieved, no more random BSOD from the driver and my Steam servers show just fine.

Good product Bigfoot but god awful driver support - shafting the people who got you going whilst concentrating on your new cards isn't the best way to retain business.

[malic3]

When I am on Teamspeak 3 and switch between modes, I get disconnected from TS3. Can someone confirmed?

[Marz_22]

There seems to be a new issue/bug with Teamspeak 3, which keeps crashing (TS3) when ever I have KillerNIC M1 set to Application mode.

[Futurama]

The same Problems with the K1

[newittc21]

Do we know if they are currently looking into this issuse? i cant use my killer nic card on game mode if I want to use flight simulator 2004 and teamspeak 3!

please please please can you investigate!!!

[chaosquall]

flight simulator 2004 is it even online? i dont see why the killer would effect it.

[Arrakiv]

Yeah, I'm a little confused on that as well...

Although wikipedia seems to suggest it does, in fact, have multiplayer.

[SeLeX]

Greetings all; I've been away, but lurking for some months.
In that time, I have since purchased and installed Win 7 64bit; a nice transition from XP.
In doing so, I decided to re-insert and re-install my Killer NIC M1 using the 4.1.0.144 drivers for Win 7 64bit !!
The reasons I removed this card were due to issues mentioned; [Here], and
[Here].

After installing the card and it's drivers, I saved the diagnostics first thing upon reboot;

LLR-64 (Version=4.1.0.37) Configuration request

 KillerNIC M1 LLR Mode is currently set to GAME Mode
  LLR Version Number      = 4.1.0.14
  Proxy Version Number    = 4.1.0.15
  Firmware Version Number = 4.1.0.10
  Card SubSystemID        = 0x101 (indicates a M1)
  Number of Raw NIC SGLs  = 1 
  Number of LLR SGLs      = 1 
  Current LLR Ping Control= 0 
  Current LED CONTROL     = Blinking
  LLR Game Priority       = Boosted 
    Boot Partition        = Side B 
    Boot Status Value     = 0 
    Boot Running Status   = KillerNic Boot Successful 
    Boot Strap Version    = 0x000003e8 
  KillerNIC Secondary IP Address=192.168.254.2 Mask=255.255.0.0
  KillerNIC Tx Poll Timer Setting = 1000us 
  KillerNIC Rx Poll Timer Setting = 1000us 
  KillerNIC Firmware IP_TABLES is NOT Loaded
  KillerNIC M1 FNA support= Enabled 

  LinkSpeed = 100Mps Mode=Full Duplex 

<==SetUdpConfig


Winsock 32-bit Catalog:
=======================
1013 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1014 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1015 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1016 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1011 - MSAFD RfComm [Bluetooth]
1012 - BfLLR


Winsock 64-bit Catalog:
=======================
1013 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1014 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1015 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1016 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1011 - MSAFD RfComm [Bluetooth]
1012 - BfLLR
 
 
 
Killer Suite Version: 4.1.0.144

Tested this playing, Unreal Tournament, and like before, this was how all the servers would ping when in Game Mode



Incidentally, I get the same results when I put my PC in DMZ !! My installation of Win 7 was a clean one, and the installation of this card and drivers was a first attempt on this O/S. Tried flashing the card, only to end up with the same results.

After this failure, I decided to disable the portmanager service. I found with XP this gave mixed results.
Upon doing so; powering my PC off and on, it yielded these results...in Game Mode:

LLR-64 (Version=4.1.0.37) Configuration request

 KillerNIC M1 LLR Mode is currently set to GAME Mode
  LLR Version Number      = 4.1.0.14
  Proxy Version Number    = 4.1.0.15
  Firmware Version Number = 4.1.0.10
  Card SubSystemID        = 0x101 (indicates a M1)
  Number of Raw NIC SGLs  = 1 
  Number of LLR SGLs      = 1 
  Current LLR Ping Control= 0 
  Current LED CONTROL     = Blinking
  LLR Game Priority       = Boosted 
    Boot Partition        = Side A 
    Boot Status Value     = 0 
    Boot Running Status   = KillerNic Boot Successful 
    Boot Strap Version    = 0x000003e8 
  KillerNIC Secondary IP Address Has not been Set!
  KillerNIC Tx Poll Timer Setting = 1000us 
  KillerNIC Rx Poll Timer Setting = 1000us 
  KillerNIC Firmware IP_TABLES is NOT Loaded
  KillerNIC M1 FNA support= Enabled 

  LinkSpeed = 100Mps Mode=Full Duplex 

<==SetUdpConfig


Winsock 32-bit Catalog:
=======================
1013 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1014 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1015 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1016 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1011 - MSAFD RfComm [Bluetooth]
1012 - BfLLR


Winsock 64-bit Catalog:
=======================
1013 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1014 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1015 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1016 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1011 - MSAFD RfComm [Bluetooth]
1012 - BfLLR
 
 
 
Killer Suite Version: 4.1.0.144

Pinging in Unreal Tournament...



Under these conditions, I am able to join these servers, and when checking pings from within, they turn out to be relatively normal...eg: 30 - 70 server depending.
When playing the game, it does seem as if Game Mode is working as it should, in that I'm able to frag more and achieve higher accuracy. It's a very subtle thing, but noticeable.
I am confused as to why the server pings are so elevated. When left, it gradually drops from a random figure in the 900s to 30s-40s, then shoots back up to the 900s and climbs down again. So far I've only noticed this phenomenon when using UT's own server browser.
When using XFire to ping UT servers, they show up as they should.
When I switch to App Mode, the pings show as normal...in the 30 - 70 range randomly throughout the servers.

To make sure, I manually started the portmanager service, but did not power my PC off. Instead I disabled and enabled the Killer NIC, then checked its diagnostics:

LLR-64 (Version=4.1.0.37) Configuration request

 KillerNIC M1 LLR Mode is currently set to GAME Mode
  LLR Version Number      = 4.1.0.14
  Proxy Version Number    = 4.1.0.15
  Firmware Version Number = 4.1.0.10
  Card SubSystemID        = 0x101 (indicates a M1)
  Number of Raw NIC SGLs  = 1 
  Number of LLR SGLs      = 1 
  Current LLR Ping Control= 0 
  Current LED CONTROL     = Blinking
  LLR Game Priority       = Boosted 
    Boot Partition        = Side A 
    Boot Status Value     = 0 
    Boot Running Status   = KillerNic Boot Successful 
    Boot Strap Version    = 0x000003e8 
  KillerNIC Secondary IP Address=172.31.254.2 Mask=255.255.255.0
  KillerNIC Tx Poll Timer Setting = 1000us 
  KillerNIC Rx Poll Timer Setting = 1000us 
  KillerNIC Firmware IP_TABLES is NOT Loaded
  KillerNIC M1 FNA support= Enabled 

  LinkSpeed = 100Mps Mode=Full Duplex 

<==SetUdpConfig


Winsock 32-bit Catalog:
=======================
1013 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1014 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1015 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1016 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1011 - MSAFD RfComm [Bluetooth]
1012 - BfLLR


Winsock 64-bit Catalog:
=======================
1013 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1014 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1015 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1016 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1011 - MSAFD RfComm [Bluetooth]
1012 - BfLLR
 
 
 
Killer Suite Version: 4.1.0.144

One thing I noticed was that the, Killer NIC Secondary IP Address was different. This was an issue I had raised before, but was never offered a solution other than to replace my card.
Under these circumstances, the card yielded similar results to when portmanager was disabled. More to the point, I recall the 172.x.x.x IP in the diagnostics of the first Killer NIC I bought, when it actually worked out the box.
However, when I power my PC off and on, the IP reverts back to the 192.x.x.x.

As things stand, I am currently using my Killer NIC M1 with portmanager; firewall, and bandwidth control all disabled. It does seem to work for me this way; no doubt I should test out other online FPS games.
I'm hoping it's not a fluke and that Game Mode is continuing to offload UDP packets under these conditions.

----------------------------- Update ---------------------------------

Turned on my PC this morning, and my Killer NIC refused to boot. Again; something I have encountered numerous times before, so I decided to reset.
The card booted as normal afterwards, but reverted back to blocking game servers within UT and XFire. The diagnostics were the same as the last one I posted; portmanager disabled, as well as Killer Firewall and Bandwidth Control.
Powered off my PC for a few minutes, then tried again...same result of null pings.
As the Killer NIC is essentially a mini PC, for whatever reasons, it had issues booting and hence powered down. I am assuming it then reverted to a default set-up irrespective of the Killer Config, which was why it reverted back to 'old ways'.
To regain control, I decided to re enable portmanager; power my PC off and on, and check diagnostics for the familiar 192.x.x.x secondary IP signature.
Finally, I stopped and disabled portmanager; powered my PC off and on again, and checked UT and XFire servers. Fortunately this worked, and I've been able to continue using my M1.