I second this as I also just gave that a read thru. Nice article with Pics and all...lol

And yes that process explorer is great....

Wow, I didn't even think to click on that process explorer link. It is excellent! There's even an option to have this program replace the default task manager, and by the looks of the amount of system data you can monitor - that might be worth it!

I have a question about applying the LAA patch and OBSE. I'm not sure the previous thread made this clear, but will applying the patch cause the oblivion.exe to be incompatible with OBSE? I seem to recall reading a couple of different opinions: at first it was thought that there should not be an issue since the patch is so small, but then someone said that it WOULD make a difference regardless of how small the patch is. This last poster confused me, then, by stating that OBSE doesn't check for the change - even though the patch would generally make it incompatible with OBSE - so all in all it is not an issue? This may be making no sense, let me try to go quote whoever that was.

cheers!

@taajikhan:
Obse makes a checksum of the exe file but ignore the byte where the LAA flag is set so no, there is no issue with obse...

@WalkerInShadows:
LAA patch has no use on a 32 bit os, it's written on the first post of this thread, sorry.

Only the process of Oblivion or the use of the entire ram was at 3.8?

Post Scriptum:
I have 1GB of VRAM and 8GB of system RAM, I use Win7 Ultimate 64bit, I installed OSR and PCB, and Oblivion crashes always at about 1.8.

You are a good candidate for the LAA fix from the first post. It will help you.

gothemasticator

I have already used the patch, but does not work.

Looks like I missed out on what went on here last night...

@taajikhan - Great article! Answers pretty much all the questions that have been whirling in my head over LAA. I'm an avid Anandtech reader, surprised I hadn't seen this. They certainly were ahead of the game as I'm sure many PC gamers are only now finding the downfall of 32bit OS gaming. Windows7's recent release has more than likely attributed to the re-discussion of the 32bit addressing issues.

@WalkerInShadows - Since you are running Windows XP 32 the LAA patch will not work. When using any 32bit OS your max ram ceiling for the Oblivion.exe process is going to be somewhere between 1.65gb and 1.85gb. Anything below 1.6gb is safe, but anything above that is likely going to result in a CTD within the range I posted above.

@gothemasticator - I will add a link the Anandtech article. Thanks for the suggestion. I've neglected to update the OP because up until the forum face lift, I wasn't able to edit the OP anymore for some strange reason. I only recently found that I can now edit again.


Thanks for keeping this thread alive guys. It seems someone new is always able to provide insightful information that everybody stands to benefit from.

Hmm. Okay. Thanks anyway.

Since that was to me I will Respond...I have a Screen Shot Of this....

That was Only the Oblivion Process.....as seen in Task manager...one sec...gonna look and get exact #'s

Time in game .....1:21:30 (yes hour and half)
Mem Working Set....3.806,776
Private Mem Set......3,784.796
Page Faults ........ 5,961,024

So ya Works as Described!!!

You must have some intense mods fired up to exhaust your memory so fast. Were you playing the game or doing more of a test run during that hour and a half? I find when I just play the game at a normal pace, my game time before a CTD lasts longer. When I am testing, I'm usually purposely stressing the game to try and break it.

EDIT - Don't get me wrong... I would be satisfied with an hour and a half of game time with a fully modded Oblivion load order. Oh yah, did you use http://www.microsoft.com/technet/sysinternals/utilities/Processixplorer.mspx. to get those numbers? Thinking of using that from now on. Want to start getting an idea how much virtual memory I am using etc...

Fully Moded Game......But i think that was back when i was building my BASH patch wrong. When Merging mods into patch i wasn't UNticking them so had 2 copies of those...lol DUH!

And ya that was when testing to push to the limits so i knew what they were and could back down from there. and no that was thru task Manager not the Process Explorer one.

Short list ..mods installed 187
Seen by Oblivion 137 Differance being the merged files in BASH

This includes QTP 3 Redimized, FCOM , RAEVWD (Full install but no ESP"S ) Landscape LOD"S ect....ect...

EDIT..and all the UL landscaoe mods!

Always good to hear this type of feedback. :goodjob: You do a better job than me on keeping track of your numbers man! After I play around with that new process explorer, I hope to give some very good detailed numbers as well from play testing.

Not working yet, I tried to delete OSR and PCBs, I tried to replace the exe and put the patch, but does not work. I have the GotY version, could depend on that? Do you have any suggestions?

edit, double post.

Does the above apply to you in any way shape or form?

When you say "Not working yet" what essentially isn't working? If you are talking about the 4gb LAA patch not working, what makes you think it isn't working? Please provide us a bit more detail.

I have an original copy of the game, is GotY edition. My OS is 64 bit Win7 Ultimate. The graphics card is a 4870x2 with 1GB of VRAM useful, and I have 8GB of system RAM, so I think in terms of hardware I have enough power. I installed QTP3 Redimized, and all UL, and all the textures made by Mikal33 and even Dark Regal IC Optimized.

Everything works fine, the only problem I have is the crash that occurs when the system RAM is occupied by the process of Oblivion up to 1.8GB.

So I tried to patch the exe of the game (7MB) with LAA 4GB, but does not work, because I still have the same crash when I get to have 1.8GB of RAM occupied by Oblivion, I see this from the task manager.

Thanks for giving us more info. My initial guess is that their may be an incompatibility with the GOTY edition exe. You are the first to specify goty on this thread.
Can anyone else confirm that the 4gb LAA patch works with their goty oblivion.exe file?

Aretino, what ver of obse are u running? Just curious.

18 beta 6

As i know this is frowned on but may help......

I have the Original Collector Edition Game (Rated TEEN) Bought the Week of Release!

Disk in Drive = no (no further Discussion here please)

I can follow the Memory usage easy with the program...Riva Tuner. this shows me...the usage on all 8 threads,(yes Oblivion uses 4 ) temp of video card(including ambiant), speed of video card fan( its set to ramp up as temp increases) but most important Both Physical & Page File Memory usage .(plus much more like voltages)

With all that said ...I know for a fact I could not go over 1.8 gig used TILL I patched Both Oblivion & OBSE with the 4 gig Patch. I do not know why . but this is what I experienced. Cant hurt to try now can it....lol

The link to the LAA patch doesn't seem to be working... is there an alternate location?

It did seam to be down ...i just tried again and it loaded.....http://www.ntcore.com/4gb_patch.php

Yep, it's working now, thanks

Interesting, I'll try this out. You know, the first time I installed the 4gb patch, I installed it to both, but after that I don't remember ever doing this. But I haven't been testing since either. Will have to monitor my memory usage and find out how things are running with and without as well.

So there you go Aretino... Maybe you should try patching your OBSEloader.exe with the 4gb LAA patch as well to see if you get different results. Worst that could happen is you have to re-install OBSE.

Guys, patching the loader will not work! That's not the program using the memory.

As to the patcher not working - Isn't the linked version of the patcher the one that displays feedback confirming that the flag has been changed? If it is, then you can confirm whether or not the LAA flag has indeed been set. The patcher shouldn't be failing to set the flag while deceiving you to think it is done. If it is indeed incapable of appying the flag to the GOTY edition (which I find hard to believe), then running the patcher should indicate some sort of failure.

gothemasticator

Yeah, I just tried w/ and without adding the LAA patch to OBSEloader.exe

I experienced no difference. The LAA patch works fine for me without the need to patch OBSEloader.exe

Sorry for causing anyone confusion...

@ camaro-69_327 - I don't know why you are experiencing something different. But, whatever works man.