![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#1 |
Gunner
![]() Join Date: Apr 2005
Location: La Spezia Italy
Posts: 93
Downloads: 3
Uploads: 0
|
![]()
Mates i'm in trouble!
After the installation of the latest GWX 2.1 following all the instruction erase the older installation including documents and residue folder trees, then patch 1.4b , GWX 2.0 and so, the game crashes after few seconds of the loading screen and windows report shows an error message regarding "ntdll.dll" Naturally I've redone the complete erase of SH3 with the SH3 disc tool, then the remaining folders tree and then again a cleaning with CCleaner . After that a fresh installation of SH3 with 1.4b emea dvd patch and GWX2 . At the end the GWX 2.1. The game still crash on loading at about one third of the intro screen ,but receive always the same error message , as you can see in the screenshot , the problem is the ntdll.dll. Redoing the procedure three more times give me the same results . ![]() before GWX2.1 my 2.0 works at the best. I've only added Rubini water stream with JSGME without any problem and i've done too some tryouts with SH3 fresh installation 1.4b patched only but got the same ntll.dll error..... Changing the dll with another one taken from Microsoft site producted no effects. The ctd on loading is still present with always the same error message. The same after the upgrade of the DirectX 9c with the latest release. In many forum this is reported as a common problem for many different games but, at the moment, i was no able to find a thread with a clear explanation of the solution adopted. I'm pretty sure is a Windows problem related other than a SH3 one. The GWX 2.1 installation should be only a time coincidence! BTW ,opening the Error contents report i've noticed a strange incongruence... ![]() It's clearly shows that the "System informations" claim that the system is Windows NT 5.1 and an AMD cpu chipset but.... i have an Intel Celeron and run WIN XP Pro .....!!!! What's the meaning of that? Could it be related to the dll error? If someones can help me before i'm getting totally crazy.... ![]()
__________________
"Six Italians, dressed in rather unusual diving suits and equipped with materials of laughably little cost, have swung the military balance of power in the Mediterranean in favour of the Axis". Sir Winston Churchill, on the sinking of HMS Valiant and HMS Queen Elizabeth by Italian Combat Divers ![]() Last edited by Scire; 04-21-08 at 07:37 AM. |
![]() |
![]() |
![]() |
#2 |
Eternal Patrol
![]() Join Date: Mar 2006
Location: CATALINA IS. SO . CAL USA
Posts: 10,108
Downloads: 511
Uploads: 0
|
![]()
Good Morning Scire.
![]() I'm haveing .dll and .act errors myself. I'm looking for answers too. I also have XP pro sp2 2005 ver. I think it's built on NT platform ? Sorry I'm no help. Wanted to let you know your not alone. ![]() |
![]() |
![]() |
![]() |
#3 |
Navy Seal
![]() Join Date: Oct 2005
Location: Cornwall, UK
Posts: 5,499
Downloads: 45
Uploads: 1
|
![]()
Hi Scire.
Last ditch effort here. When you reinstalled SH3, did you reinstall DirectX that came with the disc? If so, make sure you have the latest version installed by checking MS Update. Also, how much RAM are you running and is your Pagefile large enough. @ Firewall If your sig is to be believed, you have no problem with RAM, so the same question to you about DirectX. Also, answer the requests in your other thread. Bloody hell guys, I'm scraping the bottom here if this doesn't work. The only thing I would suggest after trying the above is a full removal of SH3, run a reg cleaner, run a system checker (either System File Checker or 3rd party), full 3rd party defrag (not windows own), spyware scan and virus sweep. Then check GFX card is seated correctly, also check you RAM sticks and that your case is free from dust. Nothing short of a full systems check really. @ Scire I have no doubt that your Kernel error and the following ntdll.dll errors have been caused by the removal of SH3 and the following corruption of these files is a direct result of that but there's so many things that can cause these issues within the windows shell.
__________________
![]() |
![]() |
![]() |
![]() |
|
|