cannot install drivers after overclocking PC

[Beladi Nasralla]

Gee, I got a problem with my homebuilt PC. This happened after I
overclocked the comp, and it rebooted by itself a few times because I
pushed it too far. (I put the FSB back since then.)

The menus in the "Display Properties" changed. Their number decreased,
and they reverted to the standard Windows amount and look. Anyway, I
went to "Device Manager", and then to "Computer". It says: "ACPI
Multiprocessor PC". I do not remember if this should be. I think the
driver should have the name of my MSI motherboard instead of this
generic one. I thought maybe I should have re-installed the driver. So
that I installed again the "system driver" and the "AMD driver".
Nothing changed :-( Also, I noticed that in "Device Manager -->
System Devices --> Motherboard resources", the Motherboard resources
is a generic driver. I am not sure if that should be generic and not
the MSI one.

I reinstalled Windows, and did a clean install of all of the drivers.
The situation is still the same. Maybe I screwed the BIOS ? Can you
please tell me what is going on ? And, firstly, shold the "ACPI
Multiprocessor PC" be there as a generic driver ?

Thanks.

 

[Beladi Nasralla]

Gee, I got a problem with my homebuilt PC. This happened after I
overclocked the comp, and it rebooted by itself a few times because I
pushed it too far. (I put the FSB back since then.)

The menus in the "Display Properties" changed. Their number decreased,
and they reverted to the standard Windows amount and look. Anyway, I
went to "Device Manager", and then to "Computer". It says: "ACPI
Multiprocessor PC". I do not remember if this should be. I think the
driver should have the name of my MSI motherboard instead of this
generic one. I thought maybe I should have re-installed the driver. So
that I installed again the "system driver" and the "AMD driver".
Nothing changed :-( Also, I noticed that in "Device Manager -->
System Devices --> Motherboard resources", the Motherboard resources
is a generic driver. I am not sure if that should be generic and not
the MSI one.

I reinstalled Windows, and did a clean install of all of the drivers.
The situation is still the same. Maybe I screwed the BIOS ? Can you
please tell me what is going on ? And, firstly, shold the "ACPI
Multiprocessor PC" be there as a generic driver ?

Here is more clue. My PC seems to work OK. It is just that the
motherboard does not show up on the Device Manager. This means to me
that the motherboard is running on the generic Windows driver, and
thus is not optimised for a speed. The CPU-Z shows up the name of the
motherboard.

 

[Frank McCoy]

Here is more clue. My PC seems to work OK. It is just that the
motherboard does not show up on the Device Manager. This means to me
that the motherboard is running on the generic Windows driver, and
thus is not optimised for a speed. The CPU-Z shows up the name of the
motherboard.

Sounds to me like your BIOS chip might have been damaged.
(That happened to me with one overclocking attempt.)
You probably need to flash it again.
You're lucky it didn't get destroyed totally.
You need at least a partially working BIOS to flash a BIOS.
(Catch-22)

 

[Sleepy]

Gee, I got a problem with my homebuilt PC. This happened after I
overclocked the comp, and it rebooted by itself a few times because I
pushed it too far. (I put the FSB back since then.)

The menus in the "Display Properties" changed. Their number decreased,
and they reverted to the standard Windows amount and look. Anyway, I
went to "Device Manager", and then to "Computer". It says: "ACPI
Multiprocessor PC". I do not remember if this should be. I think the
driver should have the name of my MSI motherboard instead of this
generic one. I thought maybe I should have re-installed the driver. So
that I installed again the "system driver" and the "AMD driver".
Nothing changed :-( Also, I noticed that in "Device Manager -->
System Devices --> Motherboard resources", the Motherboard resources
is a generic driver. I am not sure if that should be generic and not
the MSI one.

I reinstalled Windows, and did a clean install of all of the drivers.
The situation is still the same. Maybe I screwed the BIOS ? Can you
please tell me what is going on ? And, firstly, shold the "ACPI
Multiprocessor PC" be there as a generic driver ?

Thanks.

ACPI Multiprocessor PC is correct if you have a dual core CPU like a AMD X2
(which I have ) and I assume its the same for Core 2s. Your motherboard does
not show up in the Device Manager. Stuff like a specific IDE controller or
PCI to AGP driver maybe but you wont see a mention of the Motherboard make
and model.

 

[Beladi Nasralla]

ACPI Multiprocessor PC is correct if you have a dual core CPU like a AMD X2
(which I have ) and I assume its the same for Core 2s. Your motherboard does
not show up in the Device Manager. Stuff like a specific IDE controller or
PCI to AGP driver maybe but you wont see a mention of the Motherboard make
and model.-

OK, I did more digging around. When I installed DigiCell, it
complained: "Failed to load driver". DigiCell (a motherboard utility)
used to work before. I could not load the Dual Core Centre could not
load either. The situation is like described by the guy

http://www.tek-tips.com/viewthread.cfm?qid=1067265&page=1

He thinks that the motherboard does not load utilities/drivers.
Perhaps this is a corrapted BIOS or motherboard. I am yet to find out
how to "flash the BIOS".

 

[Sleepy]

OK, I did more digging around. When I installed DigiCell, it
complained: "Failed to load driver". DigiCell (a motherboard utility)
used to work before. I could not load the Dual Core Centre could not
load either. The situation is like described by the guy

http://www.tek-tips.com/viewthread.cfm?qid=1067265&page=1

He thinks that the motherboard does not load utilities/drivers.
Perhaps this is a corrapted BIOS or motherboard. I am yet to find out
how to "flash the BIOS".

Ive never heard a bios becoming corrupted in the way you describe and bios
updates are for adding new features like new CPU support etc ... I'd
strongly advise against flashing the bios. If Windows reboots repeatedly it
can easily get messed up and even get to the point where it wont boot at
all. Formatting the drive and installing Windows afresh will sort it but
doing a repair installation - maybe not. It would help to reset the bios by
disconnecting power and pulling the CMOS battery out for a minute. Then boot
up and put all bios settings to defaults. Go into Windows and reinstall
drivers beginning with Mobo drivers then graphics and sound etc....

 

[Beladi Nasralla]

Ive never heard a bios becoming corrupted in the way you describe and bios
updates are for adding new features like new CPU support etc ... I'd
strongly advise against flashing the bios. If Windows reboots repeatedly it
can easily get messed up and even get to the point where it wont boot at
all. Formatting the drive and installing Windows afresh will sort it but
doing a repair installation - maybe not. It would help to reset the bios by
disconnecting power and pulling the CMOS battery out for a minute. Then boot
up and put all bios settings to defaults. Go into Windows and reinstall
drivers beginning with Mobo drivers then graphics and sound etc

Mmm... I reinstalled the Windows afresh (on one of the two partitions)
-- it did not help. I still get pop-up window saying that the "driver
failed to load". I flashed the BIOS with the MSI Live Update service
-- I still get the "driver failed to load" message. Oh, gosh... I will
try to install the new system driver (NVIDIA MC55), and then AMD
driver if this does not help. I do not know what to do next. Perhaps I
will live as it is now... because I could play the games probably. I
am going to use 3DMark06 to see if the performance of my PC took a hit
because of the "driver which cannot load"...

 

[Beladi Nasralla]

Mmm... I reinstalled the Windows afresh (on one of the two partitions)
-- it did not help. I still get pop-up window saying that the "driver
failed to load". I flashed the BIOS with the MSI Live Update service
-- I still get the "driver failed to load" message. Oh, gosh... I will
try to install the new system driver (NVIDIA MC55), and then AMD
driver if this does not help. I do not know what to do next. Perhaps I
will live as it is now... because I could play the games probably. I
am going to use 3DMark06 to see if the performance of my PC took a hit
because of the "driver which cannot load"...-

OK, so I updated the AMD driver... still, when my computer starts up,
the window pops up saying that the GLM7X.dll's function "find
motherboard info failed" (this DLL belongs to the MSI Live Update).
Thus, I can say that this is the MB which gor toasted... perhaps I
need a new MB some time in the future...

 

[Paul]

OK, so I updated the AMD driver... still, when my computer starts up,
the window pops up saying that the GLM7X.dll's function "find
motherboard info failed" (this DLL belongs to the MSI Live Update).
Thus, I can say that this is the MB which gor toasted... perhaps I
need a new MB some time in the future...

Enter the BIOS and make notes on paper, of what settings you are using.
For example, if you changed a disk controller from SATA mode to AHCI or
RAID, you want to write down what you did, so you can put the settings
back later.

Then, try clearing the CMOS. The procedure should be listed in your manual.
Usually, the procedure starts with unplugging the PC. There should be
a jumper plug or a switch to clear the CMOS. In the manual it could be
described as CLR_RTC.

The CMOS memory in the Southbridge stores some settings. Flashing the
BIOS should have cleared anything stored in the flash chip itself,
such as DMI/ESCD. Clearing the CMOS will remove anything that is
corrupted in there.

Sometimes a CMOS setting can disable some hardware, and that could be
why the driver is not seeing the hardware it expects.

"ACPI Multiprocessor PC" is known as the HAL or hardware abstraction layer.
That value is perfectly normal and that is what my motherboard is using
right now. That value would be appropriate for a dual core processor or
for a processor with Hyperthreading.

Paul

 

[Beladi Nasralla]

Enter the BIOS and make notes on paper, of what settings you are using.
For example, if you changed a disk controller from SATA mode to AHCI or
RAID, you want to write down what you did, so you can put the settings
back later.

Then, try clearing the CMOS. The procedure should be listed in your manual.
Usually, the procedure starts with unplugging the PC. There should be
a jumper plug or a switch to clear the CMOS. In the manual it could be
described as CLR_RTC.

The CMOS memory in the Southbridge stores some settings. Flashing the
BIOS should have cleared anything stored in the flash chip itself,
such as DMI/ESCD. Clearing the CMOS will remove anything that is
corrupted in there.

Sometimes a CMOS setting can disable some hardware, and that could be
why the driver is not seeing the hardware it expects.

"ACPI Multiprocessor PC" is known as the HAL or hardware abstraction layer.
That value is perfectly normal and that is what my motherboard is using
right now. That value would be appropriate for a dual core processor or
for a processor with Hyperthreading.

Thanks. I had flashed the BIOS and had installed the latest version. I
cleared CMOS by switching the jumper. No luck. The computer mostly
runs al'right, except that when I initiate the program DigiCell (and
other utilities from MSI), a window pops up saying "failed load of
driver". When I go to the Control Panel/Administrative Tools/Event
Viewer, it says that the system could not find the specified path (to
the driver ?)

And here is the clue. There was no startup sound when I booted the PC.
Obviously, there was a corrupted installation of Windows. The
corruption started when the PC restarted after being too overclocked.
I re-installed Windows, but I got no start up sound, among other
things. I would like to check if Windows got all the files it supposed
to have. There was a command, but I forgot it. Anybody could remind me
please ?

Here are more symptoms. I used the MSI driver utility to install new
AMD CPU drivers. But whatever I did, they did not install (the
installed driver turned out to be old). I went to the Device Manager,
and tried to update the drivers for the processors. I downloaded the
latest drivers, and showed the path to them. The Windows told me that
it installed the new drivers. However, when I checked, the processor
drivers were still old ones !

Funnily, the computer works stable in both standard and overclocked
regimes. I ran 3DMark6, and the computer perfomed as well as before.
So, I rather keep the current setup, but I still want to fix it. (I
presume this is either faulty installation of Windows, or faulty
motherboard, or there is just some switch which I have to turn and
which I do not know about.)

Thanks.

 

[Ed Medlin]

Thanks. I had flashed the BIOS and had installed the latest version. I
cleared CMOS by switching the jumper. No luck. The computer mostly
runs al'right, except that when I initiate the program DigiCell (and
other utilities from MSI), a window pops up saying "failed load of
driver". When I go to the Control Panel/Administrative Tools/Event
Viewer, it says that the system could not find the specified path (to
the driver ?)

And here is the clue. There was no startup sound when I booted the PC.
Obviously, there was a corrupted installation of Windows. The
corruption started when the PC restarted after being too overclocked.
I re-installed Windows, but I got no start up sound, among other
things. I would like to check if Windows got all the files it supposed
to have. There was a command, but I forgot it. Anybody could remind me
please ?

Here are more symptoms. I used the MSI driver utility to install new
AMD CPU drivers. But whatever I did, they did not install (the
installed driver turned out to be old). I went to the Device Manager,
and tried to update the drivers for the processors. I downloaded the
latest drivers, and showed the path to them. The Windows told me that
it installed the new drivers. However, when I checked, the processor
drivers were still old ones !

Funnily, the computer works stable in both standard and overclocked
regimes. I ran 3DMark6, and the computer perfomed as well as before.
So, I rather keep the current setup, but I still want to fix it. (I
presume this is either faulty installation of Windows, or faulty
motherboard, or there is just some switch which I have to turn and
which I do not know about.)

Thanks.

Since everything is working ok, I would lean more towards a software
problem with the MSI utility. Something could have gotten corrupted
there. I would uninstall that utility and run some kind of registry
cleaner then do an in-place repair install of Windows if the problem
still persists. If the problem goes away after getting rid of the MSI
utility, I would find some other way of monitoring MB info other than
that particular utility or check MSI's site for an updated version.

Ed

 

[Beladi Nasralla]

Since everything is working ok, I would lean more towards a software
problem with the MSI utility. Something could have gotten corrupted
there. I would uninstall that utility and run some kind of registry
cleaner then do an in-place repair install of Windows if the problem
still persists. If the problem goes away after getting rid of the MSI
utility, I would find some other way of monitoring MB info other than
that particular utility or check MSI's site for an updated version.

I did a clean install of Windows and cleared CMOS. I intsalled the
latest motherboard and CPU drivers taken from the manufacturer's
website. Surprisingly, the same problem still persisted. The MSI
utilities which monitored the performance of CPU (namely DigiCell and
Live Monitor) could not load. The error message was that the driver
could not load, or could not find a path to a driver. The Windows'
"Display Properties" did not have the nVidia-specific tabs which were
installed during the motherboard and/or CPU driver installation (the
"Display Properties" had a plain vanilla look of standard Windows).
Other than that, the computer works without problems.

So I thought if the complete reinstallation of OS did not help, then
the problem is with the motherboard. It could either be a hardware
failure or the corrupted settings in CMOS memory. (But I cleared the
latter !)

So here I am thoughtless not knowing what to undertake next. I have
written to the Technical Support of MSI thinking they should have
definetely come across such a problem, but I got no reply.

 

[Paul]

Beladi Nasralla wrote:

So I thought if the complete reinstallation of OS did not help, then
the problem is with the motherboard. It could either be a hardware
failure or the corrupted settings in CMOS memory. (But I cleared the
latter !)

So here I am thoughtless not knowing what to undertake next. I have
written to the Technical Support of MSI thinking they should have
definetely come across such a problem, but I got no reply.

There is another possibility. When you did the complete reinstall,
did you test the computer, before doing all the Windows Updates ?

Maybe something from a Windows Update has upset the "Path" for
the Digicell code. I got the idea for this, from this recent
thread. Check out the symptoms in the first posting, item #5.

http://groups.google.ca/group/micro..._frm/thread/59b26edc41a45df8/60d7eeb693571bde

Paul

 

[Beladi Nasralla]

Beladi Nasralla wrote:

<<snip>>





There is another possibility. When you did the complete reinstall,
did you test the computer, before doing all the Windows Updates ?

Maybe something from a Windows Update has upset the "Path" for
the Digicell code. I got the idea for this, from this recent
thread. Check out the symptoms in the first posting, item #5.

http://groups.google.ca/group/microsoft.public.windowsxp.general/brow...

It's all very frustrating. I cannot get help nowhere :-(

I had a look at the link. It looks like the guy might experience
problems due to the same cause as I might do. He is talking about
"services.msc" and going
action->properties. Guess what, I have no "Properties" menue choice or
a tab. I checked my other computer (which is al'right) -- it does not
have either.

It occurs to me that there might be a checkbox somewhere inside of the
Windows which I have to check near "Allow driver's paths to the CPU"
or smething like that, and then my problem would be solved. I thrawled
the Internet for the general articles on how Windows work in regarding
this instance, and I could not find anything.

In the latest Windows clean install, I did not use the "Windows
Updates".