none
OC30.dll issue - Program has stopped working RRS feed

  • Question

  • Hi

    We have a VB4 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 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: 2015.3.0.10, time stamp: 0x56091bfa

    Faulting module name: oc30.dll, version: 3.20.0.0, 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

    Saturday, February 13, 2016 10:14 AM

Answers

  • Hi PaulByrneZP,

    Thanks for your post.

    Windows Forms General is discussing about Discuss client application development using Windows Forms controls and features.

    Since your thread is about VB4 and Dlls, you could get more support at VB forum.

    Here are some help links below(VB forum is in the list on the Visual Basic 6.0 Resource Center):

    msdn for vb 6.0

    Visual Basic 6.0 Resource Center

    Regards,

    Moonlight


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Monday, February 15, 2016 6:24 AM
    Moderator

All replies

  • Hi PaulByrneZP,

    Thanks for your post.

    Windows Forms General is discussing about Discuss client application development using Windows Forms controls and features.

    Since your thread is about VB4 and Dlls, you could get more support at VB forum.

    Here are some help links below(VB forum is in the list on the Visual Basic 6.0 Resource Center):

    msdn for vb 6.0

    Visual Basic 6.0 Resource Center

    Regards,

    Moonlight


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Monday, February 15, 2016 6:24 AM
    Moderator
  • Same issue. Would like to see MS fix OC30.DLL so the existing software does not need rewrite and, time and energy wasted. Used in many programs in the Windows computing world written by many besides VB programmers.

    Thanks


    • Edited by VinC54 Friday, March 4, 2016 8:55 PM
    Friday, March 4, 2016 8:53 PM
  • Did you ever find a solution to the OC30.DLL 'stopped working' error? We have a customer that reported the same thing. We looked for hours for a solution or conflict and would appreciate your reply.
    Tuesday, January 24, 2017 8:58 PM
  • Hi,

    Same issue I am facing oc30.dll error in windows 10. Not able to find the solution. Please help as we are using the f1book a lot in the application.

    If there are any alternatives for f1book please suggest that also.

    Thanks

    Gautham S

    Wednesday, May 2, 2018 7:06 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:00 PM