Jump to content


Photo

LOOT.exe has stopped working

loot mod organizer falinv errors

  • Please log in to reply
11 replies to this topic

#1 hazelwolf

hazelwolf

    Guard

  • Members
  • PipPip
  • 191 posts

Posted 20 April 2017 - 06:46 PM

I'm just running through the Fear and Loathing installation process but I am unable to properly sort my plugins.

 

Most of the time I start LOOT up through Mod Organizer, it stops upon the initial startup with a basic "a problem caused the program to stop working correctly".

 

This wasn't an issue around the point of the Interior Lighting Overhaul, but the more plugins I add beyond that, the more chance LOOT has of stalling upon startup or upon plugin sorting until nothing can be done.

 

I've never had this issue before and am using a 64bit Windows 7 os.

 

My c: drive has become awfully full in recent months so I don't know if it's simply a lack of room but I am at a loss now. I have reinstalled a clean version of LOOT and googled as much as I can on this issue but I am finding nothing.

 

Does anyone have any suggestions for what I can try?


  • 0

#2 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,899 posts

Posted 20 April 2017 - 07:20 PM

Sounds like the message is coming from Windows, so I'd investigate your system, maybe a recent MS update has broken something.

Perhaps you can take a screenshot so we can see what exactly is said and from whom/where.



#3 hazelwolf

hazelwolf

    Guard

  • Members
  • PipPip
  • 191 posts

Posted 20 April 2017 - 07:53 PM

Ok. Screengrab of the message is:

 

oxorgn5.png

 

It happens either upon start-up of LOOT via MO or, if not, upon sorting load order or applying the changes. It does appear that the heavier the load order, the more likely it is to happen.

 

Incidentally, I picked up this error when I accidentally started up NVSE mid-installation:

 

 

DEBUG (01:17:09.0295): createfile w: D:\steam\steamapps\common\Fallout New Vegas\Data\Armor Replacer Child NPC Fix.esp -> D:\steam\SteamApps\common\Fallout New Vegas\Mod Organizer\mods\Armor Replacer Child NPC Fix\Armor Replacer Child NPC Fix.esp (0 - 3) = 00000848 (0)
DEBUG (01:17:09.0295): handle opened with backup semantics: D:\steam\steamapps\common\Fallout New Vegas\Data\Game Tweaks..esp
DEBUG (01:17:09.0296): createfile w: D:\steam\steamapps\common\Fallout New Vegas\Data\Game Tweaks..esp -> D:\steam\SteamApps\common\Fallout New Vegas\Mod Organizer\mods\Game Tweaks\Game Tweaks..esp (0 - 3) = 00000848 (0)
INFO (01:17:09.0296): Windows Exception (c0000005). Last hooked call: void *__stdcall CreateFileW_rep(const wchar_t *,unsigned long,unsigned long,struct _SECURITY_ATTRIBUTES *,unsigned long,unsigned long,void *)

ERROR (01:17:09.0296): This is a critical error, the application will probably crash now.
DEBUG (01:17:09.0296): handle opened with backup semantics: D:\steam\steamapps\common\Fallout New Vegas\Data\Vurt's WFO.esp
DEBUG (01:17:09.0377): createfile w: D:\steam\steamapps\common\Fallout New Vegas\Data\Vurt's WFO.esp -> D:\steam\SteamApps\common\Fallout New Vegas\Mod Organizer\mods\Wasteland Flora Overhaul\Vurt's WFO.esp (0 - 3) = 00000848 (0)
DEBUG (01:17:09.0377): hooks removed

ERROR (01:17:09.0490): Crash dump created as D:\steam\SteamApps\common\Fallout New Vegas\Mod Organizer\hook.dll.dmp. Please send this file to the developer of MO
DEBUG (01:17:14.0366): hooks removed

I figure it has something to do with the fact I had misunderstood the installation and had cleaned the Vurt's WFO.esp plugin in FNVEdit. Regardless, I can't seem to be able to rid myself of the message.


Edited by hazelwolf, 20 April 2017 - 08:04 PM.

  • 0

#4 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,899 posts

Posted 20 April 2017 - 09:14 PM

LOOT issue does seem to be related to your Windows system, not specifically a MO or FNV fault. Aside from the usual recommendations to avoid UAC folders, which it looks like you have, try disabling any AV software or any game related tools also running such as those from Razer/AMD/Steam or the like. (In game helper applications)

 

As for the error in the MO log, the mod tweak plugin looks to have an extra "." in the name, try renaming it.



#5 Gogan

Gogan

    Citizen

  • Members
  • Pip
  • 65 posts

Posted 21 April 2017 - 11:38 AM

LOOT crashes for me all the time.

On start-up and when running the sorting function.

 

I'm just restarting the damn thing over and over again, until it does the job.

 

Sometimes it crashes 10-20 times, sometimes it doesn't once.


  • 0

#6 hazelwolf

hazelwolf

    Guard

  • Members
  • PipPip
  • 191 posts

Posted 21 April 2017 - 01:27 PM

OK. I gave my system a thorough clean and tidy (long overdue, so at least this has given me reason to). I disabled my Avira's Real-Time protection, heuristic analysis and set the whole New Vegas installation folder as an exception. I've disabled as many gaming tools as I can (but can't really disable steam as it's required to run).

 

End result: nada. Nothing seems to have fixed it.

 

Here is the error log:

 

 

Log Name:      Application

Source:        Windows Error Reporting
Date:          21/04/2017 19:32:53
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Clarion
Description:
Fault bucket 1300280363, type 25
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: LOOT.exe
P2: 0.10.3.0
P3: 58729e8e
P4: hook.dll
P5: 2.7.5.0
P6: 55eaff17
P7: c0000005
P8: 00018f94
P9: 
P10: 
 
Attached files:
C:\UsersHazelwolf\AppData\Local\Temp\WERC773.tmp.WERInternalMetadata.xml
 
These files may be available here:
C:\Users\Hazelwolf\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_LOOT.exe_b71dd043c3ba57ca61d88c60fc674eb3cac9976_189b7f7c
 
Analysis symbol: 
Rechecking for solution: 0
Report Id: d1f410d0-26c0-11e7-bfa7-94de8008a06d
Report Status: 0

 

I also edited the Game tweaks.esp though I still am unable to shift that error message.

 

All in all I'm stumped because LOOT was working fine when I ran it through NMM earlier this week with a similar load-out of plugins (at this point I have 90 enabled and am getting nowhere)

 

I've tried just mashing load over and over to mostly no effect.


Edited by hazelwolf, 21 April 2017 - 01:38 PM.

  • 0

#7 hazelwolf

hazelwolf

    Guard

  • Members
  • PipPip
  • 191 posts

Posted 21 April 2017 - 04:18 PM

Hot damn! Managed to find a fix.

 

right click LOOT.exe> Properties> Compatibility tab > set compatibility mode for Windows 7

 

Figures it would be that simple.


Edited by hazelwolf, 21 April 2017 - 04:20 PM.

  • 1

#8 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,899 posts

Posted 21 April 2017 - 06:45 PM

While I'm glad you are able to use LOOT again, I fear the true solution is still out there. Running LOOT, or MO for that, matter, is not a true solution as both these tools work perfectly well for many users on Win10. Something else is different with your setup and it is that which needs to be isolated.

 

Nevertheless it isn't your task to suffer through hours of trial just to find out what.

Have fun.



#9 Madparsnip

Madparsnip

    Prisoner

  • Members
  • 3 posts

Posted 02 May 2017 - 07:12 AM

I had the same problem exactly. Loot becomes more error prone until after a certain number of plugins it never starts. I originally got to a point where I gave up on modding FNV and only recently built up the patience to try again with a fresh install. The result was the same. I was about to tear my hair out when I saw this post. The compatibility solution works for me too!

 

Thanks Hazelwolf!


  • 0

#10 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,899 posts

Posted 02 May 2017 - 05:52 PM

Again, whilst I'm glad that you managed to get that to work, running it in compatibility mode isn't the true answer, it's just masking the culprit from being spotted.

I have a Win10 machine and the full F&LNV plugin list (~127 plugins) and LOOT functions just fine. Without more diagnostic evidence to figure out what is happening, we can't determine what the true solution is.



#11 Skadi

Skadi

    Citizen

  • Mod Authors
  • Pip
  • 86 posts

Posted 08 May 2017 - 10:10 PM

I've been having this issue as well, and I can confirm that running it in compatibility mode for Win 7 fixes it... on Win 7. I dual boot and running it with default settings on Win 10 presents no problems. However, on Win 7 I had repeated crashes until I made this change.
  • 0

#12 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,899 posts

Posted 08 May 2017 - 11:42 PM

Win 7 compatibility mode on Win 7!!  :huh:





Also tagged with one or more of these keywords: loot, mod organizer, falinv, errors

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users