odd crashes

civimike · Post by **civimike** » Thu May 25, 2006 9:37 pm

Im getting more and more odd crashes at spacific locations. (wynon prioty, one of the castle courtyards) it seems to be a graphic issue since i am able to enter the area if i set the graphic options to very low and then start the game.....anyone else come across this? i did put in some of the graphics mods that are supposed to help with distant views, and i di install the BT MOD.....but i uninstalled them after this started and it still happens. i did also install the latest beta patch AFTER this started....

Salem Verano · Post by **Salem Verano** » Thu May 25, 2006 10:57 pm

Well,

Did you fiddle around in the ini ile ? if so, you might have disabled bDoSpecularPass, turning this off causes the game to crash in certain locations, especially weynon priory, Skingrad Castle Courtyard and Anvil castle.

civimike · Post by **civimike** » Fri May 26, 2006 4:20 am

you rock!!!

if i could buy you a beer i would!!!!

Salem Verano · Post by **Salem Verano** » Fri May 26, 2006 10:23 am

I don't drink, but thanks anyway

And you're welcome, I'm on this board to help

Mishra · Post by **Mishra** » Fri May 26, 2006 2:22 pm

I've had this same problem recently trying to get into Thieves Den, it was my first time with this problem. Lowering all my settings then going in worked for me.

DeathUK · Post by **DeathUK** » Fri May 26, 2006 4:13 pm

My housemate bought 2.5 Gigs of RAM, that seemed to sort out most crashes :twisted:

Salem Verano · Post by **Salem Verano** » Fri May 26, 2006 8:01 pm

DeathUK wrote:My housemate bought 2.5 Gigs of RAM, that seemed to sort out most crashes :twisted:

That's rather childish, and lots of ram is not a guaranteed fix for crashes and any other malfunctions.

And Mishra, you might have the same problem, so check your Oblivion.ini file, if that's not the case, I suggest you give us more details what exactly happens, there are too many parameters in this game to say for sure how/why it crashes some of the times.

Vook · Post by **Vook** » Sat May 27, 2006 11:51 am

Lots of RAM helps against memory leaks (most common reason of crashes) but only by delaying them, not by preventing them. Simply the game uses up more and more of memory till it uses it all and then unable to find more, crashes. If you have lots and lots of RAM, it will take much longer to fill the memory.

DeathUK · Post by **DeathUK** » Sun May 28, 2006 3:52 pm

Salem Verano wrote:
DeathUK wrote:My housemate bought 2.5 Gigs of RAM, that seemed to sort out most crashes :twisted:
That's rather childish, and lots of ram is not a guaranteed fix for crashes and any other malfunctions.

It was simply a light hearted comment, Mr Verano. You had already answered correctly and solved the problem, I was merely adding another way to prevent crashes. And more RAM does do that! Memory doesn't just get used up and used up until it crashes you know, its a constant flow of temporarily stored information. As I previously "childishly" stated, I have seen first hand a huge improvement in game stability by the addition of a lot more RAM. Now I think you owe me a PM apology

Salem Verano · Post by **Salem Verano** » Sun May 28, 2006 7:59 pm

Sure lots of ram will improve any game's experience and stability, that's pure logics, but alot, if not most of the crashes aren't related to low ram.

Colin · Post by **Colin** » Mon May 29, 2006 3:08 am

I also get random game crashes, sometimes its a graphics problem, sometimes the game stops itself with the "send error to Microsoft" screen.
Problems can happen anywhere in the game, even on startup. When it decides to work OK, it can then run for hours without a problem. Other times, it will freeze or crash every half hour or less. I have 2 Gb RAM, running 2 6800 cards in SLi and an AMD 64 chip.
Anyone have a solution?

i9ub · Post by **i9ub** » Mon May 29, 2006 5:48 am

Just a note and a bit of friendly advice extracted from past experience.

If you are crashing and have tried to resolve the problem through all of the standard methods without any luck, read on.

For months and months after World Of Warcraft's release, people had strange problems with crashing. No one, and I mean no one, had any clue what was going on and subsequently most people blamed Blizzard. One thing that all of the people suffering from the crashes had in common was that they had home-built their PC.

Finally the primary problem was identified. The memory latency timings, the one with four numbers (ex. 2-2-2-5), were being improperly identified by the motherboard. The motherboard defaulted to a safer, slower memory speed and forced the memory to run at 2-3-3-5 or so. Normally you could still play games and not crash, however World Of Warcraft stressed memory more than nearly any game before it, so the problem surfaced. Oblivion would definitely demand enough memory to cause this problem.

To fix this, figure out what your memory latency timings are. You can usually do this by just looking at one of the memory modules. Then go into your computer's BIOS and manually configure the memory timings. What your looking for are three letter acronyms (ex. CAS) with small numbers next to them (ex. 2, 2.5, or 3).

I am sure many people know this, don't be offended by this post. It is merely to help the few that could be having this problem.

Salem Verano · Post by **Salem Verano** » Tue May 30, 2006 12:02 am

It's a great tip i9ub, and doubt there are alot of people who know this, except people like me who's hobby and job is computers

But, you can't always manually change the CAS in the bios, depends on Biosversion and alot of other things, but if you can change it, try it if you're crashing either way, just be carefull, it can really mess up your comp if you put it too high, always test it in small amounts and for several hours atleast.

UESP Forums

odd crashes

odd crashes

frequent crashes

Hmm