Transferred computer parts to new tower, now BSOD 0x050

[DrLove'sKuDang]

You won't be able to use the DDR2 in your DDR3 system. Incompatible.

ok. on my way to frys i guess.


is the most plausible answer the mem sticks?


on a similar side note. when you install windows and its starts with the "loading windows files"... where are those files being saved to?


i dont think my problem is hhd related, because it freezes before i even get the the stage of picking an install location.

[DrLove'sKuDang]

Well the memory isn't it. I just got a new set and windows still won't load. =(

This is the saddest day in the history of America. I have no computer

[DrLove'sKuDang]

Well, I seem to have found the issue, but I have no idea what it's gotta do with the memory errors I was getting. I was able to reinstall windows, but upon restarted, it froze again. So I plugged in a different hhd that had windows xp on it, and it booted up right away. Eventhiugh it was in a completely different system, with different parts and drivers, it worked.


I just don't understand why a bad harddrive would bring up memory errors. It it worked well enough to allow me to reinstall windows, but then not boot up after install.

[accordztech]

Thats interesting, what if you wipe the drive and then reinstall windows...

I hate blue screens. A pain to figure out. Its not like our hondas, we all know what is happening with a symptom lol

[DrLove'sKuDang]

Thats interesting, what if you wipe the drive and then reinstall windows...

I hate blue screens. A pain to figure out. Its not like our hondas, we all know what is happening with a symptom lol

Yea no kidding. A BSOD code means nothing. Because no matter what the code is, they still say it could be a whole list of things. I racked my brain over a memory error, and I was just a damn messed up drive.

[stevediraddo]

I just don't understand why a bad harddrive would bring up memory errors.

You got an interrupt error during the memtest. this is caused when some piece of hardware is bugging the CPU when it isnt supposed to. In this case, your harddrive was likely doing something to itself, then sending a fail signal after some time had passed (S.M.A.R.T). When installing or booting windows, a file could be incorrectly loaded into memory (This environment uses Direct Memory Access) and causing the memory to lose its shit and throw the whole OS into a crash.

Long story short, any piece of hardware, in todays computers, can cause problems with any other piece of hardware. Much like modern cars in which a complicated-ass computer controls the entire goddamn car.