My Teststand crashed with the following error:
And here is error report:
#Date: qui, 25 de Fev de 2016 16:11:27
#OSName: Windows 7 Professional Service Pack 1
#Version: 14.0.1f1 32-bit
#LabVIEW Base Address: 0x30000000
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 4 processors
InitExecSystem() call to GetNumProcessors() reports: 4 processors
InitExecSystem() will use: 4 processors
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: e566f74f-c640-4760-8afc-fb4098ab137d
0x0ECC11AB - nierInterface <unknown> + 0
0x0ECC5E96 - nierInterface <unknown> + 0
0x0ECC621C - nierInterface <unknown> + 0
0x7686031F - KERNEL32 <unknown> + 0
0x7776344F - ntdll <unknown> + 0
0x77729855 - ntdll <unknown> + 0
0x00000000 - SeqEdit <unknown> + 0
Does anyone know what could be the possible cause of it?
Thank you in advance for your help,
An access violation always occurs when an user space application tries to access memory which is protected (e.g. kernel mode memory).
That being said, the reason is most likely created by invalid references.
Does this error occur every time you use TS or only with specific sequences?
This happenned twice so far. In a teste that runs in cycle for 6 hours.
It's running in loop, what do you think that can be happening?
The issue obviously occurs in a LV module. Can you identify and post that VI?
If you click the View Report link in that dialog, or go to the LabVIEW Data Folder (Likely in C:\Users\Documents\LabVIEW Data) and navigate to LVInternalReports\SEqEdit\<version> and find the folder with the Report ID from your dialog, you will see a crash dump file that might provide more information. Can you post that file as well? If the file is too large, you can send me a private message and I'll send you information about FTP'ing the file to us.
Try to change the adapter for labview
go to configure >> adapters>> Labview >> (change from Runtime to Develpment Enviroment)