Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
If your seeing something like this
•"STOP: 0xC0000221 unknown hard error C:\Winnt\System32\Ntdll.dll"
•"STOP: C0000221 unknown hard error \SystemRoot\System32\ntdll.dll"
•"AppName: [PROGRAM NAME] ModName: ntdll.dll"
•"[PROGRAM NAME] caused a fault in module NTDLL.DLL at [ANY ADDRESS]"
•"Crash caused in ntdll.dll!"
•"Unhandled exception at [ANY ADDRESS] (NTDLL.DLL)"
Try these steps untill you find a solution
1.Restart your computer. The ntdll.dll error you're receiving could be due to a one-time, temporary issue and a simple reboot may resolve the problem completely.
Option 2 should be a last resort
2.Reinstall Diablo 3 if the ntdll.dll error only displays when you use a specific program.
13.While extremely rare, if everything else has failed, including the clean installation from the last step, you could be dealing with a hardware issue with your hard drive. If so, replace the hard drive and then perform a new installation of Windows.
Edited by corestorm#1637 on 5/29/2012 12:20 PM PDT
All that being said, i just resolved that issue but i'm having another one it's saying diablo 3 is already running then just retarting the loader...
Not sure why it's saying initalizing and everything is up to date. Does anyone have a direct download link to a blizzard updater ?
Apparently if you change your language settings to something other than english it will download an update for the language pack on the game its self and auto update to the latest patch this seems to work and resolve the issue and is a walk around for the ntdll error.
I changed my language, let the download complete and tried to play in the second language and had the same error. Switching back to English and problem persists. Changing location to Europe and get in fine, so assuming it is a local bnet authentication problem and nothing to do with my local install.
Just as another tip. Before reinstalling windows you can use the SFC tool to repair damaged and corrupted system files. This is also considered a "dire repair" step as it can irrevocably nuke a windows install, unless you know how to do a command console recovery to fix it.
You will need your windows CD or repair/recovery CD for this.
To use it, drop into a command prompt by typing:
cmd via run
I solved my problem. Well I didnt solve it, it just kind of happened.
I got the ntdll.dll error for sometime. Wasnt able to play for about a week or so. The other day i uninstalled and reinstalled, and I thought that would fix it. It didnt.
This morning while looking up something related to the ntdll.dll, i found this post by blizzard.
In summary, that means, whichever installer you used to install the game (there are different regions), then you'd have to wait for that regions patch to go live before you can play again. For me, I have some weird setting where my computer thinks Im from GB, and it always downloads the UK version of things. And i had the diablo3_GB installer.
I googled up when the european patch goes live, and earlier this morning, the patch went live.
I was able to update and play.
Threats of violence. We take these seriously and will alert the proper authorities.
Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.
Harassing or discriminatory language. This will not be tolerated.