Jump to content
  • 0

CTD When Pressing "Print Screen" to take screenshot


Question

Posted (edited)

So, I just got STEP Extended set up and going, and everything seems to be working pretty well.  

  • I'm running all options except the 101 bugs mod and the Dual Sheath mod.  
  • I selected the HD option whenever it was available.
  • I have no errors or conflicts on Mod Organizer.
  • Game experiences no stuttering, and frame rate has never dropped below 60 fps.
  • I am using NVIDIA GeForce Experience to watch frame rate if it matters.
  • I have confirmed all drivers are up to date.

 

As soon as I got to Whiterun, I was so impressed by the look of the town I decided to take a screenshot, as soon as I press print screen, the game crashes.  I don't know if this is a STEP issue, a Mod Organizer Issue, or something else entirely.  This is a much more complicated mod setup than I've ever used, so I am honestly slightly out of my element here.

 

Any help would be appreciated, and please let me know if there is additional information I neglected to include that could be helpful.

 

Load Order (From loadorder.txt in Mod Organizer):

 

  Reveal hidden contents

 
System Specs in Signature.
Edited by Riverwolf

4 answers to this question

Recommended Posts

  • 0
Posted

Everything in the ini files seems to be correct.
 
When you use PrtScrn without any overriding settings, the screenshots are saved directly in the Skyrim directory (C:/Program Files (x86)/Steam/SteamApps/common/Skyrim) and this can result in a lot of potential issues with permissions, security, etc. If you have a any screenshots in this folder already, move them all to another folder to get them out of Skyrim's executable folder.
 
Check your Skyrim.ini and I recommend settings like this for the screenshots:
 

[Display]
bAlllowScreenshot=1
sScreenShotBaseName=C:\Users\Greg\Pictures\Skyrim\Screenshots\ScreenShot

bAllowScreenshot just allows PtrScrn to take a screenshot so you likely don't need to worry about this one.

 

sScreenShotBaseeName is used to override the default path and prefix used for the screenshots. In the setting above, I redirect the screen shots to my personal Pictures folder so I don't have to muck with the permissions in Program Files. If you set up an override path like this, make sure the entire path is correct and that all the folders already exist. The easiest way to to do this use to use Explorer to create the folders, then click the address bar, and copy the entire path into the clipboard. Finally, open Mod Organizer's INI Editor, and paste this path right after sScreenShotBaseName=.

 

Note that normally when you press PrtScrn you'll see a message like "Saved ScreenShot2.bmp" If you set sScreenShotBaseName, you'll see "Saved C:\Users\Greg\Pictures\Skyrim\Screenshots\Screenshot2.bmp" (with the full path) instead of just the file name.

 

In SkyrimPrefs.ini, check this setting:
 

[Display]
iScreenShotIndex=1

I don't know how Skyrim handles iScreenshotIndex when it reaches the "maximum", so you might consider resetting it back to 1 to see if this makes any difference.

 

Finally, have you installed any third-party screen capture software recently that might be trying to take over when you press PrtScrn?

  • 0
Posted

Are you using F12 (Steam screenshot) or PrtScrn (Skyrim's screenshot)?

 

Also, have you checked the memory settings in skse.ini and enblocal.ini to verify these are correct?

  • 0
Posted

I am using PrtScrn.

 

I believe I have the ini files set up correctly, but it's possible I misunderstood something.   I have SKSE.ini in .\steamapps\common\skyrim\data\SKSE and it contains only the following lines:

 

  Reveal hidden contents

 
As for enblocal.ini, I have it located in .\steamapps\common\skyrim\ 
  Reveal hidden contents
[PROXY]
EnableProxyLibrary=false
InitProxyFunctions=true
ProxyLibrary=other_d3d9.dll
 
[GLOBAL]
UsePatchSpeedhackWithoutGraphics=true
UseDefferedRendering=false
IgnoreCreationKit=true
 
[PERFORMANCE]
SpeedHack=true
EnableOcclusionCulling=true
 
[MULTIHEAD]
ForceVideoAdapterIndex=false
VideoAdapterIndex=0
 
[MEMORY]
ExpandSystemMemoryX64=false
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=512
VideoMemorySizeMb=3746
EnableCompression=true
AutodetectVideoMemorySize=false
 
[WINDOW]
ForceBorderless=false
ForceBorderlessFullscreen=false
 
[ENGINE]
ForceAnisotropicFiltering=true
MaxAnisotropy=16
ForceLodBias=false
LodBias=0.0
AddDisplaySuperSamplingResolutions=false
EnableVSync=true
VSyncSkipNumFrames=0
 
[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=10.0
 
[iNPUT]
//shift
KeyCombination=16
//f12
KeyUseEffect=123
//home
KeyFPSLimit=36
//num /       106
KeyShowFPS=106
//print screen
KeyScreenshot=44
//enter
KeyEditor=13
//f4
KeyFreeVRAM=115
 
[ADAPTIVEQUALITY]
Enable=false
Quality=1
DesiredFPS=20.0
 
[ANTIALIASING]
EnableEdgeAA=false
EnableTemporalAA=false
EnableSubPixelAA=false
 
[FIX]
FixGameBugs=true
FixParallaxBugs=true
FixParallaxTerrain=false
FixAliasedTextures=true
IgnoreInventory=true
FixTintGamma=true
RemoveBlur=false
FixSubSurfaceScattering=true
FixSkyReflection=true
FixCursorVisibility=true
FixLag=false
 
[LONGEXPOSURE]
EnableLongExposureMode=false
Time=1.0
BlendMax=0.0

 
I would appreciate a more experienced eye on these to make sure I set them up properly.
  • 0
Posted

Changing the path for screenshots fixed it!  Thanks a ton, I was worried it was a symptom of something much more serious.  Thanks a ton for the help.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.