Windows 7 Trying to Boot As Windows XP???

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860
I have a new Asus P7P55D, and when trying to boot into Windows 7, it BSODs. Upon pressing F8 to get advanced boot options, Windows recommended to boot into Windows XP, which does not exist. Please help!
 
Solution
To anyone in the future who is looking back at this post, it definitely was the motherboard. The CPU was fine. It was probably a faulty SATA controller. Putting the drive in another, newer PC allowed me to boot in just fine. There was nothing wrong with the drive.

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


I just got it installed and upgraded from a Dell motherboard that also has SATA 2 and 3, due to being 1156 sockets. Only a single OS, no transfers. It shows the multi-colored dots for a few seconds when booting into 7, then they freeze and a BSOD flashes in for 1/2 of a second, then the PC restarts.
 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


It says in boot up:

Please Select the Operating System to Start:
Microsoft Windows XP Professional

Use the up and down arrow keys to move the highlight of your Choice.
Press ENTER to choose.

For troubleshooting and advanced startup options for Windows, press F8.

Upon Pressing Enter, it says:

Windows could not start because the following file is missing or corrupt:
<Windows Root>\system32]hal.dll
Please reinstall a copy of the above file.
 
http://www.tomshardware.com/news/win7-windows-7-mbr,10036.html

Since you have this error AND a replacement board I suspect your data got corrupted. Possibly due to the motherboard having issues but hard to say.

There may be MORE errors so you may want to consider doing this:
1) run MEMTEST86 to confirm system memory (i.e. DDR3 sticks) fine. run full pass or until errors
www.memtest86.com

2) run HDD/SSD diagnostics (see manufacturer site for software)

3) backup data, write down program names to reinstall, e-mail info etc (plan CAREFULLY)

4) Reinstall Windows 7

5) install video drivers, fan control software, antivirus, programs etc

6) optional: backup an IMAGE of your Windows partition so you can restore in case of data corruption or drive failure
 

Ralston18

Titan
Moderator
This motherboard? Do you have the manual and installation instructions?

https://www.google.com/shopping/product/17635739492630183488/specs?q=Asus+P7P55D&ie=&oe=&sa=X&ved=0ahUKEwj334Pryb7VAhUI7IMKHbGPDfAQuC8IiAE

What processor is installed?

To be honest (full disclosure) I am not sure about any immediate fix. My thought is that you need to take a close look at all of the installed components and look for something not meeting or matching the specs.

If all seems well, doublecheck your installation work. Pull out all but the basic component requirements - the GPU for example, extra drives, network cards etc.

The goal is to achieve a successful boot and then add back components until the boot again fails.
 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


i5-760 is installed.
 

Ralston18

Titan
Moderator
Listed processors are Core i5, Core i7

However, the lack of more specific information (e.g. i5-760) would concern me.

Not at all uncommon that a manufacturer "skimps" on specifics by using the general versus the specific.

Or sometimes all "dashed versions" work excluding one or two that are only mentioned in the fine print.

That said I am sort of out of ideas at the moment.

No disagreements with Photonboy's suggestions. Very tangible and doable.
 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


The 750 vs the 760 being not supported shouldn't be much of a problem, should it? I actually have a 750 laying around. Do you think that could be the problem?
 

Ralston18

Titan
Moderator
Honestly do not know.

But "not supported" is more direct and honest (IMO) than something like "fits all models" where the physical aspects are correct but the functional aspects are not.

Two choices: 1) try the 750 and hope, 2) research the 750 and 760 to see for sure.

Choice 1 may immediately provide some result albeit good or bad. Choice 2 may take more time but result in more knowledge or lead to a solution. And at little or no risk to hardware.

Choice 2 recommended.
 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


https://www.asus.com/Motherboards/P7P55D_EVO/HelpDesk_CPU/ I have the most up to date BIOS on the board (2101), and it says that the 760 is in fact supported... The drive booted just fine with an old Dell board (DQ57TM), and the drive was not moved around too much/bumped since the installation of the new board...
 

Ralston18

Titan
Moderator
The CPU could be the problem. Even supported components can fail.

And going back a few posts....

This:


Windows could not start because the following file is missing or corrupt:
<Windows Root>\system32]hal.dll
Please reinstall a copy of the above file.

Are you able to boot from a recovery disk or USB drive? If so, do so and reinstall the hal.dll file.

 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


That hal.dll error was caused by booting to the wrong HDD, so i removed them, and now I'm left with BSODing after seeing the first 3 blobs fly in to make the Windows logo while booting. It seems that the PC crashes after loading classpnp.sys. If I rename it to classpnp.old, it never loads classpnp and just crashes on loading disk.sys.
 

Ralston18

Titan
Moderator
Starting to feel that you may need to do a Windows 7 reinstall as the existing installation may be corrupted.

Not sure what else to suggest. Perhaps someone else following this thread will comment and correct some error of omission or commission on my part. No problem with that.....

 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860


I've run chkdsk, to find no bad sectors, and a full SFC scan revealed that nothing was wrong. I think it could be a complicated driver issue I've been seeing with other threads dealing with this. If there's something else that could be wrong, I don't know what it could be.
 

RektSkrubz

Reputable
Sep 12, 2015
408
0
4,860
To anyone in the future who is looking back at this post, it definitely was the motherboard. The CPU was fine. It was probably a faulty SATA controller. Putting the drive in another, newer PC allowed me to boot in just fine. There was nothing wrong with the drive.
 
Solution