Windows 8,10 - crashing unexpectedly - oc30.dll RRS feed

  • Question

  • Hi

    We have a DELPHI 6 program which has been working away happily for the last decade or so. It is in use by about 50,000 customers. Lately we are starting to receive reports of the program crashing unexpectedly with the explanation ... "(Program Name) has stopped working. A problem caused the program to stop working properly. Windows will close the program and notify you if a solution is available." Seems to be happening mostly on W8, W10 machines. The user is not doing anything with the program when the crash occurs. It is usually just in memory.

    The event log says:

    Faulting application name: xxxxxx.exe, version: 2016.0.0.0, time stamp: 0x56091bfa

    Faulting module name: oc30.dll, version:, time stamp: 0x2fc10ea3

    Exception code: 0xc0000005

    Fault offset: 0x000532ae

    Faulting process id: 0x66c

    Faulting application start time: 0x01d128fbc05ee1e1

    Faulting application path: C:\xxxxxx\xxxxxx.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\oc30.dll

    Report Id: 43766fbb-94f3-11e5-becb-7845c428c7f8

    Faulting package full name: 

    Faulting package-relative application ID: 

    Obviously the "xxxxxxx"s are for anonymity!

    Any suggestions?

    Many thanks

    • Moved by Stanly Fan Wednesday, May 10, 2017 5:57 AM from windows form general
    Tuesday, May 9, 2017 10:39 AM

All replies

  • Hi,

    this is a known issue, but it seems that there's no fix or workaround...


    and: [german]


    and [french]




    Tuesday, May 9, 2017 10:49 AM
  • Hi Rui,

    This forum is discussing and asking questions about the Windows Form and ClickOnce, it will be more appropriate to ask your question at Microsoft Community.

    Thank you for your understanding.

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Wednesday, May 10, 2017 5:57 AM
  • I ran into this issue as well and after researching I found that the 0xc0000005 exception is an access violation exception. I then noticed that the path referenced for the faulting module C:\Windows\System32\oc30.dll was invalid in my case. The oc30.dll didn't live in system32. I found a copy of it in SysWOW64 and copied it to System32, which resolved our issue. Good luck.
    Friday, August 23, 2019 7:02 PM