pmw57
-
Posts
95 -
Joined
-
Last visited
-
Days Won
1
Everything posted by pmw57
-
You may want to test your hardware more extensively then. Burn-in tests are used by most companies to stress-test machines before shipping them out to customers. You can use PassMark's BurnInTest which gives a 30-day trial for you to use.
-
That's a possibility, yes. For the record I'm running Oblivion on Windows 10 with no troubles caused by it at all. You may want to test your memory with memtest86, and your hard drive using recommendations from this best hdd diagnostic / test thread. Edit: without to with, our to your.
-
These runs from Anvil to Gottshaw Inn (with Oblivion Reloaded and Oscuro's Oblivion Overhaul) were all done while enjoying an Armin van Buuren video on the second screen. Times 1 to 3 were at normal speed from an Alternate Start game saved outside of Anvil. Time 4 was at at a player speed of 255 to try and push things a bit. Time 5 was also at speed, at which I didn't reload the save game so that future runs are all continuous. Time 6 was on a horse, that goes stupidly fast at 255, so brought it back to 128. It couldn't handle the drops at speed though. Time 7 was on a new horse at a 128, it had trouble when going back to Anvil, as the downward sections resulted in the horse going airborne at speed. They don't like that sadly. Time 8 I went for the guard's horse, which goes at speed too but still couldn't survive. Cornering cannot occur quickly, sadly. Time 9 the guard became a pincushion as I backed away from towards Gottshaw Time 10, as the The other bandit at Gottshaw just told me to bugger off I brought the other one closer to Anvil with me for the journey. It's solid as a rock for me dammit.
-
Okay - I've created a fresh new Oblivion install and installed OR (using the install instructions on the nexusmods page), and OOO. Using alternate start in Anvil, I'm running to Gottshaw Inn along the road. Do you use any kind of speed boost? I'll try running back and forth along there until I've got to Gottshaw 10 times over, and report back.
-
The information from you certainly has been helpful. I don't recall seeing you mention yet anything about MenuQue. Is that involved in your process?
-
I think that I'll have time to investigate this in a few days too. Having a reproducible confirmation from a different person really helps to lend weight to the issue, and your step-by-step guide is a really big help. I would like to ask though, after installing how do you get to the trouble area? Do you load up a save game, do you go through the sewers creating your character and travel in some way there, or do you do something else?
-
Can you give us a blow by blow set of instructions for how you install both OOO and OR? For example: 1. Open the OOO zip file 2. extract the contents to ... or 1. In the Installer tab of Wrye Bash right/click on the Package tab and create a new marker called OOO 1. Drag and drop the OOO zip file into the Installer tab of Wyre Bash 2. Right-click on the archive and unpack to projects 3. Delete the archive 4. If needed, drag the unpacked archive to the OOO marker section And so on. With enough detail so that someone on a different computer can follow your instructions, so that they can experience the same trouble that you are having for the purposes of troubleshooting.
-
Is there some way that the construction kit can be used in those problem areas to help figure out or even fix the problem?
-
It's likely that your oblivion.ini file is causing the problem. The way to fix that is to delete it and have Ovlivion recreate it when the game starts. Be sure to take a backup so that you can transfer over any important setting when it's done.
-
That's not a virus - you have just reformatted your computer. Your graphics and audio drivers will be out of date. Update your drivers and you should see an improvement.
-
I know nothing on this, but a Google search turns up the following successful advice that I'll condense below: In the end series.ini file, disable detailed shadows and ambient occlusion. Then try a more recent version of ENB before enabling them nice again.
-
I am reminded of a doctor joke. The patient says, "Doctor, it hurts when I do this." "Then don't do that!" I look forward though to further details in regards to Ill Omen and Horn Cave though.
-
I found that half the time I was crashing due to computer setup, with interference coming from antivirus and other causes. Most of the other half was from failing to follow instructions. Either from the Mythic Dawn guide or from the mod documentation itself. Does yours still crash when all mods are disabled? If no, turn them on in groups until you find what is causing the problem. If yes, start with a clean install. If that still crashes, we can investigate what there may be about your computer system that is getting in the way.
-
That sounds quite plausible, as there a many configuration settings that can be made which are far beyond anything the game was designed to work with.
-
Okay, well let me know when you have a reliable situation occurring.
-
Are these crashes ones that you can reliably get to occur over and over again? Because only when you can reliably cause the crash, will you know that you've fixed the crash from a change that you've just made.
-
It's a matter of ruling out possible causes. Can we please see the details for both of those codes for your most recent crash.
-
Mostly it's from research - google is your friend - backed up by a hefty amount of experience to help filter out the useful information. I have kept several of my crash logs, what they said and how they were successfully fixed. Other information can be gleaned from that crash log, such as the location of the crash, but that's only useful if you have access to the source code. Without that, we can only connect random numbers to certain patterns of behaviour. For example, commonly the crash happens at 462392c7 but that didn't occur this time, so the usual troubleshooting for that section wouldn't apply. 0x005881be is only found on one unrelated page, so this is a situation that people have rarely reported on. The 0xc000000d exception code is instead 0xc000000e with normal Oblivion crashes, so chasing up the 0xc000000d error code, ignoring results relating to unreadable boot sectors, was the most reasonable course of action to take.
-
The two important parts are the Faulting application path, and the Faulting module path. The module is what caused the fault, which can sometimes be the graphics driver, or the antivirus program, or something else. When the application and the module path are both Oblivion.exe, that means that the problem occurred from inside of Oblivion, where it has pointed to a memory location outside of where it's allowed to be, usually by a badly configured mod. Your error does have something rather unique compared to other ones that are seen, in that it's an 0xc000000d exception, which usually means that some kind of pre-existing windows system file damage has caused the problem. Details about this and a repair tool can be found at https://thewinwiki.org/the-exception-unknown-software-exception-0xc000000d/
-
Yes indeed, it was just a matter of finding and fixing issues when they arrived. The real challenge is turning it in to a reliable issue. And from there figuring out what's causing the problem in the first place. I now enjoy Oblivion without crashing for several gaming sessions. I'm not sure if my mod list will help, but here it is. Screenshots of my Installers and Mods tabs are found at: https://i.imgur.com/S3Lg9ER.png https://i.imgur.com/WigLUab.png and my plugins.txt file is:
-
I'm on Windows 10 too. You can try turning some of the mods off (I do them in groups of around 5) until things stabilize, then enable them again. The tricky thing for you is that it's an intermittent crash. Real progress can only be made when you figure out what needs to be done to guarantee a crash.
-
Good one. The faulting application and module are the same, so it's Oblivion itself losing control. There's some good information on how to deal with this in the Oblivion Crashing in Windows 7 thread, at the following post: https://forum.uesp.net/viewtopic.php?p=310319&sid=ecb678b619d680590c375e99e5abfe2a#p310319
-
The Event Viewer is what phone scammers get you to bring up, to prove that your computer has viruses. It's also a place that has useful information about what caused a crash to occur. Type "event viewer" in to the start menu, and in Window Logs > Application you should find info about what crashed Oblivion.
-
Something that you can do is to investigate the Event Viewer to find out what is causing the crash. Sometimes it's due to something outside of Oblivion that can be resolved.
-
Finding a way to reliably cause the crash is often the hard part. Even without that though, there are ways to improve the situation. Some mods like the Curse of Hircine and RTT are known to cause stability problems. What you can do is to disable several of these mods and continue to do stuff around Leyawiin. If things remain stable then it's a good bet that one of those mods were responsible. Personally, I had stability issues with both, and found reliable ways to make the crash occur. With the Curse of Hircine I found that when exiting West from the Imperial City, that turning North from Weye would guarantee a crash. I could save at the road signs and guarantee a crash by heading North up that way. This allowed me to try removing different mods to figure out hat was causing it. I was only able to get through by removing the Curse of Hircine. I wasn't interested enough in that mods to chase down why it was causing the crash, and so have left it out. RTT on the other hand I was more interested in, and found that things would sometimes crash when mounting my horse. Further investigation found that it it would always crash when my Ruined-Tail companion was with me during a specific set of events, that being when I dismounted to kill a creature, then quickly mounted again. When a creature is killed, Ruined-Tail would bend down to the creature to check its pulse, during which if I mounted my horse he would attempt to summon his own horse at the same time as checking the creature, causing the crash. An edit to his script fixed the problem. Such detailed knowledge of the problem was only possible after investigating closely to figure out the actual cause of the crash. I hope that you find a way to learn more about what is causing the problem for you around Leyawiin, so that a working solution can be obtained for you.
