Bektorkhan

Be sure to use the MFr utils software.. for overclocking etc.. If you say use ASUS GPU Tweak on an MSI card or vice versa. Maybe your friend did that... You could set the wrong data in power and clock chips!! Since they may not use the same chips!! That could manifest the symptoms you describe!! An unstable combination of Clock and Voltage settings!! If the Caps were faulty you would probably get the same result all the time!! You could measure the Voltage on PCIe connector +12 V should be > 11.5 Volts preferably > 11.9 Volts Yellow is +12 V and black is Ground

Sure, just measure it in the PCIe connector (black 3 wires closest to lock is Gnd, Yellow furthest away from the lock is +12V) , the probes should be able to feel the connectors while the connector is connected. Just push them in aside the cables, tested now and they should stay in place, diagonally GND in one corner and +12V in the oposite.. _:::`` . If you have a current probe put all black or yellow through it!!

I don't think it was... In the Asus Bios it's not quite sure what you use... tried now to force Uefi... disabling Legacy Bios and there was no bootable devices left.... Being cautious I choose Legacy Bios on accessing the Boot USB Stick .. doing so, it looks like I selected Legacy Bios .. I still have UEFI drivers first in BIOS but have no clue what it's using... Have to read up about it... we are now a long way from me 14, progamming a Space Invaders Game on a Sinclair Zx81 with diy 2kbyte RAM expansion to 3k RAM...

I don't think it would and most gpu boards don't have any way telling you I need more 12V please... posting 5 beeps would be No VGA bios error!! First dissconnect AC power !!!! Connect 12 V (Yellow) and Gnd (Black) from your old HDD power connectors, just strip the ends of four or six cables (about 1.5 mm2 / 15 AWG), to two or three HDD connectors, and push them in the holes! On the PCIe stide its male pins but it should work against the isolating walls! Gnd is on the side where the lock is! Or get a HDD to PCIe converter, ussually Two old HDD connectors to one PCIe 6-pin connector. Just look/think two or three times to see you connected it right, before connecting AC power and powering up.

@bcguru9384 Being ooold don't fancy UEFI... care to point out/link UEFI vs Bios pro cons. Might be what caused it... UEFI might be the major choice now!!? But get it: Bios API etc must have been there since 1985.. so you need to break away sometime!!

"Solved" for me: My Win 10 was an Win 7 upgrade ... Sadly my only solution was to reinstall a clean Win 10 install (W10X64.6x1.ENU.FEB2016) , by getting a MS account and there saving my License and format My Win partition!! Only had to install AMD 17.30 Chipset drivers and Nvidia Graphics drivers to get all drivers installed (Working, not latest). (ASUS Prime X370-PRO Ryzen 5 1600 Nvidia GTX1050Ti ), while always checking LatMon. Strangly after Chipset drivers installed there was still DPC > 2 ms, after Nvidia graphics drivers it was solved! Now I have +100 MByte/s copying files from my server with < 500 us DPC for some minutes. Sorry was trying to find the true cause but is to lacy or dum... so Wtf reinstallation is quicker!! Then don't fix.. what aint broken policy...

@RAM555789 You might be right..... my mistake 3200Mhz (Not 3666 ) CL16 DDR4 I almost got stable @ 1.385 Volts.. 1 -2 errors in every pass Memtest! Now they run on 3066MHz @ 1.35 Volts.

Have the same issue on my ASUS Prime X370-PRO Ryzen 5 1600 16Gb 3666MHz DDR4 on 3200MHz . My mouse studders also under network load... a good system should not!!! Was stable (memtest for 4 passes) and no DPC latency issues when built some weeks ago.. It is not overclocked right now exept mem on 3200MHz! Since NDIS is windows networking system.. LAN drivers should be the issue! Tested so far: Newest Intel E211 drivers 12.15.184.0 - Prevoius Intel E211 drivers - Latest MB Bios 0902 - PCIx RTL8168 1Gbit card disabling Intel E211 - Latest Chipset drivers 17.30 from the start..! - Will try uninstall/remove all drivers and reinstall next! ...... I have minimized the problem as much I can... tested all sorts off things, but increasing receive and transmit buffers in the Intel E211 drivers made some result, but still shit. My son's Z170 board had the same issue solved by a late BIOS update from Gigabyte! I get 320Mbit/s 0.5-5 ms lat while he has 1000Mbit/s < 0.1ms and we have the same AVG Zen Total Security same network etc! Still testing.. Tested clean boot earlier... nothing!!