Labview 2012 SP1 Crashes in Windows 7 SP1

[TescomAustin]

I have Labview 2012 SP1 on my Dell Optiplex 780. I'm not a heavy user, so please bear with me.  Light enough use in fact, that it will be an issue to be able to get a purchased update.

My Labview 2012 SP1 (32 bit) crashes just about no matter what I ask it to do.  I can open the program and start a new project. I am trying to do simple things like operate an Agilent 34420A to make temperature measurements.  Even when I try using Instrument Assistant, it crashes.  I am suspecting a compatibility problem between my 2012 Labview and Windows 7 Service Pack 1.  This seems to be a popular break point in compatibility.

Is anyone aware of such a compatibility issue?

[ML927]

I don't see any compatibility problem as stated here http://www.ni.com/product-documentation/53409/en/

Did you check what the error logs say ? https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PA7mSAG

[TescomAustin]

I've had some recent issues where NI software says it is compatible with Windows 7 (but does not specify Windows 7 Service Pack 1) .  There is some NI software that specifies compatibility with Windows 7 Service Pack 1 (versus just "Windows 7") where it does indeed make a difference.  That matrix does say copatible with Windows 7, but there is no information about Windows Service Pack 1 requirements or compatibility.  

[tyk007]

I have run 2012SP1 patch f5 in my Windows 7 SP1 VM for several years and many projects without any issues.

[TescomAustin]

That's actually encouraging.  At least perhaps my version of LabVIEW will work on my platform.  Following is the LVLOG.TXT file.

####
#Date: Thu, Apr 12, 2018 3:20:46 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 12.0.1f9 32-bit
#AppKind: FDS
#AppModDate: 05/13/2014 23:06 GMT
#LabVIEW Base Address: 0x00400000

<LVExec>
{"a":[
{
"vi": "C\\Program Files (x86)\\National Instruments\\LabVIEW 2012\\instr.lib\\Agilent 34420\\Public\\Initialize.vi",
"ctx": "Main Application Instance",
"type": "subVI"
}
,
{
"vi": "C\\Program Files (x86)\\National Instruments\\LabVIEW 2012\\instr.lib\\Agilent 34420\\Examples\\Agilent 34420 Read Single Temperature.vi",
"ctx": "Main Application Instance",
"type": "topVI"
}
] }
</LVExec>

<DEBUG_OUTPUT>
4/12/2018 3:27:56.823 PM
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: 8c2c7416-2a0e-45ef-916d-45be5d616344
ExceptionCode: 0xC0000005.¥luñ

</DEBUG_OUTPUT>
0x01AF3549 - LabVIEW <unknown> + 0
0x01AF3A58 - LabVIEW <unknown> + 0
0x721F85FA - mscoreei <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77A950D7 - ntdll <unknown> + 0
0x77A59805 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

[ML927]

Have you tried to run a really basic VI ? Like just a loop doign a simple calculation a certain number of time. From what I understand from your description, it seems that LabVIEW crashes when you try to access some kind of instruments.

[TescomAustin]

I am on my second instrument.  First I worked with an Agilent 34420A, and now, a Fluke 8508A. In both cases, I have tried very simple things. On each, I tried using the RESET.VI. I selected the correct GPIB address which showed up. Then as soon as I hit the PLAY/GO (right arrow) button to start the VI, LabVIEW crashed. I tried this with a number of different simple VI's. Always the same result. I can't do anything without LabVIEW crashing.  

I did a REPAIR reinstall, and updated from f5 to f9.  I am about to try completely uninstalling and removing all NI software, and reinstalling freshly.  

[TescomAustin]

I also just upograded RAM on the Optiplex 780 where my LabVIEW 2012 SP1 f9 is installed, from 4 GB to 16 GB to eliminate that as a possible cause.  No.  Problem is still there.  My next step is a complete de-installation of my NI software, and re-install from scratch.

If anyone has any ideas, let me know.

[ML927]

Maybe look here and check if the DWarnDialog may give you clues about your specific crashes.

[TescomAustin]

That statement doesn't exist in my ini file.  If I interpret correctly, I should add a line that says:

DWarnDialog=True

Is that correct?