System crash after unhandled exception during pending A/D conversion

Anybody experienced similar phenomena and/or has a fix ?:
I'm using the DAQ components (6.0) for ActiveX (subset delivered with the NI-DAQ driver-CD) from VB 6.0 (SP6) to control measurements with a 6040/6070 E-series card.
The application starts a delayed (with CWpulse) A/D conversion and waits for the "acquired data" event. In the meantime, several other application-handled events can happen (mouse, kbd, timer, network link).
We have a watchdog application which monitores the main application, but...:
If there occurs an unhandled exception while the A/D conversion is pending, the system crashes after the "serious error..." message / error reporting of the O/S is confirmed - both on Win2000 and XP (SP1a). One can here the HDD retract and the (mostly) reboot. Two times, the system locked up so bad, it won't even restart until a complete power-cycle - of course at the customer's site... :-(
That kind of behaviour is reproduceable when I force an exception (e.g. div-by-zero) after the CWAI component was started.
I tried that on systems with NIDAQ 6.9.3 and also with 7.1, but both give me no chance to return to the O/S after the application failure.
Does anybody know about the reason for such unfriendly behaviour or can help me to solve that problem?
Any help will be much appreceated!

While DAQmx is not officially supported through Visual Basic 6.0, it can be done. I am not a VB6 user and haven't tried it, but you can look at the following Knowledge Base explaining how to accomplish this. You can also look at the following MSDN article explaining how to access DLLs and the Windows API through VB. Essentially you end up making DLL calls as you normally would through VB using the DAQmx C API. I hope this helps.

Similar Messages

IMovie has frozen up on me. I've tried rebooting and reinstalling the apps- no help. I can play some of the files- but I can't get into the libraries.Even when I can get something to play the whole system crashes after a few minutes. What can I do?

I desperately need your help. I was working on iMovie last night when the thing froze up on me. I've tried rebooting. I've tried reinstalling the apps. No change. I can play some of the files- although I can't tell which ones will play until they magically appear. I can't get into the project library or the event library. The bar that lets me scroll through the clips is gone. Even when I can get something to play the whole system crashes after a couple of minutes and generates a "problem report" that says "iMovie Quit Unexpectedly". This all started when I was adding cutaways- and one clip just would not load. After I tried several times everything froze up. Have you ever heard of something like this? Maybe I pushed a button or somehow changed a setting? Maybe some of the video is corrupt? What do you recommend?
Thanks for any advice you can offer!

I have tried all the above and nothing seems to work. Any other suggestions?

System crash after sleep mode

Hello,
Since I've updated to Tiger, the system always crashes after getting back from sleep mode, upon trying to use Firefox or Thunderbird. I can't even restart using alt-apple-esc and will have to use the power button.
Has anyone experienced the same problem? Does anyone know a solution to that problem?
Thanks a lot in advance!!
Additional info:
I'm using airport to connect to the internet (DSL connection with a Zyxel Prestige 600 Router).
Firefox 1.5.0.2; Thunderbird 1.5; Norton Internet Security 3.0
imac g5 Mac OS X (10.4.6)

Hi Pat,
just checked. Firefox is running java 0.9.5
Then you're OK with that...
However upon checking the java version on my mac, I got the following answer: "Exception in thread "main" java.lang.NoClassDefFoundError: version".
What does that mean? How to fix it?
However, there's something wrong with your Java installation:
A NoClassDefFoundError is thrown when a classloader or the Java Virtual Machine tries to load a class and no definition of the class can be found. This could happen when using the new expression or during a normal method call. The reason this would occur at runtime is because the missing class definition existed when the currently executing class was compiled, but now that definition cannot be found.
If that sounds to geeky, then just check (via Software Update) if you're running the latest version of Java or if there's an update waiting to be installed in your system
Did you notice any other problematic Java-related behaviour?
Safari runs OK?
Did you take all the appropriate steps before upgrading to 10.4.6? What version have you been runnig before 10.4.6?
Macs running 9.x, Macs running 10.4.x and SGI workstations running Irix 6.5.x

System crashes after waking; problems with distnoted, graphics chip error

I am running 10.3.9 on a Dual 1 GHz G4, with 1.5 GB SDRAM, a GeForce4 Ti 4600 LCD display, and a LaCie 1394 external drive. I have recently started to put my computer to sleep at night, rather than leaving it running 24 hours a day (I also installed sleepwatcher, to allow me to put my computer to sleep remotely, and anacron, to allow the nightly system maintenance jobs to continue to run). This was working fine for about a week, but for the last two days, when I woke my computer up in the morning, I got kernel panics after a few minutes. First some aspects of the display would start to get mangled (e.g. strange lines appearing, some text that I typed not showing up, icons in the dock looking speckled, etc.), then some applications would stop responding, and then a minute or so later I would get the feared kernel panic message ("You need to restart your computer" in multiple languages).
This problem only seems to occur after the computer has been asleep for a long time (I've only experienced it after it's been asleep for 12 hours or so, and not when it's only been asleep for a few minutes). The only thing I can think of that I've changed in the last few days is an AppleScript that mounts my external LaCie drive (using "do shell script diskutil mountDisk ...") before backing up my files - using FoldersSynchronizer - then putting my computer to sleep (before I was never UNmounting this drive, so I didn't have to mount it in the AppleScript - I was still using the script to back up the files then put the computer to sleep).
I have tried running Apple's Disk Utility (both to repair the permissions, and to repair the disk), DiskWarrior (to rebuild my startup disk), fsck, and TechTool Deluxe. None seemed to reveal any major errors except the "Surface Scan" in TechTool, which failed, presumably because of media defects in the disk (but my understanding is that fixing this would require reformatting my disk, something that I only want to do as a last resort).
My system.log shows the following, from the time I woke my computer to the time I restarted (I've highlighted some suspicious-looking lines). It seems like the problem might either be occurring in distnoted, or with the graphics chip. Any thoughts on how I can determine the cause of the problem?
Mar 28 10:58:31 localhost kernel: System Sleep
Mar 28 10:58:38 localhost kernel: System Wake
Mar 28 10:58:38 localhost kernel: Wake event 0020
Mar 28 10:58:38 localhost kernel: enableClockSpreading returned with 0
Mar 28 10:58:38 localhost kernel: AppleNMI unmask NMI
Mar 28 10:58:38 localhost kernel: Adaptec warning: Resetting SCSI bus.
Mar 28 10:58:38 localhost kernel: FWOHCI handleSelfIDInt - nodeID not valid (reset bus and retry 1)
Mar 28 10:58:38 localhost kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Half Duplex
Mar 28 10:58:44 localhost mDNSResponder[186]: mDNSResponder Waking at 1236250
Mar 28 10:58:44 localhost SymMissedTask - parent[233]: sleeptime recorded: Mon Mar 27 16:05:06 2006
Mar 28 10:58:44 localhost SymMissedTask - parent[233]: waketime is: Tue Mar 28 10:58:44 2006
Mar 28 10:59:04 localhost crontab[436]: (root) LIST (root)
Mar 28 10:59:04 localhost crontab[438]: (root) LIST (sage)
Mar 28 11:05:09 localhost crashdump: Unable to determine CPSProcessSerNum pid: 151 name: distnoted
Mar 28 11:05:09 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/sbin/distnoted": exited as a result of signal 10 [pid 151]
Mar 28 11:05:09 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/distnoted.crash.log
Mar 28 11:05:09 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/distnoted.crash.log
Mar 28 11:05:10 localhost kernel: Graphics chip error! Restarted.
Mar 28 11:05:15 localhost last message repeated 2 times
Mar 28 11:05:19 localhost crashdump: Unable to determine CPSProcessSerNum pid: 448 name: distnoted
Mar 28 11:05:19 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/distnoted.crash.log
Mar 28 11:05:19 localhost mach_init[2]: Server 180b in bootstrap d03 uid 0: "/usr/sbin/distnoted": exited as a result of signal 10 [pid 448]
Mar 28 11:05:19 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/distnoted.crash.log
Mar 28 11:05:20 localhost kernel: Graphics chip error! Restarted.
Mar 28 11:05:29 localhost last message repeated 7 times
Mar 28 11:06:59 localhost last message repeated 12 times
Mar 28 11:07:01 localhost crashdump: Started writing crash report to: /Users/sacks/Library/Logs/CrashReporter/MouseWorks Background.crash.log
Mar 28 11:07:01 localhost kernel: Graphics chip error! Restarted.
Mar 28 11:07:02 localhost crashdump: Finished writing crash report to: /Users/sacks/Library/Logs/CrashReporter/MouseWorks Background.crash.log
Mar 28 11:07:11 localhost kernel: Graphics chip error! Restarted.
Mar 28 11:07:14 localhost last message repeated 2 times
Mar 28 11:07:24 localhost kernel: NVKernel::initializeChannel time out.
Mar 28 11:08:43 localhost syslogd: restart
Yesterday's crash looks similar, except that the Graphics chip error occurs 13 seconds before the distnoted error (rather than after the distnoted error), and rather than a crash of "MouseWorks Background" there was a crash of "WindowServer". A log file from a few days ago, when I woke my computer up without a crash, has one line that is now absent: Mar 23 08:48:43 nitrogen kernel: AFPSleepWakeHandler: waking up.
panic.log contains:
Tue Mar 28 11:08:55 2006
Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x000000003AA4C34E PC=0x000000000099E54C
Latest crash info for cpu 1:
Exception state (sv=0x2CD3AC80)
PC=0x0099E54C; MSR=0x00009030; DAR=0x3AA4C34E; DSISR=0x40000000; LR=0x0099EFA0; R1=0x19D63AC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0099FF28 0x0099EFA0 0x00997468 0x00988020 0x0027E650 0x00280324 0x0007AC48 0x00021668
0x0001BCE8 0x0001C0F0 0x00094318 0x00000000
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(3.4.2)@0x981000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x4b3000
dependency: com.apple.iokit.IOGraphicsFamily(1.3.5)@0x4c6000
dependency: com.apple.NVDAResman(3.4.2)@0x4fc000
dependency: com.apple.iokit.IONDRVSupport(1.3.5)@0x4e6000
Proceeding back via exception chain:
Exception state (sv=0x2CD3AC80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2CDA8000)
PC=0x900078B8; MSR=0x0200F030; DAR=0xE0FA8000; DSISR=0x42000000; LR=0x90007438; R1=0xBFFEE3D0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 1): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x2CD3AC80)
PC=0x0099E54C; MSR=0x00009030; DAR=0x3AA4C34E; DSISR=0x40000000; LR=0x0099EFA0; R1=0x19D63AC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0099FF28 0x0099EFA0 0x00997468 0x00988020 0x0027E650 0x00280324 0x0007AC48 0x00021668
0x0001BCE8 0x0001C0F0 0x00094318 0x00000000
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(3.4.2)@0x981000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x4b3000
dependency: com.apple.iokit.IOGraphicsFamily(1.3.5)@0x4c6000
dependency: com.apple.NVDAResman(3.4.2)@0x4fc000
dependency: com.apple.iokit.IONDRVSupport(1.3.5)@0x4e6000
Exception state (sv=0x2CDA8000)
PC=0x900078B8; MSR=0x0200F030; DAR=0xE0FA8000; DSISR=0x42000000; LR=0x90007438; R1=0xBFFEE3D0; XCP=0x00000030 (0xC00 - Sp
The distnoted.crash.log refers to the following exception:
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000006
(I can post this whole log if it would be helpful.)
Any thoughts on what might be causing this problem? I will continue to test the effects of changing various aspects of my configuration, but since I can only get the problem to occur once a day (after my computer has been asleep for a while), it might take me a few days or weeks to track the problem down through blind trial-and-error.
Thanks!
Dual 1 GHz G4 Mac OS X (10.3.9) 1.5 GB SDRAM, GeForce4 Ti 4600 LCD display, LaCie 1394 external drive

After a little experimentation, I've managed to narrow the problem down a little, but still haven't resolved it. My computer still crashes almost every time I wake it up after a long sleep (multiple hours). Things work fine for a few minutes, but then some aspects of the display start to get mangled (e.g. strange lines appearing, text becoming distorted, etc.), then some applications start crashing and the system hangs. Sometimes I get a kernel panic, but not always - but I always need to reboot to solve the problem.
The errors in the system log files differ from crash to crash, but the one thing that seems to be consistent is that I get a "Graphics chip error". Is this usually a hardware problem, or can it be due to a software problem? Sometimes this graphics chip error is the first error to occur, although sometimes an application will crash a few seconds before the graphics chip error is recorded in the system.log.
In my original post, I suggested that the problem might be due to an AppleScript that mounts an external drive. I have since determined that this is NOT the cause of the problem.
Any thoughts on what might be going on?
Here's the relevant part of the system log file from today's crash:
From /var/log/system.log:
Mar 31 13:52:18 nitrogen kernel: System Sleep
Mar 31 13:52:24 nitrogen kernel: System Wake
Mar 31 13:52:24 nitrogen kernel: Wake event 0020
Mar 31 13:52:24 nitrogen kernel: enableClockSpreading returned with 0
Mar 31 13:52:24 nitrogen kernel: AppleNMI unmask NMI
Mar 31 13:52:24 nitrogen kernel: Adaptec warning: Resetting SCSI bus.
Mar 31 13:52:24 nitrogen kernel: FWOHCI handleSelfIDInt - nodeID not valid (reset bus and retry 1)
Mar 31 13:52:24 nitrogen kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Half Duplex
Mar 31 13:52:30 nitrogen mDNSResponder[159]: mDNSResponder Waking at 19764350
Mar 31 13:52:30 nitrogen mDNSResponder[159]: -1: DNSServiceRegister("Bill's Mostly Celtic Music", "daap.tcp.", "local.", 3689) failed: Client id -1
invalid (-65549)
Mar 31 13:52:30 nitrogen mDNSResponder[159]: -1: DNSServiceRegister("iTunesCtrl5DC89B66EC5DD60B", "dacp.tcp.", "local.", 3689) failed: Client id
-1 invalid (-65549)
Mar 31 13:52:30 nitrogen SymMissedTask - parent[240]: sleeptime recorded: Thu Mar 30 17:58:59 2006
Mar 31 13:52:30 nitrogen SymMissedTask - parent[240]: waketime is: Fri Mar 31 13:52:30 2006
Mar 31 13:52:50 nitrogen crontab[659]: (root) LIST (root)
Mar 31 13:52:50 nitrogen crontab[661]: (root) LIST (sage)
Mar 31 13:57:07 nitrogen kernel: Graphics chip error! Restarted.
Mar 31 13:57:24 nitrogen last message repeated 19 times
Mar 31 13:57:24 nitrogen crashdump: Started writing crash report to: /Library/Logs/CrashReporter/WindowServer.crash.log
Mar 31 13:57:24 nitrogen crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/WindowServer.crash.log
Mar 31 13:57:25 nitrogen kernel: Graphics chip error! Restarted.
Mar 31 13:57:31 nitrogen last message repeated 42 times
Mar 31 14:00:00 nitrogen CRON[667]: (root) CMD ("/Library/Application Support/Symantec/Scheduler/SymSecondaryLaunch.app/Contents/schedLauncher" 1 "/Applications/Symantec Solutions/LiveUpdate.app/Contents/MacOS/LiveUpdate" " " "oapp" "aevt" "exAG" "-update LUdf -liveupdatequiet YES -liveupdateautoquit YES")
Mar 31 14:00:00 nitrogen /Library/Application Support/Symantec/Scheduler/SymSecondaryLaunch.app/Contents/schedLauncher[667]: launch for id = 1 event = oapp result = 0
aped[186]: Attach denied: super-user process, for LiveUpdate[674]
aped[186]: Attach denied: super-user process, for loginwindow[686]
aped[186]: Attach denied: super-user process, for SecurityAgent[690]
aped[186]: Attach denied: super-user process, for IRTool[710]
aped[186]: Attach denied: super-user process, for loginwindow[836]
aped[186]: Attach denied: super-user process, for SecurityAgent[839]
Mar 31 14:01:55 nitrogen sudo: sacks : TTY=ttyp1 ; PWD=/private/var/log ; USER=root ; COMMAND=/sbin/shutdown -r now
Mar 31 14:01:55 nitrogen shutdown: reboot by sacks:
Mar 31 14:01:57 nitrogen syslogd: exiting on signal 15
Mar 31 14:08:44 localhost syslogd: restart
Dual 1 GHz G4 Mac OS X (10.3.9) 1.5 GB SDRAM, GeForce4 Ti 4600 LCD display, LaCie 1394 external drive

System Crash after waking from sleep

Hi guys,
Running 10.9.2 on 3.5 GHz Intel Core i7, 8GB RAM, GeForce GTX 775M, 3TB Fusion Drive. No extras added - everything fitted by Apple. Only thing attached is the CD drive via USB, the Bluetooth mouse and keyboard and the ethernet cable.
Today I have had 5 or 6 system crashes. What happens is that the spinning beach ball kicks off and nothing will work except holding the power to restart the machine.
I think that each time it has happened has been after the machine wakes from sleep and doesn't always happen immediately but after a few minutes or so.
I have run Disk Utility on startup to Repair Disk Permissions and Repair Disk. I have reset PRAM etc.
As far as I know nothing has been installed from before, other than the Epson Printer Drivers 2.1.7 update combo from the Apple Site to get an old scanner to work. Didn't have problems the day I installed that (yesterday).
One thing I have had probably more so since 10.9.2 is the internet speeds slow down (both WiFi and ethernet). But no problems with the modem / router that I know of and my ISP can find no problems. Interestingly I wonder whether this has also happened from sleep (eg broadband speeds getting slower).
I'm not quite sure where to find any possible error logs or which ones may be useful but any help is much appreciated. Thanks

If anyone else has this problem and maybe to help...
I found that the cause of my system crashes was somewhere within the Epson printer drivers and other associated drivers I downloaded from - http://support.apple.com/kb/dl1398. (Epson Printer Drivers v2.17 for OSX).
As you're unable to 'show package contents' on right-click from this downloaded file, I installed the excellent Pacifist and looked at the files within the download listed above. I then manually removed every trace of every file except the one specific to my need (an Epson Perfection 1670 scanner). With those files gone, I haven't had any problems.
So I believe my system crashes were related to a file within the Epson Printer Drivers v2.17 for OSX.

System crash after recent update

Hi all,
As of yesterday, my laptop has started crashing after a little while open (sometimes right away, sometimes ten minutes in, sometimes right after bios). I believed it was to do with the recent alsa-utils update and I downgraded that package which helped for a little bit. When it updated again and the core dump from the previous update disappeared, I upgraded and the problem starting happening again. Then I downgraded and no change.
So I think it is not to do with alsa anymore...but I can find no information at all in dmesg or journalctl. There seem to be no errors, warnings whatsoever. I have tried chrooting in and looking at all the logs but to no avail.
The update that broke my system installed the following:
alsa-lib alsa-utils gcc-libs gcc isl kmod libcdio-paranoia pyalpm namcap
I have since downgraded both isl and kmod and it looks my laptop is running okay so far. After this update I also updated the kernel, but running from the fallback initramfs did not change the issue so I don't think it was that either.
I have trawled the forums for recent problems with recent updates .ut did not find anything apart from the alsactl core dump.
Does anyone know if there are any problems with the above packages? Or if there are other important logs other than journactl, dmesg, and pacman.log I can try looking at to troubleshoot this? I apologise for not being able to provide much more information, as I said I can't seem to find anything out of the ordinary in the aforementioned logs.
Any help would be appreciated.

Crash still occurs...now found this in dmesg
[ 2.425173] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20121018/utaddress-251)
[ 2.425179] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425250] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
[ 2.425254] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425258] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 2.425260] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425261] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 2.425263] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425264] lpc_ich: Resource conflict(s) found affecting gpio_ich
I have looked online about these though, and so far it looks like it doesn't actually make anyone crash
EDIT: Also found that this is not actually a kernel bug...hmm.
Last edited by thesystematic (2013-04-16 00:51:03)

System Crash after updating Boot Camp beta 1.3 to 1.4

After dowloading the latest BootCamp version 1.4, I double clicked on the icon and the Installation started. I have an option to upgrade the BootCamp currently installed in my system which is version 1.3. And so I clicked on the "Upgrade" button, I waited for about five minutes but then nothing happened. So clicked on the "Go Back" button and just cancelled the installation. I restarted the system and then the screen just went black and the BSD something prompt appeared. I restarted several times but the same Black screen with the BSD prompt happened. I called up support and was able to recover my system after reinstalling the entire OS. The support guy told me they already got several calls with the same system crash problem after updating the BootCamp. Just wondering what just happened?

I just bought the new Mac OS Leopard, it already comes with built-in Boot Camp.

System crash after patch installation

After the installation of some actual patches the system crashes. I've a SUN Solaris 5.8 installed on a ultra sparc machine. I heard about a patch that leads to a system crash if there are not sysc. mirrors. Does anyone know this patch?

It was'nt possible to send an E-Mail at Noel.del@Rosario
For that reason here is the patch listing:
108434-04 108919-15 109134-28 109695-03 110389-05 110934-13 111883-14
108434-09 108919-17 109147-12 109778-14 110453-03 110934-16 111883-23
108434-10 108919-20 109147-20 109783-02 110453-04 110945-04 111958-02
108434-14 108921-20 109147-21 109793-12 110460-13 110945-07 111958-03
108435-04 108940-61 109147-27 109793-14 110460-23 110945-08 112003-03
108435-09 108949-07 109149-02 109793-23 110460-26 110951-03 112039-01
108435-10 108949-08 109152-02 109805-04 110461-03 110951-05 112138-01
108435-14 108968-07 109181-04 109805-12 110609-04 110953-06 112161-03
108528-12 108968-08 109202-05 109805-15 110615-05 110955-04 112168-03
108528-17 108968-09 109223-02 109805-17 110615-08 110957-02 112218-01
108528-19 108974-14 109223-04 109815-20 110615-10 111023-03 112237-06
108528-29 108974-25 109234-09 109862-03 110662-06 111085-02 112237-07
108652-46 108974-27 109238-02 109873-22 110662-09 111111-03 112237-10
108652-61 108974-37 109277-02 109882-05 110662-11 111177-06 112254-01
108652-66 108975-05 109277-03 109882-06 110662-12 111293-04 112325-01
108652-78 108975-06 109279-18 109885-09 110668-02 111299-04 112396-02
108725-06 108975-08 109318-21 109885-14 110668-03 111302-02 112425-01
108725-11 108977-02 109318-28 109887-18 110668-04 111308-04 112438-02
108725-12 108981-07 109318-31 109888-13 110700-01 111317-05 112459-01
108725-15 108981-09 109318-34 109888-15 110723-04 111321-03 112472-01
108727-09 108981-10 109320-04 109888-20 110723-05 111325-02 112609-02
108727-19 108981-13 109320-06 109893-04 110723-07 111327-05 112668-01
108727-22 108985-03 109320-09 109896-24 110820-10 111504-01 112792-01
108727-26 108987-07 109322-09 109898-05 110838-05 111588-04 112796-01
108773-18 108987-09 109324-03 109904-05 110838-06 111606-02 112846-01
108806-12 108987-12 109324-04 109922-04 110842-08 111606-03 113648-03
108806-15 108987-13 109324-05 109928-05 110842-10 111606-04 113650-01
108806-17 108991-18 109326-06 110068-04 110842-11 111624-05 113650-02
108813-17 108993-05 109326-09 110283-05 110896-02 111626-01 113685-05
108827-12 108993-11 109326-10 110283-06 110898-06 111626-03 113687-01
108827-34 108993-13 109326-14 110286-04 110898-08 111659-03 113792-01
108827-40 108993-32 109328-03 110286-10 110898-09 111659-07 114162-01
108869-11 109007-06 109354-22 110286-11 110903-02 111792-09 114673-01
108869-19 109007-07 109458-03 110322-02 110903-05 111826-01 114802-02
108869-22 109007-09 109460-10 110335-03 110903-07 111874-02 114984-01
108875-10 109007-15 109657-06 110380-04 110916-03 111874-05 115576-01
108875-12 109077-14 109657-08 110386-02 110916-04 111874-06 115797-01
108875-13 109091-05 109657-09 110386-03 110916-05 111881-01 115827-01
108899-04 109091-06 109667-04 110387-04 110934-04 111881-02 116602-01
108901-06 109134-27 109667-05 110387-05 110934-10 111881-03 116610-01

Why does Final Cut cause a hard system crash after upgrading computer's memory?

2x2.8 gHz Quad-Core Intel Xeon MacPro that orginally came with 2gBs of memory. We upgraded to 4gBs of memory by adding 2 1gB ram chips. Ever since, Final Cut Pro has been causing hard system crashes. Does anybody have an idea why this is happening?

Installing memory is very specific
the correct type of DIMMs must be installed in the correct slots dependant on the type of processor fitted
install exactly as per the Mac Pro guidelines here:
Mac Pro Memory DIMM Instalation
you will have to reload the web page a few times after the page warning to down load correctly (command R)
if it is per the instructions and your having trouble, the DIMMs are most likely faulty

System crashing after running a few applications/games after extended use

So, I know that everyone is going to say that temperature might be an issue, but I believe it might be due to a defect/software error because my CPU/GPU is very well cooled, and this only started very recently... I have taken all measures to get a new case,
more fans, clean out entire GPU and dusted everything very immaculately but it still seems to crash... I have no idea on how to see how/why my system crashed though.. there is no blue screen just a black screen.
Can anyone help me?

https://onedrive.live.com/redir?resid=ED07DBB027FFA77F!673&authkey=!AKclPJjsvZjTELA&ithint=file%2c.rar
Here it is
EM
This one DMP is called a BCC124 and is hardware related. Since it references AuthenticAMD I would run the CPU stress test first.
You also really need to update to SP-1 as there are many bug fixes in it.
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications,
games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether
the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Wanikiya and Dyami--Team Zigzag

System Crashes after Blue Dots

It's mainly light blue dots that sometimes appear in small parts of contrast, like for example along the shadow of a window or something. Then if time goes by the blue dots become so many that they're all over my screen. They start creeping all over until my computer malfunctions, vertical lines of either blue or yellow appear and start flashing and kind of going from left and right like a meter would measure volume. Then my mouse stops moving, and shortly thereafter my system crashes!
It happens a few times a day. I've tried fsck and Disk Utility but it doesn't fix it. I know its not my OS because i recently changed from 10.2.8. to 10.4.2. and the problem carried on. Could I have a virus?

It's mainly light blue dots that sometimes appear in small parts of contrast, like for example along the shadow of a window or something. Then if time goes by the blue dots become so many that they're all over my screen. They start creeping all over until my computer malfunctions, vertical lines of either blue or yellow appear and start flashing and kind of going from left and right like a meter would measure volume. Then my mouse stops moving, and shortly thereafter my system crashes!
It happens a few times a day. I've tried fsck and Disk Utility but it doesn't fix it. I know its not my OS because i recently changed from 10.2.8. to 10.4.2. and the problem carried on. Could I have a virus?

Gnome 3.2 - system crashes after update

Hi,
since the Gnome 3.2 update, my system has been crashing/halting regularly.
I run XFCE, not Gnome, but I use GDM for login. If I leave a session logged in and walk away, after a while the system will just halt. An unclean shutdown, no kernel panic. I suspect the problem is with gdm, gnome-session, or any of the gnome components it invokes (gnome-screensaver, ...?), since I don't have the problem when using SLiM instead.
The following is syslogged right before the crash:
Oct 6 21:47:56 boris gnome-session[24717]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=IsInhibited
Oct 6 21:47:56 boris gnome-session[24717]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=IsInhibited
Oct 6 21:47:56 boris gnome-session[24717]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=IsInhibited
Oct 6 21:47:57 boris kernel: [344214.625926] EXT4-fs (dm-1): re-mounted. Opts: commit=0
Oct 6 21:47:57 boris kernel: [344214.669797] EXT4-fs (md0): re-mounted. Opts: commit=0
Oct 6 21:47:57 boris kernel: [344214.771486] EXT4-fs (dm-2): re-mounted. Opts: commit=0
Oct 6 21:47:57 boris kernel: [344214.773156] EXT4-fs (dm-3): re-mounted. Opts: commit=0
Oct 6 21:47:57 boris kernel: [344214.967545] EXT4-fs (dm-4): re-mounted. Opts: commit=0
Oct 6 21:47:57 boris kernel: [344214.969814] EXT4-fs (dm-5): re-mounted. Opts: commit=0
I'm using the xf86-video-ati driver if it matters.
Any ideas?

I have been having the same problem. I may have found a solution. I removed 'gksu' anything with pacman. And I followed this blog's http://dev-loki.blogspot.com/2010/06/su … nsuse.html instructions to create 'xsudo' as a replacement for gksu.
Its to early to tell if the problem is fixed, but I am not recieving any error messages with gedit or nautilus when I run them with 'xsudo' account.
I hope this fixes it for us. Luck
Last edited by jo-shva (2012-11-14 13:53:33)

System crashes after thunderbird upgrade.

Thunderbird made an auto-update. After that, whenever I try to run it, the system reboots.

Thank you for the suggestion. I tried to run in safe mode, with the combinations of "disable add-ons" and "reset toolbars - controls" options.
Each time the system rebooted as soon as I run, except for the time when these options were not checked.
Thunderbird run for a few moments and as the new messages arrived I received errors like these: "cannot write message to folder xyz. No space left or not enough permissions..."
(I have some filters for message groups, people etc. Some of them worked fine but other failed with errors similar to above.)
And then system rebooted.
Afraid of loosing all the mail archive, I backed-up everything with mozbackup. I will try a clean installation and try to restore.

System Crashed after Partitioning an External Drive

I tried to add a second partition to my external drive but now my system freezes whenever the drive attempts to mount.
Originally, my external drive had a single partition used for Time Machine backups. I used the partition tab in Disk Utility to add a new partition. I selected a size for the partition that was less than the space being taken up by time machine backups. After clicking apply, disk utility seemed to work for 10-20 minutes and then my system suddenly crashed. Everything freezes and the following message appears:
"You need to restart your computer. Hold down the power button for several seconds or press the restart button".
If I try to restart, the system will crash as soon as the drive begins to mount. The only way I am able to get my system to restart, is to unplug my external drive. I have tried safe mode and I have tried opening disk utility before mounting the external drive but nothing seems to work. It still crashes the system.
I have other backups of this data so I'm not concerned with loosing anything. I just want to get back into disk utility with this drive so I can reformat. Does anyone know how I can bypass without getting the "restart" message so I can erase the disk and start from scratch?
Oh, I forgot to mention, this issue may have resulted from accidentally disconnecting the FW800 while the last backup was taking place. Irregardless, I think the drive is now corrupt and I want to start from scratch.
HELP!

Thank you VK. Worked like a charm. I used the start-up disk and deleted the problematic partition within Disk Utility. Seemed to work fine after that, but I went ahead and reformatted the drive and started from scratch just to be safe.
Thanks again for the help.

New Install Works Fine then System Crashes After Time Machine Backup

I have installed Snow Leopard and everything went fine. I setup my external drive as the backup drive for Time Machine and did a backup. Then when I next used it, various applications started crashing. Then the System began crashing and gave me the gray screen restart and would never load again.
I got out the Snow Leopard disk and used DIsk Utilities to repair the disk and permissions, which seemed to work well. The computer worked great for a while. Then after I used Time Machine to back it up, when I next used it the System began crashing again.
What is going on here? It seems to be too much of a coincidence that the problems started immediately after I performed my first Time Machine backup to an external drive.

Woodwyn wrote:
Actually I already did that more or less. I re-installed the Snow Leopard printer drivers from the DVD after I previously repaired my system using DIsk Utilities. After which, I was prompted to download and install the 10.6.2 Combo update again. Which I did. After which, I ran disk utility and repaired and permissions verified the disk. But if you think going back to the original 6.0 install is important, then I presume you also mean I need to run all the subsequent updates as well?
So you only re-insalled printer drivers and updated the existing OS to 10.6.2? Then that may be enough. Otherwise, if the issue returns, I would suggest a full re-install of the OS at 10.6.0 followed by updates to 10.6.2.
However, first I am going to repair the drive and NOT enable Time Machine or perform a back-up, to see how long it lasts without crashing. The last two times, the crashing began within an hour of finishing the install and repairing the disk (immediately following a "co-incidental" Time Machine backup both times, of course). It's entirely possible Time Machine is not the culprit, however, that will confirm whether it has been the trigger.
Good troubleshooting strategy. Only time will tell.
Another thought occurs to me...Is the RAM that is installed on your Mac the original cards supplied by Apple - or did you upgrade it with 3rd party RAM yourself. The crashing you described earlier could very well be from a bad RAM card - even one that came from Apple.
It is one 2GB card, or two 1GB cards? If the crashing continues, I would suggest taking one of them out and seeing how things perform, then switching them and seeing if things change.

System crash after unhandled exception during pending A/D conversion

Similar Messages

Maybe you are looking for