Participating Frequently

Question

Frame won't start - 0xc0000005 error clash with ntdll.dll

Forum|Forum|11 years ago
October 8, 2014
5 replies
2157 views

Good day everyone,

After installing Framemaker 12, I cannot start the program. Windows 7 Enterprise gives me an error 0xc000005. Looking at the event viewer, there is a clash with windows file ntdll.dll. If I start Windows in safe mode, I can start Framemaker. Same with safe mode with networking. I tried turning off all services and system settings to no avail.

I have all the most recent patches for Windows and Frame, tried every option out there on the Internet and Can't get it to work.

Has anyone else encountered or heard of this? I thought I'd ask the users at large before giving in to contact Adobe and Windows support.

I'm looking for any other options to start and use Framemaker. Running it only in Safe Mode won't do, as I can't print and the video is way too big.

Thanks

_Don

This topic has been closed for replies.

My1kAuthor

Participating Frequently

More info. I had the IT guys look into this. The good news, is he gets the same problem, so its not just me :-)

So it may be something with the way the corporate systems are configured - something that internally is not loaded or turned off or whatever, that Framemaker needs. Some more investigation is underway.

My1kAuthor

Participating Frequently

I just realised I never completed this. It was an issue with the policies used within the company. They are still not sure which bit is the issue, but I have a special policy so Framemaker can talk to the Internet and I can get on with my work.

Bob_Niland

Community Expert

> ntdll.dll

You might right-click on C:\WINDOWS\system32\ntdll.dll

and report Version > File Version

There are nearly 2500 entry points (API calls) in the various versions of NTDLL, so it's impossible to guess which function call may be triggering the crash. But if your NTDLL has been replaced by an incompatible version, that might be apparent (but doubtful, as probably everything that runs on post-NT Windows calls at least one API in this DLL). This assumes that FM is invoking the installed standard NTDLL on the machine. Thanks to Side-by-Side assemblies in Win98 and later, FM might be invoking it's own (older) version.

You might also look in C:\WINDOWS\WinSxS\Manifests

and see if there's any evidence of a manifest file for Adobe Framemaker

Arnis Gubins

Inspiring

Don,

Typically 0xc0000005 errors are due to system file corruption, faulty hardware (RAM) or a driver issue.

You can run SFC /SCANNOW Command - System File Checker to check for any system file corruption.

To check for any memory errors, you can try the Windows Memory Diagnostics tool (see: Memory Diagnostics Tool - Windows 7 Help Forums)

There's also the possibility that some malware has snuck into your installation.

My1kAuthor

Participating Frequently

Blowing up right away. I don't even get a splash screen. As in double-click icon, error.

Jeff_Coatsworth

Community Expert

Try an uninstall/re-install? If that’s doesn’t fix it, contact Adobe Support

My1kAuthor

Participating Frequently

Yeah, I tried the install thing a few different times in different ways - in safe mode, with various things turned off. I guess I'm calling Support.

This is ridiculous.

Jeff_Coatsworth

Community Expert

Did you install it with full admin rights?

My1kAuthor

Participating Frequently

Yes, I have full admin rights on the system.

Jeff_Coatsworth

Community Expert

Any anti-virus settings killing .exe processes?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded