- Joined
- Nov 14, 2012
- Messages
- 47 (0.01/day)
- Location
- Panama City Beach, Florida, USA
System Name | Current System |
---|---|
Processor | AMD Ryzen 2700X |
Motherboard | asus rog crosshair vii hero (wi-fi ac) |
Cooling | Custom Loop |
Memory | 16 Gigs DDR4 G.Skill 4133 B die |
Video Card(s) | RX 5700 XT |
Storage | SSD M2 Sata 250, Samsung 840 250 EVO SSD, 2x 4 TB WD |
Display(s) | viotek gn32q 144Hrz Freesync, LG 29UM-69-P |
Case | Termaltake The Tower 900 |
Power Supply | EVGA 1050 GS |
Mouse | Logitech G602 |
Software | Win 10 64, 3dmark, and so on. |
Benchmark Scores | Just ask for my current benchmarks. Firestrike https://www.3dmark.com/fs/20129473 |
the problem was the killer driver for some ppl, not everyone had trouble with the software, that's what i experienced myself.
I understand...but the new drivers with or without the package no longer cause me any issues...it has been updates about a half dozen time. The issue way back was we could not get the driver without the full network manager software. My understanding was for most people the issue came with the killer suite network manger.
But anyhow the new website and offering not only new killer suite but also a stand alone driver was a finally a smart move. The new killer suite by the way runs smooth on win 10 TP. I do use both from time to time. If I need to check network usage I will install the suite...right now just running the driver. It is nice they finally gave us a choice
Though honestly I could seem to detect a difference between using the drivers from the OP and using the stand alone drivers from Killer. The one thing I could not figure out was that there is a small linux "box" with the killer e2200 built in and could not figure out how to test it and understand what that Linux kernal actually does.