Share via

App Crashing on First Open with error Faulting module name: USER32.dll, version: 10.0.18362.1171, time stamp: 0x13516cf1 Exception code: 0xc0000005

Paul Bill 66 Reputation points
2020-12-03T20:50:22.407+00:00

The error is: Faulting module name: USER32.dll, version: 10.0.18362.1171, time stamp: 0x13516cf1 Exception code: 0xc0000005 Fault offset: 0x000000000000afd5 Faulting process id: 0x1dcc

I am at a loss. I recently installed this same application for the same client two weeks ago on a different machine with no issues. Now, after I have installed it on a new device for the same client and try to open the application I'm getting an error with the above .dll. I've ran sfc /scannow on the device and it finds nothing wrong. This install package was created back in July. The device is running on Windows 10 Enterprise Version 1909 OS Build 18363.1198. Any ideas or help is appreciated?

VB
VB
An object-oriented programming language developed by Microsoft that is implemented on the .NET Framework. Previously known as Visual Basic .NET.
2,640 questions
Accepted answer
  1. Michael Taylor 50,431 Reputation points
    2020-12-04T15:33:49.67+00:00

    It is an access violation error. What does the stack trace look like in the event log that is generated when your app crashes.

    Also note that hopefully you're generating PDBs when you build your code. In that case drop the PDB files into the directory where the app is running. Then run the app and let it crash. In the WER dialog that pops up is an option to view the technical details. In that UI is a link to the crash dump file. Grab the crash dump file and move it to a machine that has your app's code, the binaries being used by the client and Visual Studio. Then load up the crash dump in VS and you should be able to quickly narrow down where it is crashing and probably why.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Paul Bill 66 Reputation points
    2020-12-07T23:13:29.503+00:00

    cooldadtx: Where do I find that stack trace? I go into event viewer but I just get the generic error. When I click on the dump file it says it can't open it. It's crashing trying to access the System32 folder. I'm thinking it's a permission issue on the device, possibly related to the domain/network, NT Network/Authority or SQL since our Application utilizes SQL or a service has stopped that needs restarted but I can't pin it down. SQL Services are running, not sure if I need to open ports for the TCP/UDP etc.