Re: Random Loading Screens and Occasional Graphics Driver Crash

The difficulty with a lot of the fixes I attempt is that the loading screen doesn't trigger until anywhere from 5 min to hours into gameplay.

I also tend to get the message "swtor.exe has been denied access to graphics hardware" or something of the like saying that my computer's graphics driver has stalled then restarted, though this is less frequent.

It's not a temperature issue, I very rarely break 70 degrees celsius.

@RydarusVeneris

I am aware of issues with the newest drivers and 860M cards might go and see if anything related to 880m cards

@RydarusVeneris

here is a 860m thread if your interested in looking as well

@RydarusVeneris

355.98 seems stable for the 860m not sure if you want to try it as well ?

it is here  just remember to select custom install and tick clean install

already tried it a few days ago, I also tried 352.86.

Also I misunderstood your post and didn't realize that deleting disk cache arena was a valid thing for the nonstreaming client and not just the streaming client since you put it below the streaming client (was late and wasn't thinking)

Tried that, won't know if it'll work until I don't crash for a while I guess, I'll keep you posted!

Thanks man!

Still not working, reattempting, going to try to see what happens when I disable the loading screens.

I did manage to find an area of my stronghold with consistent crashing so I can use that as a benchmark of sorts.

Running FixLauncher

So.... repairing the launcher gives me the original launcher and even after the update it still has be at the pre update launcher.

yup, running fix launcher sticks me with the old UI for the launcher uhh /shrug

Still crashing, probably just going to have to get a new computer at this rate.

I'm noticing that the "same crash" doesn't happen more than once if the game stays on.

@RydarusVeneris

using the repair utility here will return the new launcher style

Seems like the crashing miiiiight be a hardware issue, but I don't know. I'm getting a new computer anyway but this is annoying to say the least.

thanks for all your help though.

@RydarusVeneris

Welcome, any crash issue is a PITA and frustrating.

Have you looked in the reliability monitor to see if any details is listed when this occurs ?

nothing in the reliability monitor, I did have a BSOD today due to running out of memory, apparently CCleaner has a few incompatibilities with win10.

Nothing in relation to tor though.

@RydarusVeneris

Nothing in the reliability monitor makes it hard

if you use this it may provide more information if dumps where made on the crashes.

As it stands right now I can reliably get the game to "reload" itself but I can't reliably reproduce a driver crash, mostly because they happen significantly less often in windows 10.

In other games I occasionally see flickering which makes me think it might be a GPU problem, but who knows at this point :\

got these from the WhoCrashed app, though these I believe were from the CCleaner crash.

On Thu 11/26/2015 10:14:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112615-33609-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGADAPTER::ProcessComponentIdleList+0x157)
Bugcheck code: 0xA (0x26C, 0x2, 0x0, 0xFFFFF802A96101B1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 11/26/2015 10:14:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGADAPTER::ProcessComponentIdleList+0x157)
Bugcheck code: 0xA (0x26C, 0x2, 0x0, 0xFFFFF802A96101B1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

@RydarusVeneris

This is the bug check reported

Now this is occurring in the directx kernel, so it is tied to the graphics side of the house, and would think more related to the error your getting ingame

doesn't help with an actual cause though

if you want to post a dxdiag , can have a look as a 2nd set of eyes if anything looks out of place

http://hastebin.com/ajaxaqanuh.tex

@RydarusVeneris

have you tried going back to the dell drivers ,

use DDU to remove both the NVidia and intel driver then use the drivers here

Install the Intel driver first , reboot and install the NVidia driver , reboot and then see if it is still the same

You may need this to stop the auto update

Double post

I've never used DDU period, I've only ever used the default Nvidia clean install. I'll try DDU before using current drivers, and if that doesn't work I'll use the original Dell Drivers.

Additionally I actually do need my computer to have the latest drivers for different games, so using the original dell drivers would be a stopgap measure for me at best.

Nada.