Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Apr 2015 14:56:42 +0100
From:      "Dave B" <g8kbvdave@googlemail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Debugging bad memory problems
Message-ID:  <553E401A.6119.163DF7C@g8kbvdave.googlemail.com>

Next in thread | Raw E-Mail | Index | Archive | Help
On 26 Apr 2015 at 23:05, Fernando Apestegu=EDa wrote:

> I booted from a memtest CD-ROM. It passed a couple of tests fine and
> then it rebooted while doing a "bit fade" test at around 93%.
> Removing the modules is tricky since this laptop has screws all
> around in dark corners (even removing the battery needs a screw
> driver). I will try to limit physical memory with hw.physmem and see
> if it makes any difference.
> 
> Thanks!
> 

Check for CPU cooling problems too, such as an obstructed cooler or grumbl=
y 
fan.  (Also if you can, check for bad power supply issues.)  

Older AMD CPU's don't take kindly at all to running too hot, unlike some I=
ntel 
devices that will start to cycle skipping to lower the disipation, just sl=
owing down 
in effect.  

"Supliment the cooling" when running such tests, RAM can disipate quite a =
bit of 
power when worked hard (as Memtest86 does.)   Elevate the laptop and waft =
air 
under it, but not in such a way as to oppose it's own intended airflow.  

Hope you find the trouble.

Dave B.




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?553E401A.6119.163DF7C>