Problemmo.

[Louster]

YO BUDDIES.

So, my dad puts PCs together.
A while ago, my computer had this really odd problem where doing things like duplicating a file would result in a corrupted duplicate. Lots of weird errors floating around all over the place, random crashes and the like. It was "solved" by reducing the amount of RAM in my computer from 512mb to 384 - it seemed that something about the amount of memory was screwing stuff up (although all the seperate sticks of RAM were fine on their own - proven by a long weekend of testing.)
This was on Windows 98 first edition. I can't remember the type of memory offhand though I'm sure I could find out.
The thing is, he's recently gotten Windows 2000, put together a new computer with different makes of pretty much all the hardware, and the 512mb problem has appeared again. Solved by halving it.

HELP ME BUDDIES. Relieve this veil of ignorance. Or, if you can't do that, point me at a place where people can. (I did a quick search at the 'TechNation' website for this! But it didn't help!)

 

[FuZor]

Got any more details? like M/B??? RAM type etc???

 

[Louster]

I hadn't gone to the trouble of finding details out yet because the problem has occurred on two totally different machines, which goes to prove something or other. I was just wondering if anyone had ever heard of this before.

 

[Xavier]

you've got to eliminate the 'common factors' in this one I think...

for one, have you any idea what chipset the system is using, or for that matter if that system and the second are of similar setup....

The only OS's which balk @ or over 512mb are win9x so it's odd that windows 2000 would give similar symptoms...

Post full specs to both machines here plus details of how win2k was installed (fresh install, upgrade etc) and we'll see what we can do!

Xav

 

[Louster]

Hrm. Well I asked my dad to email me with info, this is what he said:

Motherboard: Intel D815EGEW

----------

a) OS: Windows 2000 Pro

Syndrome: works fine with 256Mb RAM. With 512Mb fitted, hard disk interface
has problems - copied files are corrupted.

----------

b) OS: OpenBSD 3.0

Syndrome: machine locks up completely, frequently. Also fxp0 network device
timeouts.




I wasn't aware there were problems with OpenBSD as well. Is it the motherboard's fault? (I think that those two setups were on the same machine.)

 

[Xavier]

hmm, what about the other machine that was experiencing similar symptoms - same motherboard?

Have either of them had a bios update since installation?

 

[Wij]

cheap generic memory can suck in more stressful situations (IE where it has to live in harmony with 3 other banks). what type is it ?

 

[Louster]

Mlech. I'll pester him for more info. Heh.

 

[old.Wuzup101]

Yes...cheep memory is probably at fualt. I had similar problems when i was running 256+128 in a AMD/Win98 machine. Both sticks would run ok by themselves (I say ok b/c they still weren't perfect). They couldn't work together very well. I ended up bringing the computer back to the place I bought it and told them that they gave me shit ram. They removed it and I went elsewhere and bought some crucial pc133. I now have 2 sticks of crucial pc133 in my box. They run perfectly together even thought they are overclocked to 150mhz are running cas2 and have 4 bank interleave turned on....I never have a problem. I'm also running XP right now...but i was using 98SE before that and didn't have any problems at all for the 8 months or so I was using it.