BSOD Stop: 0x0000007b when Win XP is slected for boot.

I get the BSOD only when I select the XP to boot. (entry 1) The string is Stop: 0x0000007b (0xb84c7524, 0x00000034 etc.
No other message appears but from what I've read in many forums is the thought that \NST\ntldr can't be found.
The folders exist but the ntldr is not in this folder but in the root. I built another drive and tried using the rocovery console
to evaluate the issue but no luck. Chkdsk, no virus, no problems. Used Active Boot Disk v5 and don't see anything
out of ordinary.
Any Ideas from anyone?

Default: Win XP
Timeout: None
EasyBCD Boot Device: C:\
Entry #1
Name: Win XP
BCD ID: {default}
Drive: C:\
Bootloader Path: \NST\ntldr

Entry #2
Name: Win7 SSD
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe
Entry #3
Name: Win7 Sata
BCD ID: {fb096dc6-e991-11e0-8fed-9aca24d0f91f}
Drive: N:\
Bootloader Path: \Windows\system32\winload.exe
Entry #4
Name: XP Sata
BCD ID: {fb096dce-e991-11e0-8fed-9aca24d0f91f}
Drive: C:\
Bootloader Path: \NST\easyldr1
Entry #5
Name: Win7_64
BCD ID: {fb096dcf-e991-11e0-8fed-9aca24d0f91f}
Drive: L:\
Bootloader Path: \Windows\system32\winload.exe
Entry #6
Name: WinXP_64
BCD ID: {fb096dd0-e991-11e0-8fed-9aca24d0f91f}
Drive: C:\
Bootloader Path: \NST\easyldr2


Knows where his towel is.
Staff member
Hi and thanks for the reply.
This system and configuration above has been working for months. The only thing that changed were MS updates last week and when I woke up the pc in the morning it was displaying the BSOD. From what I read from your post I understand that the lack of the intel driver can cuse this too but this doesn't explain why it was working then doesn't. I have duplicate machines and copied this SSD to place in the other machine and it BSOD as well. I could play with that setup so I don't affect the main pc and see if something comes of it. What do you suggest?


Mostly Harmless
Staff member
Have you tried turning AHCI off?