Order Gigabyte Z690 AORUS ELITE with event 1014, DNS cutout.
Order Gigabyte Z690 AORUS ELITE with event 1014, DNS cutout.
CPU specifications: Intel Core i7-13700KF running at 3.4 GHz with 16 cores. GPU: Asus TUF GAMING OC V2, equipped with a GeForce RTX 3080 and 10GB LHR. Video card: Gigabyte Z690 AORUS ELITE AX ATX, LGA1700. Motherboard: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-5600 CL36. Power supply: Corsair RM750x (2021), 750W. I started assembling my PC about seven months ago. This was my first attempt at building a computer. Overall, everything went smoothly. Unfortunately, I often encounter problems with the network/DNS server not responding. In these cases, it usually happens immediately after each other, though sometimes there are hours or even days between incidents. I’ve noticed this tends to occur more frequently when the connection is under heavy load. Although I can’t recreate the exact situation, it seems to happen more often during live streaming. My previous PC didn’t have this issue, and this one was connected via the same cable. All other devices in my home use either Wi-Fi or a wired connection, and it doesn’t seem to affect them. I used to run a virtual machine with Pihole, but I removed it once the problem started after the build. After a full Windows reset, all settings returned to normal. I’ve searched for possible causes and tried several fixes. Checked drivers from both Gigabyte and Realtek. Disabled and deleted the Gigabyte Control Center program, turned off CPU offload, reinstalled Windows, adjusted network power settings, changed IPv4 routing, modified duplex settings, reset network via the Windows button, disabled IPv6, cleared DNS cache using Command Prompt, and even tried registry edits. I contacted Gigabyte for assistance, who suggested a clean install with fresh partitions and driver updates from Control Center. Solutions varied over time, sometimes taking weeks or months to resolve. I also investigated whether the issue might stem from the Realtek Gaming 2.5GbE controller, but it was resolved with a driver update (though that didn’t fix my problem). I’m still puzzled by the problem and would really appreciate any guidance in resolving it.