On Thu, Nov 20, 2008 at 1:10 PM, Lee Revell <rlrevell@email-addr-hidden-job.com> wrote:
> On Wed, Nov 19, 2008 at 8:54 PM, Loki Davison <loki.davison@email-addr-hidden> wrote:
>> On Thu, Nov 20, 2008 at 12:20 PM, Lee Revell <rlrevell@email-addr-hidden-job.com> wrote:
>>> Lockups under Windows are not normal, at least since Win2K.
>>>
>>> Try resetting BIOS to defaults, and if that does not help, fiddle with
>>> the BIOS memory settings.
>>>
>>> I had a similar problem with an Athlon XP system that I eventually
>>> worked around by changing some obscure RAM timing setting.
>>>
>>
>>
>> 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 ? ;)
>
> No, it did not. I think it was triggered by my sound card (SBLive)
> doing DMA, which would not show up on memtest. There was a well known
> problem with that card on certain VIA chipsets, but none of the
> workarounds helped.
>
> I would first reset the BIOS to defaults, then if the problem recurs,
> change one thing at a time.
>
> Are you using the latest BIOS?
>
> Lee
>
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
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Thu Nov 20 08:15:01 2008
This archive was generated by hypermail 2.1.8 : Thu Nov 20 2008 - 08:15:02 EET