Access crashing at all times

[Burroughs70]

Good evening, guys and thanks for accepting me in this forum.
I'm using Windows 11 ARM version on a MacBookPro 14'' with a M1 processor.
My Office version is 365 for Enterprise (version 2111 Build 16.0.14701.20240, 64 bit).

Every time I try to open an Access file or create it from scratch, the application crashes and even though I've updated both the operating system and the Office suite nothing changes.
This is what Event Viewer in Windows says (it's in Italian but it should be clear the same):

Nome registro: ApplicationOrigine: Application Error
Data: 27/12/2021 14:28:00
ID evento: 1000
Categoria attività100)
Livello: Errore
Parole chiave: Classico
Utente: N/D
Computer: TENNY
Descrizione:
Nome dell'applicazione che ha generato l'errore: MSACCESS.EXE, versione: 16.0.14701.20262, timestamp: 0x61ba84b9
Nome del modulo che ha generato l'errore: ntdll.dll, versione: 10.0.22523.1000, timestamp: 0xa11a3130
Codice eccezione: 0xc0000409
Offset errore 0x000000000016f840
ID processo che ha generato l'errore: 0x1304
Ora di avvio dell'applicazione che ha generato l'errore: 0x01d7fb258e13b218
Percorso dell'applicazione che ha generato l'errore: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Percorso del modulo che ha generato l'errore: C:\WINDOWS\SYSTEM32\ntdll.dll
ID segnalazione: 487e792b-176e-4a66-bc30-f869e26add20
Nome completo pacchetto che ha generato l'errore:
ID applicazione relativo al pacchetto che ha generato l'errore:
XML evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-12-27T13:28:00.6976384Z" />
<EventRecordID>724</EventRecordID>
<Correlation />
<Execution ProcessID="10940" ThreadID="0" />


<Channel>Application</Channel>
<Computer>TENNY</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>16.0.14701.20262</Data>
<Data>61ba84b9</Data>
<Data>ntdll.dll</Data>
<Data>10.0.22523.1000</Data>
<Data>a11a3130</Data>
<Data>c0000409</Data>
<Data>000000000016f840</Data>
<Data>1304</Data>
<Data>01d7fb258e13b218</Data>
<Data>C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>487e792b-176e-4a66-bc30-f869e26add20</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

There's two or three databases I use very often, so it would be really important for me to get this problem sorted.
Any ideas???

[Minty]

I would initially try an Office repair or reinstall, as if you can't even open a new database it sounds like a Access problem not a database file problem.

[Welshgasman]

Seems to me that ntdll.dll might be the culprit?

Try a sfc /scannow in an admin command window ?

[CJ_London]

translated using google translate

log-name: ApplicationOrigine: Application Error
Date: 12/27/2021 2:28:00 PM
Event ID: 1000
Activity Category100)
Level: Error
Keywords: Classic
User: N / A
Computer: TENNY
Description:
Name of the application that generated the error: MSACCESS.EXE, version: 16.0.14701.20262, timestamp: 0x61ba84b9
Name of the module that generated the error: ntdll.dll, version: 10.0.22523.1000, timestamp: 0xa11a3130
Exception code: 0xc0000409
Error offset 0x000000000016f840
Process ID that generated the error: 0x1304
Start time of the application that generated the error: 0x01d7fb258e13b218
Path of the application that generated the error: C: \ Program Files \ Microsoft Office \ Root \ Office16 \ MSACCESS.EXE
Path to the module that generated the error: C: \ WINDOWS \ SYSTEM32 \ ntdll.dll
Report ID: 487e792b-176e-4a66-bc30-f869e26add20
Full package name that generated the error:
Application ID for the package that generated the error:
XML event:
<Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name = "Application Error" />
<EventID Qualifiers = "0"> 1000 </EventID>
<Version> 0 </Version>
<Level> 2 </Level>
<Task> 100 </Task>
<Opcode> 0 </Opcode>
<Keywords> 0x80000000000000 </Keywords>
<TimeCreated SystemTime = "2021-12-27T13: 28: 00.6976384Z" />
<EventRecordID> 724 </EventRecordID>
<Correlation />
<Execution ProcessID = "10940" ThreadID = "0" />
<Channel> Application </Channel>
<Computer> TENNY </Computer>
<Security />
</System>
<EventData>
<Data> MSACCESS.EXE </Data>
<Data> 16.0.14701.20262 </Data>
<Data> 61ba84b9 </Data>
<Data> ntdll.dll </Data>
<Data> 10.0.22523.1000 </Data>
<Data> a11a3130 </Data>
<Data> c0000409 </Data>
<Data> 000000000016f840 </Data>
<Data> 1304 </Data>
<Data> 01d7fb258e13b218 </Data>
<Data> C: \ Program Files \ Microsoft Office \ Root \ Office16 \ MSACCESS.EXE </Data>
<Data> C: \ WINDOWS \ SYSTEM32 \ ntdll.dll </Data>
<Date> 487e792b-176e-4a66-bc30-f869e26add20 </Data>
<Date>
</Data>
<Date>
</Data>
</EventData>
</Event>

As WGM says - looks like it is the ntdll file - here are a couple of links as to how to fix

https://www.drivereasy.com/knowledge...l-crash-issue/
https://answers.microsoft.com/en-us/...0-7eb72df05b2a

[Burroughs70]

Thanks to everyone for your quick replies.
sfc /scannow says everything is alright, if I try to remove ntdll.dll as an administrator from the command line I get the following message:

the module "ntdll.dll" was loaded but the entry-point DllRegisterServer was not found

[Minty]

I would be very wary about simply deleting a dll file, just because it is showing as generating an error, it doesn't mean it is the cause.
As I said earlier, the fact that you can't even create anew blank database suggests that Access itself is damaged or something within the office environment isn't well.

[Micron]

I seem to recall that the latest bug (which many of you have recently commented on) caused error messages on PC but an absolute crash on Macs. I doubt that I would be able to find that now. So could that be the issue? This is not the page where I read that, but it might be a start.

https://support.microsoft.com/en-us/...0-d079a46f5acc

[Minty]

@Micron Might have a valid point there my Build Version is later than the OP's

Microsoft® Access® for Microsoft 365 MSO (Version 2111 Build 16.0.14701.20254) 64-bit

[Burroughs70]

I've uninstalled Office 365 and now I'm using a developer version which should be "optimized" for my platform (ARM).
Well, it's the same as before, the bug seems to affect Access only.

[Welshgasman]

Thanks to everyone for your quick replies.
sfc /scannow says everything is alright, if I try to remove ntdll.dll as an administrator from the command line I get the following message:

You used to be able to extract files from the windows cabinet files?

See post #3 here for the bug fix at least.
https://www.access-programmers.co.uk.../#post-1802189

[Welshgasman]

https://support.microsoft.com/en-us/...3-966e85d4094e

[Burroughs70]

In the end I was able to get this thing sorted by installing a fresh copy of Windows 11 Home using my Parallels Desktop license.
It was clearly a bug and/or something similar concerning the Developer Preview I was using.
Thanks, guys, for your precious help.