EVGA

Either my gpu is bad or SW Battlefront is bad. How to be sure?

Author
Fumigator
Superclocked Member
  • Total Posts : 184
  • Reward points : 0
  • Joined: 2011/05/25 17:55:45
  • Status: offline
  • Ribbons : 0
2016/05/13 16:06:34 (permalink)
Hi guys,
I'm wondering what exactly I should do to solve my problem?
 
Short history: my 2500k or my p-67 pro decided it wanted to retire early in March. One day Rainbow6 Seige started throwing black screens, followed by the message, "no input device" from my monitor. At first it happened once in a while, then frequently. It got to the point where I couldn't even play a round. Also, the system would no longer hold an overclock, so I updated with a new psu, new mobo, new cpu, new ram, new ssd: Seasonic Platinum 760, Asus z170 pro gaming, 6600k, g.skill 3200 cl14, Samsung 850 pro.
 
Everything was fine, for ~ a month. Since Rainbow6 went to crap, I started playing SW Battlefront. At first I thought my problems were solved. I would play a round or two here and there while testing my overclock stability. However, I started seeing a lot of directx crashes, tdr's, and just about 20 minutes ago, the dreaded no input. At first I thought it was my overclock, but it's now happening running the cpu at stock. I've never overclocked the card (didn't need to), so there's nothing to undo on that end.
 
The system is stable in all other respects. Passed 8 hours memtest with zero errors at 3200MHz cl14 at stock and at 4.5GHz. The system has also passed RealBench, OCCT, and Prime95 v26.6 stock, at both 4.5GHz and 4.6GHz for an hour each.
 
The only other games I have installed are Wolfenstein Old Blood and Tribes Ascend (just moved to Seattle, all my stuff is in storage). I can play these for hours stock or overclocked. I've tried every single driver set (beta included) from 358.50 to the current 365.10's. Battlefront crashes with them all the same way: sometimes a black screen, sometimes the game crashes with no message that I can see, sometimes directx error telling me I don't have a card... which... yeah...
 
Other tools which have zero issues are Valley, Cinebench, Aida64, and 3DMark. I noticed that there may be an issue with gtx 780's and Battlefront, but can't be sure because internet: https://forums.battlefront.starwars.ea.com/discussion/11617/regarding-dx-crashes-for-nvidia-780-780ti-users
http://forums.battlefront.starwars.ea.com/discussion/8754/repetitive-direct-x-crash-nvidia
However, these are my exact issues.
 
Temps are not an issue. Recently installed a Noctua NH-D15 with both fans; stressing the cpu with OCCT or Prime max temps are 70C no matter the voltage I've applied. I also run Precision every once and a while and gpu temps are always ~ 60C.
 
What test can I run to make sure my card isn't bad that I haven't tried? Has anyone deal with this Battlefront issue?
 
Thanks in advance for your time.
 
 
 
post edited by Fumigator - 2016/05/13 16:16:58

i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
Asus Prime Z270 AR
Noctua NH-D15/ Kryonaut Thermal Grizzly
16GB G.Skill 3200MHz 14-14-14-34
EVGA GTX 1080Ti SC Black iCX
Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
Creative Recon3D
Seasonic Platinum 760
Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
BenQ XL2720Z-rev2
Logitech Z-5500
Lian Li K62
#1

16 Replies Related Threads

    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/13 16:21:48 (permalink)
    I see you're running a 780 SC. Please try retesting sw battlefront with the card running in debug mode. Information on debug mode can be found here under #3.
    #2
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/13 16:50:16 (permalink)
    Hi Sajin,
     
    Thanks for the reply.
     
    Just ran a quick game of Battlefront in debug mode with the cpu at stock with 365.10's. It crashed after ~ 10 min with the DirectX function error. What now?
     
    *edit*
     
    One of the suggested tips is to reinstall the c++ redist, which I seem to do almost daily now. Also, it's been my experience that once this crashing starts, the only thing that will make it stop is a driver reinstall, and then, that only works for a little while... and by that I mean playing more than 1 round at a time, which is bad because then I never get the play the other side of the map.
     
    **edit2x**
     
    Since my stuff is in storage, do you have any idea where I can get the driver that came with the card? The earliest I can find on nvidia's site are the 352.86's.
     
    ***edit3x***
    /sigh....
     
    I suppose I should also mention that the last few times I've uninstalled drivers the monitor loses signal right after I'm asked to reboot. Just happened again now. Have to press the reset button to get it to reboot... which is met with a "windows didn't shut down properly" message.
     
    I'm getting the impression this card is not long for this world.
    post edited by Fumigator - 2016/05/13 17:15:11

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #3
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/13 17:33:35 (permalink)
    Are you running any monitoring utilities while you play the game? If yes, close them all out before you play.
     
    Try running driver 347.88 to see if it helps with the problem.
    #4
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/13 17:43:40 (permalink)
    When overclocking I was running HWMonitor. I tried with it off after confirming temps were safe, same issue. Oddly, the one thing that has allowed me to play the longest without crashes is running Precision... it's almost like it knows I'm keeping an eye on it so it behaves. Although that doesn't last long either. On or off same thing. Just reinstalled the 356.10's without experience; I'll give those another whirl after dinner. I'll also try the new 365.19's and the 88's you linked (thank you!).
     
    **edit**
     
    365.10 no experience: crash after 10 min.
    347.88 no experience: driver 358.91 or later required to play game message.
    365.19 no experience: internet crapped out ~ 5 min in. i'm in wallingford seattle and a raccoon got into sub station the other night and killed power for 40k. ever since we've been having strange electrical issues, losing the internet and having the house alarm go off happens about every 3-5 hours.
     
    when it rains it pours.
     
    **edit2x**
     
    I suppose I should mention that when uninstalling the 365.10's that I lost signal again... this time before I was asked to reboot... the screen just went black on me and the system light turned orange. That's got to indicate something very wrong, right? Stuff like this just never happened with this card before.
    post edited by Fumigator - 2016/05/13 22:35:36

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #5
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/14 16:22:06 (permalink)
    Not sure if this update is good news or bad, but here it is:
     
    365.19's debug mode played all night last night. Not a single crash. This was at stock then at 4.6GHz. Played quite a bit this afternoon @ 4.6GHz and not a single crash either. This is unusual because prior I could, without fail, crash at 4.6GHz despite every tool telling me the rig was stable. 4.5GHz would let me play a round or two here and there, but 4.6 was immediate crash. I have to say though... running in debug mode is noticeably slower. The card just doesn't feel good at all. Maybe it's just this driver set and this game, but wow... stock clocks on this card feel terrible. I'll try the 365.10's again later today.

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #6
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/14 16:28:51 (permalink)
    So you had no crashes at stock cpu/gpu clocks while running 365.19?
    #7
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/14 16:37:56 (permalink)
    Not a one.
     
    Bout to install 365.10 and give them another whirl.

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #8
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/14 16:55:04 (permalink)
    Hmm. Maybe the issue was finally fixed in driver 365.19?
    #9
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/14 17:09:47 (permalink)
    Sajin
    Hmm. Maybe the issue was finally fixed in driver 365.19?


    I think I misunderstood? This was all done in debug mode, so "stock clocks" = reference. Haven't mustered the courage to try regular clocks...
     
     

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #10
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/14 17:17:38 (permalink)
    Fumigator
    Sajin
    Hmm. Maybe the issue was finally fixed in driver 365.19?


    I think I misunderstood? This was all done in debug mode, so "stock clocks" = reference. Haven't mustered the courage to try regular clocks...

    Oh, ok. Try regular clocks on the gpu and stock on the cpu next.
    #11
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/15 01:28:07 (permalink)
    Sajin
    Hmm. Maybe the issue was finally fixed in driver 365.19?
    Oh, ok. Try regular clocks on the gpu and stock on the cpu next.

    I dared to get optimistic and rebooted to stock cpu. Could this be? Loaded up the game and played a round, then 2 with none of that gpu killing debug stuff. What's this? Could this be? Then the next map came and I managed to get through that too. OMG! YES!! It's fixed... I said to myself as I was enjoying the mythic second side of the 2nd map. My wife tells me a grin appeared on my face. I say pics or it didn't happen. Third map loaded and I was about to call it good when the screen froze and the error came. :(
     
    Experience tells me that to get rid of this cascading I need to reinstall the drivers and repair the c++ redist. In the middle of the driver uninstall the screen lost signal... which seems to be a pattern: if I uninstall drivers directly after one of these directx errors without rebooting inbetween the error and the uninstall, I lose signal. Instead of pressing the machine's reset button I just went ahead and hit enter, because despite not being able to see anything, I kinda knew the process was still going on behind that black screen... and it was. The machine rebooted with no 'you're bad at closing windows' message.
     
    That was 365.19.
     
    I installed 365.10, rebooted to 4.6GHz, went into debug mode and have been playing for the last couple hours straight, not a crash or error message in sight; although, again, I hate running in debug mode; fps is down, even at 4.6, and things just don't feel right. Fairly certain I don't have to bother testing 356.10 at stock cpu speeds?
     
    What's the verdict?
    post edited by Fumigator - 2016/05/15 01:37:21

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #12
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/15 13:49:52 (permalink)
    Fumigator
    What's the verdict?

    Time to rma the card or buy a new one.
    #13
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/15 14:34:10 (permalink)
    Given the timing, neither option sounds appealing. I was sorta hoping to hear some voltage razzle-dazzle.

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #14
    Fumigator
    Superclocked Member
    • Total Posts : 184
    • Reward points : 0
    • Joined: 2011/05/25 17:55:45
    • Status: offline
    • Ribbons : 0
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/27 16:59:28 (permalink)
    Well, it turns out the gpu was bad after all. Did the rma (cross shipped) and I've been putting the new card through quite the workout all week. Not a single issue, game crash, or error message at any clock speed. Kinda sad... I loved that 780. On the bright side, evga sent me a 970 sc, so I think I'll be able to hold off on a 1080 until the Ti's come out.
     
    So, a big thank you to evga. This is expressly the reason why I keep buying evga stuff. Now hurry up with the 1080Ti's. :-)

    i7 7700k @ 4.9GHz delidded/Conductonaut Thermal Grizzly
    Asus Prime Z270 AR
    Noctua NH-D15/ Kryonaut Thermal Grizzly
    16GB G.Skill 3200MHz 14-14-14-34
    EVGA GTX 1080Ti SC Black iCX
    Samsung 950 Pro/850 Pro/ WD RE2/ 8TB WD Red
    Creative Recon3D
    Seasonic Platinum 760
    Deathadder Elite / Artisan Hayate Othu/ Quickfire TK
    BenQ XL2720Z-rev2
    Logitech Z-5500
    Lian Li K62
    #15
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49167
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/27 18:30:45 (permalink)

    #16
    XrayMan
    Insert Custom Title Here
    • Total Posts : 73000
    • Reward points : 0
    • Joined: 2006/12/14 22:10:06
    • Location: Santa Clarita, Ca.
    • Status: offline
    • Ribbons : 115
    Re: Either my gpu is bad or SW Battlefront is bad. How to be sure? 2016/05/28 19:00:58 (permalink)
     
    Glad you got fixed up.      

                My Affiliate Code: 8WEQVXMCJL
     
            Associate Code: VHKH33QN4W77V6A
     
                 
     
     
                      
     
     
     
              
     
       
     
               
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     



     
     
     
     
     
     &nbsp
    #17
    Jump to:
  • Back to Mobile