win xp blue screen

when i load win xp on a NEW build, about 1/3 of the way thru it gives me the
blue screen with this code
07b 0xf78da63c 0xc0000034 00000000000 0000000000
and the win install stops--will not let me go further,when i reboot it just
goes that far.


is it an hdd failure? i have 4 of them,could it be not reading one of them?
at the top of blue screen it says run check disk/f

"bob h" <> wrote in message
news:lLWdnUffE-uqnfPZRVn-...
> when i load win xp on a NEW build, about 1/3 of the way thru it
gives me the
> blue screen with this code
> 07b 0xf78da63c 0xc0000034 00000000000 0000000000
> and the win install stops--will not let me go further,when i reboot
it just
> goes that far.
>
>
> is it an hdd failure? i have 4 of them,could it be not reading one
of them?
> at the top of blue screen it says run check disk/f
>
>

D/L a disk testing utility from the manufacturer and test the ones
involved in the install.
D/L memtest86, burn image to CD, boot and ensure there's no problem
with the memory.

If neither of these identifies the problem try again here.

Eric

--
Remove the dross to contact me directly

Let me take a stab in the dark (it's been awhile)...

The first number, 07b is the hardware interrupt "address". You take
this number and divide it by 4 to get the hardware interrupt "number".
So 7b hex divided by 4 = 1e hex. According to this table, interrupt
1e has something to do with "Points to disk base table".

http://ece.wpi.edu/~wrm/Courses/EE3803/Labs/roehrl.html

So something to do with the hard disk perhaps??

Forrest

Motherboard Help By HAL web site:
http://home.comcast.net/~mobo.help/


On Fri, 19 May 2006 11:27:45 -0600, "bob h" <>
wrote:

>when i load win xp on a NEW build, about 1/3 of the way thru it gives me the
>blue screen with this code
>07b 0xf78da63c 0xc0000034 00000000000 0000000000
>and the win install stops--will not let me go further,when i reboot it just
>goes that far.
>
>
>is it an hdd failure? i have 4 of them,could it be not reading one of them?
>at the top of blue screen it says run check disk/f
>

I think there are error codes if he searches the MS KB.

"- HAL9000" <> wrote in message
news:...
> Let me take a stab in the dark (it's been awhile)...
>
> The first number, 07b is the hardware interrupt "address". You take
> this number and divide it by 4 to get the hardware interrupt "number".
> So 7b hex divided by 4 = 1e hex. According to this table, interrupt
> 1e has something to do with "Points to disk base table".
>
> http://ece.wpi.edu/~wrm/Courses/EE3803/Labs/roehrl.html
>
> So something to do with the hard disk perhaps??
>
> Forrest
>
> Motherboard Help By HAL web site:
> http://home.comcast.net/~mobo.help/
>
>
> On Fri, 19 May 2006 11:27:45 -0600, "bob h" <>
> wrote:
>
>>when i load win xp on a NEW build, about 1/3 of the way thru it gives me
>>the
>>blue screen with this code
>>07b 0xf78da63c 0xc0000034 00000000000 0000000000
>>and the win install stops--will not let me go further,when i reboot it
>>just
>>goes that far.
>>
>>
>>is it an hdd failure? i have 4 of them,could it be not reading one of
>>them?
>>at the top of blue screen it says run check disk/f
>>
>
>

More detail...

This page calls interrupt 7b as "INACCESSIBLE_BOOT_DEVICE" and gives
some possible causes.

http://aumha.org/win5/kbestop.htm

Error codes are usually spit out by "applications". Blue screens are
problems at the hardware level, such as a device driver or the
operating system's kernal (hardware manager) software.

Forrest

Motherboard Help By HAL web site:
http://home.comcast.net/~mobo.help/


On Mon, 22 May 2006 23:03:30 +0800, "dobey" <> wrote:

>I think there are error codes if he searches the MS KB.

Hope this helps:

Stop: c000026c {Unable to load Device Driver}
"\device\floppy0\%driver% device driver could not be loaded.
Error Status was 0xc0000034
unable to load device driver

Well, yes it would be called stop code, but it is still an error code.

Either way if he searches the MS knowledge base he might have more luck.

"- HAL9000" <> wrote in message
news:...
> More detail...
>
> This page calls interrupt 7b as "INACCESSIBLE_BOOT_DEVICE" and gives
> some possible causes.
>
> http://aumha.org/win5/kbestop.htm
>
> Error codes are usually spit out by "applications". Blue screens are
> problems at the hardware level, such as a device driver or the
> operating system's kernal (hardware manager) software.
>
> Forrest
>
> Motherboard Help By HAL web site:
> http://home.comcast.net/~mobo.help/
>
>
> On Mon, 22 May 2006 23:03:30 +0800, "dobey" <> wrote:
>
>>I think there are error codes if he searches the MS KB.
>
>

Well, there is one thing for sure, LOL, stop messages have nothing to
do with interrupt addresses ! ! My stab in the dark was WAY OFF.
LOL, the egg was drooling down my face.

It does look like a good MVP driven web page though. Had to follow
up...

Forrest

Motherboard Help By HAL web site:
http://home.comcast.net/~mobo.help/

- HAL9000 wrote:
>
> Well, there is one thing for sure, LOL, stop messages have nothing to
> do with interrupt addresses ! ! My stab in the dark was WAY OFF.
> LOL, the egg was drooling down my face.
>
> It does look like a good MVP driven web page though. Had to follow
> up...
>
> Forrest
>
> Motherboard Help By HAL web site:
> http://home.comcast.net/~mobo.help/

Oops !!!!!!!1

Qed

bob h wrote:
> when i load win xp on a NEW build, about 1/3 of the way thru it gives me the
> blue screen with this code
> 07b 0xf78da63c 0xc0000034 00000000000 0000000000
> and the win install stops--will not let me go further,when i reboot it just
> goes that far.
>
>
> is it an hdd failure? i have 4 of them,could it be not reading one of them?
> at the top of blue screen it says run check disk/f
>
>
I'd start by swapping out the memory....thats usually been the culprit
in my experiences with this type of problem

-Dylan C