18 replies to this topic

[Jay Sovereign]

I am receiving this error lately and it causes me to crash every time. It's really messing things up because I am crashing while loading waiting to drop into matches then unable to rejoin.

I tried everything to fix the problem, Display Driver Uninstaller, updated drivers, running repair tools and verifying game files, etc. MWO support was responsive and tried to help me fix this and we cannot fix the problem.

Anyone know anything about this and possibly how to fix it?
____________________

EDIT* Issue still unsolved. I will list all current notes about my situation and my computer specifications...

Similar threads:
https://mwomercs.com...i-error-device/
https://steamcommuni...12122400928874/

- Thermals:
I clean my system of dust regularly. I run my fans at high speeds while gaming; my GPU only reaches in the upper 50s and sometimes low 60s Celcius when gaming. Unless something's happening that's shooting my temps up quickly and then dropping it back down before I realize, I think my temps are fine.
***Also, this usually happens to me while waiting to join matches, or in the mechlab. This has only happened in the middle of playing a few times, whereas I have had this error while in the mechlab and loading waiting to drop much more. My system isn't really under full load when in the Mechlab or after the map vote screen or while loading (or maybe it is I'm not sure)

- This issue seems to be MWO exclusive

- I play the game in full windowed mode

- All system power settings are set to high performance

- Display device settings are set to use my GPU (MSI NVIDIA GeForce GTX 1060 3GB)

- I used DDU for driver uninstallation:
I used 'Display Driver Uninstaller' to uninstall all drivers before reinstalling GeForce Experience and downloading new ones.

WHAT I WILL BE TRYING NEXT: I will uninstall and reinstall DirectX. If that doesn't work I'll reseat my graphics card.
____________________

System Specs:

My rig was shop bought several years ago but has been taken apart, rebuilt and customized with no issues. The only original parts are the case, motherboard, and 2 out of the 4 sticks of RAM.

OS - Windows 8.1 64-bit
CPU - Intel Core i7 3770 @ 3.40GHz Ivy Bridge 22nm Technology
RAM - 16.0GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Mobo - MSI Z77A-G41 (MS-7758) (SOCKET 0)
GPU - 3071MB NVIDIA GeForce GTX 1060 3GB (MSI)
Monitor - SAMSUNG TV (1920x1080@60Hz) connected to GPU via HDMI cable
PSU - BeQuiet 600w that is only a few years old

Edited by Jay Sovereign, 01 May 2020 - 01:48 PM.

[Monkey Lover]

Looks like a directx error. Can we still select the version of directx we want? Might try using the other one. (At work so can't check)

other thing might look at disabling your on board video card. Or focusing it to use th faster card. Just guessing because of the name. Looks like it might be reading one or the other. My laptop has this issue because of the two cards.

Edited by Monkey Lover, 30 April 2020 - 10:02 PM.

[LordNothing]

try full window

[D V Devnull]

Hello, Jay... I've only seen this problem when my GPU is getting too hot, and MWO gags due to the temperature. I suggest that you blast the dust off of your Graphics Card (or CPU if the GPU is built into that) somehow, preferably with an air can.

~D. V. "that usually tends to fix GPU issues for me" Devnull

[VonBruinwald]

D V Devnull, on 01 May 2020 - 12:56 AM, said:

Hello, Jay... I've only seen this problem when my GPU is getting too hot, and MWO gags due to the temperature. I suggest that you blast the dust off of your Graphics Card (or CPU if the GPU is built into that) somehow, preferably with an air can.

~D. V. "that usually tends to fix GPU issues for me" Devnull

Check this, 99% of the time it's the culprit. Also, if you've never opened your case before, post before and after pics

It's normally heat or power issues that cause "Device_Removed".

Things to try:

• If you've over-clocked your card, revert to stock settings (shouldn't be an issue if you've reinstalled the drivers*).
  
• Check for dust/clogs (dust=heat=crash).
  
• Check your system power settings (Make sure windows is set to high performance).
  
• Re-seat your graphics card.
  
• Check your power supply** - Normally this is only an issue on ageing PCs.

*How did you go about uninstalling/reinstalling drivers. Did you use DDU or the default uninstaller?

**Is this build custom or shop bought? Have there been any recent "upgrades" to the hardware/OS (if you've installed the latest drivers it might be worth rolling back to an earlier one if you know it was stable..

If you can, post system specs, and how long have you had this rig? Does this, or any other errors, occur during other usage or is this a MWO exclusive?

Edited by VonBruinwald, 01 May 2020 - 02:17 AM.

[Jay Sovereign]

Thanks for all the input, everyone.

I will list all current notes about my situation and my computer specifications...

Similar threads...
https://mwomercs.com...i-error-device/
https://steamcommuni...12122400928874/

- Thermals:
I clean my system of dust regularly. I run my fans at high speeds while gaming; my GPU only reaches in the upper 50s and sometimes low 60s Celcius when gaming. Unless something's happening that's shooting my temps up quickly and then dropping it back down before I realize, I think my temps are fine.
***Also, this usually happens to me while waiting to join matches, or in the mechlab. This has only happened in the middle of playing a few times, whereas I have had this error while in the mechlab and loading waiting to drop much more. My system isn't really under full load when in the Mechlab or after the map vote screen or while loading (or maybe it is I'm not sure)

- This issue seems to be MWO exclusive

- I play the game in full windowed mode

- All system power settings are set to high performance

- Display device settings are set to use my GPU (MSI NVIDIA GeForce GTX 1060 3GB)

- I used DDU for driver uninstallation:
I used 'Display Driver Uninstaller' to uninstall all drivers before reinstalling GeForce Experience and downloading new ones.

WHAT I WILL BE TRYING NEXT: I will uninstall and reinstall DirectX. If that doesn't work I'll reseat my graphics card.
____________________

System Specs:

My rig was shop bought several years ago but has been taken apart, rebuilt and customized with no issues. The only original parts are the case, motherboard, and 2 out of the 4 sticks of RAM.

OS - Windows 8.1 64-bit
CPU - Intel Core i7 3770 @ 3.40GHz Ivy Bridge 22nm Technology
RAM - 16.0GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Mobo - MSI Z77A-G41 (MS-7758) (SOCKET 0)
GPU - 3071MB NVIDIA GeForce GTX 1060 3GB (MSI)
Monitor - SAMSUNG TV (1920x1080@60Hz) connected to GPU via HDMI cable
PSU - BeQuiet 600w that is only a few years old

Edited by Jay Sovereign, 01 May 2020 - 01:47 PM.

[Tarl Cabot]

4 sticks of ram and 2 of them are new? Potential memory issue. Remove two sticks and test, switch sticks out and test. The times listed, several of those the system is under load.

Is the GPU overclocked any, or did it come from the mfg OC? May need to underclock it. (per the other thread)

Also, is the PSU is a BeQuiet PSU, hmm..

Just to be on the safe side, download, unpack and install directx 9c, potential file corruption. May be running game as dx11 but some components of it still utilizes dx 9c. The dxdiag will always show the latest Directx installed. Also in game you can also test by changing Directx Version from DX11 to DX9 in the video setting of the game.

https://www.microsof...ls.aspx?id=8109

As for GPU drivers, as a reminder by default Windows 10 automatically downloads/install drivers. It can be disabled by jumping through a few screens but beware, I have had it reset to default on twice. One will not realize it until there are game issues.

Edited by Tarl Cabot, 01 May 2020 - 02:29 PM.

[LordNothing]

D V Devnull, on 01 May 2020 - 12:56 AM, said:

Hello, Jay... I've only seen this problem when my GPU is getting too hot, and MWO gags due to the temperature. I suggest that you blast the dust off of your Graphics Card (or CPU if the GPU is built into that) somehow, preferably with an air can.

~D. V. "that usually tends to fix GPU issues for me" Devnull

i always thought this was more of a power issue than a heat one. my old 750ti used to do this a lot, and it was because that card had no external power connection and had to draw all its juice from the mobo. which is fine until you push the card to its limits and it suddenly needs more power which just isnt available. my 1060 didnt do this at all, and then i moved up to a 2070 super, which has only crashed a few times, mostly because i forgot to put it back into full window mode after resetting defaults for the new card, enabled that and it hasnt crashed since. full window fixes probibly 90% of the known crashes.

Edited by LordNothing, 01 May 2020 - 03:18 PM.

[D V Devnull]

LordNothing, on 01 May 2020 - 03:06 PM, said:

i always thought this was more of a power issue than a heat one. my old 750ti used to do this a lot, and it was because that card had no external power connection and had to draw all its juice from the mobo. which is fine until you push the card to its limits and it suddenly needs more power which just isnt available. my 1060 didnt do this at all, and then i moved up to a 2070 super, which has only crashed a few times,

For some strange reason, I'm always pushing the GPU to the max, and the heat gets high enough if I haven't kept things dusted off as to knock me out of MWO entirely. It appears 80°C is where MWO doesn't like the GPU anymore, and likely the NVidia driver is auto-protecting the card. This has now happened to me with two different cards, one without extra power requirements (GT 440) and one with extra needs (GTX 670), which is why my first instinct will normally be to dust the card off in order to get the temps back under control. Thankfully, I think I've had less crashes with the better card.

LordNothing, on 01 May 2020 - 03:06 PM, said:

mostly because i forgot to put it back into full window mode after resetting defaults for the new card, enabled that and it hasnt crashed since. full window fixes probibly 90% of the known crashes.

Interesting... For me, using Full Windowed mode actually slows my running MWO Client down too much. Using the FullScreen mode seems to generally work better for me, but I bet that's because of my older-generation (please, don't ask, I know they're a joke by now, even though they have worked reasonably with MWO for some time) CPU and mobo. I had even better performance when MWO had a 32-Bit Client, and have taken a noticeable impact since the forced move to 64-Bit too. (It makes me wish for the return of the 32-Bit Version.)


~D. V. "different system, different mileage... right?" Devnull

[Biomechtric]

A drop in your internet can also cause this exact error. It doesn't need to be much, a tiny drop\packet loss is enough.
I had this very issue before I had proper hardwired internet, on wifi I had crashes every few games with this very error code, as soon as my new net was up & running it's been a non issue. Nothing else was changed on my rig, no hardware, software or settings.
Hope this helps the mystery.

[Spinning Broccoli]

If it is a heat/power related issue, you could also try lowering graphics settings as a test, in hope it would cause less strain on your graphics card.

[James Saxon]

For me this is much more likely to happen if I alt tab around while waiting for game and then match start, and I continue playing. I actually don't know if me alt tabbing is the culprit, but correlation is there for me.

Edited by James Saxon, 17 June 2022 - 04:26 AM.

[LordNothing]

its a combination of alt tab and full screen. if you want to alt tab, use full window. alt tabbing out of full screen causes the video card to enter a lower power state and also pages data out of the video memory. when you tab back in it wants to go but its in the wrong state to do so and doesnt have all its data. also it can take a lot longer to alt tab into and out of full screen than full window. full window works because it doesnt try to unload anything and maintains the current power state.

Edited by LordNothing, 17 June 2022 - 07:13 AM.

[LordNothing]

Kurb, on 02 May 2020 - 03:56 AM, said:

If it is a heat/power related issue, you could also try lowering graphics settings as a test, in hope it would cause less strain on your graphics card.

can be. i know my old 750ti (since upgraded and upgraded again) had this problem because it didnt have dedicated power connectors and usually couldnt source enough power from the pcie slot. however this particular error happens more when using fullscreen mode while alt tabbing, use full window instead. he is using a 1060 and shouldn't have this problem, it was specific to lower end cards.

also someone call a necromancer.

Edited by LordNothing, 17 June 2022 - 07:19 AM.

[James Saxon]

My bad, just that I uninstalled it for some time due to inability to resolve the issue even when I was in full windowed. I installed it recently and it's currently keeps freezing my computer so I have to hard restart everytime, and time to time it fails a little more gracefully, and I see the dialog mentioning about DXGI

I should make a new thread if that's what I should be doing.

[TELEFORCE]

Fixed mine by swapping the GPU, then the PSU died shortly after that swap, so I'd check either the GPU or PSU.

[Tarl Cabot]

James Saxon, on 17 June 2022 - 06:12 PM, said:

My bad, just that I uninstalled it for some time due to inability to resolve the issue even when I was in full windowed. I installed it recently and it's currently keeps freezing my computer so I have to hard restart everytime, and time to time it fails a little more gracefully, and I see the dialog mentioning about DXGI

I should make a new thread if that's what I should be doing.

I would say no need to make a new thread, since the only thing that has really changed is how MWO is triggering the system instability, going from a Dxdiag error to a system lock up. You likely have a component (s) that may be dying, or while playing MWO, is triggering the event which then is causing the system becomes unstable, generating the error/system lock up.. This could be any program, and if you were to use a program that would stress test the system, you would run into the same thing.

Ask a mod to move this thread to Workarounds since the hardware/Accessories was dropped to the Archived section. Imho, hardwire/accessory should at least be moved under Workaround. At least in the Workaround, it would not get lost in the general posts.

Bu to tough base, lets take the lease resistant route and check it first. As noted in a previous post, 2 sticks of ram is new/er than what was in it. Remove 2 sticks then test. Switch out the pair then test. Though I also believe the primary culprit is likely the PSU, followed by the GPU. You can also use other programs to stress test the system.

• Generate and post the top half of your dxdiag, from the beginning up to and including the sound card drivers.
  
• If it is memory related first.... With the above information may be able to determine which bios is loaded up.. 4 of the last 6 bios updates were for memory compatibility from the motherboard mfg website.
  
• Use MSI Afterburner - then have the ability to underclock the GPU.
  
• Also, since ya still using Win 8.1 - make sure windows driver updates has been disabled.
  
  • To prevent Windows 8.1 from automatically installing new drivers: From the StartScreen search for "Device installation settings ". In the dialog that opens, select "No let me choose what to do ". From there select "Never install software from Windows Update"
    
  • .

Edit. Other option is to not play MWO til the system issue has been resolved but it will not go away. Play something else or run another program that is able to generate the event, and eventually, if it is the PSU and/or CPU, and not the different sticks of ram, when one of those components fail, it has the potential of taking out the motherboard too especially the PSU I wanted to stress this part, even if you no longer want to play MWO.

Edited by Tarl Cabot, 21 June 2022 - 04:33 PM.

[Meep Meep]

I have a basically brand new system with all up to date drivers and such and mwo will crash now and then along with minecraft for some reason. Everything else I play is rock solid. The issue is that its using a ten year old game engine that hasn't been properly updated in years to meet modern standards. Its a shame they can't easily port it to a newer unreal engine version but I guess thats simply too much money. I wonder if they could crowd fund it though? At this point I would be willing to go unusual routes to keep the game alive and evolving.

[TELEFORCE]

Meep Meep, on 21 June 2022 - 04:43 PM, said:

I have a basically brand new system with all up to date drivers and such and mwo will crash now and then along with minecraft for some reason. Everything else I play is rock solid. The issue is that its using a ten year old game engine that hasn't been properly updated in years to meet modern standards. Its a shame they can't easily port it to a newer unreal engine version but I guess thats simply too much money. I wonder if they could crowd fund it though? At this point I would be willing to go unusual routes to keep the game alive and evolving.

Is it crashing for the reason the OP posted? Just because your system is relatively new doesn't mean that some components may be defective. I suggest considering a warranty replacement of the GPU or PSU.