Application error for the experts

chredwdew · 06-09-2005, 02:24 PM

I am having problems installing V6.12 on my new computer. This computer is only a month or so old. I would appreciate any help you could give me, as I am really starting to fall behind in my online league.

Here is the following error.

The Application has failed to initialize properly (0Xc0000005) click on ok to terminate.

Hope someone will be able to help.

chredwdew · 06-09-2005, 02:29 PM

Forgot to post my system specs.

------------------
System Information
------------------
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: OptiPlex GX280
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz
Memory: 502MB RAM
Page File: 351MB used, 872MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

Scott Vibert · 06-09-2005, 02:50 PM

The first thing I would try is a fresh download of the install. Make sure you clean out your temp files first. Also make sure you aren't running anything else in the background during the install.

chredwdew · 06-09-2005, 04:53 PM

Thanks for the Idea. It did not work, but seemed reasonable as I always had somthing running when I installed before.

chredwdew · 06-10-2005, 10:21 AM

Ok, I am very determined to get this to work. I have done some more research on this and found out about the event viewer.
Hopefully this will shed a little more light on the problem for someone that understands computers better than I do.

System log of the error

Item Name Value

Company Name Microsoft Corp
Date 6/10/2005
Event ID 26
File Name ntdll.dll
file version 5.1.2600.2180
Product name microsoft windows corp
product version 5.1.2600.2180
source application popup

Thanks.

chredwdew · 06-15-2005, 02:06 PM

Well with 6.5 out I am even more anxious to get this working.

If no one has a solution for this. Maybe I could get someone that knows computers better than I do to possibly explain what I am looking at. Then I can do some research on my own.

Thanks.

Treches · 06-15-2005, 03:32 PM

Seems that the file at fault is ntdll.dll, which I think is a quite important Windows .dll. I read a while ago that this one was pretty vulnerable to trojan, virus and all that crap, and the way of knowing if it was damaged was checking its location (if it's in the Windows folder, then is OK --so they said).

I'm pretty much outdated in these regards, so I may very well be way off, but looks like the thing here is the machine is failing to get the game to popup after the install. Here's a longshot: try executing ootp's exe instead of clicking on the icon.

ChinMusic · 06-15-2005, 10:50 PM

I did a quick search for your initial error 'failed to initialize properly (0Xc0000005)' thru microsoft. All of the instance I found seem to indicate that the application can't start b/c the .exe or one of its dependent .dlls is corrupt or can't be loaded for some reason. ntdll.dll is a major OS file and your machine could be in a bad state if that is corrupt. Most likely, that file is fine (unless you have a virus) and a different file is causing the problem.

A couple things that you could try:

- run windows update and make sure you have the latest patches

- run an antivirus scan on your machine just to make sure you haven't caught something. if needed, you can find some freeware AV apps on the web that should be good enough.

- since you are running SP2 and getting the error on install, I'm wondering if the windows firewall is blocking your elicense connection. I know that I had to temorarily open some holes in my FW to get v6.5 to register. If the app doesn't handle this situation you may get the error you are seeing.

- this is a real longshot but you MAY be able to figure out which file is causing the problem by running depends.exe against ootp.exe. This is a freeware tool that will pretty much tell you what dlls are being loaded and from where. It should also identify any dlls that can't be loaded. I think that the v6.12 download is a self-extracting exe. You would have to get past that part first. Depends.exe needs to be run against ootp6.exe.

I hope that one of these helps.

chredwdew · 06-16-2005, 08:55 AM

Thank you both for your insight and help.
I am sure that a complete reinstall of windows would fix this problem. Unfortunatly this is a work computer, and while I do have admin rights I don't think reinstalling xp will be an option.
I am going to do some research and try a few things along the line of your suggestions.
As far as the windows firewall blocking the e license connection that could be somthing I have not looked into. While the xp firewall is not active the complany does have another running.
Also if it does turn out tho be a corrucpt dll file is there any way to replace any of these without the complete os install.
Once again thank you for all of your help and I will post and update of the situation after I give some of your ideas try.

ChinMusic · 06-16-2005, 12:36 PM

System restore may be an option if the ntdll.dll is really corrupt. I've never used it and usually keep it turned off to free the disk space. I doubt that is your problem though. You would probably have a lot of programs crashing if ntdll.dll were corrupt.

For comparison, my work PC is running the same version of XP SP2. Here are the stats for my ntdll.dll:

Size: 708,096
Ver: 5.1.2600.2180
Created: 7/24/2003 1:22 pm

chredwdew · 06-16-2005, 12:49 PM

I had a chance to try out a couple of your ideas. I tried the icon in the program folders to start with as that would be an easy fix.... no dice. Then I tried turning off the firewall that was installed I had to go thru msconfig to get it to turn off. still no help then to make sure I unplugged the network connection and tried again and that did not work.
I am going to give the depends.exe a try. I may have to repost here with the results as I will probably have no I dea what the mean.

Here are the specs for my ntdll

Size: 708,096
Ver: 5.1.2600.2180
Created: Wednesday, August 04, 2004, 7:00:00 AM
only diffrence seems to be the day it was created.

Thanks again

chredwdew · 06-16-2005, 01:06 PM

ok I ran the depends.exe and while it makes some sense to me most of it is way beyond my computer knowledge. So I am hoping for a little more help. attached is a screenshot of depends.exe. To me it looks like the mrp.dll is the problem and is holding up the ntdll, but that just my uneducated guess.

Treches · 06-16-2005, 02:02 PM

Quote:

Originally Posted by chredwdew

I tried the icon in the program folders to start with as that would be an easy fix.... no dice.

Nope, the thing was trying this: Start>Run>search for ootp65.exe>enter

chredwdew · 06-17-2005, 08:36 AM

Quote:

Originally Posted by Treches

Nope, the thing was trying this: Start>Run>search for ootp65.exe>enter

I gave this a try but got the same error message as usual. Thanks for the Idea though.

I think I might be on to something with the depends.exe ... I actually recognize and error message in there but I have no idea what to do with it. Anyone that could decode that into English I would appreciate it.

Thanks again

ChinMusic · 06-17-2005, 01:01 PM

The mpr.dll notice is pretty standard. I'm not sure why but I see that notification on almost every app I look at. It is not your problem. Good guess though. That one just happens to be the exception to the rule. Your ntdll.dll looks good to so you can rule that out.

Basically, if you are seeing nothing else highlighted in depends, it is telling you that all of you statically linked dlls are being found and loaded correctly. DLLs can also be dynamically loaded. To check that, you would have to use the profiling feature of depends. You are really starting to get into windows now.

Are you positive that your FW is off? What brand is it? Most third party FWs run as services (sometimes multiple) and have one or more device drivers installed. A lot of time, you don't even have to stop the services. The FW UIs usually have a permit/allow all mode that effectively makes the FW a passthru. Also, most FWs have a log that should show you what, if any, traffic is being blocked.

chredwdew · 06-17-2005, 01:58 PM

Quote:

Originally Posted by ChinMusic

Are you positive that your FW is off? What brand is it? Most third party FWs run as services (sometimes multiple) and have one or more device drivers installed. A lot of time, you don't even have to stop the services. The FW UIs usually have a permit/allow all mode that effectively makes the FW a passthru. Also, most FWs have a log that should show you what, if any, traffic is being blocked.

The more I look into this I am not even shure that my computer has a firewall installed. I connect through a network and the only thing that seems to be installed is a mcafee suite. that I have no access to (this is what I turned off earlier.)
If you are willing to give it a look I am attaching the text file from the depends.exe that I got from the prolfiling.

Once again I appreciate all of your help on this.

ChinMusic · 06-17-2005, 11:07 PM

Saw the following line in the log that you posted:

00:00:00.313: First chance exception 0xC0000005 (Access Violation) occurred in "d:\program files\out of the park developments\ootp 6\ELICEN40.DLL" at address 0x02481000 by thread 1.

Definitely a problem with elicense but I can't really tell you much more than that. Later in the log, you will see a similar message for ntdll.dll. That is probably the result of the eLicense error. My best guess is that eLicense threw an exception that was caught. While the exception is being processed, a second exception in ntdll.dll was thrown. This one was not caught and that is the crash that you are seeing.

I can also tell you that the exception in the ntdll.dll occurred in the RtlRaiseStatus API (from the addr 0x7C964ED1 in the log). This seems to support the exception within an exception theory.

Unfortunately, I can't tell you much about why eLicense is failing. You might be able to gleam some more tidbits of info by enabling failure audits thru Administrative Tools | Local Policy but that is a crap shoot. It all depends on what is causing the exception.

The best advice I can offer is probably to look at the eLicense threads on this board. Maybe something in there will lead down the right path. My gut tells me that it is something in the Mcafee suite - FW, AV scanner, etc. Also, if you are doing this at work, the corp FW could be causing problems. Did you install v6.0 under the same conditions? Did it have any eLicense problems? It does look like the eLicen40.dll was updated between v6.0 and v6.5. You could try copying the v6 version to the v6.5 folder (save the original) and then running. I'm not sure if that will work but maybe. I'm grasping at straws here.

chredwdew · 06-20-2005, 03:15 PM

Thanks I really appreciate you taking time to look over all of this and help me out.

I am going to try a feww things here to see if I can get around the firewall. Maybe email eliscens to see if they would have a solution. I will let you know how it works out.

Also I was wondering if the problem would be resolved by ordering a copy of OOTP on disk? Just a thought of another out if none of this works.

Thanks again.

chredwdew · 06-24-2005, 01:11 PM

Success

I had another new program at work encounter a similar Dll problem. The IT department was as baffled as I was and tried a couple of things with no luck. Eventually they just wiped the machine clean and started over.

So my advice to anyone that gets a 0X00 error is that it involves dll's and you might as well just save everything important and just reinstall windows.

Thanks again for all of the help, it was much appreciated.

06-09-2005, 02:24 PM	#1
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Application error for the experts I am having problems installing V6.12 on my new computer. This computer is only a month or so old. I would appreciate any help you could give me, as I am really starting to fall behind in my online league. Here is the following error. The Application has failed to initialize properly (0Xc0000005) click on ok to terminate. Hope someone will be able to help.

06-15-2005, 03:32 PM	#7
Treches Hall Of Famer Join Date: Dec 2001 Location: Damned Hell Posts: 2,150	Seems that the file at fault is ntdll.dll, which I think is a quite important Windows .dll. I read a while ago that this one was pretty vulnerable to trojan, virus and all that crap, and the way of knowing if it was damaged was checking its location (if it's in the Windows folder, then is OK --so they said). I'm pretty much outdated in these regards, so I may very well be way off, but looks like the thing here is the machine is failing to get the game to popup after the install. Here's a longshot: try executing ootp's exe instead of clicking on the icon. __________________ The Computer Baseball League

06-16-2005, 01:06 PM	#12
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	ok I ran the depends.exe and while it makes some sense to me most of it is way beyond my computer knowledge. So I am hoping for a little more help. attached is a screenshot of depends.exe. To me it looks like the mrp.dll is the problem and is holding up the ntdll, but that just my uneducated guess. Attached Images

06-09-2005, 02:29 PM	#2
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Forgot to post my system specs. ------------------ System Information ------------------ Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519) Language: English (Regional Setting: English) System Manufacturer: Dell Inc. System Model: OptiPlex GX280 BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03 Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz Memory: 502MB RAM Page File: 351MB used, 872MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.2180 32bit Unicode

06-09-2005, 02:50 PM	#3
Scott Vibert Hall Of Famer Join Date: Dec 2001 Location: My Computer Posts: 8,264	The first thing I would try is a fresh download of the install. Make sure you clean out your temp files first. Also make sure you aren't running anything else in the background during the install.

06-09-2005, 04:53 PM	#4
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Thanks for the Idea. It did not work, but seemed reasonable as I always had somthing running when I installed before.

06-10-2005, 10:21 AM	#5
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Ok, I am very determined to get this to work. I have done some more research on this and found out about the event viewer. Hopefully this will shed a little more light on the problem for someone that understands computers better than I do. System log of the error Item Name Value Company Name Microsoft Corp Date 6/10/2005 Event ID 26 File Name ntdll.dll file version 5.1.2600.2180 Product name microsoft windows corp product version 5.1.2600.2180 source application popup Thanks.

06-15-2005, 02:06 PM	#6
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Well with 6.5 out I am even more anxious to get this working. If no one has a solution for this. Maybe I could get someone that knows computers better than I do to possibly explain what I am looking at. Then I can do some research on my own. Thanks.

06-15-2005, 10:50 PM	#8
ChinMusic Minors (Rookie Ball) Join Date: May 2004 Location: Columbus, Ohio Posts: 27	I did a quick search for your initial error 'failed to initialize properly (0Xc0000005)' thru microsoft. All of the instance I found seem to indicate that the application can't start b/c the .exe or one of its dependent .dlls is corrupt or can't be loaded for some reason. ntdll.dll is a major OS file and your machine could be in a bad state if that is corrupt. Most likely, that file is fine (unless you have a virus) and a different file is causing the problem. A couple things that you could try: - run windows update and make sure you have the latest patches - run an antivirus scan on your machine just to make sure you haven't caught something. if needed, you can find some freeware AV apps on the web that should be good enough. - since you are running SP2 and getting the error on install, I'm wondering if the windows firewall is blocking your elicense connection. I know that I had to temorarily open some holes in my FW to get v6.5 to register. If the app doesn't handle this situation you may get the error you are seeing. - this is a real longshot but you MAY be able to figure out which file is causing the problem by running depends.exe against ootp.exe. This is a freeware tool that will pretty much tell you what dlls are being loaded and from where. It should also identify any dlls that can't be loaded. I think that the v6.12 download is a self-extracting exe. You would have to get past that part first. Depends.exe needs to be run against ootp6.exe. I hope that one of these helps.

06-16-2005, 08:55 AM	#9
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Thank you both for your insight and help. I am sure that a complete reinstall of windows would fix this problem. Unfortunatly this is a work computer, and while I do have admin rights I don't think reinstalling xp will be an option. I am going to do some research and try a few things along the line of your suggestions. As far as the windows firewall blocking the e license connection that could be somthing I have not looked into. While the xp firewall is not active the complany does have another running. Also if it does turn out tho be a corrucpt dll file is there any way to replace any of these without the complete os install. Once again thank you for all of your help and I will post and update of the situation after I give some of your ideas try.

06-16-2005, 12:36 PM	#10
ChinMusic Minors (Rookie Ball) Join Date: May 2004 Location: Columbus, Ohio Posts: 27	System restore may be an option if the ntdll.dll is really corrupt. I've never used it and usually keep it turned off to free the disk space. I doubt that is your problem though. You would probably have a lot of programs crashing if ntdll.dll were corrupt. For comparison, my work PC is running the same version of XP SP2. Here are the stats for my ntdll.dll: Size: 708,096 Ver: 5.1.2600.2180 Created: 7/24/2003 1:22 pm

06-16-2005, 12:49 PM	#11
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	I had a chance to try out a couple of your ideas. I tried the icon in the program folders to start with as that would be an easy fix.... no dice. Then I tried turning off the firewall that was installed I had to go thru msconfig to get it to turn off. still no help then to make sure I unplugged the network connection and tried again and that did not work. I am going to give the depends.exe a try. I may have to repost here with the results as I will probably have no I dea what the mean. Here are the specs for my ntdll Size: 708,096 Ver: 5.1.2600.2180 Created: Wednesday, August 04, 2004, 7:00:00 AM only diffrence seems to be the day it was created. Thanks again

06-17-2005, 01:01 PM	#15
ChinMusic Minors (Rookie Ball) Join Date: May 2004 Location: Columbus, Ohio Posts: 27	The mpr.dll notice is pretty standard. I'm not sure why but I see that notification on almost every app I look at. It is not your problem. Good guess though. That one just happens to be the exception to the rule. Your ntdll.dll looks good to so you can rule that out. Basically, if you are seeing nothing else highlighted in depends, it is telling you that all of you statically linked dlls are being found and loaded correctly. DLLs can also be dynamically loaded. To check that, you would have to use the profiling feature of depends. You are really starting to get into windows now. Are you positive that your FW is off? What brand is it? Most third party FWs run as services (sometimes multiple) and have one or more device drivers installed. A lot of time, you don't even have to stop the services. The FW UIs usually have a permit/allow all mode that effectively makes the FW a passthru. Also, most FWs have a log that should show you what, if any, traffic is being blocked.

06-17-2005, 11:07 PM	#17
ChinMusic Minors (Rookie Ball) Join Date: May 2004 Location: Columbus, Ohio Posts: 27	Saw the following line in the log that you posted: 00:00:00.313: First chance exception 0xC0000005 (Access Violation) occurred in "d:\program files\out of the park developments\ootp 6\ELICEN40.DLL" at address 0x02481000 by thread 1. Definitely a problem with elicense but I can't really tell you much more than that. Later in the log, you will see a similar message for ntdll.dll. That is probably the result of the eLicense error. My best guess is that eLicense threw an exception that was caught. While the exception is being processed, a second exception in ntdll.dll was thrown. This one was not caught and that is the crash that you are seeing. I can also tell you that the exception in the ntdll.dll occurred in the RtlRaiseStatus API (from the addr 0x7C964ED1 in the log). This seems to support the exception within an exception theory. Unfortunately, I can't tell you much about why eLicense is failing. You might be able to gleam some more tidbits of info by enabling failure audits thru Administrative Tools \| Local Policy but that is a crap shoot. It all depends on what is causing the exception. The best advice I can offer is probably to look at the eLicense threads on this board. Maybe something in there will lead down the right path. My gut tells me that it is something in the Mcafee suite - FW, AV scanner, etc. Also, if you are doing this at work, the corp FW could be causing problems. Did you install v6.0 under the same conditions? Did it have any eLicense problems? It does look like the eLicen40.dll was updated between v6.0 and v6.5. You could try copying the v6 version to the v6.5 folder (save the original) and then running. I'm not sure if that will work but maybe. I'm grasping at straws here.

06-20-2005, 03:15 PM	#18
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Thanks I really appreciate you taking time to look over all of this and help me out. I am going to try a feww things here to see if I can get around the firewall. Maybe email eliscens to see if they would have a solution. I will let you know how it works out. Also I was wondering if the problem would be resolved by ordering a copy of OOTP on disk? Just a thought of another out if none of this works. Thanks again.

06-24-2005, 01:11 PM	#19
chredwdew Minors (Triple A) Join Date: Mar 2002 Posts: 273	Success I had another new program at work encounter a similar Dll problem. The IT department was as baffled as I was and tried a couple of things with no luck. Eventually they just wiped the machine clean and started over. So my advice to anyone that gets a 0X00 error is that it involves dll's and you might as well just save everything important and just reinstall windows. Thanks again for all of the help, it was much appreciated.