Random crashes talking to dll

I have a vi where I am talking to a dll. This vi will crash LabVIEW at random intervals, usually after I have run the app a number of times and then close out the vi. Can someone with more experience with dlls look at this and let me know where I am not working this right? I have found out the hard way that the timers are required where they are.
This dll access some hardware, so I don't expect you to be able to have it run, but maybe somwhere I have the function calls incorrect. The hardware is a Silicon Labs CP2102 USB to UART Bridge Controller chip.
Files attached, including the dll documentation.
NOTE: you will have to change the "CP210xManufacturing.txt" extension back to "dll". I can't post a dll extension to the forum.
Thanks!
Tay
Attachments:
CP210xManufacturing.txt ‏88 KB
an1441.pdf ‏364 KB
GetPartNumber1.vi ‏23 KB

The documentation has for that function:
Return Value: CP210x_STATUS = CP210x_SUCCESS, 
                                                        CP210x_INVALID_PARAMETER,
                                                        CP210x_INVALID_HANDLE,
                                                        CP210x_DEVICE_IO_FAILED
In Appendix A, CP210x_STATUS is defined:
// Type definitions
typedef int CP210x_STATUS;
Thus, the return value is an integer (I32 in LabVIEW).
A "1-byte" value is just a U8/I8 in LabVIEW. Note that this function requires you to pass a pointer to the value. You should wire a constant to that node:
Attachments:
GetPartNumber1-1_BD.png ‏2 KB

Similar Messages

  • Access 2010 SP1 - random crashes relating to vbe7.dll

    We are experencing the same problem as described here in a post on
    Microsoft Answers.  However was are also still occasionally seeing the problem after uninstalling SP1. 
    Has anyone come across any better workarounds? 
    Microsoft: can we please have some information on when this is likey to be fixed - this is a major problem!
    After installing Office 2010 SP1, you may receive random crashes when opening objects in certain databases and when trying to open the VBA window in those databases.  If you look in the event viewer the crash info may look similar to the following:
    Faulting application: msaccess.exe
    Version: 14.0.6024.1000
    Stamp: 4d83e4fc
    faulting module: vbe7.dll
    version: 7.0.16.19
    stamp: 4d430aec
    Workaround:
    Microsoft is aware of the issue and it is currently being investigated.  In order to work around the problem, you can try the following:
    1.      Make a copy / backup of your database.
    2.      On the problematic machine decompile the database by running the following from a Run command line: MSACCESS.EXE <path to database file> /decompile
    (example: C:\Program Files (x86)\Microsoft Office\Office14\MSAccess.exe "C:\folder\database.accdb"  /decompile)
    3.      Close the database.
    4.      Open the database again normally.
    In addition to this, if you experience the crash please send the error report when prompted to do so after the crash.

    Hello,
    Have you tried the workaround? It should work after you decompile your databases.
    And if there is better solution released by Microsoft, you will be able to find them in certain KB like:
    http://support.microsoft.com/kb/2533794
    Sincerely,
    Max Meng
    Forum Support
    Please remember to
    mark the replies as
    answers if they help and
    unmark them if they provide no help.
    If you have any feedback on our support, please contact
    [email protected]

  • Adobe Acrobat 8 Professional Random Crash (Access Violation)

    hi all. first time poster. long time reader.
    i have encountered an odd access violation problem - 'ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "blah" referenced memory at "blah". The memory could not be "blah" - in 'acrobat.dll' recently with a customer who is experiencing seemingly random crashes with adobe acrobat 8 professional.
    they are running the application off a citrix presnetation server 4.5 server (windows server 2003 R2 with service pack 2). each server is hosting about 8 or more users per server per day. every now and then, ie once a day, adobe acrobat crashes during use. there doesn't appear to be anything consistent in so far as the action the user is performing. they will be mid-way through marking up a document and it will just crash for one of them. all the others will continue working fine.
    i have access to numerous crash dumps and nothing seems to really stand out...other than 'Acrobat_3000000!AVAcroALM_Destroy'. For example...
    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0012f96c 0343c3e1 46e4e58d 0839ce58 0012faa0 Acrobat_3000000!PDDocCreateWordFinderEx+0x59641
    0012f9a0 0343c479 0000004d 00000000 46e4e5f5 Acrobat_3000000!AVAcroALM_Destroy+0x30afe
    0012f9d8 0343c94a 08650e08 0000004d 0012f9fc Acrobat_3000000!AVAcroALM_Destroy+0x30b96
    0012fa68 0343cea2 08650e08 0000004d 0012fab0 Acrobat_3000000!AVAcroALM_Destroy+0x31067
    0012faf8 0343d0a3 08650e08 0000004d 0bbf6748 Acrobat_3000000!AVAcroALM_Destroy+0x315bf
    0012fb4c 0343d8da 08650e08 00000000 46e4e7e5 Acrobat_3000000!AVAcroALM_Destroy+0x317c0
    0012fbc8 03182465 08e6e808 0012fc48 00000000 Acrobat_3000000!AVAcroALM_Destroy+0x31ff7
    0012fc1c 0309eeba 0bbf6748 0012fc48 00000000 Acrobat_3000000!PDPageGetFlippedMatrix+0x471d
    0012fc88 030ae925 00000000 08dd9798 03098f43 Acrobat_3000000!PDDocCreateWordFinderEx+0x378ef
    0012fce8 0300e9f7 0003007a 0300d5c9 000004d3 Acrobat_3000000!PDDocCreateWordFinderEx+0x4735a
    0012fd04 7739b6e3 0003007a 00000113 000004d3 Acrobat_3000000!WinMain+0x24a4
    0012fd30 7739b874 0300d1bf 0003007a 00000113 user32!InternalCallWinProc+0x28
    0012fda8 7739ba92 00000000 0300d1bf 0003007a user32!UserCallWinProcCheckWow+0x151
    0012fe10 7739bad0 0012fe54 00000000 0012fe90 user32!DispatchMessageWorker+0x327
    0012fe20 0300a597 0012fe54 0012fe70 03ca2d20 user32!DispatchMessageW+0xf
    0012fe90 0300aece 46e4e2e5 00d40068 03ca2d20 Acrobat_3000000+0xa597
    0012fec8 0300c517 00000000 0012ff2c 00000000 Acrobat_3000000!AXWasInitViaPDFL+0x76a
    0012fedc 0300c649 00000005 0040a77c 0012ff2c Acrobat_3000000!AXWasInitViaPDFL+0x1db3
    0012fefc 00402d5f 03000000 00400000 001524e0 Acrobat_3000000!WinMain+0xf6
    0012ff30 00403281 00400000 00000000 001524e0 Acrobat+0x2d5f
    0012ffc0 77e6f23b 00000000 00000000 7ffd4000 Acrobat+0x3281
    0012fff0 00000000 00403402 00000000 00000000 kernel32!BaseProcessStart+0x23
    ...or another...
    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0012f6e0 222cb7ad ad0d64ee 00000000 1398c0d8 Annots!PlugInMain+0xa9198
    0012f830 2091b7db 0012f934 0012f9f4 56433230 Annots!PlugInMain+0x1ca425
    0012f8d4 20913957 0850f3a0 0340f043 0850f3a0 AcroForm!DllUnregisterServer+0x10798b
    0012f900 0340f385 00000001 51ab7765 000000df AcroForm!DllUnregisterServer+0xffb07
    0012f940 034dda17 0850f3a0 00000001 51ab77d1 Acrobat_3000000!AVAcroALM_Destroy+0x3aa2
    0012f9f4 034454fa 00000000 084ce5c8 ffffff84 Acrobat_3000000!AVAcroALM_Destroy+0xd2134
    0012fa14 034451cb 084ce5c8 ffffff84 000000df Acrobat_3000000!AVAcroALM_Destroy+0x39c17
    0012fa3c 034451f0 084ce5c8 ffffff84 000000df Acrobat_3000000!AVAcroALM_Destroy+0x398e8
    0012fa5c 033e4a92 00fd0540 084ce5c8 ffffff84 Acrobat_3000000!AVAcroALM_Destroy+0x3990d
    0012fadc 033e6c01 084ce5c8 00000000 00000001 Acrobat_3000000!PDDocSetXAPMetadata+0xf227f
    0012fb24 033b0fbf 00000065 000000e3 00000001 Acrobat_3000000!
    ...continued in next post 'cause it keeps getting truncated ?!

    0012fbb4 030abb9e 00000065 000000e3 00000201 Acrobat_3000000!PDDocSetXAPMetadata+0xd9998
    0012fbd4 030abd6f 00000201 00000001 00e30065 Acrobat_3000000!PDDocCreateWordFinderEx+0x445d3
    0012fbf0 7739b6e3 000200ca 00000201 00000001 Acrobat_3000000!PDDocCreateWordFinderEx+0x447a4
    0012fc1c 7739b874 030abd08 000200ca 00000201 user32!InternalCallWinProc+0x28
    0012fc94 7739bfce 00000000 030abd08 000200ca user32!UserCallWinProcCheckWow+0x151
    0012fcc4 773b0463 030abd08 000200ca 00000201 user32!CallWindowProcAorW+0x98
    0012fce4 20b8e182 030abd08 000200ca 00000201 user32!CallWindowProcA+0x1b
    0012fd04 7739b6e3 000200ca 00000201 00000001 AcroForm!DllUnregisterServer+0x37a332
    0012fd30 7739b874 20b8e132 000200ca 00000201 user32!InternalCallWinProc+0x28
    0012fda8 7739ba92 00000000 20b8e132 000200ca user32!UserCallWinProcCheckWow+0x151
    0012fe10 7739bad0 0012fe54 00000000 0012fe90 user32!DispatchMessageWorker+0x327
    0012fe20 0300a597 0012fe54 0012fe70 03ca2d20 user32!DispatchMessageW+0xf
    0012fe90 0300aece 51ab70ed 00d40068 03ca2d20 Acrobat_3000000+0xa597
    0012fec8 0300c517 00000000 0012ff2c 00000000 Acrobat_3000000!AXWasInitViaPDFL+0x76a
    0012fedc 0300c649 00000005 0040a77c 0012ff2c Acrobat_3000000!AXWasInitViaPDFL+0x1db3
    0012fefc 00402d5f 03000000 00400000 001524e0 Acrobat_3000000!WinMain+0xf6
    0012ff30 00403281 00400000 00000000 001524e0 Acrobat+0x2d5f
    0012ffc0 77e6f23b 00000000 00000000 7ffde000 Acrobat+0x3281
    0012fff0 00000000 00403402 00000000 00000000 kernel32!BaseProcessStart+0x23
    is 'AVAcroALM' to do with licensing?
    other than advising them to bring citrix presentation server 4.5 up to date (HRP2) i'm at a loss what to advise. citrix often have issues with seamless published applications when spread across multiple monitors (as in this case), hence, my reason to ask them to bring their software up to date. often the funtion called will be different - often times 'Acrobat.dll!PDDocCreateWordFinderEx', other times 'Acrobat.dll!PDDocAcquirePage' and there are others.
    i can post more of the mini-dump if required. any - and ALL - assitance appreciated.
    thanks.

  • Premiere Pro random crashing since update to 2014.2

    Been working on the SAME big project over 18 months, in Pr Pro CC, 2014, working on the SAME PC:
    Win 7 SP1 pro 64bit, i7-3770K, 32GB fast memory (25.7 available for Pr), Intel HD 4000 graphics on Asus motherboard with 30" NEC Multisync screen at 2560 x 1600 (same as for years)
    42GB free on my SSD drive C: and 54GB free on my SSD drive S: for preview files, 24GB free on my SSD drive T: for caching files.  Project files etc stored on a normal hard drive F: (for Files!) 1.25TB free.
    NOW last update to 2014.2 and I get constant RANDOM crashes (Windows encountered a fault and had to close this program) despite updating graphics driver and trying different settings in preferences, use mercury etc.  No particular action causes it  - sometimes I am just watching it play a sequence and it just stops. Though of course it may be rendering the last edit at the time.
    Sometimes it runs for all of 15 mins and I think the problem has sorted then it goes again and I have to restart the project, find where I was and re-do my last edits.  If I remember to press Ctrl-S very frequently (every few seconds) it seems to run for a while then I forget for 5 mins and it crashes.
    Grrrr what did you do to the latest version, Adobe??  I need to get this project finally finished in a hurry.... I wish I had not updated the program!  Of course I cannot go back as it says the saved copy is now incompatible with earlier Pr Pro versions.
    I then tried running a previous version at the same time, as simonray suggested in his post - it worked!  So I am able to continue as normal provided I do this stupid bodge fix.
    So it really is down to Adobe as it is the same project, same PC, just different version update.  You did something to a great, stable, program that made it unstable, Adobe...
    To ANSWER RAMEEZ from previous thread:
    A variety of issues can cause PPRO to crash:
    a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin. >>  DIDN'T CHANGE ANYTHING since 1½ years running previous PrPro versions on SAME PROJECT on SAME PC
    the graphics driver  Checked for latest version - didn't stop the crashing
    third-party plug-ins - don't have any
    a problem with the cache files. I am using the same 2 x SSD I have been using for years for autosave and caching. 54GB free space / 24GB free space (current cache in place)
    a problem with the project file (if you're loading a project...)  Doesn't apply
    the Preferences files be set to read-only  How would that happen? Never happened before on any other update and I can change it.
    the user not having administrator rights  Only one user on PC since installation, full rights
    a conflict/incompatibility with some OS setting  Haven't changed anything
    a problem on the licensing/authentication side.  I'm signed up to full Adobe CC. Everything else works, Ps, Lr, Id ...
    A log file might help identify the cause of the crash. Please right-click 'My Computer', select "Manage," look under 'Event Viewer->Windows Logs->Application' to see if there's an event there from Premiere Pro. If so, copy the contents of that log and paste them here.
    >>>>>>>>>>>>>>
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: VideoFilterHost.dll, version: 8.2.0.65, time stamp: 0x5486bf85
    Exception code: 0xc0000005
    Fault offset: 0x000000000006d692
    Faulting process id: 0x19d0
    Faulting application start time: 0x01d022d29c3e2d43
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\VideoFilterHost.dll
    Report Id: 1097ced4-8ec8-11e4-aaaf-08606e6e6383
    <<<<<<<<<<<<<<<
    Thanks,
    Rameez

    Problem Solved! (with a small catch)
    While searching crashing issues I came across this thread,"Premiere Pro random crashing since update to 2014.2"
    Marc_Lec  Answered (and I paraphrase here)"...I had the same problem and this is what I did. In 'Preferences Memory'  I increased the memory reserved for other application to at least half the installed and changed the optimize render from 'performance' to 'memory."
    Thank You Marc_Lec for what has been a game changer for me since my last computer and the beginning of PremiereCC problems.
    I changed my Memory reserved for Other Applications from the default 7gigs to 1/2 of my approx.31 available Gigs = 16Gigs. Viola!
    No more crashing what-so-ever!
    I still have to purchase an older  GTX 980 graphics card to take advantage of Adobe's approved code to utilize X=Cuda Cores and GPU, but I think I'll hang onto my new TitanX, in hopes that Adobe will write code and approve it someday in the near future.
    Now why doesn't Adobe say this officially about Memory Settings? (I don't know maybe they do and I missed I somewhere)
    Mine and probably many peoples computers problems here on this board may be attributed to a simple Memory adjustment, because the computer needs more than 7Gigs to run itself, not to mention Premiere.

  • Random crashes, Windows 7

    Hey there Adobe community! I have seen a number of "random" crash threads without much resolution. Well, here is mine!
    System is an HP Elite 8300 Workstation, i5 processor 3.2ghz, 6GB ram, Windows 7 SP1, good Nvidia graphics card with updated drivers.
    However, drum roll please.....
    Random crashes occur, and I do mean random - no particular time/process when it crashes.
    Event log always logs illustrator.exe with either DVAUI.DLL or MSVCR100.DLL as the faulting mod.
    Faulting application name: Illustrator.exe, version: 16.0.0.682, time stamp: 0x4f6e45b7
    Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
    Exception code: 0xc000041d
    Fault offset: 0x000000000003c9ca
    Faulting process id: 0x378
    Faulting application start time: 0x01cd9b1aee274657
    Faulting application path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\Illustrator.exe
    Faulting module path: C:\Windows\system32\MSVCR100.dll
    Report Id: faa0a2c8-072f-11e2-be24-80c16eff3ba7
    Faulting application name: Illustrator.exe, version: 16.0.2.682, time stamp: 0x5056c659
    Faulting module name: dvaui.dll, version: 6.0.0.0, time stamp: 0x4f6e3e47
    Exception code: 0xc0000005
    Fault offset: 0x0000000000041521
    Faulting process id: 0x208
    Faulting application start time: 0x01ce04841ada6398
    Faulting application path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\Illustrator.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\dvaui.dll
    Report Id: 6e6ed6c9-70a9-11e2-b720-80c16eff3ba7
    Recently, a new addition to the event log:
    The program Illustrator.exe version 16.0.2.682 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
    Process ID: 10bc
    Start Time: 01ce0564749617ca
    Termination Time: 452
    Application Path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\Illustrator.exe
    Report Id: 19255145-717b-11e2-b3c1-80c16eff3ba7
    Any ideas?
    Thanks in advance!
    - Matt

    More errors....anyone???
    Faulting application name: Illustrator.exe, version: 16.0.0.682, time stamp: 0x4f6e45b7
    Faulting module name: dvaui.dll, version: 6.0.0.0, time stamp: 0x4f6e3e47
    Exception code: 0xc0000005
    Fault offset: 0x0000000000041521
    Faulting process id: 0x2bc
    Faulting application start time: 0x01ce15c642d463a6
    Faulting application path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\Illustrator.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\dvaui.dll
    Report Id: 571ed565-8204-11e2-8438-80c16eff37e5
    The program Illustrator.exe version 16.0.0.682 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
    Process ID: b08
    Start Time: 01ce18f297731b75
    Termination Time: 47
    Application Path: C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\Illustrator.exe
    Report Id: 43650b0f-8515-11e2-b77e-80c16eff37e5

  • Apple, please fix safari random crash and tab auto refresh

    Apple, are those issues ever going to get fixed? They destroyed iOS 7's usability and the latest 7.1 beta doesnt seem to address either.
    1) Safari randomly crashes -  happens multiple times a day. Sometimes opening new pages, sometimes scrolling through existing page.  This issue has NEVER happened on iOS 6.
    2) Tabs auto refreshing when you switch from 1 tab to the next - it is EXTREMELY annoying, for example when i was typing up a post in a tab or looking at the result of a long search, then need to lookup something else so i open up a new tab, then when I go back to the original tab, it automatically refreshes wiping out everything i just typed or the searh result.  This issue has NEVER happened in iOS 6.
    I am using ipad air with the latest update. Please fix them, it's unacceptable.

    This is a user-to-user forum hosted by Apple. You are only talking to other users here not Apple.
    If you have a suggestion for Apple use: http://www.apple.com/feedback/ipad.html

  • Photoshop CS6 keeps randomly crashing

    I bought CS6 upgrade from CS5 this week but it keeps randomly crashing I mainly use CS6 for digital art with my wacom intuos tablet. I have never had this problem with CS5 and I have a decent spec PC with 8 GB Ram and a quadcore CPU so I dont understand why this is happening. In the preferences menu I have save in backround and automatically save information every 10 minutes options checked. But the ironic thing is that when I have been drawing a long time and Photoshop crashes and when I reopen CS6 there is no recovery file and the origional file hasnt been updated with auto save. I have 7 different versions of a particular digital painting I have been working on but CS6 only saved 2 recovery files from the 7 versions and has crashed atleast 16 times between my work. I have CS6 updated to the latest version from online update but the problem still persists. Can anyone offer me any advice?

    I have this problem and follwed to the red error details: Log Name:      Application Source:        Application Error Date:          7/19/2012 12:46:40 PM Event ID:      1000 Task Category: (100) Level:        Error Keywords:      Classic User:          N/A Computer:      Ramona-HP Description: Faulting application name: Photoshop.exe, version: 13.0.0.0, time stamp: 0x4f61c045 Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a Exception code: 0x40000015 Fault offset: 0x00000000000761c9 Faulting process id: 0x14a4 Faulting application start time: 0x01cd65da5e3a1967 Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe Faulting module path: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\MSVCR100.dll Report Id: 13889778-d1d2-11e1-bef5-00038a000015 Event Xml:           1000    2    100    0x80000000000000        60784    Application    Ramona-HP            Photoshop.exe    13.0.0.0    4f61c045    MSVCR100.dll    10.0.40219.1    4d5f034a    40000015    00000000000761c9    14a4    01cd65da5e3a1967    C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe    C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\MSVCR100.dll    13889778-d1d2-11e1-bef5-00038a000015 

  • Photoshop CS6 Randomly Crashes using Intel HD Graphics 4000

    When using Photoshop CS6 on Windows 8 [Surface Pro], it randomly crashes. I normally can only use Photoshop for less than a minute, doing less than ten actions, before it crashes. I get an error message saying "Adobe Photoshop CS6 has stopped working." If I debug it using Visual Studio, I get this message:
    Unhandled exception at 0x5442B60E (ig7icd32.dll) in Photoshop.exe: 0xC0000005: Access violation reading location 0x0000002C.
    I looked up ig7icd32.dll and it seems to be published by Intel and related to my graphics hardware, so I assume the problem is related to my Intel HD Graphics 4000.
    Does anyone have any idea on how to fix this problem or as to what might be causing it?
    EDIT:
    Also, when launching Photoshop, I get this message:
    Photoshop has encountered a problem with the display driver, and has temporarily disabled enhancements which use the graphics hardware.
    Check the manufacturer's website for the latest software.
    Graphics hardware enhancements can be enabled in the performance panel of preferences.
    For more information, visit:
    http://www.adobe.com/go/photoshop_gpu_en
    All my drivers are fully updated, and all Windows updates are installed. No other applications have any problems with my graphics hardware.

    If Intel does not have an updated driver, I would check the MS Surface Pro Web site.
    If no updated driver exists, you might get it to run, if you turn off all graphics acceleration.
    Unfortunately, Intel graphics chips are good, but driver support has been horrible. I recommend against using them, if one has programs like Ps CS 6, Premiere Pro CS 5 - 6, Premiere Elements 9 - 11, After Effects CS 6, any 3D applications, etc.. The Intel chips and drivers are OK for checking e-mail, surfing the Web, doing light wordprocessing, or some spreadsheet work, i.e. the tasks that they were designed for. They fall far short with video-intensive applications, that need to interface with the video driver.
    Good luck,
    Hunt

  • Adobe Premier random crashing?

    Having issues with Premier randomly crashing. Anyone have any ideas?
    Log Name:      Application
    Source: Application Error
    Date: 10/15/2014 2:29:30 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User: N/A
    Computer:
    Description:
    Faulting application name: Adobe Premiere Pro.exe, version: 7.2.1.4, time stamp: 0x52aed7f3
    Faulting module name: dvacore.dll, version: 7.2.1.4, time stamp: 0x52ae9723
    Exception code: 0xc0000005
    Fault offset: 0x00000000000719e0
    Faulting process id: 0x1fe0
    Faulting application start time: 0x01cfe8bc8869ec54
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC\dvacore.dll
    Report Id: 5867cc7f-54b2-11e4-9cd8-d4bed99f4757
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-15T21:29:30.000000000Z" />
    <EventRecordID>98108</EventRecordID>
    <Channel>Application</Channel>
        <Security />
      </System>
      <EventData>
        <Data>Adobe Premiere Pro.exe</Data>
        <Data>7.2.1.4</Data>
        <Data>52aed7f3</Data>
        <Data>dvacore.dll</Data>
        <Data>7.2.1.4</Data>
       <Data>52ae9723</Data>
        <Data>c0000005</Data>
        <Data>00000000000719e0</Data>
        <Data>1fe0</Data>
        <Data>01cfe8bc8869ec54</Data>
        <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe</Data>
        <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC\dvacore.dll</Data>
    <Data>5867cc7f-54b2-11e4-9cd8-d4bed99f4757</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source: Application Hang
    Date: 10/15/2014 2:10:59 PM
    Event ID:      1002
    Task Category: (101)
    Level:         Error
    Keywords:      Classic
    User: N/A
    Computer:
    Description:
    The program Adobe Premiere Pro.exe version 7.2.1.4 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
    Process ID: 1720
    Start Time: 01cfe7fd2ae595e9
    Termination Time: 1221
    Application Path: C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe
    Report Id: bcba0c0d-54af-11e4-9cd8-d4bed99f4757
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Hang" />
        <EventID Qualifiers="0">1002</EventID>
        <Level>2</Level>
        <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-15T21:10:59.000000000Z" />
    <EventRecordID>98107</EventRecordID>
    <Channel>Application</Channel>
        <Security />
      </System>
      <EventData>
        <Data>Adobe Premiere Pro.exe</Data>
        <Data>7.2.1.4</Data>
        <Data>1720</Data>
        <Data>01cfe7fd2ae595e9</Data>
        <Data>1221</Data>
        <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe</Data>
    <Data>bcba0c0d-54af-11e4-9cd8-d4bed99f4757</Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
      </EventData>
    </Event>

    Rather than playing 20 questions, please read PPro Information FAQ http://forums.adobe.com/message/4200840 and provide all information
    Including... What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    For Windows, do NOT rely on Windows Update to have current driver information
    -you need to go direct to the vendor web site and check updates for yourself
    ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • Premier Elements 12 randomly crashing

    Premier Elements 12 randomly crashing, WIndows 8.1, Dell 9020 AIO
    event viewer shows;
    Application: Adobe Premiere Elements.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: exception code c0000005, exception address 000000000AD443D5
    Faulting application name: Adobe Premiere Elements.exe, version: 12.0.0.0, time stamp: 0x52251824
    Faulting module name: TitlerCreator.dll, version: 12.0.0.0, time stamp: 0x5225108b
    Exception code: 0xc0000005
    Fault offset: 0x00000000000043d5
    Faulting process id: 0x27c4
    Faulting application start time: 0x01cf50362d4954b8
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Elements 12\Adobe Premiere Elements.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Elements 12\TitlerCreator.dll
    Report Id: 272de427-be53-11e3-be81-c81f66abbe4a
    Faulting package full name:
    Faulting package-relative application ID:
    Faulting application name: Adobe Premiere Elements.exe, version: 12.0.0.0, time stamp: 0x52251824
    Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
    Exception code: 0x40000015
    Fault offset: 0x00000000000761c9
    Faulting process id: 0xf4c
    Faulting application start time: 0x01cf529e81a9051d
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Elements 12\Adobe Premiere Elements.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR100.dll
    Report Id: 422270fa-be96-11e3-be82-c81f66abbe4a
    Faulting package full name:
    Faulting package-relative application ID:

    WhiteLeroy
    Thanks for your recent posts detailing your TImeline issues. Because of the varied remedies and setbacks with which you are dealing with, let us recap for a moment about some basics so as not to take anything for granted.
    Premiere Elements 12 on Windows 8.1 64 bit
    1. What is the video card/graphics card that the computer uses and is it up to date according to the web site of the manufacturer of the card? Does you Device Manager/Display Adapters area show 1 or 2 cards?
    2. Review your settings under Edit Menu/Preferences/Audio Hardware ASIO Settings.
    3. Delete the Adobe Premiere Elements Prefs file, and, if necessary, the whole 12.0 Folder in which it exists.
    Local Disk C
    Users
    Owner
    AppData
    Roaming
    Adobe
    Premiere Elements
    12.0
    and in the 12.0 Folder is the Adobe Premiere Elements Prefs file that you delete. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path cited.
    4. Do a ccleaner run through (regular cleaner and registry part)
    https://www.piriform.com/ccleaner
    5. Assure that you do not have pile up of preview files, conformed audio files, or conformed video files.
    See Libraries\Documents\Adobe\Premiere Elements\12.0 and Adobe Premiere Elements Preview Files Folders (for preview files), Media Cache Files Folder (for conformed audio cfa and pek).
    See Edit Menu/Preferences/Media and the Media Cache Database area Clean button.
    6. Generally check Scratch Disks for location and free space at the location to which each is directed.
    See Edit Menu/Preferences/Scratch Disks.
    7. General question...how project specific have these issues become?
    Please review and let us rule these factors in or out.
    Thanks for the follow ups.
    ATR

  • MMC.exe random crashes AD users & computers

    We are experiencing issues when editing users & computers on a newly installed Server 2012 R2.
    The MMC randomly crashes when creating a new user. Sometimes we can enter 10-20 users flawlessly and sometimes it crashes every 2-3 users. In the logs we can find the following error (in Dutch - sorry):
    Naam van toepassing met fout: mmc.exe, versie: 6.3.9600.16384, tijdstempel: 0x5215ef8f
    Naam van module met fout: ntdll.dll, versie: 6.3.9600.17114, tijdstempel: 0x53649e73
    Uitzonderingscode: 0xc0000374
    Foutmarge: 0x00000000000f87a8
    Id van proces met fout: 0xfdc
    Starttijd van toepassing met fout: 0x01cfac99667c332f
    Pad naar toepassing met fout: C:\Windows\system32\mmc.exe
    Pad naar module met fout: C:\Windows\SYSTEM32\ntdll.dll
    Rapport-id: 3085a3b0-188d-11e4-80ba-0050568b4b6a
    Volledige pakketnaam met fout:
    Relatieve toepassings-id van pakket met fout:

    We might have found the problem. It probably isn't a windows problem but a problem in de VMWare esxi version we are using. We are using 5.1 which apparently doesn't support windows server 2012 R2 yet. We will soon upgrade to version 5.5 and I'll
    post the test results here.

  • Firefox experiences random crashes which persist even in safe mode (linux + gnome)

    Since maybe version 29, my Firefox has become less stable than before and started to crash for seemingly no reason; sometimes it crashed shortly after started with few tabs on, and sometimes it crashed when many tabs were open or (not constantly) with music playing. In short I cannot find an exact pattern by which crashes are triggered. Only one thing is certain, once it broke down, it kept crashing on every restart (even in safe mode or with the user preference directory reset by a complete removal), until a reboot.
    I checked some threads, where people suggest that such random crashes may be caused by a flawed RAM, but I feel it unlikely because in this same system no other software (including Chromium) have shown similar problem, and on Windows the same computer Firefox (v31) has been rather stable.
    Although it didn't happen frequently, the need to reboot the computer before Firefox gets usable again is really annoying. I appreciate a lot if anyone could give some hints, thanks.
    The environment:
    base system: openSUSE 13.1 (Bottle) (i586) 32-bit
    desktop: Gnome 3.10.2
    cpu: AMD C-60 APU with Radeon(tm) HD Graphics × 2
    RAM: 4G
    ====================UPDATE=======================
    Sorry I forgot the crash reports, here they are:
    bp-53142ca2-076d-4413-9d1a-2d2c72140928
    bp-ec9c9990-0cde-48e5-a792-27bd22140928
    bp-425bcbf0-5c79-4050-999f-ebc692140928
    bp-30bc9187-5a52-47ba-a193-9c6b82140928
    bp-d39f099c-758a-405d-a566-d3bd72140928
    bp-7aff96dc-bbc2-4e41-9888-af5d62140928
    bp-fef7b101-e586-4a8c-94a7-6dc842140928
    bp-c8785c65-4c72-4f9b-b0fb-439ac2140928
    bp-47244ab2-dfa5-49a9-9345-500342140928
    bp-cc104c04-516f-4f48-a2cf-ff4fa2140926
    bp-f38876f1-48c2-4788-b5aa-54cce2140926
    bp-3057d6a8-59d8-4cfe-8720-338072140926
    bp-c17b4506-fde9-4389-8b2d-ac6a72140923
    bp-a3d651aa-613b-457f-9cc9-44e812140922
    bp-af7593e9-b7d1-44f6-aebc-bd0d72140920
    bp-7055424f-8212-4c54-9fcc-39bb32140917
    bp-026ab307-ace0-4ef5-a286-7d70a2140917
    bp-ab4e4111-33f1-4d0c-820d-3b8332140917
    bp-be24878b-eda9-4afd-a942-204502140917

    All of your crash reports say;
    Signature: libxul.so@0x3868df | libxul.so@0x38691f | libxul.so@0x10ee1b0 | firefox@0x12f15
    Crash Reason SIGSEGV
    Someone else will have to talk to you about it.
    '''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode]''' {web link}
    While you are in safe mode;
    Type '''about:preferences'''<Enter> in the address bar
    Select '''Advanced > General.'''
    Look for and turn off '''Use Hardware Acceleration'''.
    Poke around safe web sites. Are there any problems?
    Then restart.

  • Smartview causing Excel to randomly crash

    We have recently installed Hyperion Smartview 9.3.1.2 for a number of users who are now experiencing random crashes in Excel. they are not using Smartview at the time but this has only started happening since Smartview was installed and enabled. Disabling the plugin seems to stop this issue from happening. Does anyone have any idea how to resolve this? We are using Excel 2002 (XP) at the moment.
    I have found the following error in the Event Viewer under Office Applications:
    Event Type: Error
    Event Source: Microsoft Office 10
    Event Category: None
    Event ID: 1000
    Date: 22/05/08
    Time: 13:47:56
    User: N/A
    Computer:
    Description:
    Faulting application excel.exe, version 10.0.6841.0, faulting module ole32.dll, version 5.1.2600.2726, fault address 0x00092dd8.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 65 78 63 ure exc
    0018: 65 6c 2e 65 78 65 20 31 el.exe 1
    0020: 30 2e 30 2e 36 38 34 31 0.0.6841
    0028: 2e 30 20 69 6e 20 6f 6c .0 in ol
    0030: 65 33 32 2e 64 6c 6c 20 e32.dll
    0038: 35 2e 31 2e 32 36 30 30 5.1.2600
    0040: 2e 32 37 32 36 20 61 74 .2726 at
    0048: 20 6f 66 66 73 65 74 20 offset
    0050: 30 30 30 39 32 64 64 38 00092dd8
    0058: 0d 0a ..

    I found a fix for this issue and others involving smartview and Excel.
    1. Ensure Excel is closed down and is not in any browser sessions - checking the processes tab in task manager is a good way to ensure there are no hidden sessions of Excel open.
    2. Search the local user's C drive for *.xlb and be sure to check 'Search hidden files and folders' under advanced options.
    3. Delete all files with the xlb extension found. These are normally called 'Excel10.xlb' for Excel XP and are usually found in documents and settings folders under the user however they can be called anything with an xlb extension and can be located anywhere on the local drive and there can be multiple files so be sure to delete all of them - they will be recreated in the next step.
    4. Open up Excel. Any required .xlb files will be recreated when Excel opens.
    These steps have resolved 3 different issues we had after installing Smartview. Hope this helps others.

  • Random crashes in powerbuilder 11.5 application

    Hello,
    We're a reseller of an application that was written in powerbuilder 11.5.  We have one customer who is struggling with this application with random crashes in various parts of the software.  Because we resell it we don't have the code and the people we resell for are not being very forthcoming on helping us saying that the customer needs to use a new machine, which of course they do not want to do.  Note this is the only customer who has this so it is something to do with their environment and we're not sure where to start.
    Event viewer shows an access violation pbdwe115.dll for every event.
    Because the crash is random and sometimes there can be three in a day and sometimes none for three days we can't put /pbdebug on as the log files could potentially be massive.
    Therefore decided to turn on crash dump file creation.  The crash dumps show the same stack for every dump, which is as follows
    PRIMARY_PROBLEM_CLASS:  INVALID_POINTER_READ
    BUGCHECK_STR:  APPLICATION_FAULT_INVALID_POINTER_READ
    LAST_CONTROL_TRANSFER:  from 7c353984 to 1172bccd
    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    00129c68 7c353984 7c35226a 00000809 00129c50 pbdwe115!dwMessageBoxDlgProc+0x192d
    00129cc0 770ba53c 8089a674 09e8b690 0012a2e0 msvcr71!__crtLCMapStringW+0x258
    00cbd5e8 00000000 ff315330 8865d520 fe21d5e8 user32!ScreenToClient+0x4b
    Has anyone got any experience of this kind of crash?  We've had some fun with this application and printer drivers on citrix in the past, however it's generally solid.
    The application is powerbuilder 11.5 on Windows 7 accessing a SQL Server 2008 R2 database.
    Any suggestions very gratefully received!
    Many thanks,
    stevensns

    These are just unhandled systemerrors and nearly impossible to trace down without PBDEBUG.  SInce you can't use that, try and eliminate other variables...
    Does it happen on every workstation at the customer?  Or just one?
    Is there one window or tabpage where it happens more often?  Have the customer keep a journal in OneNote or something of what they're doing when the crash occurs.  How many windows did they have open?  What report was just retrieved?  How long had the application been open since it was last restarted?  What other apps are running on the machine at the time? Stuff like that.
    Have them scan the machine for any other copies of PB*.DLL that might be lurking in the PATH somewhere.
    -Paul-

  • Random crashes win7 64

    I am having troubles with FF. I seem to get random crashes on almost any site. I've been through a few troubleshooting things but nothing has solved it yet. I did not have any troubles on this machine before, the only change was from win7 32 to win 7 64bit + ram. fresh install. things I have tried:
    disabling plugins<br />
    upgrading plugins<br />
    disable hardware acceleration (thru flash and thru FF)<br />
    updating windows<br />
    updating graphics drivers<br />
    reseting firefox<br />
    uninstall/reinstall<br />
    chkdisc - good<br />
    memtest - good
    sometimes upon closing FF, I get a windows error citing xul.dll as the fault, however that has not happened since the new reinstall.
    bp-f511ec53-76de-4b2d-881b-bfee52131208 <br />
    bp-224ab91f-0339-48bd-bffd-ef6752131207 <br />
    bp-c7c8c55c-9fca-434c-804b-a3ef12131207 <br />
    bp-089272af-3e3a-43ce-94c0-85e962131207<br />
    bp-09ec6e78-e023-44fd-ba2f-50f372131207
    also note that the crash reports say that I have Widows NT ?? is that a problem
    thanks for your time..

    All Windows versions are given an NT number.<br>
    The general public knows this Windows versions as their market name not their technical name.<br>
    For example, your reports say that you are running Windows NT 6.1. This tells me that you are running Windows 7.
    Please search for a <code>user.js</code> file located in your Firefox profile, application data, or program directory?<br>
    In most cases, this file is created by a third party program and has been known to cause some issues with Firefox.<br>
    If you locate this file, please attempt to delete it.
    Please report back soon.

Maybe you are looking for