Asus a8n sli prem. I need help getting a system device back, please.

Associate
Joined
28 Jun 2005
Posts
2,174
Location
Behind you
Hi

This all started when I installed Alcohol 120. During the install I got a BSOD while it was installing its drivers. After the PC rebooted I took of Alcohol and the 2 driver files it installed (cantremeber the names except that both started with V, 1 ended with B and the other with S). Anyway, all seemed fine but I noticed that "Plug and play bios extensions" had a yellow mark and the error was that no driver is loaded for it. I tried letting Win XP find a driver but it didn't, I then removed the device from device manager and it went, then I tried going on a hardware scan but windows wont detect "Plug and play bios extensions" anymore:( Is this important and how can I get it back? Asus update wont load since becase it cant detect the motherboard anymore. Please help get my extensions back.
Thanks
 
I just checked in system information and windows doesn't know the mobo is an Asus, nor does it know the model. It used to know both.
 
Last edited:
Are there any Unknown Devices listed in Device Manager?

When you tried to re-install the drivers did you completely remove the old ones?

Have you tried the "Reset Configuration Data" option in BIOS or to disable, boot, and re-enable the plug and play options in BIOS (forcing windows to redetect them)?

Perhaps try to roll back to a previous System Restore point?
 
I have no unknown devices. Can someone with the same mobo please check if they have "plug and play bios extensions" in system devices. I'm thinking that Alcohol may of put it in and that I never had it in the first place.
 
I have a diff mobo but do have Alcohol installed, and I have plug and play bios extensions in my system devices.

The driver says Genric.
 
Thanks guys, it was my Copperhead mouse driver. I uninstalled the mouse software and tried installing Alcohol and it worked, go figure? Oh, and Alcohol does add the "Plug and play bios extension" device.
 
Just for future reference if anything similar happens you always have the option of using system restore which would save an awful lot of headscratching.
 
Back
Top Bottom