Look for errors in your /var/log/ files? Make sure you have a look at the X log files. I've had troubles there from time to time. I hated it when I had this trouble, which turned out to be the wrong type of RAM for my mobo. Good luck!

On 18 November 2008 at 15:26, "Christopher Stamper" <christopherstamper(a)gmail.com> wrote: My 1st experience was with a Pentium I system. I put 4 sticks of 64MB EDD RAM in it. The early generation of my mobo had timing trouble with such huge server RAM, and I had to go back to 4 sticks of 32MB EDO RAM. After that it never had troubles again. I had done all of the memtest86 stuff, and done it for days on end without error. I'd swapped individual 64MB sticks out for weeks on end, and never found the problem until I stumbled on an old app note about the board indicating its limitations. My 2nd experience like this was after upgrading my distribution and getting new drivers for my ATI Radeon card. Eventually I found out that I needed to run it in "stupid" mode, meaning no hardware acceleration, not Xorg, nor ATI native. Running hardware acceleration would cause it to freeze. Both problems involved a lot of very deliberate, change only one thing at a time, troubleshooting. In the 1st case, the error would only occur about every 2 weeks, but it would take down the system and corrupt the disks sometimes. Eventually I found a kernel oops message that would occur about 1-2 days in advance, and I'd grep'd the log files with cron to detect the trouble and reboot preemptively. I knew I'd nailed that problem when the system stayed up for 6 weeks. I wonder if the original poster's problem would go away if the system was booted into console mode only, no graphical interface. That could point at X and/or the video card/driver. Good luck.... -- Kevin _______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user

Loki Davison wrote: Possible intermittent problem with the mobo slot the graphics card is going into? -- David gnome(a)hawaii.rr.com authenticity, honesty, community _______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user

On 19 November 2008 at 16:11, "Loki Davison" <loki.davison(a)gmail.com> wrote: I had to have an ABIT board serviced. I never did put it back into my machine. But yes, it quit powering up. -- Kevin

hollunder(a)gmx.at wrote: A bit of speculation here. Perhaps the slot the video card is in is just slightly low on providing power to the video card. Ordinary use of the card works. Heavy duty use (like gaming) makes the card draw more power than the slot can actually provide, producing a crash? I guess, to check this, try a different slot for the video card (if you can). -- David gnome(a)hawaii.rr.com authenticity, honesty, community _______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user

hollunder(a)gmx.at wrote: A bit of speculation here. Perhaps the slot the video card is in is just slightly low on providing power to the video card. Ordinary use of the card works. Heavy duty use (like gaming) makes the card draw more power than the slot can actually provide, producing a crash? I guess, to check this, try a different slot for the video card (if you can).

Date: Wed, 19 Nov 2008 16:11:12 +1100 From: "Loki Davison" <loki.davison(a)gmail.com>

mmm... so a mobo problem... that would be annoying. Does that actually happen?

On Thu, Nov 20, 2008 at 12:20 PM, Lee Revell <rlrevell(a)joe-job.com> wrote: Thanks for the hint Lee, did the error that was fixed with ram timings for you come up in any mem tester? memtest86+? Should i just frob the knobs with regards to timings ? ;)

ahh no idea. Do bios updates happen often? I never even thought of it. I guess i'll check. The board is Asus p5b, with a Q6600 quad core, a nvidia 9600GT and an echo gina3g. I guess i'll have a look for other reports about the board then too. I'd assumed it had to be something to do with RAM or HD.

Loki Davison schrieb: Have you checked for a faulty or _underpowered_ PSU? I've seen many problems arising because of these sort of things, which would lead to system lockups under Windows AND Linux (although linux seems to be less prone to some hardware failures, as I had a PC once which wouldn't boot anymore under Win, but still worked around 6 months with a light *nix distro). Cheers and good luck, Raphael ;) -- ________________________________ "A mind is like a parachute - It doesnt work if it's not open." |- - - - - - - Frank Zappa - - - - - - -| _______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user