PDA

View Full Version : Boot stops after ACPI controller and before DMI pool data on warm reboots.


videobruce
03-11-2009, 01:27 PM
After the line "ACPI controller" and before the line "DMI pool data", the boot process stops.

This is only on warm boots and it is only once in a while. It doesn't happen on cold boots.

nForce7 chipset MB w/ latest Bios,
Two SATA HDD's, one SATA optical and one IDE optical,
No RAID,
NO boot manager.

I did some searching and all I could find was problems durning the PCI configuration process, not after. The PCI config does complete ok as I see the last line "ACPI controller".

I don't see what would be the next line; :DMI pool data......." Again, this is only on a warm boot and not every time.

Paul Komski
03-12-2009, 06:42 AM
http://www.computerhope.com/issues/ch000474.htm

But do not run the sys command or use fdisk /mbr if you are running Win2K or above.

A loose or poor data or power connection to the HDD would be high on my own suspicion list. Could also be wise to test the HDD for problems with its maker's diagnostics. Bad memory is another item that can cause just about anything.

videobruce
03-12-2009, 10:59 AM
I don't know what happened to that last line in my orginal post. It should of read "DMI pool data...."

I'll try a 'set to defaults' setting and see what happens. Again, this is only on warm boots and not all of them. The problem just started happening in the past couple of months. The MB is just over a year old.

Paul Komski
03-12-2009, 11:06 AM
I don't know what happened to that last line in my orginal post.

:D normally results in a laughing smiley unless you submit an advanced reply and disable smileys as in this post. You can of course test it in the testing forum.

Sylvander
03-12-2009, 11:15 AM
How about...
1. Making sure one of these Windows NT 4.0, 2000, XP or Server 2003 boot floppy disks (http://www.nu2.nu/bootdisk/ntboot/) is in the FDD every time you try a warm reboot.
[BIOS must be configured to boot FDD before HDD]
Choose to attempt to load the Windows files off the 1st partition on the 1st internal HDD.
2. So it would boot that floppy rather than using the boot files on the internal HDD "System Partition".
And IF that eliminates the problem...
You've narrowed considerably the suspect area to that part of the boot sequence before the loading of the main Windows files in the Windows folder..

videobruce
03-12-2009, 12:17 PM
My typo..............

But, this only happens on a warm boot and then only some of the time.