ctds are normal.... bsod... well, that is windows normal :ping:

Sober, nope, did not help. I probably simply lack the memory (or my memory faulty somewhere) to load up that much. Even with 4gb switch it crashes within about 30-20kms of Keil. Makes me wonder if there is some huge force leaving Kiel around Sep 7, '39 :)

All convoys leaving Kiel has been removed in OHII. This fixed the ctd with the tutorial at the start of the game:up:

Try to reduce your TC to TC2 or TC4 when crossing deathline..

that is the problem... TC is at 1... :/\\!!

Will try olydebug today, see what shows..

well, being stubborn as hell, decided that fiddling around with OllyDbg will be amusing...

And this is what I get on the crash:
Log data, item 266
Address = 10024C27
Message = Access violation when reading [1C7ED0A0] - Shift+Run/Step to pass exception to the program

now, to my understanding it is possible that whatever is happening in the game trying to either read/write outside the stack or the memory is corrupt.. am I on the right track here?

As everytime you load a process into memory it gets placed wherever the Window's loader decides to place it thus giving addresses does no good. It's best to state which module and then the offset in the module. I'd be curious to take a look at your problem but you need to specify module (i.e. sh5.exe) and offset (i.e. +0x00402E). In order to get OllyDebug to show offsets scroll the window to the very top. Click on the far left bar that's showing the addresses. That'll change the way addresses are shown. Click until you get it showing offsets (first 'address' will be +0x0). To get back to where you were right click on main window and select 'Go to origin'

Thank you :)

Will take me forever to figure out how all this works.. I'm not as smart as I wish...

Well, setting Olly as a default debug gave me lovely:
Log data, item 4
Address =
Message = Process terminated, exit code C0000417 (INVALID_CRUNTIME_PARAMETER)
on ntdll module - out of things... ntdll.RtUserThreadStart...

while showing:
[196] DllMain: hModule=0x10000000, ulReason=1, lpReserved=0x00000000, gRefCnt = 0
[196] DllMain: hModule=0x10000000, ulReason=0, lpReserved=0x00000000, gRefCnt = 0

in the DbgView

Well, guess I know what I'm doing for the next month or more - reading lots on assembly

This is the end result, it is not the cause. To find the cause you need to run up the stack chain to see what caused it :yep: Place breakpoints on what you suspect might be the cause and run the game again :up: