On board Ethernet got disabled by a bootable utilities disc

[videobruce]

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.

 

[videobruce]

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.

 

[WhitehawkEQ]

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.

That's a head scratcher and a half I would not use those disks and get new disks, something on the old disks is corrupted.
Also if the NIC was disabled in the BIOS, then something on that disk has a virus.

 

[videobruce]

As I stated, I don't think it was a 'virus', just some poor code/driver that affected the chipset on the MB, leaving it in that "unknown' state after the program was closed out. I didn't see any error while running those discs at the time, just afterwards when I discovered the problem. Elsewhere someone mentioned a "flag" being set.

The 1st time the "Network Adapters" entry was completely missing from Device Manager. The 2nd time, it was there and everything showed ok, but booting back into the UBCD (Ultimate Boot CD) which I have used before (Linux desktop), under the Network icon in the bottom bar, there was no MAC address for the Ethernet adapter (all zeros).

 

[trents]

My guess is something messed with the UEFI code.