ok I have an interesting problem....

sheerdark · Post by **sheerdark** » Sun Jul 27, 2003 10:11 pm

Originally posted by rogue
Sounds like a memory problem to me. Run memtest 86 on there and see if you get any errors. The reason I say this is because my comp did the exact same thing (rebooted when copying files). However, it would also randomly reboot for no other reason, but the copying files seemed to be a repeatable example. Anyways, I fixed it by lowering my ram timings in the BIOS as well as turning off one of Abit's GAT "features".

I agree with you 100%, this would be my next step in diagnosing this problem.....hope someone here can help you.

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 12:16 am

well, unless both RAM sticks are bad, it isn't the RAM.

I did the tests ( not memtest 86 ) with only one stick in, not both, and changed them out

I will try the memtest thing now though just incase

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 12:38 am

ok the memtest thing is running now....

we shall see what that in turns

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 1:58 am

ok, so running the test with both sticks, it froze twice...

so now I am running them one by one...

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 2:34 am

ok well, it is looking like it is keeps on frezing @ the same spot now, ether stick, ether slot....

so, is that RAM or the motherboard?

BaD_HeX · Post by **BaD_HeX** » Mon Jul 28, 2003 5:49 am

try http://www.goldmemory.cz/

It sounds like a memory prob to me. If not it's the mobo itself.. related to the memory. Usually when you load large files and you have probs like a reboot, program crash, lockup it is memory related. I don't know exactly how much control you have over the clock settings on that machine but try underclocking the memory and see if that changes anything.

Post by **FlyingPenguin** » Mon Jul 28, 2003 8:35 am

Put the BIOS settings all on the "Safe" default settings to make sure you haven't got a bad setting in BIOS. If it fails in BIOS then you know it's a memory issue.

The memory could be fine, it might just not work in that computer. Doesn't happen too often anymore, but some mobos are fussy about the memory you use.

You have some memory from another system you can test in there?

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 10:42 am

Originally posted by FlyingPenguin

The memory could be fine, it might just not work in that computer. Doesn't happen too often anymore, but some mobos are fussy about the memory you use.

yeah, but the PC has been fine for a few months...

Originally posted by FlyingPenguin
You have some memory from another system you can test in there?

yeah, I can pull a stick from my rig for testing reasons

Augix · Post by **Augix** » Mon Jul 28, 2003 1:13 pm

Have you ever tried to put some gas on it and burn it ?

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 9:51 pm

ok trying memtest with a stick of my ram and it has gotten past the part it kept frezzing @

Post by **FlyingPenguin** » Mon Jul 28, 2003 10:14 pm

What I've seen happen often is you flex a stick of ram too much when you insert it and crack a trace. Just a hairline crack. Seems to work okay but as the system heats up the crack expands.

That's why one of the tests I do now is while running Windows and/or DocMemory I'll reach inside and wiggle the ram sticks a little to see if I can make it crash.

DoPeY5007 · Post by **DoPeY5007** » Mon Jul 28, 2003 10:21 pm

well, the crash still happend with my ram and memtest froze...

so, I think now I am going to look up RMA'n the MotherBoard

Post by **FlyingPenguin** » Tue Jul 29, 2003 12:34 am

Memtest runs from within Windows right? That's a worthless memory test - you could be crashing for a reason other than memory. ANY test run within windows will NOT test all your memory (Windows has to use some of it to run).

Download DocMemory and test it properly: http://www.simmtester.com/page/products/doc/docinfo.asp

If it fails or locks up with DocMemory then I'll be convinced you have a memory-related problem. It could still be PSU (voltage fluctuations will cause memory errors) but it'll help narrow it down. We'll know for sure it's not a Windows issue.

rogue · Post by **rogue** » Tue Jul 29, 2003 12:42 am

Nope, memtest runs from its own environment using a bootable floppy or cd. I bet it's similar to DocMemory, but its what all the hardcore overclockers use to test their ram

DoPeY5007 · Post by **DoPeY5007** » Tue Jul 29, 2003 12:53 am

Originally posted by FlyingPenguin
Memtest runs from within Windows right?

nope, runs from a bootable floppy

and I know it isn't the PSU, I did tests with another PSU pluged into it