Startup crash LV 2009 SP1 (bug?)

This has happened a few times, but today was the worst. Frequently I'll get the "LabVIEW encountered an error ... would you like to investigate?". Frequently (at least once a week) LV won't even start up and I get the "LabVIEW encountered an error and needs to shut down". The only workaround from that - until today - was to restart the computer. Today I could not get LV to startup at all. The only way I was able to get LV to startup was, in a moment of serendipity (or dumb luck) I double-clicked my project icon on my desktop. LV started up. I exited LV and tried to restart and it came up fine.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

Hello PaulG,
What OS are you on? It appears it isn't isolated to a particular VI of yours but just in LabVIEW in general. However, if this crash occurs specifically to a VI, please post it so we can try duplicating your issue.
Also, when prompted "LabVIEW encountered an error.." I would recommend selecting the option that allows you to investigate now which should provide directions to send the error log to National Instruments in which it could be further investigated.
Regards,
Glenn

Similar Messages

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

LV 2009 SP1 EXE Builder issue

Hi Guys:
I found that the exe file built from LV 2009 SP1 can be easily extracted by WinRAR , i can see all the main or sub vi , is this a bug? or a settings risk? I haven't found the same problem in LV 8.6 ,
thanks
Solved!
Go to Solution.

I do not think you should think to much about it. One of the first discussions about it is here http://forums.ni.com/t5/LabVIEW/decompiling-2009-executable/td-p/991662. It is correct that they will be able to extract the VIs But they will not be able to see any more than you show in your program.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.
Attachments:
Connector pane.PNG ‏4 KB

Troy K wrote:
I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
So you must be using crazy non-standard connector panes, or you would not have discovered this bug. Right? Actuall this is a good catch for it to go unnoticed for this long.
- tbob
Inventor of the WORM Global

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

Labview 2009 SP1 - Create exe option does not appear

Hello everyone,
I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other computer with the appropiate labview run time engine).
I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
Thanks for advance!
Much thanks for your time and dedication!

I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
The best solution is the one you find it by yourself

LabVIEW Run-time 2009 SP1

When I try to install LabVIEW Run-time Engine 2009 SP1 on a Windows 2000 machine I get an error message that states "Windows XP SP2 or greater required"
The compatability chart http://www.ni.com/labview/os-support/f/ states that LV 2009 is supported on Windows 2000. What gives?

Do you have administrator privileges? Also, do you have any security programs installed on your computer that could hinder the installation?
Applications Engineer
National Instruments

Application builder for Lab View 8.6.1 , 2009 SP1 and 2010 SP1

All 3 Versions seem to have huge flaws. With 8.6.1 When trying to build and application I get a duplicate name error and the application won't work. With 2009 SP1 I get Error 1003 broken VI when I have no broken VI's. Again Application won't work! With 2010 SP1 After the application is built for some reason lab view can no longer find the Excel sub VI's no matter how I place them in the build. And again application doesn't work. With all 3 versions the Vi's and over all programs work perfectly in the development environment. The application builder seems extremely flawed.
I would currently like assistance with 2009 SP1 problem the Error 1003 broken VI. I have reinstalled and rebooted my machine several times , tried including as much as possible in the build and still get the error about a broken VI. That works perfectly in the development environment. Please HELP?
Thank You
Attachments:
Broken VI.gif ‏8 KB

Scott,
Good afternoon, I'm sorry to hear you are having problems working with the application builder, hopefully I can help you get to the root of this problem.
What steps have you taken to try and resolve the error? This error can be caused by a variety of things. The link below details 8 potential solutions that may help resolve your error.
http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
I would recommend starting with these steps. Let me know if any of these solutions work for you.
-Nick-
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

Lv 2009 sp1

Bonjour, je suis actuellement sous lv 2009 f2. avec des ajout openg je vais devoir aller faire des test sur un pc ou la version 2009 sp1 est installée :
1) si je fait des modif sous le pc en sp1 , devrais je installer la sp1 sur mon 1er pc pour relire les nouveaux fichiers
2) le correctif sp1 est il un simple ajout ou bien est ce une reinstall , cad aurais je besoin d'installer a nouveau les bibli open G ?
Cordialement
Tinnitus
ps: désolé je peux pas me relire j'écris dans un champ de 1*4 cm (filtrage interne temporaire j'espère)
CLAD / Labview 2011, Win Xp
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail
Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte
Résolu !
Accéder à la solution.

bon , la reponse c'est non :
c'est une mise a jour et pas besoin de reinstaller les lib openg
CLAD / Labview 2011, Win Xp
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail
Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte

LV 2009 SP1 Build Error NI

While trying to make a build on LV 2009 SP1, I get this error:
The build was unsuccessful.
An error occured while saving the following file: Sample.VI
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference: Error 1 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Note I do not use any GPIB. Also when I build the project on VL 2009 (no SP1) on a different machine, I get no errors. Any ideas?
Solved!
Go to Solution.

Ugh. I've seen this in 2009 as well as quite a few others here. There seems to be no real explanation or consistent solution to this error. 1st thing to try is to remove all boolean constant-driven case selectors. For some reason the compiler gets confused with those - sometimes. See how that goes. Eventually this problem seems to resolve itself after a few days of development. That's been my experience. Sorry I can't be of more help.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

2009 SP1 Debug Deployment Only

I've install LabVIEW 2009 SP1 and it works fine but it indicates "Licensed for Debug Deployment only" on the opening screen. We use the Volume License Manager and it correctly checks out a Development License which is correct for me.
Is this something I should be concerned about? It doesn't seem to be constrained in any way, i.e. I can build executables.

Here they are. I'm "DC10020"
Attachments:
VLM_Screenshot.jpg ‏511 KB
NILM_Screenshot.jpg ‏227 KB

2009 sp1 slow build

Trying to build my application after I just upgraded to sp1 on LabVIEw 2009.
It seems to take a long time, while using a lot of cpu power.
Progress is very slow. Hard drive is not being used intensly.
Running the same on the 2009 f2 version. Building from the same sources.
Very slow as well.
I'm new to the performance of the build feature in 2009. Coming from version 7.1.1
And I'm very surprised on the difference. Why does the build take sooooo looooonnnnggg on the 2009 version(s)??
We build smaller apps before on 2009, and did not seem a big deal. But this bigger application.
And then after about 15 minutes, I get an error message:
Error 8 occurred at AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
So this is running with the 2009 f2 version on XP pro with 1Gb of ram. And for the 2009 sp1 version on windows 7, with 8Gb of ram....
So do not expect any memory issues with the SP1. Could this be a windows 7 x64 issue?
Anyone any experience with building larger applications?

Hello Everyone,
We have observed that building executables in LabVIEW 2009 is slower than in 8.6. In most cases it was about 10 to 20%. However, in some larger builds we have seen almost a 3x or 4x slow down. This large slow down has been reported to R&D for further investigation (CAR 205343). In the case that was reported to us the build was about 8000 VIs and took 2GB of memory to complete.
There wasn't a difference between LabVIEW 2009 and 2009 SP1. The slow down occurred between 8.6.1 and 2009. Does your slow down occur between 2009 and 2009 SP1?
Message Edited by Jon S. on 03-09-2010 08:42 AM
Regards,
Jon S.
National Instruments
LabVIEW R&D

Strange PRE11 startup crash

A little while ago my PRE11 installation (originally from DVD) started to crash as the application was started. I uninstalled and re-installed from DVD, and this appeared to fix the problem. A few days ago I attempted to use PRE11 again, and got the same strange startup crash as before. This time a re-installation from DVD had no effect, and neither did the re-installation of a fresh download from Adobe's website. After a bit of research I tried running PRE11 as Administrator (Windows 7 Pro, 64-bit), and this started just fine. Running the application as "me" (also with Administrator privileges, as it happens) crashed as before. When not running as Administrator, the crash I obtain is given below. I can also provide a core dump if this is useful. All other Adobe applications on my machine (Photoshop CS6, Lightroom 4, PSE11) are working fine.
Any suggestions as to what might be going on with PRE11 would be very much appreciated.
Ian Wilson
Cambridge, UK
FAULTING_IP:
Display!MediaCoreDisplay::VideoNode::CreateEffectNode+2fbc
00000000`0d1e30bc 488b01          mov     rax,qword ptr [rcx]
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000000000d1e30bc (Display!MediaCoreDisplay::VideoNode::CreateEffectNode+0x0000000000002fbc)
   ExceptionCode: c000041d
ExceptionFlags: 00000001
NumberParameters: 0
FAULTING_THREAD: 0000000000002020
PROCESS_NAME: Adobe Premiere Elements.exe
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: Display
FAULTING_MODULE: 00000000773c0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 505bb29e
ERROR_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.
EXCEPTION_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.
MOD_LIST: <ANALYSIS/>
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ_WRONG_SYMBOLS_SHUTDOWN
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ_SHUTDOWN
DEFAULT_BUCKET_ID: INVALID_POINTER_READ_SHUTDOWN
LAST_CONTROL_TRANSFER: from 000000000085c022 to 000000000d1e30bc
STACK_TEXT:
00000000`1c90e380 00000000`0085c022 : 00000000`14c7c7e0 00000000`00000001 00000000`0d233000 00000000`1502e090 : Display!MediaCoreDisplay::VideoNode::CreateEffectNode+0x2fbc
00000000`1c90e5c0 00000000`00858742 : 000007ff`ff672b90 00000000`00000001 00000000`00000000 00000000`0645d30f : dvacore!dvacore::threads::AdaptCurrentEventLoopAsExecutor+0x362
00000000`1c90e6a0 00000000`00858777 : 00000000`00000000 00000000`00030656 00000000`00000400 00000000`00000000 : dvacore!dvacore::threads::RunPlatformEventLoop+0x11d2
00000000`1c90e6e0 00000000`76e19bd1 : 00000000`064cd678 ffffffff`fffffffe 00000000`00000002 00000000`06570000 : dvacore!dvacore::threads::RunPlatformEventLoop+0x1207
00000000`1c90e720 00000000`76e172cb : 00000000`00000000 00000000`00858750 00000000`00000000 00000000`00000000 : USER32!TranslateMessageEx+0x2a1
00000000`1c90e7e0 00000000`76e16829 : 00000000`00000000 00000000`00000000 00000000`45544145 00000000`00000000 : USER32!SetWindowTextW+0x277
00000000`1c90e840 00000000`77411225 : 00000000`00000000 00000000`00000000 00000000`0657db80 00000000`0657db10 : USER32!IsDialogMessageW+0x169
00000000`1c90e8a0 00000000`76e1908a : 00000000`76e19055 00000000`064cb2e8 00000000`1c90eb58 ffffffff`fffffffe : ntdll!KiUserCallbackDispatcher+0x1f
00000000`1c90e928 00000000`76e19055 : 00000000`064cb2e8 00000000`1c90eb58 ffffffff`fffffffe ffffffff`fffffffe : USER32!PeekMessageW+0xba
00000000`1c90e930 00000000`0645b2f8 : 00000000`0657ac80 00000000`1c90eb58 00000000`0000c316 00000000`0646b66f : USER32!PeekMessageW+0x85
00000000`1c90e980 00000000`0645b4ec : 00000000`0657ac00 00000000`0657ac80 00000000`1c90eb90 00000000`003a6563 : DpoFeedb+0x2b2f8
00000000`1c90ea00 00000000`0645d19d : 00000000`00000000 00000000`00000000 00000000`1c90eb58 0000345d`668c701c : DpoFeedb+0x2b4ec
00000000`1c90ea40 00000000`0647ecc4 : 00000000`1c90eb90 00000000`00000287 00000000`1c90eb90 00000000`00000000 : DpoFeedb+0x2d19d
00000000`1c90eaf0 00000000`76e0797c : 00000000`00000000 00000000`00000000 00000000`1c90eb90 00000000`00000001 : DpoFeedb!OtsNotifyAll+0x684
00000000`1c90eb40 00000000`76e053e5 : 00000000`1c90ecc0 00000000`00000000 00000000`00000000 00000000`0647ecf5 : USER32!GetKeyboardLayoutList+0x19c
00000000`1c90eb70 00000000`76e10795 : 00000000`00000000 00000000`00000000 00000000`76e19bef 00000000`76e0797c : USER32!LockWindowStation+0x85
00000000`1c90ebc0 00000000`77411225 : 00000000`00000000 00000000`1c90ed40 00000000`03745f68 00000000`00000001 : USER32!SendMessageTimeoutW+0xcd5
00000000`1c90ec20 00000000`76e1041a : 00000000`76e10397 00000000`1c90f188 00000000`00000000 00000000`1c90f188 : ntdll!KiUserCallbackDispatcher+0x1f
00000000`1c90ed58 00000000`76e10397 : 00000000`1c90f188 00000000`00000000 00000000`1c90f188 00000000`1c90f188 : USER32!SendMessageTimeoutW+0x95a
00000000`1c90ed60 00000000`76e105d8 : 00000000`0000002e 00000000`80040100 00000000`06cf0000 00000000`06cf0000 : USER32!SendMessageTimeoutW+0x8d7
00000000`1c90f0d0 00000000`76e0a350 : 00000000`0000002e 00000000`14c5f290 00000000`00000000 00000000`00000000 : USER32!SendMessageTimeoutW+0xb18
00000000`1c90f220 00000000`0d34a2a3 : 00000000`14c5f290 00000000`00000000 00000000`00000000 00000000`14c5f290 : USER32!CreateWindowExA+0x70
00000000`1c90f2a0 00000000`0d35a975 : 00000000`1c90f716 00000000`00000000 00000000`1c90f814 00000000`00000000 : aif_ogl!AIF::OGL::AutoInitializer::AutoInitializer+0x4d3
00000000`1c90f5a0 00000000`0d1e3016 : 00000000`15056400 00000000`06575280 00000000`00000000 00000000`06464afd : aif_ogl!AIF::OGL::ContextOffscreen::ContextOffscreen+0x195
00000000`1c90f7b0 00000000`0085c022 : 00000000`14c7c7e0 00000000`00000000 00000000`0d233000 00000000`1502e030 : Display!MediaCoreDisplay::VideoNode::CreateEffectNode+0x2f16
00000000`1c90f9f0 00000000`00858742 : 000007ff`ff672830 00000000`00000001 00000000`00000000 00000000`0645d30f : dvacore!dvacore::threads::AdaptCurrentEventLoopAsExecutor+0x362
00000000`1c90fad0 00000000`00858777 : 00000000`00000000 00000000`00030656 00000000`00000400 00000000`00000000 : dvacore!dvacore::threads::RunPlatformEventLoop+0x11d2
00000000`1c90fb10 00000000`76e19bd1 : 00000000`064cd678 ffffffff`fffffffe 00000000`00000000 00000000`00000000 : dvacore!dvacore::threads::RunPlatformEventLoop+0x1207
00000000`1c90fb50 00000000`76e172cb : 00000000`00000000 00000000`00858750 00000000`00000000 00000000`00000000 : USER32!TranslateMessageEx+0x2a1
00000000`1c90fc10 00000000`76e16829 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : USER32!SetWindowTextW+0x277
00000000`1c90fc70 00000000`77411225 : ffffffff`ffffffff 00000000`76e19b43 00000000`76e19bef 00000000`0012c928 : USER32!IsDialogMessageW+0x169
00000000`1c90fcd0 00000000`76e19e6a : 00000000`76e19e9e 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcher+0x1f
00000000`1c90fd58 00000000`76e19e9e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!SfmDxSetSwapChainStats+0x1a
00000000`1c90fd60 00000000`008575b9 : 00000000`1504cc70 00000000`1504cc70 00000000`00858750 00000000`18c78a08 : USER32!GetMessageW+0x2a
00000000`1c90fd90 00000000`0085ca6e : 00000000`1504cc70 00000000`18c78a08 00000000`14fcf230 00000000`00000000 : dvacore!dvacore::threads::RunPlatformEventLoop+0x49
00000000`1c90fdf0 00000000`00866471 : 00000000`00000002 00000000`00000000 00000000`18c78a08 00000000`00000000 : dvacore!dvacore::threads::SyncPoint::operator=+0xbe
00000000`1c90fe50 00000000`00866327 : 00000000`18c789a0 00000000`00000000 00000000`00000000 00000000`7381334a : dvacore!dvacore::threads::GetCurrentThreadID+0x1261
00000000`1c90fe80 00000000`00205431 : 00000000`18c789a0 00000000`00000000 00000000`14c4cd40 00000000`00000000 : dvacore!dvacore::threads::GetCurrentThreadID+0x1117
00000000`1c90fec0 00000000`73812fdf : 00000000`14c4cd40 00000000`00000000 00000000`00000000 00000000`00000000 : boost_threads!boost::this_thread::get_id+0xd71
00000000`1c90ff00 00000000`73813080 : 00000000`7389cad0 00000000`14c4cd40 00000000`00000000 00000000`00000000 : MSVCR90!endthreadex+0x47
00000000`1c90ff30 00000000`76cf652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : MSVCR90!endthreadex+0xe8
00000000`1c90ff60 00000000`773ec521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`1c90ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
FOLLOWUP_IP:
Display!MediaCoreDisplay::C+2fbc
00000000`0d1e30bc 488b01          mov     rax,qword ptr [rcx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: display!MediaCoreDisplay::VideoNode::CreateEffectNode+2fbc
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Display.dll
STACK_COMMAND: ~44s ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: INVALID_POINTER_READ_SHUTDOWN_c000041d_Display.dll!MediaCoreDisplay::VideoNode::CreateEff ectNode
Followup: MachineOwner

The first thing to do when experiencing OS crashes is to run the Apple Hardware Test that came with your machine using the extented tests. If the machine passes those tests, get MemTest and wring out the RAM. See Mac OS X Kernel Panic FAQ, Resolving Kernel Panics, and Tutorial: Avoiding and eliminating Kernel panics for more details.

Premiere Pro CC updated - crashes almost immediately on my mac OS X Yosemite 10.10.3. Crashes at startup, crashes with media import, crashes when creating a sequence. NEED HELP FAST I have tried many troubleshooting solutions I found online nothing has

Premiere Pro CC updated - crashes almost immediately on my mac OS X Yosemite 10.10.3. Crashes at startup, crashes with media import, crashes when creating a sequence. NEED HELP FAST> I have tried many troubleshooting solutions I found online nothing has worked.

Hi,
Sorry to hear about the experience. Please provide your computer configuration details.
Memory, Processor, Graphics card, Exact version of Premiere Pro, Error message that you are get. If you can post screenshots of the error report that would be helpful.
Thanks,
Rameez

Startup crash LV 2009 SP1 (bug?)

Similar Messages

Maybe you are looking for