My original post was only to get memtest86 to work. Which it does now. I'm having random (seemingly) lock-up problems that I didn't used to have. Didn't install any new hardware. Running SuSE 9.1 pro amd64 on Giga-byte GA-K8NP (nforce 3 chipset) with and athlon XP 3200+ processor. I upgraded the nvidia driver to the new 7 series this morning and got a couple lockups. Updated the BIOS from f11 to f12 and then it wouldn't finish loading KDE before lockup. If I alt-F to a console, before KDE initializes, then I can run just fine until I switch to the graphical console. I'm not running any openGL apps (per se), however, I am an enterprise Qt license holder so I have the enterprise Qt (probably newer version than KDE running) compiled for threads and GL so maybe it is loading some of those libs just with KDE itself. I noticed in the Nvidia driver they talk about the change_page_attr problem that surely is effecting me (I am running 2.6.5). Now, if I boot to 'failsafe' and leave in init 3 and login as user and startx, so far no lockups. My plan is to just wait until 9.3 and do an upgrade to hopefully fix..... unless of course, this is something that is known to have a quick fix.... (new supplemental SuSE kernel or something) I didn't necessarily want to start a new thread for this... still poking around for more consistant re-produsable errors. B-) On Monday 21 March 2005 03:39 pm, N. Eschricht wrote:

Brad Bourn wrote:

...

the new (3.2) one DID work. made 158 passes over the weekend with 0 errors.

Guess ram isn't the problem!

Then please post more about your system (motherboard, chipset, how mauch ram, devices etc.). We also had problems with RAM on a multiprocessor opteron system and memtest found nothing. We had three different types of RAM-Chips delivered by the vendor (infinion, samsung and apacer) and the systems freezed every day twice. With the whole RAM only of one RAM-type it runs perfectly. + N. Eschricht