eeolivier
asked on
URGENT - 0X0000007B when rebooting
Let me tell what happened to my brother
- PC owned since 2 years. This PC has a 80 GC Western Digital CAVIAR drive.
- He want to change this drive
- He bought a Maxtor DiamondMax 10 - 8 Mo cache - 200 Go - 7200 t/min - Interface ATA/133
- Yesterday we unpluged the old 80Gb, and put the new Maxtor instead, putting it on CABLE SELECT jumper.
- We used windows XP disk to install a new fresh install of the OS. We drove crazy,because we had error messages during install progress (various messages, differents each time). So.... we GAVE UP. He will give back the disk.
- So we plug back the OLD disk, so we are in the same conf than before and ouppppsss......
- When we start the computer, we see "PRIMARY MASTER DETECTED", with the good size. Then it remains blinking cursor for a moment, then we see windows FLAG, then freeze... and blue screen with a STOP message : 0X0000007B (0xF8B0C528 0xC0000034 0x00000000 0x00000000)
WHAT'S HAPPENNING ??? How is it possible that plugging back the old disk, it don't work as before ???
- PC owned since 2 years. This PC has a 80 GC Western Digital CAVIAR drive.
- He want to change this drive
- He bought a Maxtor DiamondMax 10 - 8 Mo cache - 200 Go - 7200 t/min - Interface ATA/133
- Yesterday we unpluged the old 80Gb, and put the new Maxtor instead, putting it on CABLE SELECT jumper.
- We used windows XP disk to install a new fresh install of the OS. We drove crazy,because we had error messages during install progress (various messages, differents each time). So.... we GAVE UP. He will give back the disk.
- So we plug back the OLD disk, so we are in the same conf than before and ouppppsss......
- When we start the computer, we see "PRIMARY MASTER DETECTED", with the good size. Then it remains blinking cursor for a moment, then we see windows FLAG, then freeze... and blue screen with a STOP message : 0X0000007B (0xF8B0C528 0xC0000034 0x00000000 0x00000000)
WHAT'S HAPPENNING ??? How is it possible that plugging back the old disk, it don't work as before ???
Callandor
It's possible that in the process of opening up the case and installing the new drive, you ended up loosening a cable or memory, or gave a static shock to an electronic component. It's also possible the drive received a hard physical bump which damaged the heads. You will need to test the individual components to see which is causing the problem.
ASKER
Is it possible that plugging a different kind of drive before (ATA133) and replug an older one could drive me to this trouble ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When i come back to the initial configuration, i mean only the Old Hard drive, i have the 0X0000007B (0xF8B0C528 0xC0000034 0x00000000 0x00000000 blue screen message.
It was working during 2 years before !!
It was working during 2 years before !!
Is that a Stop 0x0000007B error? That's an inaccesible boot device error. The hard drive may no longer be bootable, but you'll have to determine if that's because a Windows driver was corrupted or the drive had a hardware failure.
ASKER
yes a stop error
The drive was working 1hour ago...
Who could be responsible if two hard drive seem not to work correctly ??
The drive was working 1hour ago...
Who could be responsible if two hard drive seem not to work correctly ??
If both hard drives don't work and they do on another machine, you'll know the drives are ok. You should test to see if your machine can boot from anything, like a floppy. If it can, then the problem would be in the IDE controller, cable, or BIOS. Is the drive detected properly in the BIOS?
ASKER
Yes with the right Size for both.
I can boot with the Windows XP CDROM. But we noticed that during Windows XP installation on the NEW hard disk we had some problems in a random way like :
- Sometimes, at reboot : ntoskrnl.exe not found
I get some copy errors when installing windows xp , but its not the CD as I have used it before and I tested it on other computer and it worked fine.
Other error I get when installing is:
Sub-component Distributed Transaction. Coordination raised on exception while processing the OC_COMPLETE_INSTALLATION setup message.
d:\nt\com\com1x\dtc\ntdtc setup\src\cdtccore.cpp(lin
Error Code= Oxffffffff
The DTC service could not be installed.
Also a few times, when I was luckly enough to get through the installation, once it try to get into windows after installation it give me this error:
STOP: c0000218 {Registry File Failure}
The registry cannot load the hive (file):
\SystemRoot\System32\Confi
or its log or alternate.
It is corrupt, absent or not writable.
Beginning dump of physical memory.
Physical memory dump complete.
Contact your system administrator or techical support group for furthur assistance.
I can boot with the Windows XP CDROM. But we noticed that during Windows XP installation on the NEW hard disk we had some problems in a random way like :
- Sometimes, at reboot : ntoskrnl.exe not found
I get some copy errors when installing windows xp , but its not the CD as I have used it before and I tested it on other computer and it worked fine.
Other error I get when installing is:
Sub-component Distributed Transaction. Coordination raised on exception while processing the OC_COMPLETE_INSTALLATION setup message.
d:\nt\com\com1x\dtc\ntdtc setup\src\cdtccore.cpp(lin
Error Code= Oxffffffff
The DTC service could not be installed.
Also a few times, when I was luckly enough to get through the installation, once it try to get into windows after installation it give me this error:
STOP: c0000218 {Registry File Failure}
The registry cannot load the hive (file):
\SystemRoot\System32\Confi
or its log or alternate.
It is corrupt, absent or not writable.
Beginning dump of physical memory.
Physical memory dump complete.
Contact your system administrator or techical support group for furthur assistance.
ASKER
So we gave up , and replug the old disk. And we have the problem as I describe at the beginning
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The situation you describe may occure if recognition fromthe OS's side has been changed; In my opinion, if you can do it commit a repair of the OS:
Links:
Heres what MS has to say about this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324103
http://support.microsoft.com/kb/316401
A step by step guide to 'repair' an installation:
http://www.michaelstevenstech.com/XPrepairinstall.htm
Hope that has been helpful...
Cyber
Links:
Heres what MS has to say about this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324103
http://support.microsoft.com/kb/316401
A step by step guide to 'repair' an installation:
http://www.michaelstevenstech.com/XPrepairinstall.htm
Hope that has been helpful...
Cyber
1) Do the drives work on another computer? Or can you boot with a CD-ROM and then access the drives?
2) When you put in the new drive, did you put in a new flatcable? I once had similar problems and it turned out to be the flat cable.
3) Was your 80gig drive an ATA/133 drive. If not, are you sure your motherboard supports this?