BSOD ox0000007b 0xb84cf524, oxc000034, 0x00000000 after xp upgrade

[wealthwise]

Lately I have been having some problems with my XP Pro install, so 3 days ago rather than do a clean install I opted to do a reinstall with upgrade path, everyone went fine till it rebooted and up came the error, I started up from the boot CD, did another install this time successful, and somehow managed to preserve my files and old system files. I would very much like to be able to keep the old system install so I have been looking for a solution, I understand this stop error could be a boot sector Virus, I have scanned the boot sector with Avira and nothing, I have run chkdsk /f and also /r, I have tried to repair the install using the install CD, twice now, I understand it could also be due to drivers missing or SATA not set in BIOS which I reset to default, but that doesn't make sense since I can boot with the other install just fine, I"m at my wits end and I really don't want to reinstall my 100 gigs+ worth of programs and would like to preserve the old install, any ideas? I also have Hiren's CD if that helps.
Thanks

 

[drtweak]

yea 7B is almost always SATA/RAID/IDE Drivers.

So you are saying you did an in place upgrade (Install over the old one)? Did you ever get into windows after you reinstalled or no?

 

[Paul NZ]

Yup 7b usually means SATA drivers.

It means it was on IDE mode originally in the BIOS. Windows was installed then someone changed it to AHCI mode in the BIOS. Bad idea.

AHCI mode needs SATA drivers. And the XP CD doesnt have SATA drivers on it.

Unless you slipstream them

This will cause this stop error. Because, if there are no SATA drivers it cant find the hdd, you crash

If this is the case change it back to IDE in the BIOS

 

[wealthwise]

yea 7B is almost always SATA/RAID/IDE Drivers.

So you are saying you did an in place upgrade (Install over the old one)? Did you ever get into windows after you reinstalled or no?

Yes in place upgrade over the old one, that's the one gving me the stop error, yes I got into windows in the other install, I could just start over with the new install but it will take a long time to get it to where it was.

 

[Paul NZ]

It must have deleted / removed the sata drivers from the original install then.

If it crashes now. You could start again but if there are no sata drivers on the cd. You'll crash again with the same stop error. Unless you change it to IDE mode in the BIOS first

 

[wealthwise]

yea 7B is almost always SATA/RAID/IDE Drivers.

So you are saying you did an in place upgrade (Install over the old one)? Did you ever get into windows after you reinstalled or no?

Yes I did an in place upgrade over the old one and yes I got into windows in the new install and yes I can access the old directory windows.0 . I checked the BIOS and it was not changed to AHCI mode. So I don't think it's the SATA drivers, besides how could it boot successfully if that were the case?
Thanks

 

[wealthwise]

It must have deleted / removed the sata drivers from the original install then.

If it crashes now. You could start again but if there are no sata drivers on the cd. You'll crash again with the same stop error. Unless you change it to IDE mode in the BIOS first

So like I mentioned above, I checked the BIOS SATA setting and it's set to IDE not AHCI, any thoughts?

 

[wealthwise]

Yup 7b usually means SATA drivers.

It means it was on IDE mode originally in the BIOS. Windows was installed then someone changed it to AHCI mode in the BIOS. Bad idea.

AHCI mode needs SATA drivers. And the XP CD doesnt have SATA drivers on it.

Unless you slipstream them

This will cause this stop error. Because, if there are no SATA drivers it cant find the hdd, you crash

If this is the case change it back to IDE in the BIOS

I should mention I'm on a Asus C90s desktop replacement with small SATA drive.

 

[Paul NZ]

Well if its been on IDE all the time. One thing that may / can cause that stop error is a rootkit. Get tdsskiller run it. See if it picks up any rootkits

If it does select cure then reboot

 

[wealthwise]

Well if its been on IDE all the time. One thing that may / can cause that stop error is a rootkit. Get tdsskiller run it. See if it picks up any rootkits

If it does select cure then reboot

That's what I have been suspicious of all along in fact I'm in Hirens Mini XP as I type this running a rootkit scanner, I will try tdsskiller and see what if finds, is there any chance that it could just be damaged sectors? Would Chdsk have detected that?
Thanks

 

[Paul NZ]

Rootkits are made to hide. So nothing may find it. I suppose it could destroy the files depending on what it does

 

[wealthwise]

Rootkits are made to hide. So nothing may find it. I suppose it could destroy the files depending on what it does

I suppose your right, I just ran TDSSKiller on the good install and no surprise, "no threats found", I suppose I should run it off a a boot CD? At this point if I can't solve the problem I may have to cut my losses, mostly time and move on, I was hoping to do upgrade to XP Pro 64 and keep my old installs, but I'm not even sure I can do that, so I will most likely have to do a clean install sooner or later I guess.
Thanks for trying

 

[Paul NZ]

So did you run tdsskiller on the PC that was crashing with that 0x7b stop error?

I would install a later version of windows. XP and XP 64 bit are a bit too old for anything these days. And there may not be drivers for XP 64 bit...

 

[wealthwise]

So did you run tdsskiller on the PC that was crashing with that 0x7b stop error?

I would install a later version of windows. XP and XP 64 bit are a bit too old for anything these days. And there may not be drivers for XP 64 bit...

Yes I ran it on the same one, now I'm running Malwarebytes Anti-Rootkit beta, it drills deep down, so we'll see, yes I was thinking maybe just upgrade to a Vista type system maybe Win 7 not sure at this time.

 

[Paul NZ]

Upload the dmp files somewhere like onedrive. Then post the link

 

[wealthwise]

Upload the dmp files somewhere like onedrive. Then post the link

https://onedrive.live.com/redir?resid=7668610D7603D88E!103&authkey=!AFvHYfLzARyQmRc&ithint=folder%2cdmp

Thanks for the help

 

[Paul NZ]

Are there any dmp files in the C:\windows\minidump folder?

 

[wealthwise]

Are there any dmp files in the C:\windows\minidump folder?

No minidump folder in C:\windows only in windows.0 and it's empty

 

[Paul NZ]

hmm k. I would look in event viewer. See what that says it maybe under windows log / system

 

[wealthwise]

hmm k. I would look in event viewer. See what that says it maybe under windows log / system

Looked in event viewer can't find log/system only Application Security and System

Don't know if this is anything it's a flag that came up in event viewer
setup error says see setuplog, ,in windows.0 it says
"10/21/2014 14:19:29.437,d:\xpsp\base\ntsetup\syssetup\syssetup.c,1938,,Setup: (non-critical error): Failed load of ismif32.dll."

 

[Paul NZ]

The XP cd you installed windows from. Did you use Nlite to create an ISO then burn it to cd??

Because that error maybe related to slipstreaming / using Nlite

 

[wealthwise]

The XP cd you installed windows from. Did you use Nlite to create an ISO then burn it to cd??

Because that error maybe related to slipstreaming / using Nlite

Nope didn't use Nlite, so your saying that error would only be related to upgrade not clean install?

 

[Paul NZ]

Well if you used the same XP cd I dont think that error would appear at all. But since no files were deleted when you did it you must have updated XP from within XP?

Because its not really an upgrade is it. Because XP was already on it

 

[wealthwise]

Well if you used the same XP cd I dont think that error would appear at all. But since no files were deleted when you did it you must have updated XP from within XP?

Because its not really an upgrade is it. Because XP was already on it

True, I think it would be more appropriate to call it an update rather than upgrade and yes that's it I updated XP from within XP, so what could have gone wrong is the question? More importantly is their a solution?

 

[Paul NZ]

What you said in the first post - since I can boot with the other install just fine

What other install? Is the PC thats crashing a copy of another install or something? Or did you put a hdd from one system into this one thats crashing?