Device dll, crash
Greetings,
I'm trying to use a device driver written by delcom to control my usb numeric indicator, but when I try and load the DLL it always crashes.
I've followed the prototyping scheme, and I'm basically trying to get just the simplest function working, which is the call library function to call the function GetNthDevice to return a string. I've set the DWORDs to LONG, and the Lpstr to String. No matter how i set it up, it always crashes.
Can anyone point me in the right direction? I'm used to working in java and this is very greek to me.
Attachments:
DelcomDLL.dll 144 KB
manual.pdf 202 KB
hi
please try the attached vi. i preallocated the "name" -Parameter with 512 Bytes (according to the manual) and used stdcall - convention. i don't have the hardware to test it, but at least labview won't crash.
regards
chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"
Attachments:
Call_Dll.vi 19 KB
Similar Messages
-
CoreFoundation.dll crash followed by iTunes Stops Working on Win7 x64
Hello
I had a Sony Vaio laptop (64 Bit Win 7 Pro and Office etc) for almost 2 years. After running latest windows updates (I think) iTunes started stopping at launch.
After searching thru support forums and testing various suggestions, I thought my Win 7 installation got old and corrupted and I was already thinking of upgrading my laptop to i5 or i7, I asked my company to renew my laptop. I started installing my new Sony Vaio.
Same problem reappeared
Safari Quicktime all works. Only iTunes crashes.
Win 7 64 bit Pro
iTunes 10.4.1.10
On event viewer, on iTunes launch, corefoundation.dll crashes, few secs later, I receive
iTunes.exe
10.4.1.10
4e4e1904
CoreFoundation.dll
1.630.14.0
4e0373f7
c0000005
0004bd33
278c
01cc87c8fafbb85e
C:\Program Files (x86)\iTunes.exe
C:\Program Files (x86)\Common Files\Apple\Apple Application Support\CoreFoundation.dll
3c09b303-f3bc-11e0-8034-c0f8daf75f5d
Version=1
EventType=APPCRASH
EventTime=129627786618304736
ReportType=2
Consent=1
UploadTime=129627786624065066
ReportIdentifier=3c09b304-f3bc-11e0-8034-c0f8daf75f5d
IntegratorReportIdentifier=3c09b303-f3bc-11e0-8034-c0f8daf75f5d
WOW64=1
Response.BucketId=2575568783
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=iTunes.exe
Sig[1].Name=Application Version
Sig[1].Value=10.4.1.10
Sig[2].Name=Application Timestamp
Sig[2].Value=4e4e1904
Sig[3].Name=Fault Module Name
Sig[3].Value=CoreFoundation.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=1.630.14.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4e0373f7
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0004bd33
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1055
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=9e27
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=9e2778096e7e1e2a2e0302fe58f3eea8
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=9e27
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=9e2778096e7e1e2a2e0302fe58f3eea8
UI[2]=C:\Program Files (x86)\iTunes.exe
UI[3]=iTunes has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a soHello
I had a Sony Vaio laptop (64 Bit Win 7 Pro and Office etc) for almost 2 years. After running latest windows updates (I think) iTunes started stopping at launch.
After searching thru support forums and testing various suggestions, I thought my Win 7 installation got old and corrupted and I was already thinking of upgrading my laptop to i5 or i7, I asked my company to renew my laptop. I started installing my new Sony Vaio.
Same problem reappeared
Safari Quicktime all works. Only iTunes crashes.
Win 7 64 bit Pro
iTunes 10.4.1.10
On event viewer, on iTunes launch, corefoundation.dll crashes, few secs later, I receive
iTunes.exe
10.4.1.10
4e4e1904
CoreFoundation.dll
1.630.14.0
4e0373f7
c0000005
0004bd33
278c
01cc87c8fafbb85e
C:\Program Files (x86)\iTunes.exe
C:\Program Files (x86)\Common Files\Apple\Apple Application Support\CoreFoundation.dll
3c09b303-f3bc-11e0-8034-c0f8daf75f5d
Version=1
EventType=APPCRASH
EventTime=129627786618304736
ReportType=2
Consent=1
UploadTime=129627786624065066
ReportIdentifier=3c09b304-f3bc-11e0-8034-c0f8daf75f5d
IntegratorReportIdentifier=3c09b303-f3bc-11e0-8034-c0f8daf75f5d
WOW64=1
Response.BucketId=2575568783
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=iTunes.exe
Sig[1].Name=Application Version
Sig[1].Value=10.4.1.10
Sig[2].Name=Application Timestamp
Sig[2].Value=4e4e1904
Sig[3].Name=Fault Module Name
Sig[3].Value=CoreFoundation.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=1.630.14.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4e0373f7
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0004bd33
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1055
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=9e27
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=9e2778096e7e1e2a2e0302fe58f3eea8
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=9e27
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=9e2778096e7e1e2a2e0302fe58f3eea8
UI[2]=C:\Program Files (x86)\iTunes.exe
UI[3]=iTunes has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a so -
Bib.dll crashing PS 5.1
Hey everyone,
I've come across what I strongly suspect is a weird font issue that's preventing me from working. Until today, PS has never acted up before. I'm running 64-bit Photoshop, v12.1. My work .psd was based on a toolkit .psd off the web - I was missing a font, and I substituted it with my own (one version of Helvetica Neue for another). But the moment I tried to edit the text, PS crashed on me. I reopened, worked on it for a couple more hours, when it crashed again doing the same action. After that I could not open either my own working file, nor the toolkit file.
The crash log says this:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 12.1.0.0
Application Timestamp: 4d90d339
Fault Module Name: BIB.dll
Fault Module Version: 1.2.2.12130
Fault Module Timestamp: 4d077745
Exception Code: c0000005
Exception Offset: 00000000000154dd
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 13eb
Additional Information 2: 13eb96961af4137840a8c77088b2606e
Additional Information 3: 18b1
Additional Information 4: 18b189364cc7acc5c20656c1fe72cd84
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
When I came across similar font issues like this one in AE I'd just deinstall the suspect fonts and things are good to go again. However even with my Helvetica removed the .psd files fail to open. I've had a coworker open the psd files on his computer with no issues (same machine and sofware specs), and I've also tried to have him change all the type to a default font and saving it as another file name, but even then I cannot open the file. I then began to suspect something was wrong with my PS, so I did a reset of my preferences and blew away my user settings. When that didn't work, I also had PS reinstalled -- still no luck.
Any suggestions how to move forward with this? I don't care so much about losing my current work file, but if I'm unable to even open up my toolkit .psd then I can't do anything. Are there other file formats I can save these files as (does that even change anything)?I just ran the script through, none of the fonts are corrupted. It seems like the issue began as a font problem, but now it's gone beyond that.
As for corrupt install, I had also tried reinstalling Photoshop. I trashed all my settings and tried opening up a new redownload of the toolkit .psd -- it appeared to be opening it but had the same bib.dll crash when it hit around 40%. I would ideally want this issue resolved without formatting my entire computer... -
BOXI 4 SP2 Patch 11 - Constant awt.dll crashes in the Event Log
Hi All,
Since implementing BOXI 4 SP2 Patch 11 I have noticed very frequent awt.dll crash error messages triggered by SAP JVM throughout the event log.
Does anyone know what is causing this and how to resolve?
=================================================================
Faulting application name: java.exe, version: 6.0.170.4, time stamp: 0x4c3bb897
Faulting module name: awt.dll, version: 6.0.170.4, time stamp: 0x4c3bfa5f
Exception code: 0xc0000005
Fault offset: 0x00000000000d2210
Faulting process id: 0x1c80
Faulting application start time: 0x01ccefaba2a15b7a
Faulting application path: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin\java.exe
Faulting module path: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\jre\bin\awt.dll
Report Id: a6ef5e00-5ba2-11e1-a8c2-da6052897efd
====================================================================
Also notice this error immediately afterwards reporting Transaction Deadlocks in our repository and auditing databases on SQL Server :-
=====================================================================
Database access error. Reason [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction..
=====================================================================
SQL Server version is 2008 Release 2.
Have deployed BOXI 4 using Tomcat 6/Java platform.
O/S in Windows Server 2008 Release 2.
This should be a supported configuration so need ideas on why this is happening?
Cheers,
GaryHi All,
SAP Support finally came through for us on this.
The issue is due to the version of the SAP JVM that comes bundled with BOXI 4 SP2 Patches 11 and 12.
If you download the latest version of the SAP JVM from the SAP support portal and install this instead then the problems are resolved.
Thanks,
Gary -
Jmc.dll crashes java.exe
First of thanks Sun's engineers for hard work on Java and JavaFX! I really enjoyed the features and demos from javafx.com.
Unfortunatly all of the demos involving media playback are crashing java.exe with jmc.dll being guilty (probably access violation - jmc.dll in the error dialog reports 0.0.0.0 version - but not sure). Well, I think it is my system's fault, because when I got rid of all codecs that could play mp3, java.exe stopped crashing (at least for DraggableMP3Player demo, SimpleVideoPlayer crashes without writing hs_err), but gave me MediaUnsupportedException. Regarding fixing my system - I'd like to avoid the pleasure of reinstalling Windows and I think it would be good for others having this problem to nail the cause of it. Could you explain how jmc.dll is dealing with platform codecs? How it checks what is installed? Does anyone else seen jmc.dll crashing java? Could it be hardware issue (I have nforce2 sound card)?
I've created issue [http://javafx-jira.kenai.com/browse/RT-2530] if you have the same problem please vote for it (you first need to register for free :))I sure have put some work in this bug. I hope this will be gone soon :). I'm somewhat surprised that nobody seen it beside me - no votes, no blogs about it. But UnsupportedMediaException is known for sure and I believe it is related (that's why I've voted for it). Thanks for all your sweat, tears and blood you put in JavaFX! :)
-
Ntdll.dll crash, exception 0xC0000005 After TestStand Deployment
I am trying to deploy a TestStand system, with custom test sequences, process model, some custom .dlls, and dynamic vi calls.
After finally getting the deployment to build, I can now successfully install on the deployment machine.
The deployment machine will successfully open my test sequence, and run my modified FrontEndCallbacks.seq.
I get stuck, when I try to run the actual test sequence!
When I do so, I get the error message telling me that ntdll.dll crashed. I don't know what this is, but I gather that is a Windows dll of some kind.
I am trying to figure out the cause.
Development machine: Win XP, 32-bit. TS 2010 SP1, LV 2011.
Deployment machine: Win 7, 64-bit. TS 2010 SP1, LV 2011 RTE.
The AE assisting me in this suggested that I had a .NET issue, but version 4, which was suggested I install, is installed.
Please help!Sure thing...
The interesting bit - this only happens if I try to run my test sequence with my modified process model. If i open a new sequence, and run it, this doesn't happen. I say this is interesting because, in either case, I am only pressing 'Test UUTs' - and this processes GUI info for the model, the test sequence isn't executed until I enter a SN and click go.
Attachments:
Run Error.png 91 KB -
Device Manager crashing: mmc.exe crashes with faulting mgr of devmgr.dll
Hello
I am unable to load device manager (either directly from control panel, or within the Computer Management MMC console. Everytime i attempt to do so, it crashes. An adminstrative event is raised on each occassion with the following:
Faulting application name: mmc.exe, version: 6.3.9600.16384, time stamp: 0x5215ef8f
Faulting module name: devmgr.dll, version: 6.3.9600.16384, time stamp: 0x5215ebc8
Exception code: 0xc00000fd
Fault offset: 0x000000000000e3a2
Faulting process id: 0x1c1c
Faulting application start time: 0x01ceff2006f4b512
Faulting application path: C:\WINDOWS\system32\mmc.exe
Faulting module path: C:\WINDOWS\System32\devmgr.dll
Report Id: 5ead3eb8-6b13-11e3-bec8-14dae9031ab6
Faulting package full name:
Faulting package-relative application ID:
There are a few similiar reports i've come across on the web, most centering around the .NET frameworks in use, invalid configs etc., but i've been unable to pinpoint anything specifically wrong.
Can anyone help?
Thanks!I was really trying to avoid a full OS reinstall, but I can't find a solution to either situation.
An Answers poster recently had an
apparent problem with DISM.exe being corrupted. Evidently an sfc /scannow either didn't notice it or try to fix it. I wondered about trying sfc /scanfile= on it. If you are about to rebuild it surely could not hurt to perform that experiment
with your two devmgmt.msc files first?
You could check them for length using a modification of the Powershell pipeline we used...
PS C:\windows> dir -Filter "devmgmt.msc" -Recurse -ErrorAction:SilentlyContinue | ft Length, FullName -AutoSize -HideTableHeaders
145640 C:\windows\System32\devmgmt.msc
145640 C:\windows\System32\en-US\devmgmt.msc
145640 C:\windows\SysWOW64\devmgmt.msc
145640 C:\windows\SysWOW64\en-US\devmgmt.msc
145640 C:\windows\WinSxS\amd64_microsoft-windows-p..cemanager.resources_31bf3856ad364e35_6.3.9600.16384_en-us_9242636cfac1b5ec\devmgmt.msc
145640 C:\windows\WinSxS\amd64_microsoft-windows-pnpdevicemanager_31bf3856ad364e35_6.3.9600.16384_none_0494fa7cf377bf21\devmgmt.msc
145640 C:\windows\WinSxS\wow64_microsoft-windows-pnpdevicemanager_31bf3856ad364e35_6.3.9600.16384_none_0ee9a4cf27d8811c\devmgmt.msc
145640 C:\windows\WinSxS\x86_microsoft-windows-p..cemanager.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3623c7e9426444b6\devmgmt.msc
Whoa. I wasn't expecting that. All the same size? Looks like the first pipeline we used which ended with fl * would be more useful. There are only 8 items so it wouldn't be too much output.
Also, that shows there might be another copy that you could use anyway (e.g. which might not be corrupted as much as the one you were getting by default.)
C.f.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/issue-with-installing-updates-on-windows-81/24b91da6-fdbe-42dd-96c6-3cc91062054b?page=4
HTH
Robert Aldwinckle -
Hi Everyone,
A Labview application I recently wrote crashed due to an error (code e0434352) in Kernelbase.dll. It had been running for several weeks, so the error really isn’t reproducible, but the application is meant to run without any human intervention so the crash is a pretty big deal for my customer.
After a bit of googling I discovered that the particular error code was associated with the .NET CLR, so now I’m trying to figure out how my program caused it.
My application is implemented using the actor framework and is running on a Windows 7 machine. It interacts with 2 spectrometers, a cDAQ with a DIO module, and a thermistor which I’m talking to with VISA USB RAW. The application also saves and loads various data and settings files. To my knowledge, Labview is implemented in C and shouldn’t run Microsoft’s CLR in any way. The only piece of my program I know of that needs it is the driver for the spectrometers (which calls a .NET wrapper from the device manufacturer).
Right now I’m spending all of my effort investigating the spectrometer driver. However I wanted to check with the forum to make sure that there’s nothing I’m overlooking. Does anyone know of any other facets of Labview that are built on or rely on .NET? Or better yet, has anyone encountered a Kernelbase.dll failure before?
Thanks for your help,
-GaryHello Gary117,
I wasn't able to dig up any information linking LabVIEW and this Kernelbase error. e0434352 seems to be a very general error and doesn't really shed any light on the issue. I agree that the driver which calls the .NET wrapper is the most likely culprit.
Jonathan L.
Applications Engineer
National Instruments -
Hey all,
We're running a LabView 8.5.1 set up, with labview controlling a front end for all of our equipment. This ranges from actual device control, to data aquisition, to data analysis, and then it saves it to a MDSPlus server - and it all runs on DataSocket between several different workstations.
We've been recently getting a bout of Labview errors with nids.dll that crash the entire program, and requires Labview to restart entirely.
The exception information is provided below:
Code: 0x80000003
Flags: 0x00000000
Record: 0x0000000000000000
Address:0x0000000007458076
Attached is the logfile it generated.
Any help on resolving this issue would be greatly appreciated.
Attachments:
ErrorReportLabview_0713_1800.txt 129 KBOK, so I've figured some more things out. We have two programs running simultaneously. One is the database save program, the other is the data streaming program. The data streaming program is constantly reading from a TCP port which is connected to a remote computer that does a lot of our data acquisition. As far as I can tell, the data streaming program is using information contained in the byte sequences it acquires from the TCP port to decide in which data socket on localhost to save the data it gets in these sequences. I am not sure whether the data streaming program gives the remote computer instructions as to which data it wants at what time or whether the remote computer simply cycles through the available data it has.
The database save program only runs once per minute. The database save program looks at each data socket individually, saves all the data collected in that data socket over the last minute to a database, then resets that data socket to a zero-by-zero array of zero.
My theory is that the crash is happening when the data streaming program and the database save program run in to each other while trying to use the same data socket. Any suggestions on how to avoid this? Is it possible to instruct both programs to wait until the other is done with a data socket before trying to use it? -
Adobe Premier Elements DVACORE.DLL Crash
Premier Elements 12 keep crashing on startup or shortly after startup with the same error message. Here's the problem details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Elements.exe
Application Version: 12.0.0.0
Application Timestamp: 523cd4d5
Fault Module Name: dvacore.dll
Fault Module Version: 11.0.0.0
Fault Module Timestamp: 523cc5bf
Exception Code: c00000fd
Exception Offset: 00000000000698b6
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
System:
Windows 7 64 bit with 16GB RAM.
Processor is an Intel Core i7-2760QM 2.4GHz
Display is an NVIDIA NVS 315
Here is what I have done so far:
1. Updated the latest graphics card from Nvidia website directly (manufacturer)
2. Tried installing older legacy versions of the driver (11 or 12 previous versions)
3. Uninstalled antivirus (McAfee)
4. Reinstalled antivirus and checked instances for programs
5. Checked Nvidia control panels and changed stereoscopic and 3D settings
6. Running in msconfig (safe boot with minimal resources) I did this to see if a service or process would be causing the crash
After reading this software's forums and a several other suggestions (spend probably over 40 hours on reading and trying fixes) there doesn't seem to be a fix for this. What is the cause of this crash?Technician907
Thanks for the follow ups. Sorry that the news were not better.
I am not sure how worthwhile it might be, but here are some possibilities
a. create a new User Account with Administrative Privileges and try to install and run Premiere Elements 12 there.
b. Download and install a new set of Premiere Elements 12 installation files...or for 13 for that matter...
http://prodesigntools.com/photoshop-elements-12-direct-download-links-premiere.html
or
Adobe Photoshop Elements 13 Direct Download Links, Premiere too | ProDesignTools
When you go this route, you need to read and carry out carefully the web page's "Note: Very Important Instructions"
in order to avoid an Access Denied message.
The history on the dvacore.dll is encouraging. But, please review and consider.
Please update us on your progress when your schedule permits.
Thank you.
ATR -
Lvrt.dll crash LV2010SP1
Problem Event Name: APPCRASH
Application Name: Test.exe
Application Version: 1.0.0.0
Application Timestamp: 4d2fa0d5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.1.4002
Fault Module Timestamp: 4d2fb3a1
Exception Code: c0000005
Exception Offset: 007487b7
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
This is LabVIEW 2010 SP1 on Windows 7.
Maybe it has something to do with "Call By Reference" , but not sure.Strange, I would also appreciate any updates on a solution. I can run my application for several days as well and then the system gives me the error. I have not checked my DEP settings, but will do so. I was leaning towards a problem with resources since I am running for several days - I thought maybe the memory or cpu usage was a problem.
I am using Windows 7, LabVIEW2013, SP1 64 bit application.
Is there any reasonable way to recover from this crash programmatically since it is a Windows error?
Problem signature:
Problem Event Name: APPCRASH
Application Name: Avionic_Communication.exe
Application Version: 5.0.0.2
Application Timestamp: 52d9885e
Fault Module Name: lvrt.dll
Fault Module Version: 13.0.1.4018
Fault Module Timestamp: 52d99503
Exception Code: c0000005
Exception Offset: 0000000000bb7e80
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 56fb
Additional Information 2: 56fb6f9c2aae0ddbb77d8c94b1041558
Additional Information 3: 848b
Additional Information 4: 848b2abc34bf08ac556f274cd9d77734
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt -
First things first, trying to find a tech support Email address or phone number has been infuriating. The "3-step support wizard" which results in "go to the forums" is also infuriating and insulting.
I have a Windows 7 64-bit PC running CS6 64-bit (updated/current), and it's crashing at random (2-3 times per day). I see events recorded in the event log showing dvaui.dll and msvcr100.dll as the source. Other people have raised this as an issue, and all I see are guesses. Does Adobe have a credible solution for this yet?
I've tried running as a domain admin, which did not help.
Illustrator CS6 32-bit seems to be working perfectly (4 days straight, no crashing).
It seems to currently affect only one computer (5 others are fine). It's not repeatable, and has no discernible cause.
Also, format and reinstall is neither a solution nor an option.
To be honest, I'm looking for Adobe to address this directly: do you know why this is happening, and how long until it is solved? If an Adobe tech support will open a case, I have a file that the designer (I'm not the designer) was using during one of the crashes. I don't know if the crashing will be related (to the file), but I have the file just in case.
David.Hi Larry,
Thank you for responding.
> CS6 is current in that it is still available for purchase and in the CC but it is now two versions behind.
I'm not quite sure what you are trying to say. Can you be explicit, please?
> As to your problem have you tried downloading the .dll files from Microsoft and reinstalling them?
I have copied and re-registered the DLL files from a known-good machine (that is to say that the machine doesn't exhibit any of the symptoms as the above machine), which did not help.
I'm really interested in having Adobe respond directly to this issue. I know they are aware of it.
It's clear that Adobe doesn't actually want to support this program, but people rely on it for their economic success. Both my client and his employees need this program to function properly and reliably, and I think anyone would agree that it's reasonable to expect that a problem like this (that affects more than just us) be, at a minimum, addressed. Adobe has my client's money, they had no problem accepting it. With that acceptance comes a duty to be responsive.
Thanks,
David. -
Hi all,
I'm having a peculiar problem.
I inherited a project saved in LabVIEW 8.6. The project must use of particular dll that was built a few years ago. The original developer and source code for this .dll are long gone. The very core logic exists, in the form of embedded C code, and that's it. The .dll is called through a Code Interface Node in LV 8.6 and this setup manages to "work". Howver, running the VI that calls this .dll in LV 2011 causes an "insta crash", as in, no "program has stopped responding". Error message pops up, then all LV windows close.
It's very similar to that described in here:
http://digital.ni.com/public.nsf/allkb/D84C9775ABD921CF8625772A005CA50C
but this KB says to try putting the amount of error handling to maximum. I tried that, but it didn't help.
Using the "Debug" option allows me to run the just-in-time debugger with CVI 2010, which then proceeds to say this:
Finally, I manage to get this out of it:
FATAL RUN-TIME ERROR: Unknown source position, thread id 0x000012D4: A non-debuggable thread caused a 'General Protection' fault at address 0x00000000.
I don't think that really helps at all, but it's there.
Here is the function prototype of the .dll:
void _inputPM@224(uint8_t arg1, uint16_t arg2, uint8_t arg3, float arg4, float arg5, float arg6, float arg7, float arg8, float arg9, float arg10, float arg11, float arg12, float arg13, float arg14, float arg15, float arg16, float arg17, uint16_t arg18, uint16_t arg19, uint16_t arg20, uint16_t arg21, uint16_t arg22, uint16_t arg23, uint16_t arg24, uint16_t arg25, uint16_t arg26, float arg27, float arg28, float arg29, float arg30, float arg31, float arg32, float arg33, float arg34, float arg35, float arg36, float arg37, float arg38, float arg39, float arg40, float arg41, float arg42, float arg43, float arg44, float arg45, float arg46, float arg47, uint16_t arg48, uint16_t arg49, uint16_t arg50, uint16_t arg51, uint16_t arg52, float arg53, float arg54, float arg55, float arg56);
(never seen a function take 50 input params like that (wouldn't you use a struct? array? something? But I digress, and I don't know anything about .dlls...))
I do have a ".lib" and a ".cdb" file with the same name as the .dll, but those also looks like some kind of compiled file.
I'm sure the answer I'm going to get is that there is no way of telling what's really going on without .dll source code. I'm hoping against hope that there may be another way or hack.
Any ideas? Thank you for you help.
Regards,
Mark G
Solved!
Go to Solution.MarkCG wrote:
Changing the call library node to stdcall (WINAPI) did the trick! No more crash. Thank you very much!
I haven't run LV2011 on windows XP, only on windows 7, so I don't know if that makes a dfference. But The call type makes no difference when using LV 8.6 on the same machine, however.
Now I've got to make the .DLL run corretly on a compact fieldpoint.... and avoid crashing IT.
Thank you for the help all!
Well, the DLL did work fine in LabVIEW 8.6 because earlier versions of LabVIEW automatically proceeded to change the calling convention to stdcall, if they noticed a function name decoration of @# (# = number of bytes passed on the stack) appended to the name. This is the default naming decoration for stdcall functions used by VisualC. However this decoration can be overwritten with linker switches, other compilers don't use them always in the same way, and most likely there are in the mean time compilers out there that can produce such decorations also for non stdcall calling convention. So this automagic trickery was removed from newer LabVIEW versions.
I do think it could be considered a bug in the code that upgrades LabVIEW VIs, that it uses the calling convention that is configuerd in the dialog, instead of the calling convention earlier LabVIEW versions used automagically, but it is an esoteric corner case.
What Compact Fieldpoint controller do you have? If it's anything newer than 20xx or 21xx forget it. The 22xx controllers use a PPC CPU and VxWorks operating system and can never get a Windows DLL to operate properly. If it is a 20xx controller it's still highly likely that DLL can not even get loaded into LabVIEW as it likely relies on other runtime libraries and possibly Win32 APIs not present in the Pharlap ETS runtime kernel used on those controllers.
There is a tool to check a DLL for incompatible imports that are not present on specific ETS RT systems. And this list summarizes the RT system used on the various NI controllers.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
I've got quite a problem here.
We are using a large LabVIEW application (written by me) for years now on different test benches.
The software changes a lot because we have to change our tests a lot. So far we had no problems since the time it was running on LabVIEW 7.1. Then 8.0, 8.2 and now 8.5.
My software was able to to it's job for hours and even days straight while handlings 128 input channels (SCXI), analog and relais outputs and CAN traffic while logging and visualizing all of the former mentioned things.
But now I have a branch of my software which crashes under very strange circumstances.
The program starts with a launcher, named Launch.vi. Here the user can open a configurations dialog or start the rest of the program.
While waiting for user input it reads the windows registry, that's basically all. This launcher level is nearly identical between all the versions, even the stable ones!
What happens is this: I run the VI and everything is fine. I can run the whole program from that point and it is perfectly stable.
BUT, if I stop the launcher and run and it again it crashes. The window borders appear but the contents are missing, just white space.
I tried to put LabVIEW into single-step mode, but it doesn't come even that far. It seems that LabVIEW crashes while it attempts to draw the window.
The crash message from my Vista x64 is:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: LabVIEW.exe
Anwendungsversion: 8.5.0.4002
Anwendungszeitstempel: 46a6a1e1
Fehlermodulname: lvalarms.dll
Fehlermodulversion: 8.5.1.1
Fehlermodulzeitstempel: 469d5675
Ausnahmecode: 80000003
Ausnahmeoffset: 000015cb
Betriebsystemversion: 6.0.6001.2.1.0.256.6
Gebietsschema-ID: 1031
Zusatzinformation 1: 1921
Zusatzinformation 2: ea0e3d40cb8bc5e7fdb3eb63fdd22b01
Zusatzinformation 3: 5fdd
Zusatzinformation 4: 6fbd21e6e8410cabced82d944fc159e1
I run it on a Core 2 Duo. But under XP and different processors (like Athlon 64 and similar) this behaviour is the same.
Under LabVIEW 8.6 its also the same.
The Launch.VI is pretty much similar to versions which runs fine, so I think that the problem must be within the rest of the program.
But at that time those VI's aren't running yet. It's just a "while" with an event structure.
I don't know where to start to look for the source of this problem and my app is quite big.
I would be really thankful for any ideas...Jochen,
I've tested the DLL from the KB article with a restored "buggy" application and it still crashes. As far as I can see the behaviour is exactly the same.
But while testing I discovered that the reentrant option was not the solution to my problem.
The sub-VI containing the buggy code consists of 4 concurrent while-loops.
One of them is the main "program" with some initializations and a big event structure.
The remaining 3 are used for a ramp functionality (I give it an end value and the time to reach that value).
2 of them were always synchronized in their start time by a create notifier VI (I wired the output to the while-loop but without using it) but the other 2 were "floating loose" in the VI.
After wiring the output of the notifier VI to one of the other 2 while-loops (and I mean while-loop #3, it doesn't help to synchronize #4) the crash disappears.
I'm still not sure why, as those 2 are very similar to each other.
The concurrent while-loops cannot be the problem as well, because I have applications with 6 oder 7 of those starting at once without any synchronization and they work perfectly fine.
The other strange thing is that all ramps are inactive at first. So the only thing the while-loops has to execute is a case with a 250ms wait in it. -
WDContextMenuHandler.dll crashes Explorer.exe
After updating to the latest WDSmartware on my laptop running Windows 7 x64 the Explorer.exe process crashes once in a while with the following error in the event log. Any suggestions as how I can fix this? Error: (03/30/2015 08:51:38 AM) (Source: Application Error) (User: )
Description: Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: WDContextMenuHandler.dll, version: 2.0.0.3, time stamp: 0x54dd49f6
Exception code: 0xc0000005
Fault offset: 0x000000000001f786
Faulting process id: 0x15c0
Faulting application start time: 0xExplorer.EXE0
Faulting application path: Explorer.EXE1
Faulting module path: Explorer.EXE2
Report Id: Explorer.EXE3Hi... I have run into the same problem today... and I've found a solution... kind of. I hope it's not too late for my answer. 1) download ShellExView from here: http://www.nirsoft.net/utils/shexview.html#DownloadLinks 2) disable the two items highlighted in the image: The context menu problem will be solved... for a little benefit of (probably) not having those shortcuts for WD utilities in the context right-click menu, but I guess you can still use them elsehow. Hope this helped you. I've found the solution myself and it worked for me.
Maybe you are looking for
-
Regarding Matrix Report Issue in (RTF Template)
Hi, We are developing the new report in XMLP (Matrix Report) and this is new stuff for us in XMLP. we dont have any material to explore about how to apply matrix report concepts in RTF Template. We have tried with some xml data with the RTF file but
-
Autoplay dialog won't open when I plug in my iPod Touch 4th gen
Hello! I need to take my iPod into be fixed because it has a cracked screen and I'm trying to import my photos onto my laptop (Windows 7) but when I plug my iPod in nothing happens except the iTunes window pops up. I went into Autoplay and made sure
-
Why is my lock screen blurred? Resetting is only a temporary fix.
-
I have already cleared the cookies and the cache. The problem does not seem to be with Yahoo, but with Firefox. No other browser causes me this problem.
-
SCCM 2012 NO SP - Reporting for application deployments not up to date
Hello, We have a problem when deploying applications with our SCCM 2012 NO SP. The reports for the application deployments and sup deployment are not up to date. The applications have been deployed on the clients but the information is not in sccm s