[SpaceCowboy706]

Anybody know what causes this Blue Screen of Death at Startup (Normal Mode and Safe Mode). Here is the Technical Error Code:

stop: 0x0000007B (0xF8B4E528, 0XC0000034, 0X00000000, 0X00000000)

Here is the Background behind the problem:

Buddy had a Gateway 510 Desktop with Windows XP MCE, Pentium 4 HT, 512 MB Ram, and thats about all I know of it. He came home from work one day and went to boot it up and found the BSD as mentioned above. He was unable to fix it and is loaded with money, so he just gave the PC to me (for my very own). I removed the 40GB hard drive that was in it and inserted my own 160GB seagate hard drive from my wifes ancient Computer(currently has Windows XP Pro SP2) (hoping to use this newer PC to upgrade her) and I received the BSD. I then repartioned and reformatted the Segate HD and reloaded windows XP. All went as normal until it came time to reboot at the end and then i receivved the same BSD at startup again and now that is as far as i can get. The only difference i can see between the 2 hard drives is that the original HD was connected via SATA and the one I am using is connected via IDE. I have tried changing the jumpers for the 1650 GB designating it as the Primary Master, Primary Slave, Secondary Master, Secondary Slave, and Cable select... all with the same BSD result. I have even tried using a different IDE slot as there are 4 of them... still with the same result.

I know the seagate 160 GB HD is good as it is what im using right now in my wifes old computer.

Can anyone offer anything here?


PS...
Changed out the Hard drive initially because I ran a CHKDSK /P from repair XP and it said the original HD had one or more unrecoverable errors.

Edited by SpaceCowboy706, 05 March 2006 - 11:19 AM.

[Advertisements]

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE

The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

• Disks or storage controllers that are failing, defective, or improperly configured.

• Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.

Possible Resolutions:

• During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.

• Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.

• Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.

• Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.

• Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.

Cool, goodluck

Edited by spike_hacker_inc, 05 March 2006 - 11:36 AM.

[Spike]

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE

The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

• Disks or storage controllers that are failing, defective, or improperly configured.

• Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.

Possible Resolutions:

• During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.

• Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.

• Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.

• Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.

• Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.

Cool, goodluck

Edited by spike_hacker_inc, 05 March 2006 - 11:36 AM.

[SpaceCowboy706]

WOW that looks like a very good copied text from Microsoft support...

was looking for someone who might be able to tell me how to correct it Spike. Reread my post again and you will see why i do not have any manufacturers documentation, and that there is nothing wrong with the hard drive itself (it's what im using right now on a different machine)

If you are able to post instructions on how to accomplish any of the possible resolutions you mentioned in your COPIED TEXT then please do so.

[Fenor]

Between your friend trying to fix it before he gave it to you and you messing with it after he gave it to you, have you tried clearing the cmos using the jumper? Could just be a screwy setting in the CMOS that is causing it. Another thing you can try is connecting the hard drive to the second IDE channel, leaving the cd-rom unplugged in the mean time. Have nothing attached to the primary IDE channel when you do this.

Fenor

[SpaceCowboy706]

Fenor is a stud once again... thats the kinda help im looking for...I tried switching the IDE ribbon to all four of its ports (with the CD and DVD removed)...as u suggested and got the same results. Even verified the BIOS was reading the changes in the Drive Periphials.

have you tried clearing the cmos using the jumper?

I have no idea how to do that.... if your referring to the itty bitty microscopic 2 pin jumper on 2 of the 8 pins beside the IDE Ribbon input of the hard drive that sets the drive as Primary, or secondary that didn't work before... if thats not what your referring to then please tell me how???

[SpaceCowboy706]

Anyone else

[Samm]

Hi ya

What Fenor meant by clearing the cmos was resetting the motherboards bios to default values. Now, normally this can be done by a jumper on the motherboard but as this is a Gateway (I shall refrain from using the long list of expletives that normally precedes the word 'Gateway'!) I'm not banking on there being such a jumper.


So...instead can you disconnect the power from the motherboard (ie the 20 pin ATX power connector), then remove the round 3v lithium battery. Leave the battery out for a few minutes, then replace.

This should reset the bios to defaults.

Also, make sure that the hard drive is currently jumpered as Master & is connected to the primary IDE channel.

Let me know if that makes any difference at all

[SpaceCowboy706]

Samm,

I have already googled an article from bierman, before you posted and was in the process of applying it... that solved my problem. here is the web page were i followed the instructions from and corrected my problem.

http://www.biermann....TOP_0x0000007B/

As you can see... now... it is working fine and my wife is much happier withy a faster pc.

[Samm]

Glad you've got it working now & thanks for the link

[SpaceCowboy706]

It can be very easy to get lazy on finding the solution to fixing your own problem when you are surrounded by other people who are much better than yourself at harware errors and failures... as was my case with this post.