View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 22 posts ] 
Go to page Previous  1, 2

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Thu Jan 05, 2006 7:39 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
tkoster wrote:
All were in the 5th test, which is typical of AMD processors according to the documentation.
I seem to remember that this is where I had the problem too (I have an AMD 1700XP), but it was fairly reproducible on my box.

tkoster wrote:
I don't know how rock solid memory has to be or how forgiving linux is to the errors, but I suspect that when those little errors come in clumps, it could cause the problems I'm experiencing.
This depends on where the error occurs, but all it takes is a single bit in error and it can completely screw your system.

tkoster wrote:
1) How did you tweak your settings to make the memory more stable?
I cant remember offhand, but I will endeavour to have a look tonight.

tkoster wrote:
Does your system take a noticable hit when you use them?
I think it took a bit of a hit, but unreliable memory is intolerable, and my system still performs OK with Standard def DVB with the slower memort timing, so I'm happy.

tkoster wrote:
2) If I have to replace the memory, what do I look for? I bought Kingston value ram because I thought they were a reputable producer. But I know there are different variations even there that I've not taken the time to learn the distinctions on CL 1, 2 or 3, ECC or non-ECC, and so on. Are there ways of improving my odds of solid memory?
Not sure about this. It could even be motherboard related, so there is no gaurentee that replacing the memory will solve the problem.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jan 05, 2006 8:24 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Many motherboard makers tend to "push the envelope" on memory timings in their BIOS so that their product gets a performance edge in reviews. What you need to do to "detune" the memory access is highly BIOS dependent. See your BIOS manual for details. If you've lost it or tossed it, visit your MB makers website and DL the PDF version.

The first thing to look at is that you've optimized the "performance" settings in the BIOS for stability. This means you haven't selected "turbo" or "aggressive" timings for your bus and RAM. After that it's time to set specific CAS/RAS timings. The general technique is to let the BIOS autodetect the settings in conservative or stability mode, switch to manual or expert mode and bump the numbers upwards a notch or two to get longer CAS/RAS delays. You might also check the Kingston website to get their recommended timings for the RAM you have and make sure the BIOS isn't trying to squeeze blood out of a turnip.

Any loss of performance should be small, say 5% or less in real world cases.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jan 07, 2006 10:41 am 
Offline
Joined: Mon Apr 04, 2005 10:50 am
Posts: 120
Just an update. I checked out the stats on my memory - it is Kingston Value RAM 3200 CL3. According to the manual that came with my board that should be fine. However, on the ASUS webpage, they recommend CL2.5. The difference is slight and CL3 should be fine for most applications. However, mythtv isn't most applications.

So I went into my bios and found the settings tjc was talking about.

My bios was already set for stable settings based on my RAM
So I changed the settings from auto to user defined which made 4 more settings related to RAS and CAS available. 2 were already maxed out. The other two I bumped up from 3 to 4.Then saved and exited.

I ran memtest86 overnight and no errors.
So far no freeze ups or lockups in mythtv either.

Many thanks for helping me with a problem that has been plaguing me for a year.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Mar 31, 2006 12:50 pm 
Offline
Joined: Tue Dec 20, 2005 3:35 pm
Posts: 57
Location: Seattle, WA
tkoster wrote:
So my question is:
1) How did you tweak your settings to make the memory more stable? Does your system take a noticable hit when you use them?
2) If I have to replace the memory, what do I look for? I bought Kingston value ram because I thought they were a reputable producer. But I know there are different variations even there that I've not taken the time to learn the distinctions on CL 1, 2 or 3, ECC or non-ECC, and so on. Are there ways of improving my odds of solid memory?

Can you offer guidance?


Did you ever get this resolved? I think I may be experiencing the same freezing problems. I'm using a KT-600 MB with a Duron CPU and mythtv seems to freeze ramdomly.
________
Chevrolet Epica


Last edited by mz4wheeler on Thu Feb 24, 2011 1:15 am, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Apr 03, 2006 10:27 pm 
Offline
Joined: Mon Apr 04, 2005 10:50 am
Posts: 120
It is definitely a problem with defective memory. My stick appears to be marginal. It took extended testing to get it to act up. Once I figured that out, manually setting the bios settings to slower speeds made my box stable. It will still freeze up on occasion, but only once a month. I can live with that until I can get a replacement.


Top
 Profile  
 
PostPosted: Sun May 28, 2006 9:54 am 
Offline
Joined: Tue Dec 20, 2005 3:35 pm
Posts: 57
Location: Seattle, WA
tkoster wrote:
It is definitely a problem with defective memory. My stick appears to be marginal. It took extended testing to get it to act up. Once I figured that out, manually setting the bios settings to slower speeds made my box stable. It will still freeze up on occasion, but only once a month. I can live with that until I can get a replacement.


I suffered through this for a long time, till I desperately tried almost every BIOS option. I finally found the provlem.... The AGP aperature size!

My GEFORCE4 MX4000 video card comes with 128MB or ram, so my BIOS detected this (properly), but also seemed to be adjustable. When I bumped it to 256 the video playback was jittery. After I set it to 64 the system suddenly became stable.

"dmesg" now shows:
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: AGP aperture is 64M @ 0xd8000000

This was unintuitave, especially since the graphics card had "128MB" as a great feature of the card. Why 64M vice 128MB? I have no idea. Any theories?
________
V8


Last edited by mz4wheeler on Thu Feb 24, 2011 1:15 am, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Feb 15, 2007 10:43 am 
Offline
Joined: Sat Nov 05, 2005 4:37 am
Posts: 191
Location: Cornwall - uk
G'day all,

Well this is still a problem for me.
I have now just got one large pata drive having removed the sata from the mix.

It seems to show up when the pvr350 wants to record something while we are watching a recording.

If it happens I can usually guess that we will have a recording starting, does not always do it though.

_________________
--
stinga

as of 17-May-2018
R8.2 - sort of working.
MB: gigabyte GA-P43-ES3G | RAM: 2GB
VGA: PNY Nvidia GT240 1GB
4 x Technisat skystar 2 dvb | 1 x TBS6981 dvb-s2
pata: 1x300Gb | sata: 2x1Tb 2x2Tb
Problems:
TBS6981 Does not work.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 22 posts ] 
Go to page Previous  1, 2



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 15 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu