50 replies to this topic

[Tarl Cabot]

Do you have your power options set to High Performance?

And what game settings are you using, including what AA?

[SarMajor]

Here is a "Ghost In The Machine" possibility, though I have rarely seen in after years of working in IT. Occasionally I will run across a specific piece of hardware that will not work with another specific piece of hardware. You can have two different pieces that do not work together, even though they are supposed to be able to do so.

For example, you could have a PCI card that works perfectly in one motherboard, but not in another motherboard of the exact same model. I've always chalked it up to inconsistencies in the manufacturing process of one of the involved parts, or damage that was unable to be seen, but enough to cause issues.

[w4ldO]

can you run gpu-z for your new gfx card and provide a screenshot?
https://www.techpowerup.com/gpuz/?

would be also interesting what that program says about the R7 360 when put into the other pcie slot

[JC Daxion]

Had issues with the new driver released yesterday, 4.11 Kept getting the IRQL_not_less_or_equal error.. according to searches it means a faulty driver. Figures the new driver that adds RTX support would be screwy with my GTX card.


I rolled back to the 3.99 from august 1st.. Hopefully that solves the issue, but if anyone has a driver that works well for them just in case that one has issues, but i'm hoping not.

[BlueStrat]

Just skimmed through the thread.

I would have suspected issues with the AMD/Radoen driver being quirky.

AMD/Radeon drivers have given me a lot of trouble over the years in both Windows systems and Linux...especially Linux and others.

I usually set up my computers to dual-boot Linux and whatever Win system (using Win7 Ultimate currently for MWO and general Windows type stuff).

AMD video drivers have been such a pain that I stick with Nvidia now because they seem to do a much better job of QA/testing than AMD does and 'it just works' on every OS I've used. (At one time a fair while back I had 7 different OS'es installed across 2 HDDs, among them Solaris, FreeBSD/NetBSD/OpenBSD, and even an old one from Bell Labs called 'Plan 9'. I learned a LOT!)

It seems like AMD drivers either like your system hardware and work, or else either won't work at all or they'll have weird issues.

Glad to hear you got things sorted.

Edited by BlueStrat, 30 September 2018 - 12:40 AM.

[MrMadguy]

Possible causes:
1) Weak or degraded power supply. Restart after boot points to this problem.
2) One of power phase short circuiting in video card itself. Faulty power transistor can cause this problem. This puts power supply to safe mode.
3) Unstable or even faulty GPU. I had one and it caused many different problems, such as driver errors, slower computer performance, etc.

[arcana75]

MrMadguy, on 30 September 2018 - 02:01 AM, said:

Possible causes:
1) Weak or degraded power supply. Restart after boot points to this problem.
2) One of power phase short circuiting in video card itself. Faulty power transistor can cause this problem. This puts power supply to safe mode.
3) Unstable or even faulty GPU. I had one and it caused many different problems, such as driver errors, slower computer performance, etc.

Speaking of "unstable GPU", my GPU is a Zotac 1080GTX. The only game that crashes on my rig now is MWO. And the pattern of crashing is for now very consistent. Here's how it goes:

1) Boot PC.
2) Fire up Chrome.
3) Fire up MWO.
4) Log into MWO, drop into a match or hit testing grounds.
5) About 10 seconds into the 3D environment, game crashes with either a MWO failure with option to report, or a D3D Device Removed error, with safe crash to desktop.
6) Restart MWO, no crash for the remainder of the session which could be 2-3 hrs long.

These days I'll purposely fire up testing grounds the first thing I do, and it crashes guaranteed, then I restart MWO. Go figure.

[Tarl Cabot]

Is the mech you start off with always the same mech, or similar mechs with decals, bolt-ons, colors, patterns, etc? Essentially mechs that have been fully loaded? And it happens only after the computer has been rebooted, that it is the only way you are reliably generate the crash and not if shutting down MWO then back in later on? Test it with a trial mech in the testing grounds with how you are doing it now.

Rebooting the system clears memory/cache.

Edited by Tarl Cabot, 03 October 2018 - 03:18 AM.

[arcana75]

Tarl Cabot, on 03 October 2018 - 03:12 AM, said:

Is the mech you start off with always the same mech, or similar mechs with decals, bolt-ons, colors, patterns, etc? Essentially mechs that have been fully loaded? And it happens only after the computer has been rebooted, that it is the only way you are reliably generate the crash and not if shutting down MWO then back in later on? Test it with a trial mech in the testing grounds with how you are doing it now.

Rebooting the system clears memory/cache.

Mech - different.
Reboot - no reboots, safe crash to desktop, immediate client restart.

Some asset thing perhaps? I now recall that it also happens if my 1st match is Canyon or any map that doesn't have the drop animation and the map renders behind the lobby screen.

[dwwolf]

BlueStrat, on 30 September 2018 - 12:21 AM, said:

Just skimmed through the thread.

I would have suspected issues with the AMD/Radoen driver being quirky.

AMD/Radeon drivers have given me a lot of trouble over the years in both Windows systems and Linux...especially Linux and others.

I usually set up my computers to dual-boot Linux and whatever Win system (using Win7 Ultimate currently for MWO and general Windows type stuff).

AMD video drivers have been such a pain that I stick with Nvidia now because they seem to do a much better job of QA/testing than AMD does and 'it just works' on every OS I've used. (At one time a fair while back I had 7 different OS'es installed across 2 HDDs, among them Solaris, FreeBSD/NetBSD/OpenBSD, and even an old one from Bell Labs called 'Plan 9'. I learned a LOT!)

It seems like AMD drivers either like your system hardware and work, or else either won't work at all or they'll have weird issues.

Glad to hear you got things sorted.

And the reality is that its been Nvidia the last 2 years that had the most driver issues

[BlueStrat]

dwwolf, on 03 October 2018 - 05:38 AM, said:

And the reality is that its been Nvidia the last 2 years that had the most driver issues

Maybe so, as I haven't been upgrading hardware and haven't had opportunities to compare for quite a while. For many years previous, however, AMD drivers were very quirky. A lot of trust was lost.