🚀 go-pugleaf

Dear Tris,


I had the same problem with the marvel. First I thought of a faulty videocard. 
I got a second from the reseller which had the same problems. Than I figures 
it should be the motherboard (asus p2l97). This appeared to be correct.

I have 64 MB memory in 2 dimm's of 32Mb. Apparently there was a problem there. 
From the firm where I bought the PC they replaced it with one dimm of 64 Mb 
and since then, everything is perfectly OK. Wetter it is a timing problem for 
the memory, of just a faulty chip, I don't know, but my problem is gone, and 
that's what counts.

By the way. I read a lot of shit about the Marvel in this group, but I still 
have absolutely no regrets in buying this one. I can recommend it to everyone!


All best,
Ben



In article <7d3gjq$t5q$1@news5.svr.pol.co.uk>, "Tris" 
<anon@REMOVEME.elustria.freeserve.co.uk> wrote:
>I've finally found out what was causing my lockups - memory!!!
>
>Has anyone heard of this before?
>
>I'm running Windows 98, IE 5 beta, G200 AGP graphics card with Busmatering
>turned on. Numerous PCI cards including Soundblaster Live!
>
>If I have 128 Mb fitted using 2 SDRAM chips in two slots (not utilising the
>slot nearest the processor) I get regular intermittent lockups, both in a
>game and outside of it. If I turn busmastering off the system is stable.
>
>If I remove the SDRAM chip closest to the processor chip leaving one 64 Mb
>chip fitted farthest away from the processor the system is stable.
>
>I think I'd rather have busmastering turned on and only 64 Mb - as this
>gives the best peformance under quake2.
>
>Anyone after 64 Mb SDRAM chip? <g>
>
>Btw I tried everything else, including refitting all the PCI cards into
>different slots, allocated manual BIOS IRQ's, and lastly disabling sound
>under Quake2 - this last one eased the problem a little.
>
>Tris
>
>