LabVIEW only crash on my computer after Tree operation

Hi All,
I started with the example as shown in attachment and implement my code. But I found LabVIEW crashed (see attachment2) ONLY on my computer after I performed operation of delete 6 steps (children).
LabVIEW can no display Tree and the Menu on every window messed up. I can repeat the failure.
I tested exact same code on the other two computer and no problem at all.
Maybe some files broken on my computer and I have to re-install LabVIEW ?
What should I be carefull with when re-install ?
Attachments:
Tree example.JPG ‏80 KB
Only on my PC.JPG ‏7 KB

Hi Brian,
When
you say LabVIEW "crashed" and the menus and windows are "messed up" can
you be more specific? The menu bar is messed up (see attached). The blue bar and LabVIEW logo is gone. I have to restart LabVIEW to recover.
Are there any error messages that pop up? No.
What
version of LabVIEW are you using? 8.5.0
Are the three computers different in
any way (operating system, LabVIEW version, etc..)? No.
Finally, can you recreate this issue with just the example VI, without any of your added code? No. I guess my code somehow hit the window drawing defect which only on my computer.
Thanks!
Attachments:
menu messed.JPG ‏13 KB

Similar Messages

How do I Sync my i-touch with my computer after I've restored my computer from a crash?

How do I Sync my i-touch with my computer after I've restored my computer from a crash? I-tunes only wants to erase all my songs and sync to a blank slate

If all your apps and music are in your iTunes library, try to make a backup of the iPod. Right click on the iPod under Devices in iTunes and select Backup. Once you have a backup, restore the iPod from thatbackup. If you can't make a backup (or get a backup from the computer backup) you must restore the iPod to factory defaults/new iPod and sync as necessary.

My ipod is not recognized on a new computer after old one crashed. I have painstakenly restored all songs and playlists. I deautorized all, and the reauthorized new computer. It won't sync.

My ipod is now recognized on a new computer after old one crashed. I installed itunes on the new computer, and have painstakenly restored all songs and playlists. I also purchased several new songs from the itunes stores. Now my ipod will not sync with the new computer. I deauthorized all computers, then reauthorozed the new one. My ipod still won't sync.

...after running diagnostics through itunes, itunes says "device not found" Seems there are a lot of others having this problem,and it seems to be related to new version of itunes. Apple should do something to fix this.

Firefox has been crashing all the time after I updated to the newest version. I tried to uninstalled firefox and all addons. Restarted the computer to reinstall Firefox and it's still crashing all the time. Please help.

Firefox has been crashing all the time after I updated to the newest version. I tried to uninstalled firefox and all addons. Restarted the computer to reinstall Firefox and it's still crashing all the time. Please help.

https://support.mozilla.com/en-US/kb/Firefox%20crashes#w_get-help-fixing-this-crash
Type '''about:crashes''' in the URL bar and hit Enter. <br />
Click the hyperlinks to bring up the Crash Report pages and copy'n'paste the URL of each of those reports into the message box here. We'll see if we can help you figure out what is causing those crashes to happen.

Using Time Machine, is it possible to back up a computer AFTER a specific date. I only want to back up files from AFTER January 2015. Is this possible, and how can I do this?

Using Time Machine, is it possible to back up a computer AFTER a specific date. I only want to back up files from AFTER January 2015. Is this possible, and how can I do this?

emilypdunne wrote:
Using Time Machine, is it possible to back up a computer AFTER a specific date. I only want to back up files from AFTER January 2015. Is this possible, and how can I do this?
Is what you're saying that you only want backups in TM of the state of your Mac from January 2015 to the current date and nothing before then? I'd think the simplest solution would just be to delete in TM all the backups prior to 1/15 and then let TM do its thing. The ultimate source for all things Time Machine is here. On this page, note the comment that "Time Machine will never delete the backup copy of anything that was on the disk being backed-up at the time of any remaining backup" which I understand to mean that if you delete all the backups in the TM file prior to 1/15, any file that wasn't present on your Mac as of 1/15 will no longer be represented in the TM file. Note that the second link also has instructions for how to delete TM files.
If you were trying to accomplish something else, then as Emily Litella (Gilda Radner in SNL) used to say, "never mind."

After mixing a project i select bounce and burn the disc that is burned plays on any cd player but when i try to burn the wav or mp3 file that was created the resulting disc will only play in a computer this also happens with video projects help please

after mixing a project i select bounce and burn the disc that is burned plays on any cd player but when i try to burn the wav or mp3 file that was created the resulting disc will only play in a computer this also happens with video projects help please are there any settings i need to alter as it seems the wav or mp3 file i ceated is being converted to a data file somewhere between the folder and disc drive

Same thing for a movie file.. If you want to play back the movie via a DVD and a DVD player you must create a Movie DVD and not just burn files to a data DVD... as Data DVDs are just storage devices for files and therefore will only work with computers...
Movie DVDs are special formats that include things like menus and special file formats.. so they can playback via a DVD Player...
You will need a 3rd party DVD Burning app like Toast which is what i actually use.... or the more popular DVD Creator app...to create and then burn a Movie DVD that will playback on a DVD Player....
https://answers.yahoo.com/question/index?qid=20101220205435AA70beb

How do I recover a Muse site back to my computer after it has crashed and I've lost the files?

How do I recover a Muse site that was uploaded to Business Catalyst back to my computer after my system crashed and I've lost the files?

Regardless of being in development or not, "Captain Obvious" is is correct and the working .muse file is lost, meaning that you will have to start again from scratch.
All the BC will contain is the published HTML and support files, not the .muse file which you would require to recover the site design.
Might want to look into Time Machine or another automatic, timed backup source while you work.

All of my music was erased from my computer after my hard drive crashed and I don't want to spend the time uploading all of my old CDs to my computer. If I plug in my iPhone with all of my current music on it, will it sync to my computer?

All of my music was erased from my computer after my hard drive crashed and I don't want to spend the time uploading all of my old CDs to my computer. If I plug in my iPhone with all of my current music on it, will it sync to my computer?

This user tip should be helpful too.
Syncing to a "New" Computer or replacing a "crashed" Hard Drive

Trying to restore music from IPOD back onto repaired computer after crash

My motherboard crashed on my computer causing me to lose all my music except for the ones I've recently purchased. Does anyone know how to get the music from the IPOD back onto ITunes without having to erase my entire IPOD?

Try senuti.
EDIT: Didn't see you were using windows. Repost in this forum.
Good luck!
Message was edited by: joshz

The new version of fire fox keeps crashing my entire computer if i pull down the scroll bar to fast and when using sites that use flash player my other browsers work fine its only started happening since it updated to 3.6.10

Firefox keeps crashing my entire computer if i pull down the scroll bar too fast or go to websites that use flashplayer and sometimes for no reason at all. My other browsers work fine and firefox did till the update.

There has been a security update of the Flash Player and the current version is 10.1 r85 , so you are two versions behind (previous was 10.1 r82).
See http://www.adobe.com/software/flash/about/

LabVIEW is crashing when i am trying to build the exe

I am trying to build an executable from a program in which i am communicating with several instruments, whenever i am trying to build an exe labview is crashing and i am getting the error Exception: access violation(0xc0000005)at eip=0x10054DD1.
after reading some posts on forum i tried builduing an exe on other system also, but still i am getting the same error.
below i am attaching the program and the image of the error i am getting.
Attachments:
labview crash.png ‏53 KB
automation.zip ‏4455 KB

Ritu wrote:
waiting for the reply....
Realize this community is by a large majority volunteer based. If you need urgent support contact NI directly
http://sine.ni.com/apps/utf8/nicc.call_me?loc=en-US
That being said I would try to disable the large amount of code. Say you have a Main that launches a bunch of stuff, put a disabled diagram code around the launching part and then try to rebuild. It is a very slow process (especially when the build takes a while to fail) but by doing this you can more isolate the parts of the code that can cause the crash. The only time I've seen a crash on build like you described, I simply rebooted and it was fine. Usually because of my own fault by stopping code in a bad way previously leaving things in memory.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AM

Sure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC)

System crashes multiple times daily after 10.9.2 upgrade

I upgraded my MacBookPro to 10.9.2 and now my computer crashes constantly. Prior to the upgrade my MBP was rock solid. Now, some days are good and it will only crash 2 or so times. Other days are bad, today it must have crased 10 times. I definately feel like I've gone back to microsoft ****.
Here is what I know and what I have done.
1) When I "upgraded" I was using firevault. I did not turn this off prior to the upgrade. I suspected this might be the problem early on because my computer asked me for 2 passwords on boot. One for "legacy firevault." I turned this off. The computer still crashed. I did a safe boot and turned off firevault. This time my computer took about 4 hours to presumably unencrypt the drive. Compuer still crashed regularly
2) I have used safe boot several times.
3) I have used disk utility to check my HDD. No errors to fix.
4) My experience seems to be that often time when moved around my folders in finder the computer crashes so I deleted finder preferences: com.apple.finder.plist
5) I have also reset the NVRAM and the SMC
Still crashing.
Here is my latest crash report. Anyone have any ideas?
Mon May 26 20:00:49 2014
panic(cpu 2 caller 0xffffff7f867d7fb0): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff80a3ff0000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.35/src/Apple MuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 2), Frame : Return Address
0xffffff80811ab140 : 0xffffff8004422fa9
0xffffff80811ab1c0 : 0xffffff7f867d7fb0
0xffffff80811ab290 : 0xffffff7f84ec0eab
0xffffff80811ab350 : 0xffffff7f84f8a49a
0xffffff80811ab390 : 0xffffff7f84f8a50a
0xffffff80811ab400 : 0xffffff7f85209056
0xffffff80811ab530 : 0xffffff7f84fadb39
0xffffff80811ab550 : 0xffffff7f84ec78fd
0xffffff80811ab600 : 0xffffff7f84ec5408
0xffffff80811ab800 : 0xffffff7f84ec6386
0xffffff80811ab8e0 : 0xffffff7f85df19c2
0xffffff80811ab920 : 0xffffff7f85e0137f
0xffffff80811ab940 : 0xffffff7f85e2f33b
0xffffff80811ab980 : 0xffffff7f85e2f39b
0xffffff80811ab9c0 : 0xffffff7f85e06e15
0xffffff80811aba10 : 0xffffff7f85dd2b5e
0xffffff80811abaa0 : 0xffffff7f85dceae7
0xffffff80811abad0 : 0xffffff7f85dcc636
0xffffff80811abb00 : 0xffffff80048cbe03
0xffffff80811abb90 : 0xffffff80048cdcff
0xffffff80811abbf0 : 0xffffff80048cb81f
0xffffff80811abd40 : 0xffffff80044b6558
0xffffff80811abe50 : 0xffffff8004426bf1
0xffffff80811abe80 : 0xffffff80044139f5
0xffffff80811abef0 : 0xffffff800441e043
0xffffff80811abf70 : 0xffffff80044c976d
0xffffff80811abfb0 : 0xffffff80044f3b46
      Kernel Extensions in backtrace:
         com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[80472F2E-D31D-32C4-88BA-2EB3D63 C159F]@0xffffff7f84e71000->0xffffff7f850d9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f84abb000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[999E29DA-D513-3544-89D1-9885B728A098]@0xff ffff7f84e61000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f84e1e000
         com.apple.driver.AppleMuxControl(3.4.35)[1BFF66C1-65E4-3BB3-9DEE-B61C3137019B]@ 0xffffff7f867ca000->0xffffff7f867dcfff
            dependency: com.apple.driver.AppleGraphicsControl(3.4.35)[09897896-ACBD-36B5-B1D4-0CCC4000E 3B3]@0xffffff7f867c2000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xfffff f7f84d28000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f84abb000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f84e1e000
            dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C66 53]@0xffffff7f867c5000
         com.apple.nvidia.classic.NVDANV50HalTesla(8.2.4)[B0E6AAA7-E970-3D81-8B43-145D56 A3A4AC]@0xffffff7f850e4000->0xffffff7f8538dfff
            dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[80472F2E-D31D-32C4-88BA-2EB3D63 C159F]@0xffffff7f84e71000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f84abb000
         com.apple.GeForceTesla(8.2.4)[B6C71E9A-E304-354B-80AD-C69C9032D367]@0xffffff7f8 5db1000->0xffffff7f85e7bfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f84abb000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[999E29DA-D513-3544-89D1-9885B728A098]@0xff ffff7f84e61000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f84e1e000
            dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[80472F2E-D31D-32C4-88BA-2EB3D63 C159F]@0xffffff7f84e71000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
13C64
Kernel version:
Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953
Kernel slide:     0x0000000004200000
Kernel text base: 0xffffff8004400000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 4076372120718
last loaded kext at 3712737034770: com.apple.driver.AppleIntelMCEReporter          104 (addr 0xffffff7f86926000, size 49152)
last unloaded kext at 4073380354702: com.apple.driver.AppleIntelMCEReporter          104 (addr 0xffffff7f86926000, size 32768)
loaded kexts:
com.apple.filesystems.smbfs          2.0.1
com.apple.driver.AudioAUUC          1.60
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AGPM          100.14.15
com.apple.filesystems.autofs          3.0
com.apple.iokit.IOBluetoothSerialManager          4.2.3f10
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.driver.AppleMikeyDriver          2.6.0f1
com.apple.driver.AppleHDA          2.6.0f1
com.apple.driver.AppleIntelHDGraphics          8.2.4
com.apple.driver.AppleLPC          1.7.0
com.apple.driver.AppleSMCLMU          2.0.4d1
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleIntelHDGraphicsFB          8.2.4
com.apple.GeForceTesla          8.2.4
com.apple.driver.AppleMuxControl          3.4.35
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.3f10
com.apple.driver.AppleUpstreamUserClient          3.5.13
com.apple.driver.AppleMCCSControl          1.1.12
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleHWAccess          1
com.apple.driver.SMCMotionSensor          3.0.4d1
com.apple.driver.AppleUSBTCButtons          240.2
com.apple.driver.AppleUSBTCKeyboard          240.2
com.apple.driver.AppleIRController          325.7
com.apple.driver.AppleUSBCardReader          3.4.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          35
com.apple.iokit.SCSITaskUserClient          3.6.6
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.5.1
com.apple.driver.AirPort.Brcm4331          700.20.22
com.apple.driver.AppleUSBHub          666.4.0
com.apple.driver.AppleFWOHCI          4.9.9
com.apple.driver.AppleAHCIPort          3.0.0
com.apple.iokit.AppleBCM5701Ethernet          3.8.1b2
com.apple.driver.AppleUSBEHCI          660.4.0
com.apple.driver.AppleACPIButtons          2.0
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleRTC          2.0
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          2.1
com.apple.driver.AppleACPIEC          2.0
com.apple.driver.AppleAPIC          1.7
com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0
com.apple.nke.applicationfirewall          153
com.apple.security.quarantine          3
com.apple.driver.AppleIntelCPUPowerManagement          216.0.0
com.apple.AppleGraphicsDeviceControl          3.4.35
com.apple.kext.triggers          1.0
com.apple.iokit.IOSerialFamily          10.0.7
com.apple.driver.DspFuncLib          2.6.0f1
com.apple.vecLib.kext          1.0.0
com.apple.iokit.IOAudioFamily          1.9.5fc2
com.apple.kext.OSvKernDSPLib          1.14
com.apple.driver.AppleSMBusPCI          1.0.12d1
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.nvidia.classic.NVDANV50HalTesla          8.2.4
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.AppleGraphicsControl          3.4.35
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.3f10
com.apple.driver.AppleHDAController          2.6.0f1
com.apple.iokit.IOHDAFamily          2.6.0f1
com.apple.iokit.IOFireWireIP          2.2.6
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.nvidia.classic.NVDAResmanTesla          8.2.4
com.apple.iokit.IONDRVSupport          2.4.1
com.apple.driver.IOPlatformPluginFamily          5.7.0d10
com.apple.iokit.IOSurface          91
com.apple.iokit.IOGraphicsFamily          2.4.1
com.apple.iokit.IOBluetoothFamily          4.2.3f10
com.apple.driver.AppleSMC          3.1.8
com.apple.driver.AppleUSBMultitouch          240.9
com.apple.iokit.IOUSBHIDDriver          660.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.6
com.apple.iokit.IOUSBMassStorageClass          3.6.0
com.apple.driver.AppleUSBMergeNub          650.4.0
com.apple.driver.AppleUSBComposite          656.4.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.6
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOAHCISerialATAPI          2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.6
com.apple.iokit.IO80211Family          630.35
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IOUSBUserClient          660.4.2
com.apple.iokit.IOAHCIFamily          2.6.5
com.apple.iokit.IOEthernetAVBController          1.0.3b4
com.apple.driver.mDNSOffloadUserClient          1.0.1b5
com.apple.iokit.IONetworkingFamily          3.2
com.apple.iokit.IOUSBFamily          675.4.0
com.apple.driver.AppleEFINVRAM          2.0
com.apple.iokit.IOHIDFamily          2.0.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          278.11
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.AppleKeyStore          2
com.apple.driver.DiskImages          371.1
com.apple.iokit.IOStorageFamily          1.9
com.apple.iokit.IOReportFamily          23
com.apple.driver.AppleFDEKeyStore          28.30
com.apple.driver.AppleACPIPlatform          2.0
com.apple.iokit.IOPCIFamily          2.9
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.pthread          1
com.apple.kec.corecrypto          1.0
Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.8 GHz, 4 GB, SMC 1.58f17
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x384A53463235363634485A2D314731443120
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x384A53463235363634485A2D314731443120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST9500420ASG, 500.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Internal Memory Card Reader
USB Device: Hub
USB Device: Built-in iSight
USB Device: IR Receiver
Thunderbolt Bus:

You have the MacBookPro6,2, the Edsel of Macs. It may have a logic-board defect covered by this recall.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider, to have the machine tested. The routine hardware diagnostics used by service providers do not detect the fault. There is a specific test for this issue that Apple calls "VST" (for "Video Switching Test.") Ask for it. A "Failed" result means that the fault is present. However, according to reports, some units may pass the test, and yet still be deemed eligible for repair under the program. Your experience may vary.
Print the first page of the panic report, if any, and the support page linked above, and bring them with you.
Note that the recall only applies within three years of purchase. After that, Apple may refuse the service. In that case, you may be quoted a price of about $300 (in the U.S.) for a "depot repair," which involves shipping the unit to a central repair facility and takes about two weeks. For that flat fee, anything found wrong with it should be fixed, not just the logic board.
The model was discontinued on February 24, 2011, so the recall has nominally ended. Some units may have been sold after that date by Apple as refurbished, or by resellers as new, and they should still be covered.
Some owners report that their unit was repaired under the program after the deadline had passed. Others report that the repair was covered by the extended warranty from a credit-card issuer. Again, your experience may vary.
Sometimes the replacement part is also defective, so be prepared for that possibility.
If it's too late for your unit to be repaired under the program, and you don't want to pay for a new logic board, you may be able to stop the panics by disabling automatic graphics switching. To use the discrete graphics processor, you'll need a third-party utility to switch to it manually.
If you're dissatisfied with Apple's response, please keep in mind that no one here represents the company or can help with customer-service issues.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
*An SSD doesn't need to be zeroed.

LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program

Hello!
We have the following problem:
LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program
We freshly installed LabView 8.2 (2006) and NI-DAQ 7.4.4 on a PC running Windows XP (Service Pack 3). We built a larger vi that remotely controls a traditional NI-DAQ card (AT-AO-10) on a second PC via NI-VISA 5.0.3. We were successfully running this program until a power failure caused the first computer to crash. After this crash we were unable to start the program again: LabView freezes while loading the vi. LabView itself can be started but freezes when adding I/O operations from the NI-DAQ palette to a block diagram.
We have tried to re-install NI-DAQ 7.4.4, but it did not help. We then re-installed all NI software, but still no improvement. In the end we decided to reinstall ALL software, first Windows XP, then LabView and finally NI-DAQ 7.4.4. This worked. However, after a few days of running the program we had to abort LabView via Windows Task manager and afterward we again experienced the same problem as before: LabView freezes when loading the program.
Obviously, we cannot afford to reinstall Windows every time. Are there any known Windows XP / NI-DAQ issues that might cause the freezing of LabView? We would be very grateful for any idea.
Best regards,
Matthias

Hello Sprice,
Browse the shipping examples according to “Directory Structure” and then select
DAQ to find the Traditional DAQ examples.
There a lot of examples that are written for counters (Counter >>
daq-stc.llb >> Count Edges (DAQ-STC).vi).
What kind of signals are your photons creating? Are they TTL compatible at a certain
frequency? You don’t care about overwriting
your buffer?
Respectfully,
Rob F
Test Engineer
Condition Measurements
National Instruments

Mainstage Crash during live use after OS X 10.7.4 install.

I am a semi-pro musician and I have added Main-stage to my set-up, in line with my hardware synths, as I transition into the soft synth world in a live situation. Up until the latest OS X install, Main-stage has been stable, which is critical for live use, and my confidence moving forward is growing. However now, my Main-stage set-up hangs up and or crashes in performance mode after about 15-20 minutes. This is not acceptable, anyone here that is invested in Main-stage for live use, understands this. 30% of my show is dependent on this too,l but crashes cannot happen on stage.
I have read that the new OS X update 10.7.4 may be responsible, as this is the only thing that has recently changed. If so, what is the solution to resolve?, is it possible to back out a OS X update and if so, how?
This is my first post, which for me, means I am desperate for an answer quickly, thanks.

And there is your reply from Apple:
MainStage 2.2.2: Release notes
Products Affected
MainStage 2.2
Symptoms
MainStage 2.2.2 is a software update for MainStage 2.2. MainStage 2.2 is a feature upgrade for MainStage 1.0 and 2.0 customers available for purchase on the Mac App Store. MainStage 2.2 includes several new features and fixes.
Resolution
About the MainStage 2.2.2 Update
Stability and Usability
Resolves an issue in which MainStage might quit unexpectedly on OS X Lion v10.7.4.
Resolves an issue in which MainStage sometimes quit unexpectedly when loading certain concerts.
Resolves an issue in which MainStage quit unexpectedly when a second mapping was assigned to a screen control that already had a mapping assigned.
Fixes an issue in MainStage 2.2.1 in which assignments and mappings could be inadvertently deleted by removing a screen control in Layout Mode.
Resolves an issue related to the download and installation of basic and additional content.
The menu item for Release Notes now opens the correct URL.
Compatibility
Compatibility with the VAX-77 keyboard is improved.
Resolves an issue in which patch lists were not updated to VAX and Axiom keyboards if the keyboard lost and then regained connection to the computer after launching MainStage
General
Resolves an issue with MainStage 2.2 and 2.2.1 in which EXS instrument files were not available if they were in aliased folders.
Fixes an issue in MainStage 2.2 and 2.2.1 in which the I/O Plug-in did not route audio to outputs.
When mapping a Screen Control to a parameter already mapped to another Screen Control by using the plug-in GUI, MainStage now correctly maintains independent mappings for each Screen Control.
Resolves an issue in which using the Command key in conjunction with up and down arrows in Edit mode with Map Parameters enabled caused MainStage to assign the mappings to Next Patch and/or Previous Patch.
Fixes an issue in MainStage 2.2 and 2.2.1 in which mapping a Screen Control to jump to a patch or a set no longer worked.
Screen Controls mapped to more than one parameter now operate smoothly over their entire range with all range scale settings.

LabVIEW only crash on my computer after Tree operation

Similar Messages

Maybe you are looking for