Quake3World

hello gents!

i am helping out a bud building his new computer and when we get to "starting windows" in the XP install, it Blue screens.

we have unhooked allmost everything, i made sure the Volt's where on par if not a little over to see if that works, and nope.
i have made a install disk that contains the Chipset drivers and etc, and still BSOD's...

Setup:
Antec p180B case
Intel P-D 805 ( 2.66 X 2 )
2 gig OCZ DDR-2 800 @ cas 4 ( running at 533 cas 4 )
BFG 7900 gt oc
assus p5wd2 W/ 0501 bios
Antec true power 480watts

i'm kinda running out of idea's here, and out of time
i dont think work would take "i was working on a computer" as a valid reason to be late...

thanks.

Format c:

Yea, thanks anyway...

and woulden't you know it! after looking around on the mobo, it seems that i had the IDE ribbon for the CD-rom plugged into the Raid ports...

what i figured was the Floppy port turned out to be the IDE port.

Plugged her in, and she is good to go!

I've had a few instances where re-installing caused a blue screen for some odd known reason.
Formatting solved the problem.

Try different ram

flipper upside down ey

SATA drive and XP with SP2?

Sevensins wrote:SATA drive and XP with SP2?

This will not cause a blue screen. It will give a message when first starting saying windows cannot find a hard drive...or some such.

Ram, obviously can cause a blue screen, but not normally at this point in the setup. Normally when it gets to installing devices. Or, if you get the message saying it cannot read certain files shortly after starting to load windows for the first time.

AMid's second post seems to indicate that the problem is solved. Yes?

zolborg wrote:

Sevensins wrote:SATA drive and XP with SP2?

This will not cause a blue screen. It will give a message when first starting saying windows cannot find a hard drive...or some such.

Ram, obviously can cause a blue screen, but not normally at this point in the setup. Normally when it gets to installing devices. Or, if you get the message saying it cannot read certain files shortly after starting to load windows for the first time.

AMid's second post seems to indicate that the problem is solved. Yes?

Ram can flake out whenever it wants to. This machine is proof of that.

SOAPboy wrote:

zolborg wrote:

Sevensins wrote:SATA drive and XP with SP2?

This will not cause a blue screen. It will give a message when first starting saying windows cannot find a hard drive...or some such.

Ram, obviously can cause a blue screen, but not normally at this point in the setup. Normally when it gets to installing devices. Or, if you get the message saying it cannot read certain files shortly after starting to load windows for the first time.

AMid's second post seems to indicate that the problem is solved. Yes?

Ram can flake out whenever it wants to. This machine is proof of that.

you sure you got the right thread?

+JuggerNaut+ wrote:

SOAPboy wrote:

zolborg wrote:

This will not cause a blue screen. It will give a message when first starting saying windows cannot find a hard drive...or some such.

Ram, obviously can cause a blue screen, but not normally at this point in the setup. Normally when it gets to installing devices. Or, if you get the message saying it cannot read certain files shortly after starting to load windows for the first time.

AMid's second post seems to indicate that the problem is solved. Yes?

Ram can flake out whenever it wants to. This machine is proof of that.

you sure you got the right thread?

Yes

I had a similar issue with THIS machine (the one im using right now)

Turned out to be bad ram, which lead to a motherboard being borked as well.


Was OCZ ram too.. hmm.

SOAPboy wrote:

+JuggerNaut+ wrote:

SOAPboy wrote: Ram can flake out whenever it wants to. This machine is proof of that.

you sure you got the right thread?

Yes

I had a similar issue with THIS machine (the one im using right now)

Turned out to be bad ram, which lead to a motherboard being borked as well.


Was OCZ ram too.. hmm.

but see, he's already figured out his problem and it wasn't ram.

Didnt read the whole thread.. gg me >_<

i think it may be that you may have the IDE ribbon for the CD-rom plugged into the Raid ports...
the Floppy port might be mixed up with the IDE port.

Plug her in, and see if she's good to go!

crosses fingers for an interbuddy

Damn ax! it worked!! You da man!

Thanks for the input everyone, glad to know that i am not the only one here that dosent read the thread before replying