Jump to content

Photo

That damned 1 file that won't validate


  • Please log in to reply
29 replies to this topic

#11
onioning

onioning

    Newbie

  • Supporter
  • Pip
  • 15 posts

Going through this may help especially section 3

Skyrim Project Stability

 

Going through these suggestions now. Some (like cleaning up the startup programs and services) I've already done. Just mentioning it in case it becomes relevant.



#12
onioning

onioning

    Newbie

  • Supporter
  • Pip
  • 15 posts

Drifting off topic a bit, but just 'cause my searching has failed me again, is it safe to use the Revo Uninstaller w/ a SSD?



#13
Lord Garon

Lord Garon

    Old hand

  • Members
  • PipPipPip
  • 880 posts

Ok. Undid the system change I made from the linked page. Reverted to the base skyrim.ini. Set BOSS, NMM, SKSE, Steam, and Skyrim (TESV) to administrator access. Loaded via SKSE, tried "coc riverwood," started to load, and crashed.

 

Edit: And same results if I start from TESV.exe. Same results if I load a game.

 

Also, is it sufficient to set the properties of a shortcut to "administrator," or do I need to find the actual file? I have the shortcut to SKSE set to have administrator access, but I don't seem to have that option when I go to the actual .exe file in my Skyrim folder.

 

Okay, thanks for doing all that.

 

When a CTD occurs during a load, its almost always an out-of-order/missing masterfile (.esm) or missing game object. Let's check:

 

1. Run BOSS GUI (Start-->All Programs-->BOSS   Right-click BOSS GUI and Run as Administrator

2. Change the BOSS log format drop-down to "Plain Text" (Makes it easy to post your log in the forum)

3. Make sure "Show BOSS Log on Completion" is checked, and that Sort Plugins is ticked with Update Masterlist checked

4. Click "Run BOSS" button.

 

The log will come up in Notepad. Select All and copy everything. When you reply, click on the third icon (little box thingy) in the upper left of the post editor and select Spoiler from the BBCode dropdown. Paste the BOSS log into the small text window. Close the log and the BOSS GUI screen. You can look at the log again by running BOSS GUI and just clicking the "View BOSS log" button.

 

Even though BOSS is doing it's thing, we need to make sure Skyrim is seeing it. Run Skyrim from Steam again. On the launcher screen, click DATA FILES and compare that list to your BOSS log; the DATA FILES list should be in the same order as the esm and esp files in the BOSS log and all should be checked (active). The BOSS log will have more entries, just make sure the DATA FILES list order is correct. (Note that some users get the Unofficial Patch esp's out of order with BOSS; just select them in DATA FILES and use the little arrows to move them just below the esm files they go with.) The reason for doing all this is related to file permissions in the directory where your load order files (loadorder.txt and plugins.txt) are kept.

 

Click OK, click PLAY, and when the load screen comes up, just exit. Now try to start Skyrim normally via SKSE. You can either try the "coc riverwood" at the load screen, or try to load a save, or even try a new game.

 

IF it still doesn't load: Go to your Skyrim Saves folder. There is an SKSE folder there; inside will be a few log files. Open up skse.log in Notepad and look for any file loading errors, or just post it here in Spoiler tags.


Edited by Lord Garon, 09 March 2014 - 01:08 AM.


#14
onioning

onioning

    Newbie

  • Supporter
  • Pip
  • 15 posts

BOSS log. Checked it against the data files reported by the launcher, and the order matches up.

 

Spoiler

 

And the SKSE log, just after I tried to load and it crashed.

 

Spoiler



#15
Lord Garon

Lord Garon

    Old hand

  • Members
  • PipPipPip
  • 880 posts

Thanks, again. I know this is a pain, but I'm just trying to eliminate related issues as we go on.

 

At this point, we need a baseline savegame. We'll go to NMM now:

 

1. On the main NMM screen, select the Plugins tab.

2. In the very left edge, click "Disable all the active plugins"

3. Enable only: Update.esm, the DLC but NOT HiResTexturePacks, the Unofficial Patches but NOT Unofficial HiRes patch. You should only have 9 plugins total enabled, Skyrim.esm will be automatically enabled.

4. Close NMM first, then fire up Skyrim as you normally would, restarting NMM if necessary.

5. We need a new savegame, but need to get Skyrim running first. At the load screen, you can try the "coc riverwood" again, or start a NEW game. Try both, but no savegames.

6. If the game still won't load, disable ALL active plugins and try again.

 

You were following the Stability Guide; did you make any major changes or additions/deletions?

 

BTW: Wrye Bash is a very useful tool for doing things besides mod management. If you would like to play with a new tool while troubleshooting, download it and we can check some things in your savegames.

 

EDIT: If the new game starts okay, you might try to enable the other plugins except for, ironically, Safety Load, and see if the savegame will load.


Edited by Lord Garon, 09 March 2014 - 08:23 PM.


#16
onioning

onioning

    Newbie

  • Supporter
  • Pip
  • 15 posts

Thanks, again. I know this is a pain, but I'm just trying to eliminate related issues as we go on.

 

 

Dude. That's not the way the thanks be flowin' here. I'm the one being helped.

 

And some big success. I can get any save running by excluding the HR packs. I still get the "some items are no longer available" with my more advanced saves, but I think that's a remnant of playing around too much with mods w/out doing so under the safety of a reserved save. In other words, I think I installed then uninstalled significantly before all this started. The game seems to run fine, I just get that warning before I start my later saved games.

 

This makes me wonder though. Going back to what I originally did to get the game running, w/ the config change, as I understand it, that was an attempt to fix a memory allocation error. And it worked. It ran pretty well w/ those HR texture packs. So is there a safer/better way to get those results? I mean, I'm happy to be able to play again, but those HR packs were pretty nice...

 

Edit: I'm still getting occasional crashes. So far I just load it up again and am able to continue. Been two crashes in a little over an hour. 



#17
onioning

onioning

    Newbie

  • Supporter
  • Pip
  • 15 posts

You were following the Stability Guide; did you make any major changes or additions/deletions?

 

Dropped a few services that I hadn't already. Went through the list on that guide and there were some I had running as automatic. That was about it. 



#18
Lord Garon

Lord Garon

    Old hand

  • Members
  • PipPipPip
  • 880 posts

 

Thanks, again. I know this is a pain, but I'm just trying to eliminate related issues as we go on.

 

 

Dude. That's not the way the thanks be flowin' here. I'm the one being helped.

 

And some big success. I can get any save running by excluding the HR packs. I still get the "some items are no longer available" with my more advanced saves, but I think that's a remnant of playing around too much with mods w/out doing so under the safety of a reserved save. In other words, I think I installed then uninstalled significantly before all this started. The game seems to run fine, I just get that warning before I start my later saved games.

 

This makes me wonder though. Going back to what I originally did to get the game running, w/ the config change, as I understand it, that was an attempt to fix a memory allocation error. And it worked. It ran pretty well w/ those HR texture packs. So is there a safer/better way to get those results? I mean, I'm happy to be able to play again, but those HR packs were pretty nice...

 

Edit: I'm still getting occasional crashes. So far I just load it up again and am able to continue. Been two crashes in a little over an hour. 

 

 

Hey, this is teamwork.

 

Its a little strange to me that the HiRes packs affect a load screen CTD, but we'll get them to work. Or know why not. However, I'm in uncharted water here due to the 32 bit Windows you are running. I'm not certain that some very useful mods I'm going to recommend will work as advertised on your system, but, neither am I certain they won't work.

 

Skyrim has some known memory issues. There are three common "Memory Patches" which attempt to limit memory issues with Skyrim. The first was an official patch from Bethesda; it included the LAA fix and everyone has it. The second one was Boris' ENBseries. The third one is Sheson's heap allocation fix. NOTHING helps Skyrim like these memory fixes. But, the last two were made and tested on 64bit Windows platforms. No matter; before we go on, let's give your setup the best chance of succeeding:

 

1. Install the latest ENBseries from the enbdev website. Don't worry, we're not gonna load down your system with an ENB, just use its memory offload capability. This install is NOT a mod and the enbseries files go in the Skyrim game directory, NOT in the Data directory. You can just open the downloaded archive with 7zip, select the following three files from the Wrapper directory and drag them to your Steam\SteamApps\common\Skyrim direcory:  d3d9.dll, enbhost.exe, enblocal.ini

 

Open enblocal.ini in Notepad and set the following entries:

 

[GLOBAL]
UsePatchSpeedhackWithoutGraphics=true

 

[MEMORY]
ExpandSystemMemoryX64=false

ReduceSystemMemoryUsage=true

VideoMemorySizeMb=1024
 

The enbseries will offload some data from Skyrim (tesv.exe), lowering ram and vram use.

 

2. Install the SSME patch. This is Sheson's heap allocation (generic memory) fix implemented by a well-known modder/programmer and prevents a major cause of Skyrim CTD's. Like Enbseries, it goes in the Skyrim directory, not Data.

 

Once those two are in, disable/uninstall Safety Load (no longer needed) and test. If its okay, enable the HiRes packs and see if the game loads. In case there is a file issue with a HiRes pack, you can enable them one at a time and see if a particular pack is causing the issue.


Edited by Lord Garon, 10 March 2014 - 02:59 PM.


#19
IsharaMeradin

IsharaMeradin

    The Pale Redguard

  • Members
  • PipPipPipPipPip
  • 4,635 posts

Something I noticed that might help...  I've not seen stated by the OP how much RAM and VRAM they have available.  The OS, CPU and GPU are there but not the memory.  Might help to know how much memory is available...

 

 

Edit: my fingers typed slower than my brain and I missed a word or two   :P


Edited by IsharaMeradin, 10 March 2014 - 03:34 PM.


#20
onioning

onioning

    Newbie

  • Supporter
  • Pip
  • 15 posts

8 Gs installed. Strongly considering adding another 8 Gs, mostly 'cause it's easily done. I let myself be talked out of 16 Gs when I put this computer together (which is only about a month ago). Now I kinda regret it. I also regret not spending more on the graphics card, but it's much easier and justifiable to add the memory than to replace a graphics card I just bought... I do have the 64 bit version of Windows 7 on this machine (Windows Ultimate), but as I understand things, I'm not using it because of the 8 Gs of RAM available. 

 

If memory serves me, VRAM is virtual RAM, or a portion of the hard drive set aside for RAM. Not sure how to check that... Also not sure how having the SS drives affects that, though I do have a conventional HD as well. 

 

Made the changes suggested above. Been "testing" (i.e., joining the Thieve's Guild...) for only about 20 minutes. I did have one crash. Reloaded and continued on my way. 

 

Edit: I'll also note that these are proper crashes. The game stops running immediately and entirely. That's as opposed to the stuck screen I was getting before that required Task Manager to end.






Page loaded in: 2.788 seconds