X370 Fatal1ty Gaming K4 - NIC not recognized
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=4935
Printed Date: 23 Dec 2024 at 2:05am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X370 Fatal1ty Gaming K4 - NIC not recognized
Posted By: Waseh
Subject: X370 Fatal1ty Gaming K4 - NIC not recognized
Date Posted: 24 Apr 2017 at 12:56am
|
" rel="nofollow - Hey guys. So i just installed my new Ryzen system yesterday, and apart from some driver problems it went pretty smooth. However today i've been having intermittent networking problems with the ethernet adapter getting disabled by Windows 10 with the error: "Windows has stopped this device because it has reported problems. (Code 43)". I tried removing and reinstalling the drivers to no avail. At first reenabling the adapter would bring back the connection, but now the adapter is completely gone, even from the device manager. I then tried a fresh install of Windows 10 and the adapter still doesnt show up in device manager. There are no lights on when looking at the physical port when the computer is turned on, however when turned off the top light blinks orange in a repeating pattern. The light turns off immediatly after turning the PC on. Im pretty much at my witts end here! I also cleared the CMOS with no effect. Edit: also trying to install the drivers for the Intel NIC results in the installation wizard saying there are no Intel NICs installed in the system. I have a gut feeling telling me this might be a dead board but do any of you guys have any insight or something else i can do to troubleshoot this? Best regards |
Replies:
Posted By: wardog
Date Posted: 24 Apr 2017 at 5:48am
Right from the get-go I'm gonna say you're downloading the incorrect drivers, and the below quote is why:
The Fatal1ty X370 Gaming K4 you intone having in the Topic has an Intel NIC, and just an Intel NIC. http://www.asrock.com/MB/AMD/Fatal1ty%20X370%20Gaming%20K4/index.asp Please use the drivers and BIOSes from the above page ONLY. |
Waseh wrote:Posted By: Waseh
Date Posted: 24 Apr 2017 at 6:52am
|
Thanks for the reply. The problem is that that's excatly the driver I downloaded. Then I tried one from Intels website with the same result before trying the ASRock provided one yet again. Edit: oh wait I see I might have been unclear - when I wrote "drivers" plural that was just a mistake. It is the single driver file from ASRock (well zip) |
Posted By: wardog
Date Posted: 24 Apr 2017 at 6:22pm
|
" rel="nofollow - Ah, ok. Clear now. Have you installed the AMD All In One also? |
Posted By: Waseh
Date Posted: 24 Apr 2017 at 7:30pm
|
Yea. Just tried again with the AMD all in one with no change. It's the fact that the NIC worked out of the box when I first installed Windows 10 (with no drivers installed manually) that irks me the most. Now a fresh install of Windows doesn't even recognized that there's even a NIC present. Also I tried to use the UEFI internet bios update tool to see if that got a connection but that also errors out. |
Posted By: wardog
Date Posted: 25 Apr 2017 at 1:04am
|
" rel="nofollow - Hmmm ..... What PSU are you using? All 8-pins are connected at the ATX power socket? Check that the dammnits on the back of the I/O plate aren't inside the NIC port. You're ok doing a fresh 10 install? With the Ethernet disconnected, do a fresh OS install, then immediately after install the AMD all in one, then the NIC driver and post back please. I'm wondering if MS WU isn't sneaking in a NIC driver behind our backs. Also, assuming the above works, do you know how to disable WU from updating hardware drivers? Stop Windows Update from installing device drivers Control Panel > System and Security > System > Advanced system settings > Hardware tab > Device Installation Settings > No, let me choose what to do > and then check Never install driver software from Windows Update > then click on Save Changes |
Posted By: grenrozo
Date Posted: 25 Apr 2017 at 1:15am
| " rel="nofollow - is it working from UEFI? |
Posted By: Waseh
Date Posted: 25 Apr 2017 at 4:03am
|
It is not working from UEFI I think I'll try to take the motherboard out of the case and see if that makes a difference. A Corsair RM650X. The 8 pin is connected, I checked and reseated everything. Yea I think I'm on my 7th Windows 10 reinstall so I might as well try another one! I'll try it without the Ethernet connected. |
Posted By: Waseh
Date Posted: 25 Apr 2017 at 5:03am
|
" rel="nofollow - Alright so I just tried to boot into the UEFI as the NIC showed up briefly in Windows (i haven't reinstalled or done anything yet) and was able to use the internet flash tool to connect and show me an available update. I left the computer running to see if I would see the same behavior as I do in windows with the NIC crapping out after 5 minutes, and I see the exact same thing in UEFI. After about 5 minutes the NIC stopped working and wouldn't connect to the server. I also tried switching the Ethernet cable and trying a different port on my switch. This rules out a driver problem right? I suppose the next step is to see if the case is creating some sort of short. |
Posted By: parsec
Date Posted: 25 Apr 2017 at 10:02am
|
" rel="nofollow - Very weird issue, I've never seen that happen with any NIC chips. I highly doubt it is a driver problem. My X370 Killer SLI/ac board uses the same Intel I211AT NIC chip, and it works fine with the ASRock supplied 21.1 version, or Intel's latest 22.1. I imagine if you had a continuous short of some kind affecting that chip, it would not work at all, instead of after five minutes. As wardog said (I think...) check the IO panel cover for those tiny tabs that touch the surface of the various connectors on the IO panel. I don't use the IO panel cover at all, it's mainly for cosmetic purposes. Checking for shorts is worth doing, but I would not dismiss the need to replace the board, sorry to say. Did you try using a different network cable? ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: Waseh
Date Posted: 25 Apr 2017 at 9:52pm
|
Yea i tried a different Ethernet cable as well. I just removed the motherboard from the case and installed all the hardware again. Same result. The first five minutes or so from a cold boot without any power to the motherboard at all the NIC works in UEFI and is able to connect to ASRocks servers for bios updates. Five minutes later both lights next to the Ethernet port on the motherboard goes dark and I am unable to connect to the bios update server. The Ethernet cable does give a connection when used on my laptop. I think I'm ready to call it a dead NIC/board |
Posted By: Waseh
Date Posted: 25 Apr 2017 at 10:15pm
Just to rule out all the last things I hadn't checked I tried another stick of DDR4 ram, no effect. Then another known good psu with no effect either. I will be sending back the board it seems 
|
Posted By: parsec
Date Posted: 25 Apr 2017 at 10:58pm
|
It sounds like the NIC chip or something related to it is failing. You probably tried this, but when the NIC seems to go off, meaning you lose connection and its LEDs no longer are on, if you unplug the network cable and then connect it again, does the NIC chip wake up? You seem confident that your router is working fine, so it must be a bad board, sorry to say. I've never had an Intel NIC chip go bad, but if things seem to break early in the life of a board, it's the board.  ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Waseh
Date Posted: 25 Apr 2017 at 11:30pm
|
When the lights on the NIC goes out removing and reinserting the cable does not wake back up the NIC. Once it goes down it pretty much stays down. I just reassembled my old rig which works fine on the same Ethernet cable connected to the same port on the same switch with no issues ;) Yea I'm pretty surprised by the bad Intel NIC as well. I've had my share of troublesome Realtek NICs so it's one of the reasons I went with a X370 board (only ones that seem to have Intel NICs) but it didn't save me this time it seems ;) |
Posted By: jorko80
Date Posted: 07 May 2017 at 3:46pm
|
" rel="nofollow - Hello, I'm having the exact same problem. I've tried many things, but the problem persists. It works for about 10mins and then comes code 43. Can you tell me what type of CPU-cooler did you used ? |
Posted By: Thundernerd
Date Posted: 09 May 2017 at 6:10am
| Very similar problem here, I had another thread about it. For the first couple weeks device manager couldn't even find the NIC. I bought a standalone PCIe network card, and after a week of running on that I decided to try the on-board again. This time it showed up in device manager. Will have to monitor it for stability now, but not a good way to start out. |
Posted By: realist
Date Posted: 15 May 2017 at 7:26am
| " rel="nofollow - I also have this problem. Seems like an issue from the production line? I bought this from April. |