Help me before I seriously kill my computer...

oscaryu1

VIP Member
Specs:

E2140
P31-DS3L
hec Orion 585W
HD3850
Rosewill Case
80GB Seagate Barracuda SATAII
Samsung DVD Burner

PROBLEM 1:

Install windows. Everything fine. Download ATI CCC and other crap... MOM.SYS load failure due to no Netframework 2.0 or something, so I decide o reformat since it won't go away...

PROBLEM 2:

I select QUICK FORMAT and format. 20%, ERROR. YOUR HDD COULD NOT BE PARTITIONED BECAUSE OF ERRORS. Ok... let's do that again... 2 tries later, I go with the slower partition... it passes! yay! Then... 6% copying file... ERROR!!! kodak_dc.idn COULD NOT BE COPIED! :mad: So, I wipe the CD, change to a 24x CD Drive I found at the recycling center...

PROBLEM 3:

BSOD! 0x00000050! OMG! MY GFX? My absolutely brand new GFX has a conflict with my OS?!

Soo... what I need yall genuises to look at...

HDD
DVD Drive
GFX...

I'll seriously kick this outta my door... First time builds failed on me.
 
Yeah, run memtest, and what "we" will do is check one component at a time, checking off the possible/components problems one by one.

Anyways, it sounds like a hard drive issue to me...but I could be wrong.
 
Well I bought it from Ebay. It's a brand her Seagate Barracuda 80GB SATAII... So I suppose it's still under warranty :)
 
Just ran MEMTEST86 from a CD... 1/2 the screen on top turned black... and the bottom... was there..."Error Confidence Value"
 
Trash vista and load XP :)

Netframework is what windows uses to verifiy software and allows it to communicate with the OS. If you do not have it, it will cause all kinds of problems. Usually if you are using xp sp1 or lower it does not load with the os, you have to allow windows to do some serious updates to get it to install.

If you tried loading all of your software before doing windows updates, that might be your problem.

So reformat (not quick format, you should never use that) and reload windows. Do not load any hardware you do not absolutley need and then run windows update. Make sure netframework is installed, then load all of your other drivers and software.

Some drivers will not load at all without netframework. Netframe work is up to version 3.0 now. If you find you have an older version, upgrade it.
 
It won't matter if he uses XP or Vista if he has a hardware failure, which seems pretty obvious to me.


Oscar, try swapping your memory cards around and try running memtest again. Maybe this time it'll load and give you a better failure.
 
PROBLEM 3:

BSOD! 0x00000050! OMG! MY GFX? My absolutely brand new GFX has a conflict with my OS?!

This happens a lot with new cards, and I've noticed ATi can be quite bad at the driver issues. On my rig when I had the X1950 unless the drivers were up to date the system would crash quite happily with a BSOD.
 
if you remember me and my friends old thread from 2+ weeks ago, we had the same problem as you. Trust me, its the ram. For sure. No doubt. Take a stick out and see what happens.
 
Trash vista and load XP

Netframework is what windows uses to verifiy software and allows it to communicate with the OS. If you do not have it, it will cause all kinds of problems. Usually if you are using xp sp1 or lower it does not load with the os, you have to allow windows to do some serious updates to get it to install.

If you tried loading all of your software before doing windows updates, that might be your problem.

So reformat (not quick format, you should never use that) and reload windows. Do not load any hardware you do not absolutley need and then run windows update. Make sure netframework is installed, then load all of your other drivers and software.

Some drivers will not load at all without netframework. Netframe work is up to version 3.0 now. If you find you have an older version, upgrade it.

Thanks paratwa :) But.. I'm using XP Pro SP2 :( I never do updates... only when I'm bored... I never install crap... ever... Hmm, I'm doing a quick format on all of my computers! Is that bad?

It won't matter if he uses XP or Vista if he has a hardware failure, which seems pretty obvious to me.


Oscar, try swapping your memory cards around and try running memtest again. Maybe this time it'll load and give you a better failure.

I tried one stick at a time with XP Pro installation. Both passed! Then I put both together and they went through XP Pro Installation fine!

This happens a lot with new cards, and I've noticed ATi can be quite bad at the driver issues. On my rig when I had the X1950 unless the drivers were up to date the system would crash quite happily with a BSOD.

Damn ATI. I'll absolutely under and circumstances buy it ever again... EVER...

if you remember me and my friends old thread from 2+ weeks ago, we had the same problem as you. Trust me, its the ram. For sure. No doubt. Take a stick out and see what happens.

Both pass through the installation with no problem. Boot with no problem :(

HEY! New BSOD! 0x00000024 :) My HDD?
 
Seriously, Oscar, run memtest for 20+ hours. If it runs through without any errors, then we can safely say your memory is good.
 
oscaryu1, dont waste time with memtest, just take out a stick of ram and try it. We had random bsod's that said hdd failure, then this falure, and that, but never ram. Yet it turned out to be bad ram, so try it.
 
The difference between the regular format vs the quick format is whether or not the volume is scanned for bad sectors, otherwise they both remover the old files.


Have you checked to see if netframework is installed? It really is needed for a lot of things. And not running updates selectively is not smart. There are tons of security updates out for XP that are really needed.

I bet you have netframework 1.1 installed now, 3.0 is out and lots of newer drivers need it to work.

This is from Microsoft
http://support.microsoft.com/kb/829019
Many commercial applications from Microsoft and from third parties rely on the .NET Framework to support their core functionality. If you have the .NET Framework installed, these applications are easier to install.


I am not saying that there are no other problems with your system, but having .net will keep things running better in the future.
 
Last edited:
oscaryu1, dont waste time with memtest, just take out a stick of ram and try it. We had random bsod's that said hdd failure, then this falure, and that, but never ram. Yet it turned out to be bad ram, so try it.

Memtest86+ is the unquestioned gold-standard test for checking out memory. It is an extremely rare occasion (as in, I've only seen it happen once in twenty years) that a RAM module will pass memtest and still be bad and, with the exception of a possible bad motherboard, I have never seen a good RAM fail memtest.

Running that program is not a waste of time, it is an exceptional way of testing one's RAM with the purpose of eliminating it as the cause of failure in the machine, particularly when the problem is variable and intermittent as in this case.
 
Memtest86+ is the unquestioned gold-standard test for checking out memory. It is an extremely rare occasion (as in, I've only seen it happen once in twenty years) that a RAM module will pass memtest and still be bad and, with the exception of a possible bad motherboard, I have never seen a good RAM fail memtest.

Running that program is not a waste of time, it is an exceptional way of testing one's RAM with the purpose of eliminating it as the cause of failure in the machine, particularly when the problem is variable and intermittent as in this case.

but why do that, when you can just take out a stick of ram in 30 secs and find out if it is crap or not?
 
Memtest86+ is the unquestioned gold-standard test for checking out memory. It is an extremely rare occasion (as in, I've only seen it happen once in twenty years) that a RAM module will pass memtest and still be bad and, with the exception of a possible bad motherboard, I have never seen a good RAM fail memtest.

Running that program is not a waste of time, it is an exceptional way of testing one's RAM with the purpose of eliminating it as the cause of failure in the machine, particularly when the problem is variable and intermittent as in this case.

FYI, the Memtest86 don't work :( Top part turns black and the bottom freezes.

UPDATE - Used my other comp's DDR2-533 1GB, it made the Seagate pass diagnostics, AND it runs great w/ no BSODS...

For all to know - a bad stick of memory can cause GFX related BSODs, HDD related errors, cause HDD's to fail testing...

RMAing is going well. Newegg is great as always.

Let's hope that the G Skills 1GB I ordered for my lappy works :(
 
FYI, the Memtest86 don't work :( Top part turns black and the bottom freezes.

UPDATE - Used my other comp's DDR2-533 1GB, it made the Seagate pass diagnostics, AND it runs great w/ no BSODS...

For all to know - a bad stick of memory can cause GFX related BSODs, HDD related errors, cause HDD's to fail testing...

RMAing is going well. Newegg is great as always.

Let's hope that the G Skills 1GB I ordered for my lappy works :(

i told u :D :P:rolleyes:
 
but why do that, when you can just take out a stick of ram in 30 secs and find out if it is crap or not?

Because a memory stick doesn't always cause catastrophic failures. How would we look if the guy pulled one stick, got the machine to boot, only to have more problems down the line because the remaining stick was bad, too?
 
Back
Top