Microsoft Access Crash with Application Load

Question

Hello,

Currently, I am having an issue involving Microsoft Access sporadically crashing when trying to load one of my applications on Microsoft Windows 10 (around once ever two or three loads). Although I have not tested it myself, my colleague is experiencing the crash every time on Microsoft Windows 7. This crash is accompanied with the following Event Viewer message:

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20082, time stamp: 0x5b524023

Faulting module name: ntdll.dll, version: 10.0.17134.165, time stamp: 0xf4df6dc2

Exception code: 0xc0000374

Fault offset: 0x00000000000f4d1b

Faulting process id: 0x2f74

Faulting application start time: 0x01d4331e42725af6

Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE

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

Report Id: 68cd91b1-b4dd-49ac-a80d-16443f253c2c

Faulting package full name:

Faulting package-relative application ID:

I found this post from a while back and followed the basic steps here with no luck.

https://social.technet.microsoft.com/Forums/ie/en-US/70cfa999-dc2a-4282-a2bd-333bd86d13e4/access-2016-crashing-event-id-1000-exception-code-0xc0000374?forum=officesetupdeploy

This started immediately after upgrading office to the monthly branch on version 1807 and does not exist in 1806. Since I believe this is a bug with the 1807 branch, is there a good place to post bug reports to?

Answer 1

Hi RobertJordan,

I am a member of the Access development team.  We believe we have identified the issue you are hitting, and have made a change to fix this problem.  Could you try restarting Access and trying to open the form again with version 1807?

Please let me know if this resolves the issue for you or not.

Mike

Answer 2

For the short term, reverting to a prior build is your only option.

I've forwarded this thread to the Access Dev Team in the hopes they'll get in touch with you to investigate things with you.

Answer 3

Yeah I figured. I clicked on the user that had "Expert" in their name and saw that their account had literally just been created. That on top of someone's first comment to a support ticket being call a support number kind of screamed troll.

This is not a new application. It's been running for a few years now and hadn't experienced this particular crash until the 1807 build. Reverting the update to 1806 and disabling automatic updates has resolved this issue for now.

Nothing too complex being done on startup. This is a front end application for an MSSQL back end so primarily just some checks on user accessing and updating current data as well as a local check on our end for updates for the application. It successfully steps through all of our written code before crashing when trying to load the modules on the primary application page. When trying to disable components one by one, the application seemingly reaches a threshold where it is allowed to always load which doesn't make too much sense since. Note that going back and removing the 'threshold item' only does not eliminate the crash. It seems like component overload which would point to hardware issues. However, this should be a non-issue since the computer we're testing on has an Intel i7-4790 processor with 16GB DDR4 RAM, a 250GB SSD, and a 2TB Data Drive. The computer is also fully up to date on the Windows side of things.

Looking through the update history on Microsoft's website doesn't provide any suggestions as to what would've changed to make way for this issue either.

Thanks for the quick response. It is much appreciated

Answer 4

Firstly, do not use any phone numbers people post.  Always use the Support links at the bottom of page to get the proper way to contact Microsoft.

Secondly, 

Is this a new application?

Did it previously run smoothly?  Is this a recent change in behavior?

Have you reverted your installations to 1806 or prior and disabled automatic updates?

Does your db compile without errors?

What exactly does your database do at startup?  Have you tried identifying the exact source of the issue by disabling, one by one, various startup functions?