wolfen420

Turn off the autoupdating in FOMM. Anywhere you see it. Turn it off.

In \fallout new vegas\Data\menus\prefabs is a DUINVSettings.xml. In there you can change settings. It is commented really well inside the xml so you should be able to find your way through it fine. There is a specific spot to enable and disable the map markers. I had to disable them, load the game, save it, exit, and set them again to on. Dunno if it was a fluke or what, but it worked for me.

Try out FNVEdit to look for conflicts with the mods?

Well if he is pirating then he is tricky by installing it into a steam folder haha.

There ya go Exception code: 0xc0000005. Memory problem. Either your vid card memory, or physical memory is stopping it. Typically that is the case. It could also be malware, spyware, or even firewall / anti virus software. Try disabling any of those if you have them. Disable any windows security as well. That is strictly to test if it is those causing it. If not, then it very well could be a memory issue. You can try using memtest http://www.memtest.org/ and see if there is a mem issue.

Ahh its on the FOMM page actually. http://www.newvegasnexus.com/downloads/file.php?id=36901 Some one posted a changed fomm.exe as well you can try. I suggest however first trying what they do. Turn off auto updates and so on. Its there in the first few posts. Just read down. You will see people with similar issues. Edit: In the comments section I mean hehe.

Yeah, the error code may help. I remember reading the other day some one having trouble though and there was specific file they deleted in the appdata folders I believe that fixed it. I was trying to find that thread again so I could point it out. I think your problem falls into the same category of problems they were having.

Look more. I don't think that is the event. There is no mention of the Fallout executables. This looks like a normal system authentication process that went through just fine. 1. Launch the game. Let it crash if it does. 2. Immediately go to your event viewer. 3. Go to "Windows Logs" 4. From there go to "Application" 5. Looks for an exclamation (!) mark in a red circle. 6. Look at the general tab and see if it mentions a fallout exe file. If it does, this is the one we want to look at. Just copy and paste the text in the general tab. (you need to use ctrl + c to copy from the general tab) For example, I use fallout 4 gigbyte enabler and nvse. I had a crash last night. This is what I see in the event viewer. Faulting application name: FalloutNV.4gb, version: 1.4.0.525, time stamp: 0x4e0d50ed Faulting module name: FalloutNV.4gb, version: 1.4.0.525, time stamp: 0x4e0d50ed Exception code: 0xc0000005 Fault offset: 0x001e0df4 Faulting process id: 0x12cc Faulting application start time: 0x01cc3f852d6efb30 Faulting application path: c:\steam\steamapps\common\fallout new vegas\FalloutNV.4gb Faulting module path: c:\steam\steamapps\common\fallout new vegas\FalloutNV.4gb Report Id: f6044548-ab7b-11e0-9be1-001d7dd4da72 The exception code 0xc0000005 is a mem error typically. I have been having this for a while with various games. I am not sure if it is my vid card mem or my regular mem. Doesnt happen often enough for me to care haha.

Did you try to uninstall reinstall it?

Have you tried disabling UAC? Have you ensured that you were not just setting the launcher to admin mode or compat mode? Are their any errors given what so ever? After the game crashes, can you take a look at your "Event Viewer" and see what windows says about the crash? And, just in case you are not sure on event viewer check this site out http://unlockforus.blogspot.com/2010/02/event-viewer-in-windows-7-and-vista.html. That should get you in there and finding the event.

Gribble: If you are correct (as I have done texture work with other games using DDS) then this means he should use the generate mipmaps feature of what ever dds plugin or tool he is using. Mipmaps are basically generated smaller versions of the texture that appears at distances. Here we go... wikipedia says (hehe) "Mip-maps are pre-calculated, optimized collections of images that accompany a main texture, intended to increase rendering speed and reduce aliasing artifacts."

I use the Ogo and Poco as well and I get the same thing except for the flickering. The distance is very obvious that the textures are not blending. The only way to fix is either make your own textures, hope ojo or poco mods fix it eventually, or just not use the mods and live with vanilla textures. Me, I got over it. I live with it. hehe

Enabled Archive Invalidation? Meaning, you may want to check in FOMM tools menu. If its checked already, uncheck and re-check. I had to do that for the Invalidation to actually kick in.

Hello there. I am using Project Nevada and Darn UI (along with other mods) as well as the unified UI project. I installed DarnUI first, then followed with Project Nevada and its DLC Patch. I then used the Project Nevada optional DarNUI support files. So just about everything looks correct so far. However, my compass markers are missing. Even with in the DUI Settings xml they are set to 1, but nothing shows up. Anyone else have this problem or know how to fix it? (Ill try setting them to 0, but I suspect that wont fix it hehe). Thanks, -Wolfen P.S. Darn, PN, and Unified are the only UI changing mods installed. Edit: Aaaand somehow turning them to 0, launching, saving, turning to 1, launching saving, some how seemed to fix it. Soooooo nevermind. =)

Did you do archive invalidation? If using FOMM you can find it in the tools menu. If it is already enabled, try disable then re-enable.