Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!uunet!bu.edu!m2c!risky.ecs.umass.edu!medr0.ecs.umass.edu!giovin From: giovin@medr0.ecs.umass.edu (Rocky J Giovinazzo) Newsgroups: comp.sys.apple2 Subject: Re: What is Fatal System Error 0308? Message-ID: <1991May24.031519.19032@risky.ecs.umass.edu> Date: 24 May 91 03:15:19 GMT References: <1991May22.213859.27603@risky.ecs.umass.edu> <53246@apple.Apple.COM> Sender: usenet@risky.ecs.umass.edu (USENET News System) Organization: University of Massachusetts, Amherst Lines: 24 Nntp-Posting-Host: medr0.ecs.umass.edu In article <53246@apple.Apple.COM> dlyons@Apple.COM (David A Lyons) writes: >In article <1991May22.213859.27603@risky.ecs.umass.edu> giovin@medr0.ecs.umass.edu (Rocky J Giovinazzo) writes: >>I often get fatal system error 0308. Does anyone have any idea what >>this is? It most often occurs when running graphics programs. >Error $0308 means that the "heartbeat interrupt queue" was discovered to >be screwed up. Meaning something went wild and changed some part of memory >that it had no business messing with. > >It could *conceivably* be bad RAM chips, but most likely it is a software >problem. > >Try to narrow down the problem--does it only happen with a few specific >applications? Try removing any third-party desk accessories or setup >files and see if that has any effect; if it does, put them back one at >a time and maybe you can determine which one is misbehaving. "Flaky" >problems like this are hard to pinpoint sometimes, because just removing >something could make the problem go away "by accident", just by changing >the relative positions of things in memory. I just had work done on my machine a couple months ago and it apparently passed whatever diagnostics the dealers run. I assume the diagnostics check for bad RAM chips? Rocky Giovinazzo