• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

On board Ethernet got disabled by a bootable utilities disc

Joined
Oct 4, 2013
Messages
157 (0.04/day)
AMD 970 chipset Gigibyte MB
Win 7 Pro
Realtek on-board chipset with a 1/18 dated driver update.

It's kinda hard to describe this,, but long story short;
I was tiring newer versions to update those bootable CD's with troubleshooting programs on them for possible future use (hopefully not) eg;
Ultimate Boot CD,
Knoppix v7.2 & 8.1
EaseUS Partition Master WinPE,
All IN One Rescue Toolkit,
MiniTool Partition Wizard
for examples.
I believe it was one of the Knoppix versions that did something as they have Ethernet drivers so one can use the included browser, but that is only a guess.

Somehow, the on -board Realtek Ethernet chipset got disabled or corrupted to a point I had to connection to the Router. The 1st time, in Device manager, the network device entry wasn't even there. I managed to get thing back, I believe by powering down and/or rebooting.

The 2nd time, Device manager had the Ethernet device entry there and it showed that it was working, but no connection. Network & Sharing showed a "Unknown Network". The Router showed the port connected as did the LED's on that back of the Tower including activity. I couldn't even access the Router.

I reset defaults in the UEFI BIOS, but that didn't work. Then I did something that I haven't had to for probably 16+ years, I cleared the CMOS on the MB, then reset the BIOS again on bootup. Connectivity was restored.

So, the question is; what could of been done and how did this happen? How could a program outside of the installed O/S affect a on-board device after the program is closed? Has anyone heard of something like this happening?

Mind you, I also didn't have connectivity when I re-loaded two of those bootable discs, so this is NOT a W7 O/S issue. I have a 2nd bootable HDD (same O/S) and that was dead also.
I don't believe it was a 'virus', the iso's that I burned to the CD's came from the original source.


I hope I didn't loose anyone, if so please re-read. It had to be some 'tampering' with the on-board Ethernet chipset and the driver it temporarily loaded.
 
Last edited:

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
40,435 (6.58/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
The disk did a low level machine code command that told the device what to do in real vs safe mode.

Just learn from this to not repeat it lol.
 
Last edited:
Joined
Oct 24, 2004
Messages
1,294 (0.18/day)
How could a program outside of the installed O/S affect a on-board device after the program is closed

Unless it's designed to reprogram an eeprom by flashing it, then it couldn't. Those WinPE/LinPE lives in RAM just long enough to help fixing things and then dissapear after rebooting.

Your network card playing tricks most probably had to do with the bios itself, and you fixed it by flushing both volatile part of the bios and motherboard condensators.
 
Joined
Oct 4, 2013
Messages
157 (0.04/day)
Problem is I don't know which program cause the problem. It's not as "I" did something other than running the program.
My further guess was the 'driver' was left behind and/or when it was deleted, it left the chipset in a inactive or disabled (of sorts) state. :confused:
 
Top