Share via

Windows xp boot up stops with "did not load driver acpi uniprocessor pc"

Anonymous
2015-02-24T19:24:39+00:00

Windows XP SP3 which has worked well for many years has suddenly started hanging during boot.  It will allow choosing of boot options  such as safe mode

etc, but will hang on any mode chosen.  Essentially the screen just goes black and the boot stops dead.  Even the recovery disk hangs and I cannot get to the command prompt.  I've loaded Ubuntu CD and scanned for viruses and captured the boot log below.  I've tried dozens of approaches but nothing has worked and I would rather not just wipe my drive.  This seems to have been a common problem at one point, has anyone found the solution? 

 Service Pack 311  6 2013 13:22:01.500

Loaded driver \WINDOWS\system32\ntoskrnl.exe

Loaded driver \WINDOWS\system32\hal.dll

Loaded driver \WINDOWS\system32\KDCOM.DLL

Loaded driver \WINDOWS\system32\BOOTVID.dll

Loaded driver ACPI.sys

Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS

Loaded driver pci.sys

Loaded driver isapnp.sys

Loaded driver pciide.sys

Loaded driver \WINDOWS\system32\DRIVERS\PCIIDEX.SYS

Loaded driver aliide.sys

Loaded driver cmdide.sys

Loaded driver toside.sys

Loaded driver viaide.sys

Loaded driver intelide.sys

Loaded driver MountMgr.sys

Loaded driver ftdisk.sys

Loaded driver dmload.sys

Loaded driver dmio.sys

Loaded driver PartMgr.sys

Loaded driver VolSnap.sys

Loaded driver cpqarray.sys

Loaded driver \WINDOWS\system32\DRIVERS\SCSIPORT.SYS

Loaded driver atapi.sys

Loaded driver aha154x.sys

Loaded driver sparrow.sys

Loaded driver symc810.sys

Loaded driver aic78xx.sys

Loaded driver dac960nt.sys

Loaded driver ql10wnt.sys

Loaded driver amsint.sys

Loaded driver asc.sys

Loaded driver asc3550.sys

Loaded driver mraid35x.sys

Loaded driver i2omp.sys

Loaded driver ini910u.sys

Loaded driver ql1240.sys

Loaded driver aic78u2.sys

Loaded driver symc8xx.sys

Loaded driver sym_hi.sys

Loaded driver sym_u3.sys

Loaded driver ABP480N5.SYS

Loaded driver asc3350p.sys

Loaded driver cd20xrnt.sys

Loaded driver ultra.sys

Loaded driver adpu160m.sys

Loaded driver dpti2o.sys

Loaded driver ql1080.sys

Loaded driver ql1280.sys

Loaded driver ql12160.sys

Loaded driver perc2.sys

Loaded driver perc2hib.sys

Loaded driver hpn.sys

Loaded driver cbidf2k.sys

Loaded driver dac2w2k.sys

Loaded driver SiSRaid.sys

Loaded driver disk.sys

Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS

Loaded driver fltmgr.sys

Loaded driver sr.sys

Loaded driver drvmcdb.sys

Loaded driver PxHelp20.sys

Loaded driver KSecDD.sys

Loaded driver WudfPf.sys

Loaded driver Ntfs.sys

Loaded driver NDIS.sys

Loaded driver viaagp.sys

Loaded driver uagp35.sys

Loaded driver sisidex.sys

Loaded driver SISAGPX.sys

Loaded driver ohci1394.sys

Loaded driver \WINDOWS\system32\DRIVERS\1394BUS.SYS

Loaded driver Mup.sys

Loaded driver dcsnap.sys

Loaded driver aswVmm.sys

Loaded driver aswRvrt.sys

Loaded driver alim1541.sys

Loaded driver amdagp.sys

Loaded driver agpCPQ.sys

Did not load driver ACPI Uniprocessor PC

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2015-02-25T22:50:46+00:00

    You do not describe symptoms consistent with a failing CMOS battery.

    It is normal to see that message (and lots like it) in the useless ntbootlog when booting in Safe Mode as seen in this example of a system that boots fine:

    Loaded driver WudfPf.sys

    Loaded driver Ntfs.sys

    Loaded driver NDIS.sys

    Loaded driver Mup.sys

    Did not load driver ACPI Multiprocessor PC

    Did not load driver Audio Codecs

    Did not load driver Legacy Audio Drivers

    Did not load driver Media Control Devices

    .

    .

    .

    Do you even have a multiprocessor system?  (Remember, we don't know much of anything about your system thanks to the MS Answers forum implementation deficiency of not prompting for fundamental system information when a new question is asked).

    That log is from a Safe Mode boot, right?

    What do you see (lastly) in a non Safe Mode boot log?

    What is your system make and model?

    What is your definition of a Recovery Disk?

    If your system will not boot, how did you get the log?

    If your system used to work properly what do you think changed since the last time it did work properly?

    Any hardware changes?

    I would start using a process of elimination starting with hardware devices.

    The next thing that wants to load are the keyboard, USB and mouse drivers so if you have any USB devices attached you may want to unplug all peripherals, reboot and see what happens.

    If the keyboard on your system of unspecified make and model is USB then I would use a PS/2 keyboard if you have one - you only need a keyboard to boot and navigate your system so unplug everything else (as a test) and see what happens.

    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-02-26T22:31:55+00:00

    That's good.

    It could just be one device...  mouse, keyboard or the hub.  Perhaps more fault isolation troubleshooting is in order.  Plug things in/out one at a time to see if you can isolate the culprit - or just the hub alone, does the system not boot if just the hub is plugged in?  Then add just the mouse and see what happens, then just then keyboard, then both, etc.  You'll figure it out.

    If it is the hub, the manufacturer may have some ideas on their support page if you contact them with the symptoms or maybe it is still under warranty.

    0 comments No comments
  2. Anonymous
    2015-02-26T18:12:32+00:00

    Many thanks for your response.  As it turns out, you may be something of a genius as your advice has enabled me to successfully boot the PC once again.  I unplugged a USB hub from a port on the front of the computer which was supporting both the USB keyboard and mouse.  I then tried the boot again and hey presto it worked.  I've been using that hub without any issues for over 6 months now and I would never have thought that was part of the problem (or indeed the whole problem).  If you don't mind, I'd like to get your view on possible reasons why the USB hub should cause the boot to fail and what I may be able to do to remedy it.  I've answered the questions you've asked below.

    You do not describe symptoms consistent with a failing CMOS battery.

    It is normal to see that message (and lots like it) in the useless ntbootlog when booting in Safe Mode as seen in this example of a system that boots fine:

    Loaded driver WudfPf.sys

    Loaded driver Ntfs.sys

    Loaded driver NDIS.sys

    Loaded driver Mup.sys

    Did not load driver ACPI Multiprocessor PC

    Did not load driver Audio Codecs

    Did not load driver Legacy Audio Drivers

    Did not load driver Media Control Devices

    .

    .

    .

    Do you even have a multiprocessor system?  (Remember, we don't know much of anything about your system thanks to the MS Answers forum implementation deficiency of not prompting for fundamental system information when a new question is asked).

    No, it's a Pentium 4 PC. 3.07GHz

    That log is from a Safe Mode boot, right?

    No, that is from a normal boot

    What do you see (lastly) in a non Safe Mode boot log?

    This is the last entry: Loaded driver \SystemRoot\system32\DRIVERS\srv.sys

    Also, on closer inspection, there are a lot of other drivers way down the list that get loaded after "ACPI Multiprocessor" - almost all SystemRoot

    Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS

    Loaded driver \SystemRoot\system32\DRIVERS\USBSTOR.SYS

    Loaded driver \SystemRoot\system32\DRIVERS\usbccgp.sys

    Loaded driver ??\C:\WINDOWS\System32\Drivers\sunkfilt.sys

    Loaded driver \SystemRoot\system32\DRIVERS\IrBus.sys

    Loaded driver \SystemRoot\system32\DRIVERS\hidusb.sys

    Loaded driver \SystemRoot\system32\DRIVERS\hidir.sys

    Loaded driver \SystemRoot\system32\DRIVERS\ndisuio.sys

    Loaded driver \SystemRoot\System32\Drivers\Fastfat.SYS

    Loaded driver \SystemRoot\system32\DRIVERS\rdbss.sys

    Loaded driver \SystemRoot\system32\DRIVERS\mrxsmb.sys

    Loaded driver \SystemRoot\system32\DRIVERS\ipnat.sys

    Loaded driver \SystemRoot\system32\DRIVERS\netbt.sys

    Loaded driver \SystemRoot\System32\Drivers\AswRdr.SYS

    Loaded driver \SystemRoot\System32\drivers\afd.sys

    Loaded driver \SystemRoot\system32\DRIVERS\netbios.sys

    Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys

    Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS

    Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS

    Loaded driver \SystemRoot\system32\DRIVERS\usbhub.sys

    Loaded driver \SystemRoot\system32\DRIVERS\rasacd.sys

    Loaded driver \SystemRoot\system32\DRIVERS\ipsec.sys

    Loaded driver \SystemRoot\system32\DRIVERS\tcpip.sys

    What is your system make and model?

    Philips Freevents desktop PC.  Running Windows XP SP3 Media Center Edition. 2GB RAM

    What is your definition of a Recovery Disk?

    The Windows XP System Restore dvd

    If your system will not boot, how did you get the log?

    After the boot failed, I shutdown and booted straight into an Ubuntu disk then retrieved the log

    If your system used to work properly what do you think changed since the last time it did work properly?

    Nothing major that I can think of.

    Any hardware changes?

    I did install a new 1.5 TB Hitachi hard drive over six months ago, but it has been working perfectly all that time.

    I would start using a process of elimination starting with hardware devices.

    The next thing that wants to load are the keyboard, USB and mouse drivers so if you have any USB devices attached you may want to unplug all peripherals, reboot and see what happens.

    If the keyboard on your system of unspecified make and model is USB then I would use a PS/2 keyboard if you have one - you only need a keyboard to boot and navigate your system so unplug everything else (as a test) and see what happens.

    Again, thanks for the help and if you have any further insight into what is the underlying cause of this, I would really appreciate that.

    0 comments No comments
  3. Anonymous
    2015-02-25T12:34:21+00:00

    Thanks for the quick reply Andrew.  I've tried your suggestion and taken out the battery, replaced it and gone into the BIOS, but unfortunately, the boot still stops dead after the Windows xp splash screen.  So I'm open to any other suggestions...

    0 comments No comments
  4. Anonymous
    2015-02-25T00:35:10+00:00

    At this point,windows hasnt started yet,its in MS-DOS..

    With an older pc,if a desktop,a simply recommended try would be to,power-off

    pc,remove the MB battery,wait 10 minutes,replace with new battery,start pc.

    On pc start,enter the BIOS,reset date/time,adjust for add-in cards,etc,save and

    exit BIOS..

    Batteries only run for a few years,this controls the BIOS (basic input output)w/o

    it,the pc runs in a "loop" on start-up...

    0 comments No comments