Share via

Applications .exe Fail to Start by Kernelbase.dll error

Anonymous
2024-04-12T03:02:38+00:00

Hello technical team,

I have encountered an issue as follows: The exe application I developed, when used with Windows 10 for a while, cannot be opened anymore. When I checked the Event Viewer, I saw an Application Error with KERNELBASE.dll. The detailed error is as follows:
"Faulting application name: Plug-in real time code.exe, version: 1.0.0.0, time stamp: 0xf77e9bf0
Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x640b6fb9
Exception code: 0xe0434352
Fault offset: 0x0013fa72
Faulting process id: 0x5520 Faulting application start time: 0x01da630107d180b2
Faulting application path: C:\Program Files (x86)\Company\Plug-in Realtime code\Plug-in real time code.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: bf211fd9-9f87-4270-bd46-5f004071ca0d
Faulting package full name: Faulting package-relative application ID: "

When I create a new user or use administrator rights, it works fine again. Please let me know how to solve this issue. Thank you.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-13T09:54:37+00:00

    Hello Roy Nguyen,

    Welcome to Microsoft Community.

    I believe that you are a highly skilled developer. After reading all the information you have posted, if you are asking how to circumvent this problem, you have already found the answer:

    1. Create a new account.
    2. Run the application you developed with administrator rights.

    However, if you want to know why this error occurs in this application, we are sorry that this is beyond the scope of community support, and we do not have the knowledge of software development and debugging.

    Please allow me to venture a counter-guess from the above answers, then the reason may be:

    1. An error in the original account profile prevented the application from running with the rights of the standard user.
    2. Account permissions are insufficient.

    But if you're looking for expert advice or help tuning your applications, I'd recommend going to our advanced technology forum, Microsoft Learn, which aims to support more advanced users like you.

    You can click on "Ask a question", there are experts who can provide more professional solutions in that place.

    I won't be able to help you, but I'll leave that question open in case one of our amazing volunteers has ideas for you.

    Best regards,

    Mitchell - | Microsoft community support expert from MSFT

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments