I'm currently getting a strange issue with the on-board ethernet adapter on my older secondary system I use in the living room that I use for mainly just desktop apps.
Before upgrading to Windows 10 pro x64 yesterday I was running Windows 7 Ultimate x64 on this system and everything was working just fine, including the ethernet adapter. When I upgraded yesterday, at first all drivers downloaded and installed correctly despite some components in this system being from 2006, compliments for the great compatibility. The ethernet adapter also had a working driver and was working fine. However when I restarted the system things got weird. The BIOS booted normally, then I briefly saw the windows 10 logo and loading icon, but they looked artifacted, the screen went black and nothing booted up. Because of the artifacts I thought the GPU may have died. I turned the PC off with the power button, and turned it on again. This time the windows logo was normal and windows booted up normally with one exception, no internet connection. Turns out that the on board ethernet device was ''not connected'' according to the hidden devices in device manager, as if I unplugged it. Luckily I could still use internet as the PC also has a backup PCI wireless network card, I'd rather use wired internet anyway. So I left the PC unplugged for 1 night, when I turned it on again in the morning, the on-board ethernet adapter was working again. When I restarted, same routine, artifacted windows logo, black screen, restart, working windows but no ethernet adapter. Fixed again by unplugging the PC, and starting again.
I understand this may be a simple motherboard malfunction of some sort, the strange this is that it worked fine until I upgraded to windows 10. It's hard to believe that the ethernet adapter or motherboard decided to malfuntion at the same moment I upgraded windows, even though possible with an older system like this.
The GPU seems to be fine, even under stress, so I think the PCI-E controller can be ruled out. Also the GPU does not have any blown capacitors or anything. Also no blown capacitors on the mobo. I'm writing this post on the same PC with a working ethernet adapted for the moment. Running stable for several hours now while I've been exploring the new features, but the issue will occur again on restart.
By the way the thernet adapter is an on-board Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller.
what are your thoughts. Old PC chose to malfunction at exactly this time? Or some strange software/hardware incompatibility issue.
Thanks for your replies.
Hi there,
I have the exact same problem. Windows 10 Pro 64bit do not recognize the Marvel Gbit Ethernet controller 88E8056. Actually, installing the windows 7/8 64bit that one would expect to work with W10, gives a BSOD referring to the corresponding sys file (yk63x64.sys) that neither system restore nor startup repair can fix.
If anyone can come up with a solution, by all means please do!
I'm not sure that is exactly the same issue. However I've found the solution for my issue. Windows 10 has a funtion that is turned on by default called fast startup. Basically this function puts the PC into hibernation when you shut down the PC instead of completely shutting it down without a saved session. When I start the PC back up out of the hibernation state for some reason my ethernet adapter is not woken up correctly or th driver is not loaded correctly. I fixed this by turning off fast startup. Now windows 10 boots normally every time with all devices and drivers enabled and loaded.Hi there,
I have the exact same problem. Windows 10 Pro 64bit do not recognize the Marvel Gbit Ethernet controller 88E8056. Actually, installing the windows 7/8 64bit that one would expect to work with W10, gives a BSOD referring to the corresponding sys file (yk63x64.sys) that neither system restore nor startup repair can fix.
If anyone can come up with a solution, by all means please do!
