Windows Odd screen on XP boot (imaged disk)

http://www.technibble.com/how-to-di...r-bsod-if-you-are-unable-to-get-into-windows/

 

Okay, after a long hiatus I'm back trying to fix this issue as it's now a matter of pride.

I have the IDE disk connected and I can now enter the recovery console. I've tried a repair over the top from the CD as per the previous suggestion but it must have kept the SATA drivers as the same 0x07E error occurs.

Once in the recovery console, I've run fixmbr, fixboot and chkdsk and problem still occurs. Does anyone know where the IDE drivers are located on the CD and where to copy them to on the HDD to replace the SATA ones?

Failing that, it's a fresh install and an attempt to retrieve data from the other (also unbootable now) SATA drive that holds a clone.

 

use hirens boot cd, load mini xp, click device manager, and remove the disk controller drivers, try rebooting, hopefully windows will find the drivers and install them properly.

 

If you can disable any SATA controller in the BIOS, or set them to IDE instead of auto
You could try running sfc /scannow from the recovery console.
Does the Stop error message indicate a specific driver file name.

 

Wow. This is one stubborn issue.

Booted into Hiren's Mini XP and removed the drivers, same occurs - tries to load Windows, flash screen appears with the moving blue bar and then the STOP error (although strangely, the screen is green, not blue - forgot to mention that as assumed it was a grpahics driver issue).

Have also checked the BIOS settings and it's not those, but don't believe sfc will fix this as I don't think it's an issue with the Windows system files directly.

++Have also just rebooted into Mini XP to check the drivers and Windows seems to have reapplied them from somewhere as the disk is again listed in Device Manager.

 

In addition, I've followed saspro's advice above (using this link http://www.technibble.com/how-to-dis...-into-windows/) but the reboot registry value is already set to 0 ie. do not reboot, so I don't see how it can be looping...?

However, I have now through some video frame trickery, managed to get the full error message from the screen, which reads as follows:

STOP: 0x0...07E (0xC0...05, 0x80609373, 0xF789E204, 0xF789DF04)

 

Just curious did both machines have the same make of CPU, I.e both AMD or both Intel ?

Scratch that, got confused though it was different machine when you have already said its just the HDD type that changed.

 

Yeah, cloned it across using DriveImageXML, forgot to use sysprep as per saspro's reminder and now have ended up like this.

Due to time, patience and the requirement for the machine to be running by next weekend, I'm perilously close to giving it a massive fkg wallop and reinstalling from scratch. But I still want to know what the problem and solution are!

 

Thought I'd go through and close off some of the threads I've started, just in case anyone else is searching for answers (I know how annoying it is to find the same problem as you're experiencing, only for there to be nothing at the end).

Sadly, with this particular case, I'm having to resort to starting from scratch. I am however doing so with a repurposed SATA drive and an OEM copy of Win 7 Pro from ebay (licence still valid, obviously) to replace the XP/IDE combo giving me a headache.

Issue resolved, but I wouldn't say solution found!