Kernel.dll Crash!!!!!!!!!!!

[redsocialist]

Originally Posted by frau kaleun

When you say you applied the 4GB patch, I'm assuming you mean that you applied the patch to the SH3.exe file that will allow it to make use of more RAM than the 2GB (?) to which it was initially limited.

However I don't think you've said whether you are running the 32-bit or 64-bit version of Windows.

If you are running the 32-bit version, it will not matter how much RAM you have installed or how much RAM the SH3.exe will be able to use - the OS itself cannot recognize more than 4GB max. Using the 3GB switch in the boot.ini file may help make more RAM available for games and other applications, but AFAIK you haven't said whether or not you are using it.

If you are running the 64-bit version your OS can recognize and use more RAM provided you have it installed, and if you do have more RAM the game should be able to use a decent chunk of it once it's been patched for that purpose.

In either case I would advise that you disable all mods and try at first to run the game without any additional modifications, if you have not done so already, to see if the same CTD occurs.

I'm runing 64 bit Windows 7

[frau kaleun]

Originally Posted by redsocialist

I'm runing 64 bit Windows 7

And you've got, what, 6 gigs of RAM in your machine? It that's the case and you've run the 4GB patch for SH3.exe, memory should not be an issue.

Do you have a separate video card, and if so, how much memory with that?

I don't know that trying to run the game with an onboard gfx controller would cause a memory-based crash, but without a graphics card with at least 64 MB RAM (128 recommended) you're still not up to spec for the stock game, much less any mods/supermods that might require more in the way of graphics performance. Someone else will have to answer the question of whether or not that would be likely to cause a Kernel.dll crash.

In the meantime I would still recommend disabling all mods and seeing if you still get the same CTD. In any CTD situation that's the only way to be sure it's not some modification that's causing the problem.