Worst pc building experience EVER.

[agentsmith101]

...it sucks. my hard drive installs win xp pro then runs fine and suddenly crashes and starts to hang up after the bios/cmos screen. Either that or it just doesnt install win xp pro after format. Comes up with stop errors like "STOP: c0000145 {Application Error}...Application failed to restart" or while installing it says it cant read files like "cinemst2.sys" and files like that randomly (Though cinemst2.sys is most frequent.)

 

[sonz70]

Did you try googling the error code?

 

[agentsmith101]

yes, nothing that helps came up

 

[notfred]

If it's your first time, it kind of has to be the worst time ever, right? I mean, it's also the best time ever, since you've only done it once.

 

[Maetryx]

I suggest Hardware Forum but I also suggest that you use the hard drive utility disk that came with the hard drive to run some low level diagnostics.

 

[agentsmith101]

Originally posted by: Maetryx
I suggest Hardware Forum but I also suggest that you use the hard drive utility disk that came with the hard drive to run some low level diagnostics.

After format is done and if (probably) it hangs up again im gonna try that cd. Thanks, didnt think of that.

 

[sonz70]

2 seconds on google

http://hardwareanalysis.com/content/topic/10284/

 

[Ikonomi]

Try disabling write caching in the hard disk's properties hardware > properties > policies tab.

 

[agentsmith101]

Originally posted by: sonz70
2 seconds on google

http://hardwareanalysis.com/content/topic/10284/

i looked at that, his symptoms are different.

 

[MustangSVT]

hmm

tell us more.

what devices have you installed on this?

 

[Megatomic]

Originally posted by: notfred
If it's your first time, it kind of has to be the worst time ever, right? I mean, it's also the best time ever, since you've only done it once.

:beer:

agentsmith101, we all have problems with our builds at one time or another. Most of us learn from our mistakes and our skills improve with each project. Don't give up, if you do you're the only one that loses out.

 

[Joemonkey]

1. You have bad RAM

2. You are overclocking

 

[Shawn]

BSODs are usually caused by either driver issues or hardware issues. Since you just installed XP and you are getting BSODs than you probably have a bad piece of hardware. It's probably your ram or possibly even your motherboard.

 

[agentsmith101]

Currently winxp is not installed on it. Its now hanging up in just installing it. thats the main prob i cant even get in to try doing troubleshooting no safe mode or anything. (Worst case scenario ill just transfer my 40gig into my system and run it though it will be low.)

 

[oogabooga]

start swapping out hardware (hopefully this is available) i'd go ram first to see if that's the source, otherwise.. try a reformat.

gluck man : we've all had terrible builds.. well not me, i'm flawless.


fine.. i've had bad ones too

 

[sonz70]

ITs a bad ram error.

 

[agentsmith101]

i already swapped out the hard drive once, thing that confuses me is that when i ran it someone elses house it ran for three days straight and when i got back, it started crashing and i had to reformat and go for a replacement hard drive. Anyone think it could be a bad 5-6 year old 15" monitor (friend said that monitor might not be compatible with video card {fx5500 o.c}

 

[sonz70]

It...is...a..bad...ram...error....

 

[Shawn]

no the monitor would have nothing to do with it. lol.

 

[clamum]

I highly doubt it's the monitor.

Try switching out RAM like some others have mentioned (if possible).

 

[Howard]

No, any monitor you can find with a 15-pin video connector should work fine.

 

[agentsmith101]

but then how did it run for three days at my friends house and suddenly just drop dead at mine? Only thing different is the monitor...

 

[sonz70]

it is the ram

/thread

 

[UpgradeFailure]

Originally posted by: agentsmith101
but then how did it run for three days at my friends house and suddenly just drop dead at mine? Only thing different is the monitor...

RAM!!!

 

[MAME]

IT'S THE MONITOR

I WORK FOR MONITORS4LESS AND WE SEE THIS HAPPEN ALL THE TIME

DO NOT LISTEN TOO THESE IDIOTS, IT'S *NOT* A RAM ERROR!

PLEASE CONTACT ME ABOUT A SWEET 13" SHAMROCK MONITOR THAT WILL FIX YOUR PROBLEM