LabVIEW Crashes While Loading Project

Hey All,
I have an interesting issue here where I try to load a large project, and somewhere near the end LabVIEW just disappears.
I'm running the latest version of LabVIEW 2010 (Just Updated) on Windows 7 Professional 64.\
The project has RT and FPGA components.
- Ken

I had the same problem with modified xcontrols and typedefs with control references.
Try to open the project vi's/classes/libs separately, fixing broken arrows and then saving them
When you are done with all files, try opening the project again.
/Roger

Similar Messages

LabVIEW crashed while loading Sensor Mapping Express VI

Dear all,
I've just installed LV8.6 evaluation with all the toolkits available in the DVD. I have two problems now, one major and one minor:
1. Whenever I tried to use the Sensor Mapping Express VI, LabVIEW crashed with the pop-up window saying that "LabVIEW 8.6 Development System has stopped working". When I expanded Window's error pop-up, the message as can be found below. The same error occurs whenever I tried to load the sensor mapping demo I downloaded from the Developer Zone. I'm using Dell Inspiron 640m, by the way. When I tried with another Dell laptop (Dell Vostro), everything was alright.What I've done so far is to uninstall all NI's softwares inside this laptop, defrag, clean the registry and then reinstall LV 8.6 again but to no avail.
Error message:
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    LabVIEW.exe
Application Version:    8.6.0.4001
Application Timestamp:    4862fd60
Fault Module Name:    ig4dev32.dll
Fault Module Version:    7.14.10.1147
Fault Module Timestamp:    457ef11c
Exception Code:    c0000005
Exception Offset:    000063b2
OS Version:    6.0.6001.2.1.0.768.2
Locale ID:    17417
Additional Information 1:    da97
Additional Information 2:    7a880e72b9f1636f81b04947e06e5c6a
Additional Information 3:    09b4
Additional Information 4:    56e138085db0c350e7bf46ba31a7691f
My computer specs are:
OS: Windows Vista Home Basic
RAM: 1.5 Gb
Harddisk: 10Gb free (after LV is installed)
Processor speed: 1.6 GHz Dual Core
Anti Virus: Kaspersky Internet Security
2. This is minor but still an annoyance. Whenever I tried to load my newly installed LabVIEW 8.6, it takes about 10-15 minutes before I got the Getting Started window. This includes the 5 minutes waiting period before I got the window stating how many days left for evaluation. This wasn't the case when I used LabVIEW 8.5.1 (even when every toolkits and modules are installed). Why so long?
I've asked the local NI engineers but they are also clueless.

Hi Lan,
Thanks for your post and I hope your well today.
1) You specs seem okay.
Minimum
Recommended
Processor
Pentium III/Celeron 866 MHz or equivalent
Pentium 4/M or equivalent
RAM
256 MB
1 GB
Screen Resolution
1024 x 768 pixels
1024 x 768 pixels
Operating System
Windows Vista/XP/2000
Windows Vista/XP
Disk Space
1.6 GB
1.6 GB (Note -- Includes default drivers from NI Device Drivers CD)
There has been some record of issues with the Sensor Mapping Express VI.
Does it crash when you place it down on the block diagram? Or when you click to move it? Or when you run it? Does this happen when you load a model into it?
However, as it seems to be an instance of your Dell Inspiron 640m, Im not sure what we can suggest - except to ask how the specs compare between the two machines?
Some advice for Dells,
#) So that LabVIEW can function properly with the video hardware, it is
occasionally necessary to reduce the video acceleration. You can do
this on Windows 2000 by right clicking on your desktop » Properties » Settings » Advanced » Troubleshooting.
Start with the second setting from the right, "Disable bitmap and
cursor acceleration.", and work your way left if the problem persists.
#) Number of other issues with versions of Dell video drivers.. upgrade?
2) If this is a new installation that is slow then you may be having issues with specs, however there are a few things to try:
a) Defrag Drive
b) VLM licensing? If so, there is a timeout of a view minutes... is your version licensed currently?
c) Clean your registry
d) Check LabVIEW ini file to make sure the tasks are all necessary and the paths are local.
e) Repair LabVIEW finally
Hope this helps make some progress,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Premiere Pro CC 2014.2 Crashing while loading project...

When trying to open Premiere project the program opens and looks like it will load and then crashes.
If I create a new project Premiere opens and I can import footage but as soon as I try to play footage in the preview window or drop it in the timeline the program crashes as well.
I am working on a Windows 7, 64-bit, i7, 8GB ram, 1TB multiple partitioned hard drive. My Graphics card is, Intel(R) HD Graphics 4600 - Driver Version: 9.18.10.3204
My Error Log is:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: MXF_SDK_4.4.33_vs10.dll, version: 4.4.33.0, time stamp: 0x534d772c
Exception code: 0xc0000005
Fault offset: 0x00000000000bdc55
Faulting process id: 0x378c
Faulting application start time: 0x01d02c3625e455c1
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\MXF_SDK_4.4.33_vs10.dll
Report Id: b1b66e81-9829-11e4-95ce-c4346b64bc4f
I can't figure out what the faulting module is.
I just installed CC 2014.2 3 days ago. It all worked fine until yesterday when Premiere started crashing. I restarted the system - same issue. I uninstalled and reinstalled Premiere2014.2 - same issue. Premiere seems to be the only faulting application. Everything else (Ps, Ae, Lr, Id, Au, Ai) appears to still be working.
My version of CS6 (Purchased before getting a creative cloud membership not downloaded through CC) is also still working properly.
Thanks for the help.

Update: I updated my Graphics Card Driver to a more recent version. Restarted computer and reopened Premiere and similar crash happened. I went through to get some more crashes and had different crash reports. The faulty module is not always the same.
Problem Event Name:                        APPCRASH
Application Name:                             Adobe Premiere Pro.exe
Application Version:                           8.2.0.65
Application Timestamp:                     5486db4a
Fault Module Name:                          devenum.dll
Fault Module Version:                        6.6.7600.16385
Fault Module Timestamp:                  4a5bded7
Exception Code:                                  c0000005
Exception Offset:                                00000000000016a0
OS Version:                                          6.1.7601.2.1.0.256.48
Locale ID:                                             1033
Additional Information 1:                  ec5a
Additional Information 2:                  ec5adb2545b190cc19da7bdfa78d5bf1
Additional Information 3:                  6e59
Additional Information 4: 6e59168cf9de1a4a9616903b4a4ba1e1
Problem Event Name:                          BEX64
Application Name:                             Adobe Premiere Pro.exe
Application Version:                           8.2.0.65
Application Timestamp:                     5486db4a
Fault Module Name:                          OpenCL.dll_unloaded
Fault Module Version:                        0.0.0.0
Fault Module Timestamp:                  50eb1a5b
Exception Offset:                                000007fee84516a0
Exception Code:                                  c0000005
Exception Data:                                   0000000000000008
OS Version:                                          6.1.7601.2.1.0.256.48
Locale ID:                                             1033
Additional Information 1:                  a527
Additional Information 2:                  a527a6af76c2b04cfd1fc255c66e5364
Additional Information 3:                  21c7
Additional Information 4:                  21c71ffc516aa3806e495b8080bd51fe
Both of those are different from the original posted report.
I did have some success following these instructions.
Premiere Pro CC 2014.1 has stopped working - Win 7 64 bit
It appears I do not have a graphics card that is compatible with the mercury engine. I have had three successful tests and one crash since I selected Renderer: "Software only"
I plan to upgrade to a Nvidia card or the supported Intel Iris Card.
This seams to be the issue but I am hesitant to use CC 2014.2 for the time being because I don't know if it will crash randomly and CS6 is working fine. The second error code with "Fault Module Name: OpenCL.dll_unloaded" seems to be directly related to the graphics card and rendering processes. I will update as I learn more.
Please comment with any suggestions or resolutions you have had.

LV crashes while loading my llb, but the built app. functions correctly???

I�m hoping someone may understand the cause of the LabVIEW crash I�m experiencing.
LabVIEW 6.1 crashes and Windows 2000 says, "LabVIEW.exe has generated errors and will be closed by Windows" when I try to load an llb by clicking on the top-level vi from within LabVIEW or when opening the llb from outside LabVIEW. It crashes while loading particular sub-vi�s of the llb. If I try to load the offending subvi�s directly, I also get the same crash. If I build the llb into an application, the build goes smoothly and the resulting application functions correctly. If I use a �splash screen� approach and do not load the offending sub-vi�s (by not opening vi references to them), they load-up fi
ne when the top-level vi loads and then I am able to edit and re-save any vi of the llb including the offending sub-vi�s. I�ve tried re-saving the llb as a separate development distribution and still get the same crash behavior. I�ve also tried saving the offending sub-vi�s to separate files outside the mother llb (after getting them open with the splash screen approach) and I get the same crash when I open these files. If I save one of the offending sub-vi�s as a separate llb, I can�t get it open even with the splash screen approach. I�ve loaded the latest video driver for my Dell Inspiron 8100 laptop and I get the same behavior on a Dell Dimension 8200 desktop that is also running Windows 2000 (Version 5 SP4). There are 110 objects in my llb that includes *.vi�s, *.rtm�s, and *.ctl�s.. Any ideas as to why/how this is occurring and how I can fix it? Is this a known 6.1 bug that is fixed in 7? Any info would be greatly appreciated. I�ve included my splash screen like loader, f
or what it�s worth. Thanks.
Attachments:
__loadVIs.vi ‏88 KB

Thanks for responding. Your understanding is correct. Mass compiling was one of the first things I tried (although I failed to mention it). I also un-installed and re-installed LabVIEW. It crashes during mass compiling of the full llb, although the vi that it appears to be working on when it crashes is not an �offender�, i.e. I can open that vi fine. The crash during mass compiling is the same crash, i.e. Windows says it had to close LabVIEW because it generated errors.
I�ve attached one of the offenders. It is missing many of it�s sub-vi�s so you�ll have to hit �ignore vi� a bunch when opening it. (The llb of it is ~2.6 MB. I thought that might be too big/rude to post.) This vi crashes LabVIEW upon mass compile or upon opening it (after hit
ting �ignore subvi� a bunch).
I was going to attach an llb of another smaller offender, but in the process of editing it to be a little prettier and better documented, the problem kind of vanished for that vi. The main routine still crashes when I mass compile the full llb, but now I can open some of the old offenders without incident. I still can�t open the main routine directly as it crashes LabVIEW. Thanks for your time.
Attachments:
aveParam.vi ‏769 KB

JVM Crash while loading StackFrame

# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.2_04-b05 mixed mode)
# Error ID: 53414645504F494E540E4350500159
# Problematic Thread: prio=5 tid=0x008cf798 nid=0x8a8 runnable
I would get very similar or same error like above.
I have got around it, but I would like to find out why it was happening.
If you look at following function, you will notice this.get_ID() call.
I used to pass "this" object instead of this.get_ID().
If I replace this.get_ID() with "this" object JVM would crash while loading stackframe.
Also, it would crash around while loading
"Iterator Keys = m_UserCollection.getKeys();"
Does anybody have any idea what might have caused above function to crash while loading stackframe?
Thanks in advance.
public void setUsers(UserCollection value)
if(m_UserCollection == null)
m_UserCollection = UserFactory.GetUsers(get_ID());
UserCollection inCol = value;
Iterator Keys = m_UserCollection.getKeys();
while(Keys != null && Keys.hasNext())
Object key = Keys.next();
User current = m_UserCollection.getm_users(key);
User newUser = inCol.getm_users(key);
if(current != null && newUser == null)
current.RemoveFromGroup(this.get_ID());
else
inCol.Remove(key);
Iterator enums2 = inCol.getKeys();
while(enums2.hasNext())
inCol.getm_users(enums2.next()).AddToGroup(this.get_ID());

Hi
Did it dump out where the function name is?
Is it happening consistenly?
Can u try running with -XX:+PrintCompilation and show the last few printed line? You will see something like
11 b java.lang.String::lastIndexOf (67 bytes)
Thanks.

I'm getting error as adobe Illustrator crashes while loading the multiple pages PDF file. Please help me. Thanks in advance.

Hi,
I'm getting error as adobe Illustrator crashes while loading the multiple pages PDF file.
Please help me. Thanks in advance.

Hi Monika,
I have downloaded the script to load the multiple page of pdf file.
I tried loading the multiple page PDF file via File Menu -> Scripts -> Other Script...
After executing the script file -> Browse and enter the page number - > OK
The PDF file is looks like created from word document. There are total 120 pages in this file.
PDF file size is 20 MB.
I'm still searching for the solutions. Please help me.
Thanks,
Lavprasad

Lighroom crashed while loading new pictures.

Lightroom crashed while loading new pictures. Cannot open it anymore: cannot read cache. Downloaded a new version: my license number is not valid???? What's next?
Thanks. Dany

Sorry for the lack of info. I wasn't sure how this forum thing worked...
Here are the details:
LR 5,7 crashed while loading pictures. I was away for a moment, when I went
back to the computer, I had to reenter my session and try to reopen LR.
OS is Windows 7 Pro
Message: LR encountered an error when reading from its preview cache and
needs to quit.
When I restart it, it still shows the same message and doesn't open. I
downloaded a new version (5.7.1) and if I enter my serial number it doesn't
recognize it. If I click on Trial, it shows the same error message...
Thanks,
Dany
2015-03-25 9:49 GMT-04:00 F. McLion <[email protected]>:
Lighroom crashed while loading new pictures. created by F. McLion
<https://forums.adobe.com/people/F.+McLion> in Photoshop Lightroom - View
the full discussion <https://forums.adobe.com/message/7348060#7348060>

My ipad crashed while loading Ios7

My IPAD crashed while loading IOS7. Now I can't restore back to factory condition neither new os is laoding.
So I took my IPAD to nearby Apple store, and apple tech can't fixed it either. After over hour of waiting, Apple tech first told me to Pay $299.00 for the replacement unit and after I refused to pay first time, then they lowered the price to $99 for the refurbish replacement unit with 3 months warranty.
Apple tech tried to fix my IPAD for couple of hrs. and only thing they could say is that my IPAD is getting generic error 101, that means it has a hardware and or software failure but can not pinpoint to the issue. There is no damage or issue prior to downloading the new OS.
Can anyone advise me what I shoud do? Thanks.

I would suspect that there is an internal hardware failure in the iPad and it will have to be replaced.

Efi detects wrong resolution - osx crashes while loading loginwindow.app

Hello,
I have a strange problem: Sometimes EFI loads OS-X with wrong display resolution which ends into a crash of loginwindow.app.
Let me explain it in more details: First I had a system with rEFIt. Everything worked like a charm ... until on some day (I think it was EFI Update 1.5.1, but I don't know it exacly) my mbp rev3 sometimes decided to show EFI menue much larger as you would expect it on a 640x480 display. This happens in about 3 of 4 boots. If this happened, OS-X crashed while loading loginwindo.app and Windows crashed before showing the windows loading screen.
Then after talking with some guys in irc unofficial support I reinstalled everything because they said all my 3rd parity software could be the reason for this error. Now I have a fresh installed leopard and the error still occures - and the error also occures when I boot into leopard disc.
*To describe the problem in a few words:*
- EFI detects display resolution wrong in about 3/4 boots
- loginwindow.app crashes if EFI detected resolution wrong
- while crashing some strange artefacts are shown on grey apple screen / on verbose mode console, sometimes screen gets orange for about 0.1 sec before artefacts are shown
*I tried following things to fix the problem:*
- reset vram: no result
- verbose mode: does not show anythingnew compared to right boot, after message "loginwindow.app is loading" "login windoe application started" i get some artefacts and the orange screen
- single user mode: did't find something in logs, but I also didn't find an efi log
- hardware diagnostics: says everything is right
- Firmware Restoration CD: does not work because my mac seems to think that everything is right.
- plug off all external usb devices: no effect
Now I really don't know what to do, I don't even have an idea where to find this error and what to try next. The mbp is my only computer, so I would find it excellent to solve the problem for myself.
Thanks for any help what to do
Message was edited by: TheInfinity

I'm not sure why you're password is wrong when you type it directly in your station, but I have found something related to remote logging.
I had always gotten the password wrong when I tried to connect through VNC from my Linux to my Mac. The problem is that for some reason, my keyboard layout is applied twice. I'm using the colemak layout, so if I want to type 'K', I need to click on the key that is marked 'N' in QUWERTY keyboard.
BUT, through VNC to my mac, if I want to type 'K', I need to type the key that is mapped to 'N' on colemak layout, which is the key marked 'J' in QUWERTY.
So to type hello, through normal colemak, I would click on hkuu;, but through VNC to the mac, I need to click on hniip.
Here's the map that can be used to generate the above:
Qwerty -> Colemak
k -> e
n -> k
j -> n
e -> f
h -> h
u -> l
; -> o
p -> ;
i -> u
My solution was to find out how my password should be typed with double-applied colemak, then after log in, change the keyboard layout to QWERTY, and then it is applied only once and I can type in normally. I'm not sure what's the cause of the bug, but at least you have something to try..

LabVIEW Crashes when Opening Project

Hey Guys,
I'm running into an interesting issue where LabVIEW crashes when opening a project. This is the second time I've run into this issue, on the same project. To get around it the first time I simply deleted and re-made my project, but since it's happened again, I need to figure out how to debug it. The symptom is that LabVIEW will crash when opening the project (sometimes I can see the "vi loading" screen) without any indication that crash has occured. It doesn't even launch the error reporter, the process just dies. Anyone know how I can go about debugging this?
Solved!
Go to Solution.

xkenneth86,
What version of LabVIEW? Have you ever had previous versions of LabVIEW on your computer? Can you attach a screenshot of the crash?
David H.
National Instruments

My MacBook Pro completely crashes while loading up games

Hey all, thanks for reading.
I'm running a MacBook Pro (<1 year old)
Processor: 2.8GHz Intel Core 2 Duo
RAM: 4GB 1067 MHz DDR3
It's connected to the power supply, and it's set to High Performance (meaning the dedicated graphics card should be in use)
Every time I try to play a game, my Mac completely freezes. I'm currently trying to play the Sims 3; hardly graphic-intensive. As soon as I click the Play button, the screen goes black and the disc drive starts to whirr (sometimes vibrating the computer violently). Then the animated EA logo swirls onto the screen, and the load music starts up. Before the EA logo can fully animate, my computer dies. The screen instantaneously goes black, and the background music keeps playing in a skipping fashion, like a broken record: click-click-click-click.
Force Quit does nothing. None of the hardware buttons, e.g. volume/brightness controls, do anything. I have to hold down the power button to restart.
It probably isn't overheating, since I've tried with my fans on full blast (smcFanControl) and I'm currently using a laptop cooling pad.
I used to be able to play the Sims for a few hours before it would crash: it has gotten much worse. I downloaded the WoW demo and got a bit farther: I could create a character, but within 5 seconds of playing this same problem would happen.
I know Macs aren't particularly good at playing games, but this seems a bit ridiculous. Can anyone help? I have the full error report saved, if that would be useful.
Summary: While loading a game, my MacBook Pro full-crashes, becoming totally unresponsive, before the EA logo can even animate.

Try it using the other (dedicated) graphics. Also, run your hardware tester.
Check out the new remodeled MacOSG website! 24-hour Apple-related news & support.
 MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

PremierePro 5.5.2 Mac Crashes While Loading Tiffen Dfx 3

Anyone using the Tiffen dfX 3.0 filters?
Since updating to PPro 5.5.2, Premiere crashes while attempting to load the Tiffen filters. Updated to Tiffen's most recent release 3.0.4.1 but crashes whenever I attempt to launch PPro.
Ned Soltz

Tiffen has just released v 3.05 of DFx and that fixes all crashing issues!
Ned

Premiere Elements 11 crashes while loading ImporterQuickTime.pm

Hi all!
I'm facing a problem with Adobe Premiere elements 11.0 whenever I launch it (even launched directly without passing the organizer's launch screen) it stops while loading ImporterQuickTime.pm.
Here's my PC specifications:
Windows 7 32bit
Ram 2GB
Intel Dueo CPU 2.20GHZ
SIS Mirage 3 Graphics adapter
QuickTime version: 7.7.4 (latest)
Is there a troubleshooting steps or logs where I can find the culprit?
Thanks for any help.

Numerdiaweb
This type of issue does not seem unique to Premiere Elements 11, and I am not certain that this is one answer to a fix.
The person with this type of issue is usually put through the drill
http://forums.adobe.com/thread/951360
which includes
a. Is latest version of QuickTime installed? If you have the latest version, have you tried uninstalling reinstalling it?
b. Is your video card driver up to date according to the web site of the manufacturer of the card?
c. Do you have the latest Windows Updates and was all working before the Windows Updates?
I ran into this issue with Premiere Elements 11 on Window 7 64 bit. The only thing that worked everytime to get beyond this block for me was to go to the Task Manager/Processes and End Process for a Process named ElementsOrganizerSyncAgent.exe. The irony of it was that this .exe was located in the Premiere Elements 8.0/8.0.1 files on the hard drive. I have since deactivated, uninstalled, reinstalled Premiere Elements 8.0/8.0.1 and the problem has not reappeared.
With the possibility of undefinited corrupted files, you might want to look at"
a. Deleting the Adobe Premiere Elements Prefs file or the whole Folder that it exists in Windows 7 64 bit...(you may need to translate these details into 32 bit system...please ask for help if you need that...
Local Disc C
Users
Owner
AppData
Adobe
Premiere Elements
11.0
and in the 11.0 Folder is the Adobe Premiere Elements Prefs file that you delete. As I mentioned, if just the Prefs files has no impact, then try deleting that 11.0 Folder that it exists in.
Remember to have Folder Options Show Hidden Files, Folders, and Drives on so that you can see the path involved.
That 2 GB installed RAM caught my attention, but I would think that you would be able to get beyond that QuickTime message even at that. But do look into increasing that 2 GB RAM to at least 4 GB (which is the maximum supported for 32 bit system).
Let us start here and see if any of the above leads to the solution.
Thanks.
ATR
Add On...I was unaware of SG's post in your thread until after I had posted mine.

LabVIEW Crashes while closing the VI

Hi all,
I am experiencing a labVIEW crash everytime I close my VI after running it. what the VI is doing is, it communicates with an opal kelly board through the okFrontPanel.dll and reads some data from it and displays it in the front panel. The vi runs fine and I get the results as well. But after stopping the vi, when i try to close the vi, labVIEW crashes.
Has anyone faced such an issue? I would appreciate if anyone can help me fix this issue.
Thanks and regards,
Nitz
(P.S: I am not able to upload the code due to restrictions and also its a quite lengthy code to create a sample vi to replicate the scenario)
Solved!
Go to Solution.

A crash is usually an indication that something inside the DLL is touching an area of memory which it shouldn't be touching. The fact that the VI runs fine is incidental. It seems that in this case the DLL touches something which is only affected when LV needs it when closing the VI. I think the only thing you can do about it on the LV side is make sure you allocate large enough buffers for variable length parameters the DLL uses. I'm assuming you don't have access to the source code of the DLL?
Try to take over the world!

Mail 1.2.5 on 10.2.8 crashes while loading 12 messages

Mail quits while loading messages. There are 12 messages. It will get anywhere from 8-11 messages before quiting. I have taken out the mail preference to the desktop and it still quits. Any ideas? It is on an ibook running 10.2.8.

Hello Steven.
If for a POP type account, try the following.
With the Mail.app quit and using the Finder, go to Home > Library > Mail > this POP account named folder (named by the user name and incoming mail server for the account) > INBOX.mbox.
Move the INBOX.mbox to the Desktop.
When re-launching Mail, a new INBOX.mbox will be created automatically by Mail within the account named folder.
If all 12 messages are successfully downloaded, this indicates the old INBOX.mbox moved to the Desktop has some corruption.
If successful, control-click on the old INBOX.mbox moved to the Desktop and at the menu window that appears, select Show Package Contents.
List the package content file names and size of each here.

LabVIEW Crashes While Loading Project

Similar Messages

Maybe you are looking for