Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Or it's the "cell-change bug", which occurs occasionally when you enter or leave cells (for example, go through doors). The probability increases with the length of your playing sessions, the "solution" is to keep them short (30 to 60 minutes, say - use your own experiences) and to save regularly (to minimise the loss of progress).
You might be able to resolve it by using the console player.coc command, but, this did not work for me. I simply crashed when I tried to move after the player.coc command. My guess is that an internal address has been incorrectly allocated and you need to go back to before this happened.
Does it happen at the specific door you mention, or at other doors, too? Is it just because you try to use this door more often than other doors? Does it always and reproduceably happen at that door? If it happens elsewhere, too: Does it happen when going through doors only? Does "doors" mean doors only, or, say, dungeon or ruin entrances or Oblivion gates, too? Does it happen while travelling?
And does "crash" mean a sudden crash to the desktop, no error message, no blue screen, no need to cancel a task with the task manager (I have no experience with the event viewer, sorry)?
"No mods installed currently" - does this mean you had mods installed on this PC before? In this case (and especially when the crash always happens at the same door) it might be caused by a leftover from one of the previously installed mods (which might have overwritten a texture or mesh file, for example).
And are the crashes possibly associated with a specific save game? Save game corruption is always a possibility, and the culprit may even be an older. not the most recent one.
I'm simply going through hypothetical possibilities and might be totally wrong.
If your save has been affected by other mods that you have uninstalled, then that might be more difficult, but it should be okay without the memory patch.
Another rule of thumb that I live by is when your playing a game, do not have a million other things running at the same time, so many things can just hog your memory. Turn it all off.
I can't judge the content - all I can say is that I'ver never used it and never missed it.
The rule of thumb you mention is a valid one, except that I doubt Oblivion has ever crashed because too many other applications were open. Performance might suffer slightly, but it would be hardly noticeable on modern PCs. And I doubt that there is any relationship between savegame corruptions and the 4 GB patch.
It seems then that the problem is outside of the game. I would make sure windows is fully updated, graphics drivers are updated and do a health check in settings. Running the game as administrator can also help.
My solution was to save game just before leaving uncommon places and when Oblivion would crash, I could reload and was able to exit safely every time.
In Windows 10: this bug doesn't seem to occur. I can play straight through for 6 hours with no crashes. As a matter of fact, Oblivion hasn't crashed at all on Win 10. I am finding it quite rewarding.
Just thought I would mention
WinXP on two different PC's, graphics: Nvidia - both had this crash issue.
Win10 graphics: ATI
Different motherboards
Other than the graphics cards, my PC builds were nearly identical.