PDA

View Full Version : Desperate for help with a Type VII-B CTD



OneTinSoldier77
04-18-2005, 12:42 PM
Hello,

I have posted about a problem I had with a CTD(Crash to Desktop) when using the Type VII-B Sub. Well, I didn't really ask for help because I thought perhaps my 'Career' files were corrupt. Well, I deleted them and started a new career. But now I have run into the same problem!

Anyway, I just got the Type VII-B in my new career(after my sixth patrol). I go out on patrol. I'm using Time Compression and come across and enemy ship. Then I get near an enemy ship(not an aircraft this time) and get a pop-up with three choices...

-Engage Target

-Maintain current orders

-Dive to Periscope depth

I choose 'Engage Target', and then the game CTD's!

Does anyone have a clue as to what the problem might be?

Arrghhh,

One Tin Soldier

OneTinSoldier77
04-18-2005, 12:42 PM
Hello,

I have posted about a problem I had with a CTD(Crash to Desktop) when using the Type VII-B Sub. Well, I didn't really ask for help because I thought perhaps my 'Career' files were corrupt. Well, I deleted them and started a new career. But now I have run into the same problem!

Anyway, I just got the Type VII-B in my new career(after my sixth patrol). I go out on patrol. I'm using Time Compression and come across and enemy ship. Then I get near an enemy ship(not an aircraft this time) and get a pop-up with three choices...

-Engage Target

-Maintain current orders

-Dive to Periscope depth

I choose 'Engage Target', and then the game CTD's!

Does anyone have a clue as to what the problem might be?

Arrghhh,

One Tin Soldier

OneTinSoldier77
04-18-2005, 03:15 PM
Ok, for what's it's worth I have more information. The following is reproducible. It causes a CTD every time.

I load up my career using the latest save(In base before mission). I start the mission. I go to the 'Crew Management' screen. On the Bridge there is a slot available for the 'Flak Gunner' position, and it's currently empty. Also on the Bridge there are three slots available for the 'Deck Casing' position, which are also empty. Any attempt to put a crew memeber into any of these empty slots results in a CTD.

Help me Ubi-Wan forums, you're my only hope.

jasaund7089
04-18-2005, 04:08 PM
corrupted save maybe? Have you been backing up your save folder? If so maybe try to restore your save folder(only if you backed it up). Try loading a game before your last docking ,in base after mission

OneTinSoldier77
04-18-2005, 04:24 PM
Hi jasaund,

Thanks for trying to help me out. I was sure hoping someone would try and help me soon! I am desperate folks! PLEASE!!

------------------------------

jasaund, I just did the following before I even saw your reply here. I loaded up the latest 'in base after mission' save. Then I gave out the medal and the ability. Then I purchased the Type VIIB. Then I went to the barracks and bought the proper amount of crew. THEN I put a guy in the Flak Gun and three guys in the Deck Casing(Deck Gun). No CTD. I thought cool! Maybe this will work out now. But nope. As soon as I started the mission it CTD. http://forums.ubi.com/images/smilies/16x16_smiley-sad.gif

I am starting to get a little bummed out. I have only had the game installed several days. I may try completely uninstalling and then re-installing the game and see what happens then. I don't think there should be anything wrong with my current installation but perhaps there is. I do not see anyone else talking about the problem I am having.

Cheers,

One Tin Soldier

mike_w72
04-18-2005, 04:54 PM
Are you using your grammaphone?

I had CTD's when I chose one of those options until I did two things:
1. updated my sound card drivers
2. stopped using grammaphone

After installing the drivers, I still had some CTD's. After I stopped using the grammaphone, I have had none (knocks on wood...)

panthercules
04-18-2005, 07:42 PM
never seen this behavior - been using a type VIIB the whole game though (maybe only happens on upgrading?)

only CTD problem I've had was the well-known intermittent "surface cruise CTD" button in the crew management screen - I just stopped using that button (actually those buttons - occasionally got CTDs on other buttons though the surface cruise one was the worst offender) and haven't had another CTD since - interesting how your CTD problem seems to be crew-management-related as well - sounds like maybe the devs have some more work to do in this area for the next patch

OneTinSoldier77
04-18-2005, 11:18 PM
Hello,

mike, I am not using the grammaphone. So that isn't it. Thanks tho.

panthercules,

I was tending to think the same thing you are and that the problem is the Crew Manangement Screen. I have been posting about this problem in the 'SH3 Unofficial BugList Collection Thread/List' because of that line of thought. But of course I am not absolutely certain if that is where the trouble lies or not as far as me being able to drive a Type VIIB. I am wondering why no one else is reporting about having this problem. BUT, I do know there are indeed crash problems in the Crew Management screen!! My real problem now is what do I do?? I really want to drive the Type VIIB in my career in a bad way! http://forums.ubi.com/images/smilies/cry.gif

Thank you guys for your input.

Cheerio,

One Tin Soldier

Kuniworth
04-19-2005, 12:14 AM
You got porn virus on computer? http://forums.ubi.com/groupee_common/emoticons/icon_confused.gif

OneTinSoldier77
04-19-2005, 02:03 AM
Lol, nope. Or at least I hope not. I have never visited a pron... err, porn site. I use Mozilla Firefox 1.0.2 and I use Norton Internet Security 2005. That doesn't rule out the possibily of Spyware/Malware or a Virus 100% completely beyond the shadow of a doubt. But I REALLY don't think that is the problem here.

Cess-SGTRoc
04-19-2005, 03:32 AM
Try disabling Norton and see what happens, it would not be the first time Norton has caused something like this to happen.
Also see what is running in your task bar, and try to disable them and then load the game and see what is up.
It is a driver conflict or a progam one by what it looks like.
Also go and get the latest driver upgrades for you Video and sound and anything else you have and see if that will help also.

OneTinSoldier77
04-19-2005, 05:03 AM
Hello,

Thanks for the reply Cess. I am not new to configuring my system for performance. But I do leave my Norton's running. I have never had a problem with installing or running any other game by leaving it enabled.

I do not claim to know everything about computers. Not by a long shot. But I am not totally naive about computer systems either. I am a Sair/GNU LCP... Linux Certified Professional. And I am the author of a guide titled 'FS2004 and WinXP Optimization Guide'. It is a thread that is a sticky in the Avsim forums and has about 27,000 hits. It concerns optmizing your BIOS and Windows XP(obviously) for better gaming performance. And, again obviously, some tweaking for MS Flight Simulator 2004. I hope by now it is obvious that I know about keeping drivers up to date.

Now, I did read a post in the Subsim forum by a fellow that was having some CTD issues with the 'Crew Management' screen and solved them by completely uninstalling/wiping the game from his systtem(expect for his saved career files) and then uninstalled his McAfee Anti-Virus. Then installed the game and now his CTD's are gone.

I am not about to 'uninstall' my Nortons just to install this game, as great of a game as it is. Yes, I could, but I should not have to go to such great lengths nor am I going to. That involves reboot to uninstall, rebbot after reinstalling, reboot after updating, rebooting again after another update. Then comes configuring and customizing the whole thing. That is not something that should be a requirement to get this game to install properly, period.

However, I had already been consdiering wiping the game from my system and starting over. Therefore, I went ahead and uninstalled it(including my saved profile/career) and wiped the folder, disabled Norton's Personal Firewall, disabled Norton Anti-Virus Auto-Protect, and then installed the game. Of course this means that the processes were still resident in memory, but disabling them for installing the game is as far as I am willing to go. Again, I've never had a problem with any other 'game' before. It is absolutely the norm for even an average user to have some Anti-Virus software installed on their system.

I am going to use one mod, Jase and Nico's Campaign Spawn Bug Fix 1.1. It consists of four files that I backed up before installing it. Only four files is very easy to keep track of as far as restoring the originals prior to updating with Patch v1.3. Assuming there will be a v1.3 Patch.

After all this said, I do want you to know that I thank you for your input Cess.

Cheerio,

One Tin Soldier

Johan217
04-19-2005, 07:02 AM
See also to this thread: http://www.subsim.com/phpBB/viewtopic.php?t=33585

It's not clear what exactly causes the ctd's, but the problem appears to be related to file corruption.

Possible fixes:
- Do not overwrite existing savegames --> this worked for me
- Turn off all programs that run in the background (including antivirus) --> worked for others

Both require that you first reinstall SH3 (full reinstall, do not use the 'repair' function).

The CTD-problem in crew management was reported to Ubi Support some time ago but there is no solid explanation for it yet.

Hope this helps.

OneTinSoldier77
04-19-2005, 08:46 AM
Hello Johan217,

Tbanks for trying to give some input with your reply. First, I'll let you know that I do not overwrite existing saves. Although if that is a problem then it is a bug that should be fixed.

I apologize in advance for the rant I am about to give. It is not really aimed at you Johan. I am kind of trying to make it clear that even though I am not some Know-It-All about computers I am not some Johnny Come Lately either. I have been a TPF Operator(Transaction Processing Facility). It's an IBM Mainframe OS. Altough I have never been a developer I have see a lot of stuff in my day. A lot of weird things on computer systems. I am a Sair/GNU LCP and ran a beta version of the GNU/Debian Linux OS for a long time. I have also worked as a Beta Tester before. I am pretty familiar with Windows XP. Read my previous post about writing an 'Optimization Guide' for it. Believe me, I do not have all kinds of stuff running in the background. You can bet your bottom dollar that I do have my Anti-Virus and Firewall software running though. My system handles running it along with a very resource intensive game called Flight Simulator 2004. I also run a BF1942 mod called Forgotten Hope at 1600x1200 resolution with 4x AA and 16 AF and play online all day long while on Teamspeak with no problem whatsoever(the same for FS2004).

As I said in my previous post I read a thread over at Subsim. I had been considering uninstalling and reinstalling the game.

-------------------------------

Posted by Capt. Perez:

I had exactly the same problem. CTD when manning deck gun or flak.

The answer is a clean reinstall.

SH3 manages a lot of CFG and DAT files and updates these constantly. The observation in a previous post that the CTD problem was due to a bad saved game may not be far from the truth - but I don't think that is the root cause.

After the frustration of trying virtually everything to troubleshoot this CTD problem, I finally concluded that one of the DLLs or some DAT file was fractured and reinstalled. Note: "reinstalling to repair" the original installation does not work. Sorry if the next bit sounds obvious, but please don't laugh - some people might find it useful. You need to:

1) Back up what you care to out of the original folders (MP3s, etc.)
2) Uninstall using "Add/Remove Programs" in Control Panel. You will be prompted to keep user saves - best to do so unless you want to start over. Saved games are in "My Documents," not in the game folders. I went there first and created copies, although this was not needed.
3) After this completes, go in and erase any vestigial remains - folders and files left behind.
4) Reinstall from scratch and immediately run patches 1.1 and 1.2.
5) Put in the mods you want.

Your career should load and work fine. I added the full vulnerability mod, crush depth mod, new interior textures (a real biggie), Neal's grammo tunes, got rid of in-game music, and added the crew uniform mods. All of these work fine. I tested functionality after each and every mod to see if I could trace the source of the problem - the mods are not it! I really did try to pin it on the crush depth mod, but it works and works very well. THANK YOU, CONTRIBUTORS, and a special thanks to Timetraveller!

Since the reinstall everything has gone "swimmingly."

The ONE CHANGE I DID MAKE -

I got rid of McAfee and made sure no other memory-resident junk was running.

Now, there's no guarantee that it will hold up of course, but my opinion is that SH3 is vulnerable to memory-resident software, particularly intrusive stuff like antivirus. If you save a game when the AV hiccups, who knows what happens? One thing's for sure - the SH3 Dev Team did not create this game on systems running a whole bunch of background ****. It probably should not be played that way, either.


-------------------------------

Also as I said, I have went ahead and wiped the game and reinstalled. I however did not uninstall my AV software to install this game. Some of what Capt. Perez is good and although I do not know everyting about computers and some of what he says is an unknown to me, I think some of it leans a little towards being hogwash. That is not really a stab at him, it's just that some of it is obviously something that is 'unknown' to him too. Maybe I am being to harsh, he even says it's his 'opinion'. So I apologize.

Memory Management is controlled by the Operating System! Ok, that may not be 100% entirely true, as I have seen messages in Norton logs about TaskInfo(a more advanced Task Manager with many functions) being denied access. But, if I'm not mistaken that is one program trying to access the memory of another. And a program denying access to an unknow intruder is certainly plausible and I can see how the OS would allow a program to deny access to another as long as that progam does not need it. Make sense? There is no reason that SHIII needs access to the memory of running processes such as my Anti-Virus program. WinXP should be able to handle any Memory Mangement needs of SHIII as long as I have enough available memory for it. It has no need to be running over the memory allocated to other programs. But more importantly, my Nortons Anti-Virus has never caused me problems with any other games. It does not go around hosing up the memory allocation of my other games or programs. I have been using Norton's ever since Norton's v3.0. That was a very long time ago in Win98. I am currently using Nortons 2005. I'm not trying to say Nortons has not ever been known to cause problems, but ever since Norton 2004 I have never personally encountered any problems. And both Nortons and Mcafee come pre-installed on many pre-configured systems these days. Think about that a little. If there are 'known' incompatiblities with other software then we as end users need to hear about it. I am not going to go on some guesswork when it come to my Anti-Virus program. I will not be uninstalling my Nortons. I cannot stress this enough, Nortons 2005 does not cause me any problems with any other piece of software/game that I have. And I have a LOT of stuff!!

As I have said, it is compltely normal for even the average user to have Anti-Virus software installed on their system. I do not expect the Devs to have tested the game with every computer configuration possible, but c'mon... Anti-Virus software is pretty much a must have these days! And many times that is Nortons or Mcafee's. If this game has problems with Anti-Virus software then the Devs need to come out and state that fact. No bones about it!

Corruption of files does occur unless the progam itself corrupts them!(more on this later) That would mean there is a bug in SHIII causing file corruption. The only other time there could be corrupted files is if the system does not shutdown cleanly(i.e. a sudden power outage). But WinXP is somewhat capable of hadling even this with it's Journaling filesystem. And I have not had any power outage or unclean shutdowns. I run a chkdsk(command prompt) and there is nothing wrong. I am not having any filesystem problems or problems with any other of my software. It is rare with WinXP, but it possible for a file to become corrupt even without the program itself causing it and/or even if you do not have an 'unclean' shutdown. But from my experience that is quite rare indeed, not a regular occurence.

Now, I once had(still have actually) an FS2004 addon program called WeatherCenter. It was acting buggy. I posted about it in the developers forum. He said he could not reproduce it. Hooey I thought, the bug is obviously there. After other people started posting about the problem he seemed to find that his program was corrupting it's own config(.cfg) file! I felt perhaps a little miffed that he did not take my word for it and others had to start complaining about it for him to look into the problem. But oh well. I'll bet at one time or another we've all just wished that someone else would just 'listen' us and not give us what seems like a brush-off.

I used to work for a company named iBeta doing beta testing. I can usually spot a bug when I see one.

My point here is that SHIII has bugs!!! Obviously. They need to be fixed. I'm not trying to say I demand something that is 100% perfect. I can live with some minor bugs. What I am saying is that I want to be able to use the software the way it was intended to be used. I find it hard to live with CTD type of bugs. I want to drive a Type VIIB in the Career Campaign for crying out loud! Lol.

To sum it up. I have been around computers quite a while. Blaming the problems on a well known and very prolific piece of Anti-Virus software to me is confounding and hogwash. I'm not ruling it out completley though but if there is a problem then the testing of this software in that regard was either non-existant or pathetic, because Nortons and Mcafee come already installed on a lot of pre-configured systems these days and are among the most well known pieces of Anti-Virus software there is.

Sorry for the rant. The bottom line is probably that the only way my problem can be solved is for the Dev Team to fix the bugs in this game. Although I have reinstalled(completley clean and fresh) and am going to work on my career again and hope that the reinstall has solved my problem. But I hope folks can understand that at this point I have my doubts. But I will keep my fingers crossed.

I WANT TO DRIVE A TYPE VIIB!!

---------------------------
System Specs(system put together personally by myself):
Intel 3.4C(C = Northwood) on Asus P4C800-E Deluxe(Intel 875P + ICH5R Chipset), Zalman 7000a-Cu HS/Fan, Enermax RG651P-VE 550W PSU, 1 GB Muskin High Performance(2-2-2) PC3200 RAM, NEC MultiSync FE2111SB 21" Monitor, ATI(Sapphire) Radeon X800 XT PE Videocard with v5.4 Catalyst Drivers, DirectX 9.0c, Creative Audigy2 Soundcard, 250 GB w/8 MB Cache Western Digital HDD, WinXP Pro SP2

BigDaddySauce
04-19-2005, 10:31 AM
Anything in event viewer?

OneTinSoldier77
04-19-2005, 11:14 AM
Hello BigDaddySauce,

While I suppose that is a good question, I have never found error messages in the event viewer to be of much help to us end users. A long time ago there was a good hint or two at some problems I was having. But overall, the Event Viewer isn't really much help.

All it shows for this is...

Faulting application sh3.exe, version 1.2.0.1, faulting module sh3.exe, version 1.2.0.1, fault address 0x000d4980.

Now, to a developer, that address in the .exe might be helpful. But I think they would probably want the entire crash dump. If some dev came along and said, "Hey, could you please reproduce that and send me the crash dump?" Then I would do my best to get it to them. But since nothing like that ever really seems to happen(lol) I just have crash dumps turned off in the Dr. Watson options(drwtsn32.exe).

However, I do have logging enabled in Dr. Watson. But looking at that is about as much fun as a crash dump for us non-dev's. But anyway, what the heck, here is the latter part of it, hehe.


*----> State Dump for Thread Id 0x8d0 <----*

eax=00000000 ebx=3c2c202e ecx=3aad32d8 edx=3bde1a90 esi=08f4b94c edi=3c282e10
eip=004d4980 esp=0012ece4 ebp=00393330 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200206

*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files\Ubisoft\SilentHunterIII\sh3.exe
function: sh3
004d496a 44 inc esp
004d496b 30fb xor bl,bh
004d496d 42 inc edx
004d496e ffd5 call ebp
004d4970 8b575c mov edx,[edi+0x5c]
004d4973 8b0a mov ecx,[edx]
004d4975 894154 mov [ecx+0x54],eax
004d4978 8b575c mov edx,[edi+0x5c]
004d497b 8b02 mov eax,[edx]
004d497d 8b4054 mov eax,[eax+0x54]
FAULT ->004d4980 8b4818 mov ecx,[eax+0x18] ds:0023:00000018=????????
004d4983 83c410 add esp,0x10
004d4986 41 inc ecx
004d4987 894818 mov [eax+0x18],ecx
004d498a 8bc6 mov eax,esi
004d498c 8d4801 lea ecx,[eax+0x1]
004d498f 90 nop
004d4990 8a10 mov dl,[eax]
004d4992 40 inc eax
004d4993 84d2 test dl,dl
004d4995 75f9 jnz sh3+0xd4990 (004d4990)

*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
ChildEBP RetAddr Args to Child
00393330 8b575608 851c247c 8b0275ff 640d8bfb sh3+0xd4980
245c8b53 00000000 00000000 00000000 00000000 0x8b575608

*----> Raw Stack Dump <----*
000000000012ece4 4c b9 f4 08 28 00 00 00 - 02 00 00 00 00 00 00 00 L...(...........
000000000012ecf4 70 20 2c 3c 00 00 00 00 - 58 d4 8b 3b 10 84 2a 3c p ,<....X..;..*<
000000000012ed04 30 5b 4d 00 10 2e 28 3c - 4c b9 f4 08 02 00 00 00 0[M...(<L.......
000000000012ed14 74 5f f4 08 9c 36 54 00 - 00 00 00 00 00 00 00 00 t_...6T.........
000000000012ed24 80 e0 32 02 52 61 6e 6b - 44 65 63 6f 33 63 32 63 ..2.RankDeco3c2c
000000000012ed34 32 33 63 30 00 84 53 00 - 90 69 40 00 b8 43 f4 08 23c0..S..i@..C..
000000000012ed44 74 5f f4 08 14 ba f4 08 - e4 ba f4 08 c4 5a f4 08 t_...........Z..
000000000012ed54 4c b9 f4 08 af 00 00 00 - 38 49 31 02 05 00 00 00 L.......8I1.....
000000000012ed64 01 00 00 00 38 49 31 02 - 00 00 00 00 b9 6f 40 00 ....8I1......o@.
000000000012ed74 05 00 00 00 a8 34 54 00 - d8 3e b1 38 c7 84 53 00 .....4T..>.8..S.
000000000012ed84 01 00 00 00 44 8b 53 00 - 00 00 00 00 01 00 00 00 ....D.S.........
000000000012ed94 38 49 31 02 e0 61 38 1a - 40 59 34 00 00 00 00 00 8I1..a8.@Y4.....
000000000012eda4 e5 87 40 00 01 00 00 00 - b0 c5 00 10 50 98 22 02 ..@.........P.".
000000000012edb4 60 cf 44 00 06 61 0d 3e - 08 20 52 1a 38 49 31 02 `.D..a.>. R.8I1.
000000000012edc4 08 bf 59 1a 00 00 00 00 - 44 41 4d 00 08 20 52 1a ..Y.....DAM.. R.
000000000012edd4 f8 a3 4c 00 06 61 0d 3e - 06 61 0d 3e c0 83 01 10 ..L..a.>.a.>....
000000000012ede4 00 00 00 00 23 43 40 00 - 01 61 0d 3e 06 61 0d 3e ....#C@..a.>.a.>
000000000012edf4 38 49 31 02 18 ff 12 00 - 06 61 0d 3e 38 49 31 02 8I1......a.>8I1.
000000000012ee04 ee 8a 40 00 00 61 0d 3e - 07 00 00 00 06 61 0d 3e ..@..a.>.....a.>
000000000012ee14 00 10 00 10 b5 1d 40 00 - 06 61 0d 3e 01 00 00 00 ......@..a.>....

Cheers,

One Tin Soldier

Daxos1942
04-19-2005, 12:42 PM
Tin Soldier, the only advice that I can give is <b> do not use Norton. </b> I haven't used Norton in years but I remember that when I did, I used to have problems with many apps. I now use AVG, and have not had any problems with SHIII, or anything else. Also, SHIII is very systems hungry, particularly in high compression scenarios, so you may try backing off depending on what type of system you have. I have an Athlon64 3200+ here w/1GB of RAM, and as I said, it's running fine, except for the Nvidia CtrlP problem, with framerate slowdown if particles are on @ 100% in UZI, and to a lesser extent with binoculars and the magnified deck gun sight, depending on wave activity, good luck.

steve_v
04-19-2005, 12:49 PM
Open to a suggestion?

When I want to engage with the deck gun, I instruct the Watch Officer from the bridge for Crew on Deck. From the menu display, I click on man the deck gun icon. I then click the deck gun icon to order the attack options.
The Watch Officer always places the gunner petty officer on deck without CTD. I am wondering if your CTD is related to proceedure. Next chance I get to use the deck gun, I'll do a save first and try manually putting them there from the Crew Management screen. If I can reproduce the CTD, we can document the bug. If not, more frustration.

Daxos1942
04-19-2005, 01:20 PM
Also, steve_v is correct, if you click on "Engage Target" or otherwise order the WO to call up the deck gun or the flak gun crew, he also automatically calls up the unterofficier(s) who have deckgun/flak gun qualifications on deck, if you have any, and removes, except for himself, the watch crew. Then, when you tell him to call up the watch crew again, he removes the gun crew(s). Your problem maybe in trying to keep both at the same time?

OneTinSoldier77
04-19-2005, 01:57 PM
Ahhh, thanks guys. Especially steve_v. Yes, I am open to suggestions. And that is a suggestion that I should try out steve_v. Perhaps it will work me around the CTD! Interestingly enough, I have heard a number of people post that they have had CTD problems with the 'Crew Management' screen, especially when trying to use Cruise Surface Mode. But others have said that they have not had problems. There is a thread in the Subsim forums where a fellow was explaing a CTD problem in the 'Crew Management' screen. Antother fellow came along and said he had not really had any problems but he would have to try and do what the other fellow with the CTD problem was doing. He did it and he said, sure enough, he got a CTD. I think the fact that quite a few people have had problems though shows that something is going on with the Crew Management screen with respect to having bugs in it. I hope they can get them sorted out and release a patch that squashes the bugs in there.

Daxos1942, thanks for your input. You may very well be correct about attempting to keep both at the same time. I have always managed the crew manually. I assure you I will be trying out what steve_v and you have suggested. Just to let you know, I won't be getting rid of Nortons, because I like it. I have heard good things about AVG though. I have been using Nortons for years and the more I think about it, I have never really had any problem with it, although I am aware other folks have. To a degree it may be considered 'bloatware' but my system handles it just fine. Perhaps because I have optimized my system to the nines. I paid for Nortons, I like Nortons and I feel I can trust it, and I'll be keeping it. Thanks for the suggestion though.

It is only the Crew Management screen that I have had CTD problems with(I think). I think any CTD problem I have had is related to the Crew Management screen even if I was not in it. Otherwise the game seems quite stable.

It will be some time before I get far enough into my career to get the Type VIIB again(i've got plenty of other stuff I have to do this week) but I will come back and post about my experience with it when I get there.

Thanks Again Guys,

One Tin Soldier

Cess-SGTRoc
04-19-2005, 02:03 PM
Ok, go to DR.Watson and see if this is there still and copy and past it here, I will need it.

After you locate the fault, you can identify the program that crashed, the Process ID (PID), date, and time of the crash:
1. On the Search menu, click Find.
2. In the Find dialog box, app.
3. In the Direction area, click Up.
4. Click OK. The search results display the program, PID, time, and date of the crash.

If this data is still there I should be able to locate the cause of this CTD.

Shark....
04-19-2005, 03:28 PM
I always get CTDs when moving the crew around using the surface attack mode or surface cruise mode buttons. Only get them when I am doing these type of crew assignments.

OneTinSoldier77
04-19-2005, 03:35 PM
I don't doubt it Shark.

Cess-SGTRoc... here you go. For whatever it's worth, here's the whole thing.

Microsoft (R) DrWtsn32
Copyright (C) 1985-2001 Microsoft Corp. All rights reserved.



Application exception occurred:
App: C:\Program Files\Ubisoft\SilentHunterIII\sh3.exe (pid=3184)
When: 4/18/2005 @ 15:54:07.953
Exception number: c0000005 (access violation)

*----> System Information <----*
Computer Name: ONETINSOLDIER
User Name: Administrator
Terminal Session Id: 0
Number of Processors: 2
Processor Type: x86 Family 15 Model 2 Stepping 9
Windows Version: 5.1
Current Build: 2600
Service Pack: 2
Current Type: Multiprocessor Free
Registered Organization: Your Company Name
Registered Owner: Your User Name

*----> Task List <----*
0 System Process
4 System
628 smss.exe
684 csrss.exe
704 winlogon.exe
748 services.exe
768 lsass.exe
912 Ati2evxx.exe
940 svchost.exe
1036 svchost.exe
1156 svchost.exe
1204 svchost.exe
1328 Error 0xD0000022
1404 Error 0xD0000022
1844 Error 0xD0000022
1856 Error 0xD0000022
1876 Error 0xD0000022
2000 Error 0xD0000022
452 dllhost.exe
504 Error 0xD0000022
620 Error 0xD0000022
820 Error 0xD0000022
1104 wdfmgr.exe
1112 SDMCP.exe
436 wbload.exe
1668 Ati2evxx.exe
1724 Explorer.EXE
2128 point32.exe
2404 CTSysVol.exe
2440 CTHELPER.EXE
2480 Error 0xD0000022
2496 cli.exe
2524 jusched.exe
2532 ctfmon.exe
228 firefox.exe
3184 sh3.exe
1772 drwtsn32.exe
408 wmiprvse.exe

*----> Module List <----*
(0000000000320000 - 0000000000334000: C:\Program Files\Ubisoft\SilentHunterIII\INTRO.DLL
(0000000000340000 - 000000000034c000: C:\Program Files\Ubisoft\SilentHunterIII\MESSAGENET.DLL
(0000000000350000 - 0000000000357000: C:\Program Files\Ubisoft\SilentHunterIII\MISSIONENGINE.DLL
(0000000000360000 - 000000000038b000: C:\Program Files\Ubisoft\SilentHunterIII\SIMDATA.DLL
(0000000000390000 - 00000000003aa000: C:\Program Files\Ubisoft\SilentHunterIII\FILEMANAGER.DLL
(00000000003b0000 - 00000000003b7000: C:\Program Files\Ubisoft\SilentHunterIII\MOVIETEX.ACT
(00000000003c0000 - 00000000003c9000: C:\Program Files\Ubisoft\SilentHunterIII\property.dll
(00000000003d0000 - 00000000003e1000: C:\Program Files\Ubisoft\SilentHunterIII\UTILS.DLL
(00000000003f0000 - 00000000003f8000: C:\Program Files\Ubisoft\SilentHunterIII\DRAWLIB.DLL
(0000000000400000 - 0000000000620000: C:\Program Files\Ubisoft\SilentHunterIII\sh3.exe
(0000000000620000 - 00000000012c5000: C:\Program Files\Ubisoft\SilentHunterIII\SH3.DLL
(00000000012d0000 - 00000000012e4000: C:\Program Files\Ubisoft\SilentHunterIII\STATEMACHINE.DLL
(0000000001b00000 - 0000000001b07000: C:\Program Files\Ubisoft\SilentHunterIII\anim.act
(0000000001b10000 - 0000000001b17000: C:\Program Files\Ubisoft\SilentHunterIII\BezierWaypoint.act
(0000000001b20000 - 0000000001b35000: C:\Program Files\Ubisoft\SilentHunterIII\CameraBehavior.act
(0000000001b40000 - 0000000001b48000: C:\Program Files\Ubisoft\SilentHunterIII\CameraManager.act
(0000000001f40000 - 0000000001f50000: D:\WINDOWS\system32\ctagent.dll
(0000000002170000 - 000000000217b000: C:\Program Files\Ubisoft\SilentHunterIII\EffectManagers.act
(0000000002180000 - 00000000021a4000: C:\Program Files\Ubisoft\SilentHunterIII\EnvSim.act
(00000000021b0000 - 00000000021b8000: C:\Program Files\Ubisoft\SilentHunterIII\EventCamera.act
(00000000021c0000 - 00000000021c9000: C:\Program Files\Ubisoft\SilentHunterIII\LipsSync.act
(00000000021d0000 - 0000000002244000: C:\Program Files\Ubisoft\SilentHunterIII\Multiplayer.act
(0000000002250000 - 0000000002260000: C:\Program Files\Ubisoft\SilentHunterIII\Particles.act
(0000000002260000 - 0000000002284000: C:\Program Files\Ubisoft\SilentHunterIII\SH3Collisions.act
(0000000002290000 - 00000000022b4000: C:\Program Files\Ubisoft\SilentHunterIII\SH3Controllers.act
(00000000022c0000 - 00000000022d2000: C:\Program Files\Ubisoft\SilentHunterIII\SH3Sound.act
(00000000022f0000 - 00000000022fb000: C:\Program Files\Ubisoft\SilentHunterIII\StateMachineCtl.act
(0000000002410000 - 000000000245c000: C:\Program Files\Ubisoft\SilentHunterIII\SH3Sim.act
(0000000002460000 - 00000000024a9000: C:\Program Files\Ubisoft\SilentHunterIII\Sound.act
(000000000aaf0000 - 000000000ad34000: D:\WINDOWS\system32\wmvcore.dll
(000000000ad40000 - 000000000ad7b000: D:\WINDOWS\system32\WMASF.DLL
(0000000010000000 - 000000001007e000: C:\Program Files\Ubisoft\SilentHunterIII\KERNEL.DLL
(0000000020000000 - 00000000202c5000: D:\WINDOWS\system32\xpsp2res.dll
(0000000030000000 - 0000000030072000: C:\Program Files\Ubisoft\SilentHunterIII\binkw32.dll
(000000004fdd0000 - 000000004ff76000: D:\WINDOWS\system32\d3d9.dll
(000000005ad70000 - 000000005ada8000: D:\WINDOWS\system32\UXTHEME.DLL
(000000005d090000 - 000000005d127000: D:\WINDOWS\system32\COMCTL32.dll
(0000000061210000 - 000000006121f000: D:\Program Files\Microsoft Hardware\Mouse\POINT32.dll
(0000000061220000 - 0000000061232000: D:\Program Files\Microsoft Hardware\Mouse\MSH_ZWF.dll
(0000000066000000 - 000000006608e000: D:\Program Files\Stardock\Object Desktop\WindowBlinds\WBlind.dll
(0000000066600000 - 0000000066617000: D:\Program Files\Stardock\Object Desktop\WindowBlinds\wbhelp.dll
(000000006d990000 - 000000006d996000: D:\WINDOWS\system32\d3d8thk.dll
(0000000071aa0000 - 0000000071aa8000: D:\WINDOWS\system32\WS2HELP.dll
(0000000071ab0000 - 0000000071ac7000: D:\WINDOWS\system32\WS2_32.dll
(0000000071ad0000 - 0000000071ad9000: D:\WINDOWS\system32\WSOCK32.dll
(0000000072d10000 - 0000000072d18000: D:\WINDOWS\system32\msacm32.drv
(0000000072d20000 - 0000000072d29000: D:\WINDOWS\system32\wdmaud.drv
(00000000736b0000 - 00000000736b7000: D:\WINDOWS\system32\msdmo.dll
(0000000073760000 - 00000000737a9000: D:\WINDOWS\system32\DDRAW.dll
(0000000073940000 - 0000000073a10000: D:\WINDOWS\system32\D3DIM700.DLL
(0000000073b50000 - 0000000073b67000: D:\WINDOWS\system32\AVIFIL32.dll
(0000000073bc0000 - 0000000073bc6000: D:\WINDOWS\system32\DCIMAN32.dll
(0000000073ee0000 - 0000000073ee4000: D:\WINDOWS\system32\KsUser.dll
(0000000073f10000 - 0000000073f6c000: D:\WINDOWS\system32\DSOUND.dll
(0000000074720000 - 000000007476b000: D:\WINDOWS\system32\MSCTF.dll
(0000000075a70000 - 0000000075a91000: D:\WINDOWS\system32\MSVFW32.dll
(0000000076380000 - 0000000076385000: D:\WINDOWS\system32\msimg32.dll
(0000000076780000 - 0000000076789000: D:\WINDOWS\system32\shfolder.dll
(0000000076b40000 - 0000000076b6d000: D:\WINDOWS\system32\WINMM.dll
(0000000076c30000 - 0000000076c5e000: D:\WINDOWS\system32\WINTRUST.dll
(0000000076c90000 - 0000000076cb8000: D:\WINDOWS\system32\IMAGEHLP.dll
(0000000076fd0000 - 000000007704f000: D:\WINDOWS\system32\CLBCATQ.DLL
(0000000077050000 - 0000000077115000: D:\WINDOWS\system32\COMRes.dll
(0000000077120000 - 00000000771ac000: D:\WINDOWS\system32\OLEAUT32.dll
(00000000771b0000 - 0000000077256000: D:\WINDOWS\system32\WININET.dll
(00000000773d0000 - 00000000774d2000: D:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
(00000000774e0000 - 000000007761d000: D:\WINDOWS\system32\ole32.dll
(0000000077920000 - 0000000077a13000: D:\WINDOWS\system32\SETUPAPI.dll
(0000000077a80000 - 0000000077b14000: D:\WINDOWS\system32\CRYPT32.dll
(0000000077b20000 - 0000000077b32000: D:\WINDOWS\system32\MSASN1.dll
(0000000077b40000 - 0000000077b62000: D:\WINDOWS\system32\Apphelp.dll
(0000000077bd0000 - 0000000077bd7000: D:\WINDOWS\system32\midimap.dll
(0000000077be0000 - 0000000077bf5000: D:\WINDOWS\system32\MSACM32.dll
(0000000077c00000 - 0000000077c08000: D:\WINDOWS\system32\VERSION.dll
(0000000077c10000 - 0000000077c68000: D:\WINDOWS\system32\msvcrt.dll
(0000000077d40000 - 0000000077dd0000: D:\WINDOWS\system32\USER32.dll
(0000000077dd0000 - 0000000077e6b000: D:\WINDOWS\system32\ADVAPI32.dll
(0000000077e70000 - 0000000077f01000: D:\WINDOWS\system32\RPCRT4.dll
(0000000077f10000 - 0000000077f56000: D:\WINDOWS\system32\GDI32.dll
(0000000077f60000 - 0000000077fd6000: D:\WINDOWS\system32\SHLWAPI.dll
(0000000077fe0000 - 0000000077ff1000: D:\WINDOWS\system32\Secur32.dll
(000000007c340000 - 000000007c396000: C:\Program Files\Ubisoft\SilentHunterIII\MSVCR71.dll
(000000007c3a0000 - 000000007c41b000: C:\Program Files\Ubisoft\SilentHunterIII\MSVCP71.dll
(000000007c800000 - 000000007c8f4000: D:\WINDOWS\system32\kernel32.dll
(000000007c900000 - 000000007c9b0000: D:\WINDOWS\system32\ntdll.dll
(000000007c9c0000 - 000000007d1d4000: D:\WINDOWS\system32\SHELL32.dll

*----> State Dump for Thread Id 0x8d0 <----*

eax=00000000 ebx=3c2c202e ecx=3aad32d8 edx=3bde1a90 esi=08f4b94c edi=3c282e10
eip=004d4980 esp=0012ece4 ebp=00393330 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200206

*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files\Ubisoft\SilentHunterIII\sh3.exe
function: sh3
004d496a 44 inc esp
004d496b 30fb xor bl,bh
004d496d 42 inc edx
004d496e ffd5 call ebp
004d4970 8b575c mov edx,[edi+0x5c]
004d4973 8b0a mov ecx,[edx]
004d4975 894154 mov [ecx+0x54],eax
004d4978 8b575c mov edx,[edi+0x5c]
004d497b 8b02 mov eax,[edx]
004d497d 8b4054 mov eax,[eax+0x54]
FAULT ->004d4980 8b4818 mov ecx,[eax+0x18] ds:0023:00000018=????????
004d4983 83c410 add esp,0x10
004d4986 41 inc ecx
004d4987 894818 mov [eax+0x18],ecx
004d498a 8bc6 mov eax,esi
004d498c 8d4801 lea ecx,[eax+0x1]
004d498f 90 nop
004d4990 8a10 mov dl,[eax]
004d4992 40 inc eax
004d4993 84d2 test dl,dl
004d4995 75f9 jnz sh3+0xd4990 (004d4990)

*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
ChildEBP RetAddr Args to Child
00393330 8b575608 851c247c 8b0275ff 640d8bfb sh3+0xd4980
245c8b53 00000000 00000000 00000000 00000000 0x8b575608

*----> Raw Stack Dump <----*
000000000012ece4 4c b9 f4 08 28 00 00 00 - 02 00 00 00 00 00 00 00 L...(...........
000000000012ecf4 70 20 2c 3c 00 00 00 00 - 58 d4 8b 3b 10 84 2a 3c p ,<....X..;..*<
000000000012ed04 30 5b 4d 00 10 2e 28 3c - 4c b9 f4 08 02 00 00 00 0[M...(<L.......
000000000012ed14 74 5f f4 08 9c 36 54 00 - 00 00 00 00 00 00 00 00 t_...6T.........
000000000012ed24 80 e0 32 02 52 61 6e 6b - 44 65 63 6f 33 63 32 63 ..2.RankDeco3c2c
000000000012ed34 32 33 63 30 00 84 53 00 - 90 69 40 00 b8 43 f4 08 23c0..S..i@..C..
000000000012ed44 74 5f f4 08 14 ba f4 08 - e4 ba f4 08 c4 5a f4 08 t_...........Z..
000000000012ed54 4c b9 f4 08 af 00 00 00 - 38 49 31 02 05 00 00 00 L.......8I1.....
000000000012ed64 01 00 00 00 38 49 31 02 - 00 00 00 00 b9 6f 40 00 ....8I1......o@.
000000000012ed74 05 00 00 00 a8 34 54 00 - d8 3e b1 38 c7 84 53 00 .....4T..>.8..S.
000000000012ed84 01 00 00 00 44 8b 53 00 - 00 00 00 00 01 00 00 00 ....D.S.........
000000000012ed94 38 49 31 02 e0 61 38 1a - 40 59 34 00 00 00 00 00 8I1..a8.@Y4.....
000000000012eda4 e5 87 40 00 01 00 00 00 - b0 c5 00 10 50 98 22 02 ..@.........P.".
000000000012edb4 60 cf 44 00 06 61 0d 3e - 08 20 52 1a 38 49 31 02 `.D..a.>. R.8I1.
000000000012edc4 08 bf 59 1a 00 00 00 00 - 44 41 4d 00 08 20 52 1a ..Y.....DAM.. R.
000000000012edd4 f8 a3 4c 00 06 61 0d 3e - 06 61 0d 3e c0 83 01 10 ..L..a.>.a.>....
000000000012ede4 00 00 00 00 23 43 40 00 - 01 61 0d 3e 06 61 0d 3e ....#C@..a.>.a.>
000000000012edf4 38 49 31 02 18 ff 12 00 - 06 61 0d 3e 38 49 31 02 8I1......a.>8I1.
000000000012ee04 ee 8a 40 00 00 61 0d 3e - 07 00 00 00 06 61 0d 3e ..@..a.>.....a.>
000000000012ee14 00 10 00 10 b5 1d 40 00 - 06 61 0d 3e 01 00 00 00 ......@..a.>....


Cheerio,

One Tin Soldier

Johan217
04-21-2005, 06:23 AM
OneTinSoldier,

Could you check if you find this file in your career folder (My Documents\UserName\SH3): crew_career_00.cfg

Apparently it is this particular file that gets corrupted and causes the CTD's. Remove this file (make backup) and load a savegame. Do you still get the ctd's?

See also these threads:
http://www.subsim.com/phpBB/viewtopic.php?t=31033&start=160 (page 9)
http://www.subsim.com/phpBB/viewtopic.php?t=33585

Hope this helps!

OneTinSoldier77
04-21-2005, 10:35 AM
Hello Johan217,

Thanks a lot for trying to help me out. I sure appreciate it. http://forums.ubi.com/groupee_common/emoticons/icon_smile.gif

I had looked around a lot at forums for a solution to my problem and had seen that second thread at subsim.com before. But more has been added to it since then. As you can see the new posts have todays date, 21st of April.

Now, when I had this problem before I had went ahead and deleted my entire career, all the folders and files under D:\Documents and Settings\Administrator\My Documents\SH3\data\cfg\Careers\One Tin Soldier, which got rid of that file of course, and then I started a new career. When I got to the point where I could get a Type VIIB again I ran into the same problem, again. So, I uninstalled and reinstalled the game as I reported I would do in an earlier post in here.

Now, since then I have just gotten to the point where I now have a Type VIIB. I happen to come out to check the forums and boom! Here is your post, lol. I took a look and I do have the 'Crew_Career_00.cfg' file and I opened it up. It does not appear to be corrupted. If I find that I am having troubles again I will do as advised by just changing it name to something like 'Crew_Career_00.cfg.bad'(essentially gets rid of it as far as the game as concerned) and see what happens. But for now I think I will leave it and just follow steve_v's(IL-2 Mantis) recommendation. Although you pointing me out to the posts concerning this file might be what ends up solving my problem in the end! Perhaps something more will come to light on this file in the near future and whether or not it is really causing trouble, especially if is does not appear to be corrupted when opening it. I will come back and give an update on how my game is working in the near future.

Thanks Again Johan.

Sincerely,

One Tin Soldier

Johan217
04-21-2005, 01:06 PM
Yup, I may have been a little trigger happy with my answer http://forums.ubi.com/groupee_common/emoticons/icon_smile.gif It's probably not necessarily this config_00 file that gets corrupted - if file corruption is indeed what triggers the ctds!

I've just re-read Mantis's reply about using the WO to order crew to the gun. It is good if it works, but in my case I got ctd's whenever:
- I used any of the shortcut buttons in the F7 screen
- I manually moved crewmen to the deck/flak gun
- I used the WO menu to order crew to the guns (!)
- I chose "Attack target" in the popup menu when a target is sighted (this also puts men to the gun)

In other words, I could not use the deck/flak gun at all. I assumed this would be the case for you too. Sorry for the confusion http://forums.ubi.com/groupee_common/emoticons/icon_smile.gif

OneTinSoldier77
04-21-2005, 02:26 PM
Hi Johan,

Yes, I am having the exact same problem as you(still untried with my new reinstall). I tried to be fairly clear what the problem was in my posts and that is indeed my problem too. The title of the thread may be a little misleading, perhaps, as I can use the Type VIIB. But the way I look at is that I cannot use it the way it was intended to be used, at least to it's fullest. And that is to be able to use the Flak and Deck Guns, even if they are rarely used and pretty much only if you have to use them as a last resort. And, using the Type VIIB does cause a CTD in this regard. No problem about the confusion though. I appreciate you trying to give input on what might be wrong.

From the other fellows posts at Subsim, and you and I(as well as others I'm sure) having this problem, Llt's hope that Patch v1.3 comes along and fixes this it. http://forums.ubi.com/images/smilies/16x16_smiley-wink.gif

A lot of people get a CTD when trying to use the 'Surface Cruise' mode. Because of all the posts I have read about that I have steered clear of even tring it. It just seems obvious to me that the Crew Management system has some bugs in it that need ironing out, and of course only the Dev's can do it. But I thought, hey, you never know, maybe someone knows a work-around for this problem. Hence my making a thread to plea for help.

Cheers,

One Tin Soldier

OneTinSoldier77
04-22-2005, 01:42 PM
Hi All,

Ok, I can now confirm that steve_v's(IL-2 Mantis) procedure/method works to keep me from getting a CTD. Here is what I do now...

----------------------------------

Put a Watch Officer on the bridge.

Press 'F4' to go to the bridge.

Click on the Watch Officer's icon(or click on the Watch Officer himself) to bring up the WO menu display.

Select/Click on your choice.. (i.e. Man the Deck Gun, Man the Flak Gun, Man the Flak and Deck gun).

----------------------------------

And Daxos1942, you might be right. Perhaps I could man the Flak and Deck Gun manually if I got rid of the crew on the bridge, other than perhaps the WO, first. Formerly, I was having the bridge fully manned and then trying to manually place crew into the Deck Gun position.

Anyway, it's working now with the WO menu method. Yipee! Thank everyone and especially steve_v(IL-2 Mantis). http://forums.ubi.com/groupee_common/emoticons/icon_cool.gif

Cheers,

OTS

steve_v
04-22-2005, 08:54 PM
<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by OneTinSoldier77:
Anyway, it's working now with the WO menu method. Yipee! <HR></BLOCKQUOTE>http://home.earthlink.net/~viner45/sitebuildercontent/sitebuilderpictures/553.gif