Blender Crashes when Trying to Edit Armors

[user826]

I can't even get BSArch to run. The window doesn't stay open long enough for me to type any commands, even when run as admin. But I don't see what difference it makes? Even if I copy a NIF over from my desktop, which I'm able to edit in Blender over there, it crashes on the laptop.

 

EDIT: It turns out that the import settings that I choose plays a part in whether or not it crashes. If I import weapons using the armor import settings, I can edit the mesh, but if I import them using the weapon import settings, it crashes as well. So now, it basically means I can't edit weapons either. These are the import settings I'm using:

 

Armor settings:

 

 

Weapon/Object settings:

 

 

I also tried uninstalling everything and reinstalling them in the following order: Python, Blender, PyFFI, and Nif Scrips, but it still crashes.

Edited October 4, 2019 by user826

[dubiousintent]

Back to basics then. Did you install Blender and the related apps to "C:\Program Files" folder trees? If so, that gets back to the whole Windows considers those trees to be "protected files" and doesn't allow changes to anything, including INI or other configuration files. Try installing them elsewhere.

 

BSArch has to be run from the "Command Prompt" line (used to be called the "DOS Prompt"). You can configure a general shortcut to open the "Command Prompt" window with the target line of:

%windir%\system32\cmd.exe

This keeps the "command line" window open until you type in "exit" followed by the <Enter> key to close it so you can see the results of the command(s). (Or click on the "x" box in the window upper right corner to close the window.) Within that open window you can use the "pushdir <drive:\folder>" command to make your new default folder where the BSArch file is located and then enter the appropriate commands. You can use "popdir" to return to the previous default folder if you want.

 

Or you might want to configure the BSArch shortcut so the "Target" line reads:

"%windir%\system32\cmd.exe" "<path to the BSArch.exe>" <archive> [parameters]

You need to surround the command with double quotation marks if there are any embedded spaces (as shown). It never hurts to do so if you aren't sure.

 

See the "bsarch_ReadMe.txt" file.

 

-Dubious-

[user826]

I installed Blender to my E:/Modding/Fallout/Tools folder, so not only is it not in any kind of protected directory, it's not even on the boot drive at all.

 

I'm going to give BSArch another shot, but I'm not optimistic that it'll make any difference.

 

EDIT: As expected, even the armors I extracted using BSArch cause Blender to crash when I try to enter Edit Mode.

Edited October 4, 2019 by user826

[dubiousintent]

It's a puzzle. That the only limited success you had was importing armor using the weapon settings suggests the install screwed up. Have you tried re-installing Blender and the related apps/tools?

 

That you can't save settings suggests an access privilege problem, which is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders.

 

You might want to review Installation of Blender (Wiki article) just to ensure you didn't overlook something. Otherwise you might want to ask on one of the "Blender Communities" for assistance.

 

Did you get anything from the Windows Eventlog?

 

-Dubious-

[user826]

No joy. I uninstalled everything, including NifSkope, then restarted the computer and followed the guide step-by-step, even installing the older versions of Python (2.6.5 instead of 2.6.6) and Nif Scripts, but it still doesn't work.

 

However, trying to apply the security settings onto the E:/Modding/Fallout/Tools folder threw up several Error Applying Security warnings, one for each folder in the Tools folder. "Failed to enumerate objects in the container. Access is denied." So, I went through and applied the settings to each folder manually, giving "Full Control" for Users, but this still didn't fix things.

 

Windows Event Log doesn't even show up when Blender crashes. As soon as I try to select a piece to modify, the mouse turns into the blue spinning ring for a second, then the Blender windows disappear.

[dubiousintent]

My apologies. You got the "access denied" message because I failed to specify that you have to be using an "Administrative Privileges" account when attempting to apply/change security settings on folders. (Any time you are trying to change security or device settings you have to do so as an "admin".)

 

Most Windows Eventlog entries do not result in a visible indication. Those tend to be reserved for events affecting the OS itself which prevent it from handling things correctly and unobtrusively (not an application such as a game). You have to manually examine the log starting under the "Applications" tab, but also including the "System" tab as well.

 

-Dubious-

[M48A5]

Is there a reason you are using an outdated version of Blender? The current version for FNV and FO3 is 2.49, not 2.48 as shown in your screen shots.

 

Also, Python 2.6.5, PyFFI 2.1.5, NifScripts 2.5.5 and NifSkope 2.0 are the ones you should be using.

[user826]

@M48A5 - I am actually using Blender v2.49b, but those are not screenshots I took myself, those are my reference images which I found online so that I know what settings to enable.

 

@Dubious - The account I'm logged into is already an Administrator account. Do I have to do any other special settings? Also, the Event Viewer shows me the following details:

 

Faulting application name: blender.exe, version: 0.0.0.0, time stamp: 0x4a9c5ce5
Faulting module name: ig9icd32.dll, version: 23.20.16.5038, time stamp: 0x5ad7a830
Exception code: 0xc0000005
Fault offset: 0x004be036
Faulting process id: 0x19fc
Faulting application start time: 0x01d57bbc94ed24aa
Faulting application path: E:\Modding\Fallout\!Tools\Blender\blender.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_ceddadac8a2b489e\ig9icd32.dll
Report Id: 373bdc03-b4c7-4354-8560-1732affb1152

 

Apparently, the exception code 0xc0000005 refers to a memory access violation, and ig9icd32.dll is an Intel graphics driver DLL. I'm going to try updating my drivers and see if that helps.

 

EDIT: Sigh... Still no luck. I updated both my Intel and NVIDIA drivers to the latest version and it still crashes. The Event Log still says ig9icd32.dll is the faulting module.

Edited October 6, 2019 by user826

[dubiousintent]

If you are using an "Admin" account, then you shouldn't have an access problem changing the security settings. You might try booting into "Safe Mode" and try then using the Admin account.

 

As you say you have both an Intel graphics driver and NVIDIA drivers, I would suggest you try disabling the Intel video (which is probably an "on-board" chip needing to be disabled in the BIOS) and try with just the NVIDIA. If that doesn't help, try the reverse. (You should only need one video adapter source and on-board chips are compromises compared to dedicated video cards.)

 

Re: "Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program writing into the memory area of the "faulting module" rather than the actual culprit, making it virtually impossible for the user to trace the source. Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections. There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude "faulting application" from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)" (or Microsoft's "Enhanced Mitigation Experience Toolkit (EMET)" for Win7). Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering. There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

-Dubious-

[user826]

SUCCESS! It turns out that having both the integrated graphics chip and the GPU running at the same time was the problem. While I wasn't able to disable the integrated graphics chip in BIOS, I just did it using the Device Manager and it worked! Now, I can toggle it off whenever I need to use Blender and then turn it back on when I'm done. Thanks so much for your patience and help with this issue!

 

EDIT: I found a better, more permanent solution and thought I should document it for posterity. My laptop has an NVIDIA GPU, but there may be a similar option for different manufacturers. In any case, right-click on the desktop and select NVIDIA Control Panel. When the new window opens, select "Manage 3D Settings" from the pane on the left. In the pane on the right, select the "Program Settings" tab. Here, you can add a special case handling option for Blender. Click "Add" beside the drop down menu under step one and browse to wherever you installed blender.exe. Under step two, choose "High-performance NVIDIA processor" from the drop-down menu. This tells the computer to always run Blender using the GPU instead of integrated graphics, and will save you from having to manually disable the integrated graphics chip every time you start up Blender.

Edited October 9, 2019 by user826