AsRock Taichi x99 - Bad/Corrupt LAN Drivers/Mobo
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=5025
Printed Date: 25 Jul 2025 at 11:38pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: AsRock Taichi x99 - Bad/Corrupt LAN Drivers/Mobo
Posted By: SoberDwarf
Subject: AsRock Taichi x99 - Bad/Corrupt LAN Drivers/Mobo
Date Posted: 02 May 2017 at 3:06pm
So, the long story short (TL;DR): Something is going on with the LAN, either the Motherboard itself or the Drivers, that is causing Windows 7 to freeze during the splash screen.
Slightly longer story: I've been having a computer issue for about a month now, where Windows 7 was constantly freezing on the splash screen. After having done a lot of troubleshooting in the past month, having tested every other possible option (including multiple fresh installs of Windows 7, replacing the Power Supply and purchasing a new SSD boot drive), the issue is undoubtedly with the motherboard itself. I was unable to make a solid connection until just recently though, when after I thought I fixed the problem, it occurred again.
Having started going through every step again, I noticed in the Device Manager was had several devices that were functioning before the issue started occurring, notably the LAN Drivers.
http://imgur.com/1huLXDb" rel="nofollow">
I remember this exact same thing happening the first time I was having the issue, and it seems to make the connection with all the troubleshooting steps I have taken. Reinstalling the drivers seems to fix the problem temporarily, but the problem always seems to return, making me think that either the Motherboard LAN component is faulty, or the drivers themselves are prone to corrupting during boot.
Any suggestions to fix this, or even disable the LAN completely and having a stable boot, would be amazing.
For added reference, the long story will be in the second post.
|
Replies:
Posted By: SoberDwarf
Date Posted: 02 May 2017 at 3:10pm
" rel="nofollow - The Long Story:
I would really appreciate some help with an issue I have with my
work/gaming computer that I have been having for about the past month. I
have tried basically everything I could to fix the issue and I keep
running into issues. (see steps taken below) This computer is how I make my living so getting this solved is the most important thing right now.
COMPUTER SPECS
OS: Windows 7 Ultimate SP1
CPU: i7 6800k
GPU: MSI 1070 Gaming X 8G
RAM: 48Gb G.Skill (3x16)
MoBo: ASrock X99 Taichi
Boot Drive (C:/): PNY SSD 120GB (formally a Corsair SSD 120GB)
Secondary HDD (D:/): Toshiba 2TB
PSU: Corsair RM850x (Formally a Rosewill Semi-Modular 650w)
-COMPUTER ISSUE-
Windows will freeze on the Windows 7 start screen (the splash screen
where the four colored orbs form into the windows logo). Exactly where
it freezes is variable, sometimes it will freeze before the orbs appear,
sometimes it will freeze at one red orb, sometimes it will freeze as
the orbs come together. It has usually always studdered (as the Keyboard
& Mouse will flicker on), but now it's just a hard freeze.
Computer will not boot into Safe Mode (it freezes as ClassPNP.sys), but will boot with Last Known Good Configuration, but will just freeze with the next boot.
-STEPS TAKEN- (Result of rebooting normally (not using LKGC) in bold)
Scanned for Viruses using BitDefender, Ran Malware Bytes, Spybot S&D and other tools. Found 1 false flag. DID NOT BOOT. Ran SFC and DSKCHK. DID NOT BOOT. Tried the Windows Repair option from a USB Boot. Would freeze
at the same splash screen as if booting from the boot drive (which made
me think it was not an issue with the drive), eventually got it to run the repair. Said it found an issue, resolved issue, but DID NOT BOOT. Ran all Windows Updates and Updated All Drivers (noticing an
error with a LAN driver). Booted once normally but after entering the
desktop, programs loaded incredibly slow (about 2-3 minutes per
program.) Rebooted to frozen splash screen. DID NOT BOOT Formatted SDD and reinstalled Windows 7. Froze on first boot, and
no longer had the option to boot from Last Known Good Configuration. DID NOT BOOT (and made the issue worse, since I could no longer boot from LKGC) Reset the CMOS, Reseated all components (RAM, GPU, Drive Cables). FIXED PROBLEM FOR 4-6 BOOTS
Worked for about as long as it took to reinstall drivers, updates and
other programs, then froze on boot. Still had no Last Known Good
Configuration option at this point. Reseated everything, including the CMOS again. DID NOT BOOT. Tested one stick of memory at a time. DID NOT BOOT REGARDLESS OF RAM SETUP. Unplugged the Secondary HDD and booted with only the SDD Boot disk. BOOTED SUCCESSFULLY 10 OR SO TIMES,
then froze once, unplugging external components (microphone, webcam,
controller, etc) Booted successfully a couple of more times, would
freeze on boot occasionally. Figuring it might have been a failing power supply issue (maybe
USB devices/HDD were drawing too much power?) ordered new PSU (the
Corsair RM850x). STILL GETTING INTERMITTENT FREEZES (About 1 out of every 4 boots.) Also SLOW BOOTS AFTER LAUNCHING DESKTOP HAPPENED MORE OFTEN. Figuring it might have been the SSD itself, removed SSD,
reinstalled secondary drive, formatted secondary drive and installed
Windows 7. BOOTED SUCCESSFULLY ON ALL ATTEMPTS (15+ or so). Bought and installed new SSD for boot drive, Installed Windows 7, ran all updates and updated all drivers to current. BOOTED SUCCESSFULLY ON EVERY ATTEMPT FOR ABOUT 4 WEEKS (Over 50+ boots). Today, I went to turn it on and it froze again at the windows 7 splash screen. WOULD BOOT FROM LAST KNOWN GOOD CONFIGURATION but would not boot normally. Almost exact same symptoms as when this issue started a month ago.
- Checked the file devices again, noticing that I had Wireless LAN but my ethernet ports were not showing up. Noticed that the drivers were giving me a Code 31. "This device is not working properly because
Windows cannot load the drivers required for this device." I can confirm
they were working just fine before the error, and if my memory serves
correctly, this was the same error that was occurring in step 4.
I'm not sure if that is the cause or just a symptom of a bigger problem, but it seems that the motherboard, especially the LAN components, seem to be a common link in all this.
|
Posted By: wardog
Date Posted: 02 May 2017 at 6:52pm
Try disabling the hardwired or wi-fi from the BIOS if possible, if not in Dev Mgr, reboot and retry.
Also, if you can, disabling wi-fi on it would be the better choice, just until you can answer if disabling it gets you over this hump.
|
Posted By: wardog
Date Posted: 02 May 2017 at 6:56pm
" rel="nofollow - Odd. What I211AT driver are you using and where did you get it?
There's no AT at the end of its enumeration shown in that Dev Mgr pic.
Link to the newest I211AT drivers at Intel: https://downloadcenter.intel.com/product/64404/Intel-Ethernet-Controller-I211-AT
|
Posted By: SoberDwarf
Date Posted: 03 May 2017 at 4:47am
Thanks for the response.
I was using the drivers supplied by the AsRock Taichi x99 page: ( http://www.asrock.com/mb/intel/X99%20Taichi/#Support" rel="nofollow - http://www.asrock.com/mb/intel/X99%20Taichi/#Support )
I managed to get it working again last night by going into RedEdit, removing the drivers manually and reinstalling the drivers using the Intel drivers. I'm only about 4 boots in, but so far, so good. If it breaks again, I'll disable the Ethernet from BIOS and see if it will allow me to boot.
Though, even after updating the drivers using the link, it still doesn't register as a 1211AT. It's still 1211.
|
Posted By: wardog
Date Posted: 03 May 2017 at 5:58am
SoberDwarf wrote:
Though, even after updating the drivers using the link, it still doesn't register as a 1211AT. It's still 1211.
|
I just Googled some I211-AT's in Dev Manager and I'm incorrect. It does show up as I211, not I211-AT.
|
Posted By: SoberDwarf
Date Posted: 04 May 2017 at 4:07am
Turns out it wasn't the issue; It froze at the splash screen again this morning. Was probably just another symptom. I'm still almost positive that it has something to do with the motherboard at this point but I can't confirm the exact issue causing it.
|
|