Saints Row 3 keeps crashing. Where to start troubleshooting this?

Discussion in 'PC Gaming' started by alfa147x, Nov 5, 2012.

  1. alfa147x

    alfa147x Lifer

    Joined:
    Jul 14, 2005
    Messages:
    29,842
    Likes Received:
    5
    Saints Row 3 keeps crashing. Where to start troubleshooting this? I really enjoyed the first 15 minutes of gameplay and I'm hooked but the game keeps crashing.

    Code:
    GIGABYTE GA-Z77X-UP5 TH LGA 1155 Intel Z77 Thunderbolt Motherboard 
    Intel Core i7-3770K Ivy Bridge 3.5GHz (3.9GHz Turbo) HD 4000 Graphics
    Asus GTX670 Top (GTX670-DC2T-2GD5)
    Noctua NH-D14 120mm & 140mm SSO CPU Cooler
    CORSAIR Vengeance LP 16GB (2 x 8GB) DDR3-1600
    120 GB OWC Mercury Electra 3G SSD MacSales
    Seasonic SeaSonic X760 -760W 80Plus Gold Certified ATX12V PSU
    SilverStone RAVEN Series RV03
    
    I had Windows 7 64 bit installed and all the latest drivers but it crashed then I wiped that install and installed Win7 32 bit and all the latest drivers and it still crashes. I can play GTA 4 and Diablo 3 perfectly fine and I logged the temps during the crash and I don't see anything abnormal. Any ideas?

    Thanks!
    Alfa
     
  2. Loading...

    Similar Threads - Saints crashing start Forum Date
    Just Cause 3 Keep Crashing PC Gaming May 19, 2017
    Saints Row 4 PC Gaming Oct 8, 2016
    Really need a new Saints Row. PC Gaming Aug 16, 2016
    Saints Row IV : Gat out of Hell PC Gaming Jan 24, 2015
    Saint's Row! PC Gaming Jan 18, 2015

  3. gorcorps

    gorcorps aka Brandon

    Joined:
    Jul 18, 2004
    Messages:
    29,903
    Likes Received:
    195
    Is your gpu overclocked? Even a factory OC can cause some games to crash. Can't imagine it's Windows as I play on 7 64 bit just fine.
     
  4. JamesV

    JamesV Platinum Member

    Joined:
    Jul 9, 2011
    Messages:
    2,003
    Likes Received:
    1
    The place you should start your troubleshooting is the Windows logs.

    Start->Right click on Computer->Manage

    Event Viewer on left->Windows Logs

    Search for entries in Application and other log entries for errors that occur when you crash. Start up SR3 again, get it to crash, and there should be an entry in those logs saying what the faulting module is (or another isssue).
     
  5. alfa147x

    alfa147x Lifer

    Joined:
    Jul 14, 2005
    Messages:
    29,842
    Likes Received:
    5
    Ah. I'm an OS X guy and I never though of looking for a log. I feel stupid. As a hackintosher I use Console a lot to view crash logs.

    I'll post back. Thanks

    Nope everything is stock even the CPU.
     
  6. crisium

    crisium Platinum Member

    Joined:
    Aug 19, 2001
    Messages:
    2,266
    Likes Received:
    261
    Mine crashes in DX 11, but not DX 9.
     
  7. alfa147x

    alfa147x Lifer

    Joined:
    Jul 14, 2005
    Messages:
    29,842
    Likes Received:
    5
    Both crash for me :(
     
  8. DaveSimmons

    DaveSimmons Elite Member

    Joined:
    Aug 12, 2001
    Messages:
    39,456
    Likes Received:
    239
    I have Win 7 64 bit, i5-2500, GTX 680. 8 GB RAM. Everything is stock speed.

    I've played about 30 hours running the DX 11 version without any crashes. This is the Steam version.

    So: it's at least possible that you can get it to work. Sorry I can't offer any tips, I didn't do anything to get it to work, just did the regular Steam install.
     
  9. PowerYoga

    PowerYoga Diamond Member

    Joined:
    Nov 6, 2001
    Messages:
    4,603
    Likes Received:
    0
    same. I'd update graphics card drivers to start and make sure you don't have any corrupt files in the install through steam verification. Dig through logs to see what's causing the crash. Maybe bad ram, maybe power supply suddenly getting spiked and it couldn't handle it... could be a lot of things.
     
  10. power_hour

    power_hour Senior member

    Joined:
    Oct 16, 2010
    Messages:
    789
    Likes Received:
    1
    Couple of things. Trying manually setting the VGA card to 100% then run the game. If game crashes in same spot then either Memory or fragmented or bad files. Check the disk's health.

    But to be honest, more times than not, memory is the culprit. But don't let that sway you from proper troubleshooting steps.