Are you getting strange CTD in Windows programs Like KERNELBASE.dll , module ntdll.dll , or module <UNKNOWN>?
You might want to try a proposed solution that one of our players (two27) figured out and is trying:
I have a preliminary explanation for the crashes I've been experiencing. The following, if accurate, may well apply to both 64-bit (like mine) and high-end 32-bit systems. As you may have noticed when I posted about the 9.0c issue, I don't simply like to find a fix, I want to know why something works or doesn't work, so I tend to dig a little deeper on issues.
After doing everything on your list and several more like insuring the Particle Density was set to Medium and checking Disable Visual Themes under Compatibility, I found a post in the BOBII General Discussion Forum by Fish 40 viewtopic.php?f=10&t=24606
. He had found a light-weight, third party program, Large Address Aware (41k) http://www.techpowerup.com/forums/showt ... p?t=112556
, that allowed BOBII to access more system memory and it solved his CTD problem.
Through that link, I found another light-weight app called Process Monitor (26k) which allowed me to chart memory usage by BOBII while it ran. The link for that app is here http://www.techpowerup.com/forums/showt ... ?p=1732756
After I figured out the correct process name to type in to Process Monitor (Bob) it was a snap to use, type Bob and click start. What I learned proved illuminating. I had not yet installed the large address program, because I wanted to see what was happening in my system and diagnose if memory was in fact a problem and at what level.
In the two crashes I documented while Process Monitor was running the peak memory used by BOBII and the memory used at the moment of the crash were 1.73Gig/1.72Gig (first CTD) and 1.78Gig/1.76Gig (second CTD). What this looked like to me was that the game ran at its maximum memory request and crashed right at about that time while the system was attempting to manage the load. If you look at the min-max range of 1.72-1.78 and allow for the OS memory required, that puts the memory used right at 2Gig.
Next I installed Large Address Aware and ran it, alongside Process Monitor, and went on playing my RAF SPC. I've had no crashes so far and the highest recorded memory usage by BOBII was 2.12Gig.
My theory is that between the original Rowan game and community additions, the game's memory requirements may be accurately stated as 2Gig, but that does not leave any room for the OS's operations. Not placing blame or pointing fingers, just following the data trail.
I am a pretty good analyst, though not technically savvy so I called a friend who is a techie and laid out this theory for him. He thought it made sense. From what he'd read on the software development side, programming to access beyond the 2Gig limit requires a new skill set and it must be done deliberately, i.e. programs won't automatically access more than that amount of memory (the first 2Gig of physical memory) unless programmed to do so.
This brings me back to the diagnosis and the solution. These two utilities are quite small and easy to use, so diagnosing a memory issue is easy. The fix is quite straightforward using LAA; it permits BOBII to access 3Gig on 32-bit systems and 4Gig on 64-bit systems (if the systems have the physical memory).
Now that I'm done testing this out, I'm hoping my install will be stable enough to run without further problems.
Maybe this gives you another set of tools to use in dealing with CTDs. This is my first flight sim and I appreciate your dedication and the quality product you've delivered. What a challenge and it is pure FUN. Thanks.
I will ask Osram to review this solution.