Just to note currently (and for a while now) SWTOR has had an issue with some Nvidia cards. The "fix" there is to downclock them by 25~100Mhz when playing.
I won't say that will fix it here but it might be worth a try as it sounds like a similar issue. If you want more information on the SWTOR issue just Google "SWTOR drivers crash" and there are some official forums thread and Reddit posts.
lawliet675 wrote: »I have a similar issue with a machine with windows 10, a laptop MSI GX70 3CC with a AMD processor and graphics and i have the last drivers in my laptop, and this issue i have in the last update of the game. But i can't even play, and I can't login, just open the game, and crash my display driver. All other games run well. But not with TESO. Please fix this.
lawliet675 wrote: »I have a similar issue with a machine with windows 10, a laptop MSI GX70 3CC with a AMD processor and graphics and i have the last drivers in my laptop, and this issue i have in the last update of the game. But i can't even play, and I can't login, just open the game, and crash my display driver. All other games run well. But not with TESO. Please fix this.
@lawliet675,
Wow, that's even worse.
I have an idea forming in my head though - especially since this is now two completely different chipsets... how far into ESO do you get? The login screen, enter your info and then boom?
I'm beginning to think it's something like this:
ESO calls DirectX to do Y, but under Windows 10 that operation isn't allowed (or not implemented) and the display driver crashes and restarts.
Might be related to one (or more) graphics settings in ESO.
(I'm gonna do some tests.)
So far (different settings in ESO), no change.
I did run Witcher 3: Wild Hunt overnight, no display driver crash after 13 hours. (I chose it because ESO and Witcher 3 are both DirectX 11 games.)
WalkingLegacy wrote: »Sounds like some driver sweeps are needed.
Google driver sweep. Use that to wipe out all graphics and audio drivers, reboot and reinstall your video and audio driver.
I use to have TRIM crashes all the time with W7. Had conflicting audio drivers and sidegrading (joke because w10 sucks) to W10 would cause same game crashes because MS thought my mobo was missing its audio driver when it's not. I have a dedicated sound card.
WalkingLegacy wrote: »Sounds like some driver sweeps are needed.
Google driver sweep. Use that to wipe out all graphics and audio drivers, reboot and reinstall your video and audio driver.
I use to have TRIM crashes all the time with W7. Had conflicting audio drivers and sidegrading (joke because w10 sucks) to W10 would cause same game crashes because MS thought my mobo was missing its audio driver when it's not. I have a dedicated sound card.
My Windows 10 is a fresh install. I mean.... fresh. There is no leftover crap.
Be careful also with third party utilities like that, a lot of them are crapware (at best) and malware (at worst).
( I'm not entirely thrilled about Windows 10 but at some point Windows 7 isn't going to be supported anymore.)
WalkingLegacy wrote: »What Nvidia driver are you using?
STACK_TEXT: ffffd001`17a185a0 fffff800`baa971fc : ffffe000`fc9364c0 ffffd001`17a18740 ffffe000`fc9364c0 ffffe000`f9c098f0 : watchdog!WdDbgReportRecreate+0x104 ffffd001`17a185f0 fffff800`bb4f148d : 00000000`00000000 00000000`00000000 ffffe000`f9478000 ffffe000`f9478000 : dxgkrnl!TdrUpdateDbgReport+0xec ffffd001`17a18640 fffff800`bb55a988 : ffffe000`f9478000 00000000`00000000 00000000`00000001 ffffe000`f947a001 : dxgmms2!VidSchiResetEngine+0x675 ffffd001`17a18920 fffff800`bb547751 : ffffe000`f9478000 ffffe000`f947a000 00000000`00000000 ffffe000`f947a000 : dxgmms2!VidSchiResetEngines+0x84 ffffd001`17a18960 fffff800`bb52de6d : 00000000`00000002 00000000`0201ee9c 00000000`003bce9f 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x19881 ffffd001`17a189c0 fffff800`bb4db8e5 : ffffe000`fab554c0 ffffe000`f947a000 ffffe000`fab554c8 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x31d ffffd001`17a18a80 fffff800`bb53a5fd : ffffe000`f944bc40 ffffd001`17a18bd0 ffffe000`f944bc00 ffffe000`f947a000 : dxgmms2!VidSchiScheduleCommandToRun+0x3a5 ffffd001`17a18b80 fffff800`bb53a5c0 : ffffe000`f947a500 ffffe000`f947a000 00000000`00000080 ffffe000`f5820000 : dxgmms2!VidSchiRun_PriorityTable+0x2d ffffd001`17a18bd0 fffff800`ef9695a5 : 00000204`acbb3dfe fffff800`ef9cd4ef 00000000`00010023 00000000`019884a0 : dxgmms2!VidSchiWorkerThread+0x80 ffffd001`17a18c10 fffff800`ef9cd626 : ffffd001`1b39c180 ffffe000`f945b840 fffff800`ef969564 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd001`17a18c60 00000000`00000000 : ffffd001`17a19000 ffffd001`17a13000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
Just to note currently (and for a while now) SWTOR has had an issue with some Nvidia cards. The "fix" there is to downclock them by 25~100Mhz when playing.
I won't say that will fix it here but it might be worth a try as it sounds like a similar issue. If you want more information on the SWTOR issue just Google "SWTOR drivers crash" and there are some official forums thread and Reddit posts.
Just to note currently (and for a while now) SWTOR has had an issue with some Nvidia cards. The "fix" there is to downclock them by 25~100Mhz when playing.
I won't say that will fix it here but it might be worth a try as it sounds like a similar issue. If you want more information on the SWTOR issue just Google "SWTOR drivers crash" and there are some official forums thread and Reddit posts.
khele23eb17_ESO wrote: »Just to note currently (and for a while now) SWTOR has had an issue with some Nvidia cards. The "fix" there is to downclock them by 25~100Mhz when playing.
I won't say that will fix it here but it might be worth a try as it sounds like a similar issue. If you want more information on the SWTOR issue just Google "SWTOR drivers crash" and there are some official forums thread and Reddit posts.
Most often the solution to unexplained driver crashes is either downclocking the card or upping the voltage on it.