Hi, I just started using FLAC and am very impressed. However I have run into a problem with the current (and other) Windows executables. If I encode with a higher compression level (say 7 or 8) I stand a high probability of BSODing or just plain rebooting. Strangely enough this behavious seems to go away if I use the default 5 compression level. Has anyone else had problems like this and is there a known fix (other than encoding at lower compression). So far this is true for 1.1.0 and 1.0.4 (the only 2 I have tried) on Win2K cheers, andy c
JC> Every report we've got like that has turned out to be hardware JC> related (e.g. overclocking, bad RAM). That's actually what I thought at first since userland programs *shouldn't* be able to do this. I guess maybe the higher settings just push the system more than usual and expose hw problems (i.e. RAM). I'll check the RAM integrity tonight... cheers, andy c
--- Andrew Chung <ac@digital-coffee.com> wrote:> Hi, > I just started using FLAC and am very impressed. However I have > run into a problem with the current (and other) Windows > executables. > If I encode with a higher compression level (say 7 or 8) I stand a > high probability of BSODing or just plain rebooting. Strangely > enough this behavious seems to go away if I use the default 5 > compression level. > Has anyone else had problems like this and is there a known fix > (other than encoding at lower compression). > So far this is true for 1.1.0 and 1.0.4 (the only 2 I have tried) > on Win2KEvery report we've got like that has turned out to be hardware related (e.g. overclocking, bad RAM). Josh __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools
Maybe Matching Threads
- Undocumented behaviour of diag when replacing the diagonal of a matrix?
- sieve-extprograms strips Return-Path headers
- R 2.0.0 (PR#7272)
- Dovecot behaviour when the server's file system fails (possible feature request)
- Re: specified network name no more available