Mobo BIOS Flash then XP Fails???

[Ron Reaugh]

Anyone:

I have an boxed Intel D865GLC + boxed Intel P4/2.60C using hyperthreading
and dual channel DDR400. I've been experiencing CPU fan speed control
problems(fan always runs at max RPM of ~2750RPM regardless of CPU temp) and
Intel TS suggested flashing their very recent P12 BIOS which I did. The
flashing process followed by their recommended CMOS clearing process(battery
removal) all seemed to work just fine. The following boot and BIOS setup
worked fine and showed P12. Incidentally the CPU fan speed control problem
remains unfixed as the fan still runs at ~2750 RPM regardless of CPU temp.

However now Windows XP Home hangs on shutdown attempts. Powerdown is
required. Same for enetring Standby...hangs..powerdown to recover. Is
there anything XP looks for in CMOS that could be causing this hang or is
this a clear case of a new and incompatible BIOS???

Intel TS has basically collapsed and become unresponsive on this issue.
Anyone help please!

 

[Crusty \(-: Old B@stard :-\)]

When you flashed the bios, and then removed the battery to clear the cmos,
you, in effect, went back to the bios factory defaults. You lost those
settings/optimizations which were necessary to allow certain functions to
operate.

Most people (in the know) who flash the bios, first go into the bios and
write down the settings. Then they can manually set the new bios to be the
same as the previous one. That way the system will operate the same.

 

[Just Me]

When you flashed the bios, and then removed the battery to clear the cmos,
you, in effect, went back to the bios factory defaults. You lost those
settings/optimizations which were necessary to allow certain functions to
operate.

Most people (in the know) who flash the bios, first go into the bios and
write down the settings. Then they can manually set the new bios to be the
same as the previous one. That way the system will operate the same.

And also what file system You are using for Your harddrive NTFS v Fat32 - in
how You update the BIO`s.
NTFS , startup with MsDos disk load into RamDrive Your Flash.exe and BIO`s
file , switch over to Your RamDrive
run the exe - Reboot - it not working out - reset the BIO`s either by jumper
switch or take out battery . Fat32 You can
have Your files on the harddrive , startup with MsDos , find and run exe -
reboot - and same as before . But I now like to
use RamDrive way of updating BIO`s ever since it cost Me a motherboard once
..

 

[David Hollway [MVP]]

Anyone:

I have an boxed Intel D865GLC + boxed Intel P4/2.60C using hyperthreading

[crossposting trimmed]

Ron

I've sent you a follow-up to this post. Check your mail.

regards

-David Hollway.

 

[David Hollway [MVP]]

And also what file system You are using for Your harddrive NTFS v Fat32 - in
how You update the BIO`s.
NTFS , startup with MsDos disk load into RamDrive Your Flash.exe and BIO`s
file , switch over to Your RamDrive

Filesystem is completely irrelevant in the case of Intel motherboards -
either update the BIOS by putting a floppy disk containing the BIOS in the
drive and booting from it, or from within Windows - no DOS needed. Intel
BIOS updates have never needed a ramdrive.

 

[CS]

Anyone:

I have an boxed Intel D865GLC + boxed Intel P4/2.60C using hyperthreading
and dual channel DDR400. I've been experiencing CPU fan speed control
problems(fan always runs at max RPM of ~2750RPM regardless of CPU temp) and
Intel TS suggested flashing their very recent P12 BIOS which I did. The
flashing process followed by their recommended CMOS clearing process(battery
removal) all seemed to work just fine. The following boot and BIOS setup
worked fine and showed P12. Incidentally the CPU fan speed control problem
remains unfixed as the fan still runs at ~2750 RPM regardless of CPU temp.

However now Windows XP Home hangs on shutdown attempts. Powerdown is
required. Same for enetring Standby...hangs..powerdown to recover. Is
there anything XP looks for in CMOS that could be causing this hang or is
this a clear case of a new and incompatible BIOS???

Intel TS has basically collapsed and become unresponsive on this issue.
Anyone help please!

Did you save the previous CMOS version to disk prior to flashing? If
you did, you might try flashing back to the older version of the BIOS.

Possibly flashing the BIOS has done something to the motherboard ACPI
capability and now you can no longer shutdown or go into standby. As
for your fan problem, it may be defective hardware. There are heat
sensor devices on the motherboard which control the speed of the fans.
The sensor may be defective or possibly the fan.

 

[Ron Reaugh]

When you flashed the bios, and then removed the battery to clear the cmos,
you, in effect, went back to the bios factory defaults.

Yes, factory defaults(aka optimized defaults) and then I reset all my other
changes to BIOS settings.

You lost those
settings/optimizations which were necessary to allow certain functions to
operate.

Does XP keep anything in CMOS?

Most people (in the know) who flash the bios, first go into the bios and
write down the settings.

Been there...did that.

Then they can manually set the new bios to be the
same as the previous one. That way the system will operate the same.

In this case it does not.

 

[Ron Reaugh]

And also what file system You are using for Your harddrive NTFS v Fat32 - in
how You update the BIO`s.
NTFS , startup with MsDos disk load into RamDrive Your Flash.exe and BIO`s
file , switch over to Your RamDrive
run the exe - Reboot - it not working out - reset the BIO`s either by jumper
switch or take out battery . Fat32 You can
have Your files on the harddrive , startup with MsDos , find and run exe -
reboot - and same as before . But I now like to
use RamDrive way of updating BIO`s ever since it cost Me a motherboard

once


Please reword and clarify the issue you are describing. My flash was a BIOS
recovery BIOS booted floppy operation with the mobo jumper in position to do
that operation. Yes the jumper was restored after the flash.

 

[Crusty \(-: Old B@stard :-\)]

If you had said you did all that in the beginning I would not have wasted my
time. Give a COMPLETE description in your first post!

 

[Ron Reaugh]

Did you save the previous CMOS version to disk prior to flashing? If
you did, you might try flashing back to the older version of the BIOS.

May try that eventually but I want to get a handle on exactly what's
happening as Intel TS is being recalcitrant and I want to be fully locked
and loaded before I go back and escalate the issue with Intel.

Possibly flashing the BIOS has done something to the motherboard ACPI
capability and now you can no longer shutdown or go into standby. As
for your fan problem, it may be defective hardware.

Both the boxed Intel CPU+fan and the boxed Intel mobo's processor fan header
have speed control vs temp. They may be fighting each other and Intel TS is
fastidiously avoiding discussing THAT with me.
ftp://download.intel.com/design/Pentium4/datashts/29864311.pdf
"7.4.2 Variable Speed Fan...."

ftp://download.intel.com/design/motherbd/lc/C3263401.pdf
"1.13.2.2 Fan Connectors...Processor fan...Closed-loop fan control that can
adjust the fan speed..."

There are heat
sensor devices on the motherboard which control the speed of the fans.
The sensor may be defective or possibly the fan.

Both defective simultaneously on new boxed Intel stuff seems VERY unlikely.

 

[relic]

Anyone:

I have an boxed Intel D865GLC + boxed Intel P4/2.60C using
hyperthreading and dual channel DDR400. I've been experiencing CPU
fan speed control problems(fan always runs at max RPM of ~2750RPM
regardless of CPU temp) and Intel TS suggested flashing their very
recent P12 BIOS which I did. The flashing process followed by their
recommended CMOS clearing process(battery removal) all seemed to work
just fine. The following boot and BIOS setup worked fine and showed
P12. Incidentally the CPU fan speed control problem remains unfixed
as the fan still runs at ~2750 RPM regardless of CPU temp.

However now Windows XP Home hangs on shutdown attempts. Powerdown is
required. Same for enetring Standby...hangs..powerdown to recover.
Is there anything XP looks for in CMOS that could be causing this
hang or is this a clear case of a new and incompatible BIOS???

Intel TS has basically collapsed and become unresponsive on this
issue. Anyone help please!

The only things in most BIOS'es that XP cares about is ACPI (ON, or Enabled),
and Plug and Play OS (OFF, or Disabled).
When you rebooted, it may have seen something it didn't like and loaded a
different HAL. In Device Manager, is "Computer" still indicating that it's an
ACPI Compliant PC? If not, you can reinstall the driver to get the correct
HAL again.

 

[Ron Reaugh]

If you had said you did all that in the beginning

Any competent reader would have seen that I did from my original post. Go
back and read it again.

I would not have wasted my
time. Give a COMPLETE description in your first post!

The clueless usually instigate yelling. Now if you want to help then
address the question that I posed in my original post:

Is there anything XP looks for in CMOS that got cleared and could be causing
this hang or is this a clear case of a new and incompatible BIOS???

 

[Ron Reaugh]

The only things in most BIOS'es that XP cares about is ACPI (ON, or Enabled),
and Plug and Play OS (OFF, or Disabled).
When you rebooted, it may have seen something it didn't like and loaded a
different HAL. In Device Manager, is "Computer" still indicating that it's an
ACPI Compliant PC? If not, you can reinstall the driver to get the correct
HAL again.

So deleting all the mobo related stuff in Device Manager and then
redetecting might solve the issue.

I've done many BIOS flashes in the past and never seen anything like this
happen. Is the behavior described in my opening post something folks have
seen before or is it unusual? Should Intel be expected to have given
warning that a new BIOS version might cause this effect?

 

[relic]

So deleting all the mobo related stuff in Device Manager and then
redetecting might solve the issue.

It could, but from what you said I would think reloading the HAL might do it.
Here's the ACPI spiel:

If you have a new machine, it will use ACPI (Advanced Configuration and Power
Interface). In Device Manager see if your computer is an ACPI Uniprocessor PC
(or dual... whatever you have). Try reinstalling its driver, then look under
System devices for Microsoft ACPI compliant System >> reinstall its driver.
(You can install ACPI by updating the "computer" driver. See next paragraph.)

When the Hardware Update Wizard starts, click on "Install from a list or
specific location (Advanced)" then Next. On the next menu, click "Don't
search. I will choose the driver to install" then Next. You should find the
ACPI Uniprocessor PC listed on the next screen. If it isn't there, you will
have to do a reinstall and press F5 at the start (see next paragraph).

Sometimes, ACPI will require a reinstall to get it sorted out correctly. At
the start of the installation you will see a request to hit F6 if you need to
install additional SCSI Drivers; hit F5 instead. Later, you will be asked to
identify what kind of PC you have, scroll up in the window near the bottom to
the ACPI types and select yours (commonly: ACPI Uniprocessor PC). Remember to
reinstall the XP Updates, especially SP1, following a reinstallation of the XP
OS.

 

[Ron Reaugh]

Thanks, I'll review that process.

I gonna fight to not have to reinstall XP.

 

[Crusty \(-: Old B@stard :-\)]

"Yes, factory defaults(aka optimized defaults) and then I reset all my
other
changes to BIOS settings."

Where in your first post do you say you did this?

"Most people (in the know) who flash the bios, first go into the bios and
write down the settings."

Where in your first post do you say you did this?

All you said is that you cleared the cmos!

 

[Ron Reaugh]

Hi Ron
Hyper threading might be your problem. Any changes to this setting results
in reinstalling the OS.
Some BIOS by default disable hyper threading and if enabled the OS must be
reinstalled.

Ah maybe that. I believe that hyperthreading was installed in both cases.
I'll check that out further. I previously flashed from the delivered P09 to
the then latest P11 without any of these difficulties.

Thanks.

 

[George]

Hi Ron
Hyper threading might be your problem. Any changes to this setting results
in reinstalling the OS.
Some BIOS by default disable hyper threading and if enabled the OS must be
reinstalled.
Regards

George

 

[Josh82]

Check out support.microsoft.com for any known issues with XP and your
mobo and BIOS. There might be a fix or at least a workaround. We all
know how windows gets upset over the littlest things...

 

[David Hollway [MVP]]

Ah maybe that. I believe that hyperthreading was installed in both cases.
I'll check that out further. I previously flashed from the delivered P09 to
the then latest P11 without any of these difficulties.

Thanks.

If you have Service Pack 1 installed, then if HT is enabled either
deliberately or accidentally in the BIOS, the OS will automatically detect
it and use it - you'll see it detect an "ACPI Multiprocessor PC" device at
boot, then be prompted for a reboot.
If you do not have SP1, then XP will ignore the presence of HT until you
install SP1 or re-install the OS - however, no harm will be done.