AdobePSL.dll Crash

One of our laptops keep crashing indesign and illustrator all the time on windows 8.
Viallisen sovelluksen nimi: InDesign.exe, versio: 9.2.2.103, aikaleima: 0x537279c1
Viallisen moduulin nimi: AdobePSL.dll, versio: 14.0.0.31988, aikaleima: 0x5272de8e
Poikkeuskoodi: 0xc0000005
Virhepoikkeama: 0x00000000005ff84f
Viallisen prosessin tunnus: 0xefc
Viallisen sovelluksen käynnistysaika: 0x01cfbb97b0aca848
Viallisen sovelluksen polku: C:\Program Files\Adobe\Adobe InDesign CC (64 bit)\InDesign.exe
Viallisen moduulin polku: C:\Program Files\Adobe\Adobe InDesign CC (64 bit)\AdobePSL.dll
Raportin tunnus: f03c3364-278a-11e4-be97-3423870fdfda
Viallisen paketin koko nimi:
Viallisen paketin suhteellinen sovellustunnus:
What should I do to fix this issue?

Hi, same error for years, in CS 5, cs 5.5 (Public.dll) CS 6 and now CC (AdobePSL.dll), iam realy pised.....
Windows Ultimate x64, 4 GB RAM, Core Duo 2.0 GHZ - functions perfect for me. all work splendid except this InDesign series....
constant error....
Faulting application name: InDesign.exe, version: 10.1.0.70, time stamp: 0x5424e38b
Faulting module name: AdobePSL.dll, version: 14.0.0.31988, time stamp: 0x5272de8e
Exception code: 0xc0000005
Fault offset: 0x00000000005ff84f
Faulting process id: 0xa44
Faulting application start time: 0x01d03d9221a1c65a
Faulting application path: C:\Program Files\Adobe\Adobe InDesign CC 2014\InDesign.exe
Faulting module path: C:\Program Files\Adobe\Adobe InDesign CC 2014\AdobePSL.dll
Report Id: 6415d487-a985-11e4-ab77-001b3833ab94
What I do !!
- removed all fonts except required in win folder
- remove Extensis Suitcase .... numerous versions
- numerus deinstalations of Adobe CC InDesign
- delete All:
Microsoft Visual studio C++ redistributable applications from 2005 to 2012..
Microsoft .NET Framework from 3 to 4.5.2
- user hive, create new user...
(All of this software, is 100% legal)
If some one know what is Adobe PSL.dll, or what it does ????????? I will be grateful, come on programmers, you know what you wrote.
I want to know this dll with what is connected (?) and there is a root of a problem !
In this forum I read all posts about this DLL and neither one is suggesting a concrete solution for years, come one...
My business is suffering...
please help.
thanks
Zdeslav

Similar Messages

Appcrash AdobePSL.dll in Illustrator CS6

Problem,
Adobe Illustrator CS6 has stopped working
Click Close the program. (can't save)
Problem signature:
Problem Event Name: APPCRASH
Application Name: Illustrator.exe
Application Version: 16.0.3.691
Fault Modeule Name: AdobePSL.dll
Fault Module Version: 13.0.0.21041
OS Version: 6.1.7601.2.1.0.256.48
Dell: Precision T1650 VGA:FireProV4900 RAM:20GB
OS: Windows 7 SP1 64bit
I re new install OS and Program.
Also a problem.

Can you please provide additional details like:
1) Is this crash happening consistently? Could you reproduce the issue with some specific steps?
2) Is the crash happening at AI's launch or while you are working in AI or instead on quitting AI?
3) Also can you please clarify what do you mean by:
I re new install OS and Program.
Also a problem. "
4) Have you made any updates to AI? Essentially, what all did you do between your last successful opening of AI and this crash?
Warm Regards
Ankit

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 so

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 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,
Gary

Hi 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

PE7 (& 8) error message missing adobepsl.dll when writing to disc

I have been using PE7 exclusively even though I purchased PE8 since it didn't work on my Windows 7 64 bit laptop. I edited a video without any problems like usual and when I went to write it to a disc, it wouldn't write and I got an error message that it was missing or error occurred in adopepsl.dll. This was on the Windows 7 laptop. I then moved the files to a Vista laptop and tried it there but got the same error message. I read a lot of forums and articles here and so I created a new user specifically for PE8 on the Windows 7 laptop and installed PE8. I tried to write the project to the DVD and once again I got the same message. As a last resort, I created a new user on my XP desktop and installed PE7 since I knew that I had successfully worked with that one for almost 2 years without a hitch. I got the same error message on the XP:
AppName: adobe premiere elements.exe AppVer: 7.0.0.0 ModName: adobepsl.dll
ModVer: 11.0.0.1656 Offset: 000e0c83
Since it was three different computers and three different systems and I never had problems before either laptop before, I am extremely confused as to why all three separate computers would be missing the same exact file and get the same error message. I installed them directly from the DVD that I purchased new and had used it to install onto the laptops when I intially started using the program and then when I purchased the second (windows 7) laptop. And then to have it also happen with the PE8, which was also bought new but never used since it wasn't working on the Windows 7 laptop. (No, I did not update it since I went back to the PE7 because I knew that worked and I was in the middle of another project at the time and didn't want to jeopardize my project or my usage of the laptop.)
How is this possible that all three computers (and the PE8) are all having trouble burning to the DVD? Is it possible that it's a program disc problem but then why would the PE8 have that same problem?
desktop info (laptops are off and I'm exhausted after having dealt with this for over 12 hours):
windows XP
processor: intel pentium 4 cpu 3.00 ghz (2cpus)
memory: 1.37 gb RAM
Any suggestions? Unfortuanately, I'm not as "techy" as the rest of you.
Thanks.

Thanks Steve. I checked that article and I already do everything on all machines in your article except #4 of weekly and #1 of monthly. I have read your articles over time and have always found them informative. I've also gone to your website for information.
I do not have Adobe Bridge or Creative software. How do I correct all three machines so that it will write to a DVD? How do I get that file back?
Thanks.

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

Illustrator CS6 64-bit dvaui.dll and msvcr100.dll crashing problem, any solution?

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.

Using code interface node with dll crashes LV 2011 but not LV 8.6... using max error handling does nothing

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

Lvalarms.dll crash

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.EXE3

Hi... 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.

Discwriter.dll crash

Elements 7 crashes when I try to burn a CD. Have uninstalled & reinstalled with same result.
I have updated & same result. I'm trying to burn an album.
I did manage to burn a slideshow but the quality was not very good (very poor resolution).
I'm expecting that if I burn an album, the quality will be better.
Error returned =
AppName: photoshopelementsorganizer.exe AppVer: 7.0.0.0 ModName: discwriter.dll
ModVer: 7.0.0.0 Offset: 00003d80
Appreciate any advice.
Tx
Bob

Well, its 4, months since my original post. For reasons unrelated, I've reformatted my hard drive & fresh installed Windows XP & Elements 7. Still get the same error. Still haven't figured out why the quality/ resolution of the slideshows is so poor either. Don't laugh but I'm saving my files as Jpgs & using Picassa to burn to disc. I wonder if I just got a buggy disc.

AdobePSL.dll Crash

Similar Messages

Maybe you are looking for