Freezing after Aug 30 Patch?

One item I didn't see listed is "Verify Integrity of Game Cache" This is done in steam.
Right click on the game in the steam menu and choose properties, go under the "Local Files" tab and down at the bottom should be the option to verify cache. Click it and it will check the files in SR4 against Steams listing for files/folders and what not.

Note:
If you have any *.asm_pc, *.xtbl, *.lua, or *.str2_pc files in the root directory of Saints Row IV those are left over from a mod you tried to remove.

IdolNinja created a batch file that comes with the SRTT GOSP mod called "Remove_all_SRTT_mods_(MOVE_ME_TO_SRTT_INSTALL_FOLDER).bat"

It will clean all non essential files from SR4 as well (same file types).
http://idolninja.com/blog/?p=1328

Sometimes missing just 1 file can cause the game to crash.
 
Thanks for all the advice, folks! I actually DID try using only 2 cores instead of 4, but that made the game impossible to run even though the title screen. Verifying the Steam game cache was actually one of the FIRST things I tried, I just forgot to put it down.

I'll try beta drivers and the sound bit soon; my wife just had emergency surgery so my time is spent keeping an eye on her. When she gets healthier I'll try these, or maybe they'll have patched the game and it will work again!

Thanks again!
 
Alright! I tried the beta NVIDIA drivers, but still got that same freeze. I think I may just have to give up on playing until a patch is released.

I attempted to contact support (when the problem first started two weeks ago) and used the inspection program they provided to send them a report of my system specs, but have heard nothing back from them.
 
try rolling back your graphics drivers to 314.22 there is a confirmed issue with people on 400-500 series cards after 314.22 check this nvidia thread out:
Code:
https://forums.geforce.com/default/topic/550032/geforce-500-400-series/nvidia-driver-320-49-whql-freezing-my-pc/1

I have an nvidia 460 gtx cyclone and it was effecting me, I did a number of things to fix this issue, I realize these may not all apply to you but they cover hours of research into this issue that was happening with multiple programs.

1. Used DDU (Display Driver Uninstaller) Made by the community at nvidia to do an entire nvidia driver clean up.
Code:
https://forums.geforce.com/default/topic/550192/geforce-drivers/display-driver-uninstaller-ddu-v7-3-2/
after doing this in safe mode, reinstall latest beta drivers available to public, I am on 326.80 which has run stable for several days now without BSOD and or black screen etc.

2. Adjust windows power setting for PCI Express > Link State Power Management (set it to off.)

3. Set nvidia to prefer maximum performance in 3d applications through the nvidia control panel.

4. Turn off hardware acceleration in firefox and internet explorer (google it, I'm a terrible instructor)

5. if you have any realtek soundcards/network cards update both drivers to the latest drivers available.
Code:
http://www.realtek.com/downloads/

6. if you have a ralink wireless product update it to the latest available driver. (Yes the manufacturer drivers are out because another company bought them out and merged you can use the HP ones which fixed BSOD/BLACK SCREEN and they are more up to date than the manufacturer if you have ralink wireless card
Code:
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-122486-1&cc=us&dlc=en&lc=en&jumpid=reg_r1002_usen_c-001_title_r0001

7. if you have any software that uses winring0.sys uninstall it and or delete the associated driver it is well known for BSOD's in game as well as being a security risk (it comes with gamebooster for example even the new razer addition)

8. If you are using nvidia HDMI audio and realtek audio together, consider choosing one or the other and disabiling the one you won't use or disabling your realtek card entirely and buying a cheap replacement, google this as this can cause issues because of driver conflicts there)

8. Look for recently installed windows updates (several have been botched and caused computer issues such as BSODS as recently removed/rolled back KB2859537 for several editions of windows) you can find more information on the latest botched windows updates and their effects here:
Code:
http://news.softpedia.com/cat/Microsoft/Patches-and-Vulnerabilities/

2ih6qty.jpg


 
Last edited:
Mayoko, you are wonderful! Rolling back the driver to 314.22 seems to have fixed my issue!

Though now I have an infinite loading screen before the Keymaster quest, but that's a totally different bug and I'll look for solutions before coming for more help.

Thank you!
 
Back
Top