LabView crashing on startup

[nreggie92]

Hello,

I've been having an issue with LabView lately where it has been crashing at the "Getting Started" screen.  The screen will be up for 5 to 10 seconds before I get a crash report (screenshot attached).  It also crashes when I open up any VI within 5 to 10 seconds.  I have done a repair and a reinstall with no luck in fixing the problem so far. Anyone have any ideas?  The crash report looks like this:

####
#Date: Tue, May 27, 2014 8:46:53 AM
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: LabVIEW
#Version: 11.0.1 32-bit
#AppKind: FDS
#AppModDate: 12/12/2011 21:27 GMT
#LabVIEW Base Address: 0x00400000

5/27/2014 8:47:05.393 AM
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 9c13bcd6-995a-49bc-9800-87899131644d
ExceptionCode: 0xC0000005
0x01AB8639 - LabVIEW <unknown> + 0
0x01AB8B78 - LabVIEW <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77E074FF - ntdll <unknown> + 0
0x77DC9F45 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

[GerdW]

Hi nreggie,

did you try to delete the LabVIEW.ini before starting LabVIEW?

(Remember to create a backup of that file before deleting it!)

[nreggie92]

Yes, I just tried it but I am still getting the same crash report.

[SkyWalka]

Since it is an Access Violation error, do you have admin privelages on this PC?  What happens when you right click LabVIEW and choose to Run as Admin?

Also, try disabling any antivirus that you may have running.

[billko]

---

@SkyWalka wrote:

Since it is an Access Violation error, do you have admin privelages on this PC?  What happens when you right click LabVIEW and choose to Run as Admin?

Also, try disabling any antivirus that you may have running.

---

I thought an exception 0xC0000005 access violation error was a Windows error meaning the application was trying to access an aera of memory that wasn't allocated to it?

[freemason]

nreggie

were you able to fix this issue?

can you share your solution. i am have the same problem but in 2016.

Thanks