If there were factory deffect(s), it would have shown immediately after bench marking it with Win10 Pro. There was a noticeable white trace on the monitor after a few weeks, but it was promptly replaced by the distributor.
Yes, I have moved it. The POST reveals I have 32GB of DDR4 RAM that is used by Win10. My game loads are tremendously boosted by the amount of RAM I have provided. It also reduces the stress on the hard drives by allowing them to load frequently used data, less frequently.
It’s the same explanation as to why all our other games works perfectly fine, except for Dirty Bomb. The game used to work properly prior to SS III, and after that, SHTF.
[quote=“joyousBowl;c-221958”]You can use Windows 7 64 bit 30 days before you have to activate it with product key. If you have old product key somewhere, you can download it from here:
https://www.microsoft.com/en-us/software-download/windows7
[/quote]I don’t have any Win 7 Pro 64 product key. Care to PM me an authentic one?
Listen, we’ve gone through the hardware, and firmware. Neither of them are at fault. If you have read the threads, changing any of hardware (eg, replace RX480 with GTX 1080), you cannot guarantee that it will go away instantly. What we have narrowed it down to is the netcode of ShooterGame-Win32-Shipping.exe, netcode of ASUS Lan Driver (highly unlikely because other games work perfectly fine), or netcode of the OS(again, highly unlikely because other games work perfectly fine).
Here’s another picture for you to find explanation:
http://i.imgur.com/v29poVk.png
The DPC stacks went in as high as 12 in this picture, and as soon as D9D has exited the game, it vanishes to 0. Notice the cliff of how CPU0 has high processing state going down? What about the rest of the CPUs? In use is a 4 core 8 thread non-overclocked, and perfectly stable desktop game PC. Now, convince me that it’s not ShooterGame-Win32-Shipping.exe that is causing it.