Crashing 5-10 minutes in
The backstory: Updated to Windows 10 when it released. Had ongoing issues with Win10 and AMD video drivers fighting. Guess they finally knocked a lamp over or something and trashed my windows inst...
Forum Discussion
Thanks, Glad it helped.
Required Files C++
Grab all 3 please & install.. (Run install as Admin *Right Click)
http://www.microsoft.com/en-us/download/details.aspx?id=5555
http://www.microsoft.com/en-us/download/details.aspx?id=14632
http://www.microsoft.com/en-ie/download/details.aspx?id=40784
Off the bat , you could try a Repair, and you 'can' (not suggesting that you should or have to) redo your drivers, using ....
"I stole this link off Owen for rolling back your Video Drivers".
Lastest Display Driver installs or reverting Display Drivers
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
The Logs that I would suggest that are worth providing, DXDIAG.log, Client_Settings for starters as you can atleast get into the game.
Thanks again for all the help.
I *think* I'm making progress. Poking around through Windows logs I did find a few issues with drivers - I'm now trying the AMD beta drivers (they just outright wouldn't work prior to my windows crash), I've also updated my sound card drivers just for the heck of it.
Also had a "generic PnP" crash - I do have a few generic drivers, but most likely culprit was keyboard, so got them updated. I'm play-testing right now to see if things are better, will check back in later and report.
Totally Stoked that you are making head-way, glad to see that your working through the problem...
Your motivation has motivated me to address a WHEA_Un blah blah blah blue screen error that I have had since Windows 10 upgrade and just quietly ignored.. (*because I'm lazy).
Remember any questions or concerns feel free to provide your DXdiag log and your Client settings.
@DBWoodynz
Don't get too stoked yet....
Ok, to give a rundown -
Got into game and was playing. Maybe 2 minutes in I had an AMD driver crash. Got the message from Windows that it stopped responding and was successfully restarted. SWTOR actually took this in stride - it reliaded itself (like the instance or planet landing screen load) and on our merry way. Not optimal by any means, but interesting reference.
What boggles my mind is that the Windows event viewer didn't show anything. It showed when the video drivers crashed and restarted, but nothing at all after that.
Other things that I had done prior:--Tried your recommended links for the .net stuff. Each one said I had newer versions already installed.
--Just for sh*ts and giggles, I went through my Device Mangler and yanked out all the "hidden" and "unknown" devices. Refreshed.
--Ran CCleaner on my registry, and fixed some issues there.--Clean boot
--Did the bitraider "clean" thing where it forces the launcher to re0check everything for integrityMy gut is telling me it is drivers - but again, nothing at all (drivers or otherwise) showed up in the event viewer for the last crash. Baffling.
Anyway - attaching the dxdiag log, and the client_settings.ini from Appdata/local - I assume that was what you were referring to?
Again, thanks so much. Not sure how many more things there are left before I nuke Windows again...Ok lets look at this, your Windows 10 - 64bit running a HD7900.
So perfect world, These drivers should have you sorted (absolutely latest and greatest).
http://support.amd.com/en-us/download/desktop?os=Windows+10+-+64
That said and done... I have been oddly happy with running the Omega Drivers for the HD7000 Series; damned if I can find the link for them now.
amd-catalyst-omega-14.12-with-dotnet45-win7-64bit.exe (295,382KB)
Odds are this is why I am blue screening every now and then, but my HD7700 allows me to play 1920x1080 - Ultra - Fullscreen Windowed (as I watch TV on the other monitor) with Shadows off.
All this gets me nice FPS and a pretty picture.
Lets see if this Attachment thingie will let me add the one I use (*unlikely).
