EVGA

driver crash in No Man's Sky 3080 with 456.71/456.38 drivers

Author
sinewave
New Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2005/08/23 18:40:35
  • Status: offline
  • Ribbons : 0
2020/10/12 11:28:30 (permalink)
Getting an nvidia driver crash fairly reliably (within 15-30min of playing) in No Mans Sky on my 3080 XC3 at stock clocks. This happens on all the 30* series (456.71/456.38/456.55) drivers.
 
Anyone else having this experience? Is this likely HAGS, nvidia driver, or 3080 stability?
post edited by sinewave - 2020/10/12 13:54:10

CPU: 9700k @4.8ghz
GPU: 3080 XC3 Ultra
PSU: Corsair RM850X
RAM: 2x16gb G.Skill TridentZ
SSD: Samsung 970 Evo 1 TB
MOBO: Asus Z390-i
CASE: Corsair Crystal 280X
#1

6 Replies Related Threads

    arestavo
    CLASSIFIED ULTRA Member
    • Total Posts : 6916
    • Reward points : 0
    • Joined: 2008/02/06 06:58:57
    • Location: Through the Scary Door
    • Status: offline
    • Ribbons : 76
    Re: driver crash in No Man's Sky 3080 with 456.71/456.38 drivers 2020/10/12 11:44:52 (permalink)
    Turn off HAGS and test, try 456.55 drivers as well if that doesn't fix it.
     
    I can try later today to see if NMS crashes for me and my 3090 FTW3.
    #2
    spoonyspork
    New Member
    • Total Posts : 21
    • Reward points : 0
    • Joined: 2018/08/21 19:29:34
    • Status: offline
    • Ribbons : 0
    Re: driver crash in No Man's Sky 3080 with 456.71/456.38 drivers 2020/10/12 12:26:28 (permalink)
    I'm on 456.55 with 3080 FTW3 Ultra -- played for three hours last night without issue. I do NOT have HAGS enabled. This is actually the very first I've even heard of that feature, somehow.
    #3
    arestavo
    CLASSIFIED ULTRA Member
    • Total Posts : 6916
    • Reward points : 0
    • Joined: 2008/02/06 06:58:57
    • Location: Through the Scary Door
    • Status: offline
    • Ribbons : 76
    Re: driver crash in No Man's Sky 3080 with 456.71/456.38 drivers 2020/10/12 13:49:56 (permalink)
    No crashing for me (4K ultra settings), but I've never enabled HAGS (too new and too many problems from what I've read). Well, except for that big, semi translucent square around the mouse pointer that I had the last time I played this game in 2017.
    #4
    spoonyspork
    New Member
    • Total Posts : 21
    • Reward points : 0
    • Joined: 2018/08/21 19:29:34
    • Status: offline
    • Ribbons : 0
    Re: driver crash in No Man's Sky 3080 with 456.71/456.38 drivers 2020/10/12 14:42:30 (permalink)
    Just wanted to say I just enabled HAGS and played for about an hour with no issues (and I have no idea if HAGS had any effect or if it was just placebo, but I *think* things were running a bit smoother)
    #5
    sinewave
    New Member
    • Total Posts : 19
    • Reward points : 0
    • Joined: 2005/08/23 18:40:35
    • Status: offline
    • Ribbons : 0
    Re: driver crash in No Man's Sky 3080 with 456.71/456.38 drivers 2020/10/12 14:59:08 (permalink)
    Well there we go, lack of consensus is unfortunate - makes me worry that the 3080 XC3 sample I pulled is not great!

    CPU: 9700k @4.8ghz
    GPU: 3080 XC3 Ultra
    PSU: Corsair RM850X
    RAM: 2x16gb G.Skill TridentZ
    SSD: Samsung 970 Evo 1 TB
    MOBO: Asus Z390-i
    CASE: Corsair Crystal 280X
    #6
    Arkiverge
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2020/10/03 08:48:02
    • Status: offline
    • Ribbons : 0
    Re: driver crash in No Man's Sky 3080 with 456.71/456.38 drivers 2020/10/14 17:17:05 (permalink)
    I've had the issue before and after getting the Win10 2004 update that included HAGS (installing 2004 and disabling HAGS made no difference) as well as both the 456.55 and 456.71 drivers.  I've tried all manner of testing to reliably reproduce or scrutinize the source and I'm still unsure.  Of the 50 or so crashes I've had, about 90% are the in the first 5 minutes, usually just after loading in or when loading into another area.  About another 10% of the crashes occur within 25 minutes of that (the first half hour or so) and no real rhyme or reason (but it's frequently during or just after coming out a menu/dialog).  Ironically after the first 30m I'm not sure I've ever had it crash, and I've got quite a few 3+ hour sessions logged.  Very weird, almost linked to texture caching/access.  Also, I've downclocked the core/memory by 200/400 and still get the crashes meanwhile all of my other games have run flawlessly (not one crash/artifact) at stock speeds and I can run Kombustor/3DMark with a 50/100 overclock for extended periods with no issues, so I'm not inclined to think I have a bad card.
    post edited by Arkiverge - 2020/10/14 17:19:08
    #7
    Jump to:
  • Back to Mobile