Constant game crashes - "Stopped working"

[connolly852]

Could anyone help me trouble shoot this? I am trying to play some Arma III, and it keeps crashing not even 5 minutes into playing. RAM has been tested, so it isn't the usual suspect. All drivers are up to date. I am running out of ideas here.

[Beghouling]

seems to me your missing files or they need to be fixed, try backup files and see if that helps, it happened to me after playing a game for 30 min and getting back on and it popped up, but it fixed it, i hope this helps :)

[connolly852]

doesn't seem to be working :/

[dirrtymartini]

connolly852 の投稿を引用：

Could anyone help me trouble shoot this? I am trying to play some Arma III, and it keeps crashing not even 5 minutes into playing. RAM has been tested, so it isn't the usual suspect. All drivers are up to date. I am running out of ideas here.

First, keep in mind that ARMA III is an Alpha release. Not excusing the breakage but it certainly isn't polished yet.

Check Windows Event Viewer. Look in the System or Applicaiton Logs and see if you get any clues. If your RAM was bad, I suspect you'd see other odd behavior -- system freezes, BSODs, and such. A single game crashing usually means the game is broken -- missing pre-reqs (graphics drivers, DirectX, visual c++ runtimes etc), files corrupt or missing, etc.

[connolly852]

dirrtygsharp の投稿を引用：

connolly852 の投稿を引用：

Could anyone help me trouble shoot this? I am trying to play some Arma III, and it keeps crashing not even 5 minutes into playing. RAM has been tested, so it isn't the usual suspect. All drivers are up to date. I am running out of ideas here.

First, keep in mind that ARMA III is an Alpha release. Not excusing the breakage but it certainly isn't polished yet.

Check Windows Event Viewer. Look in the System or Applicaiton Logs and see if you get any clues. If your RAM was bad, I suspect you'd see other odd behavior -- system freezes, BSODs, and such. A single game crashing usually means the game is broken -- missing pre-reqs (graphics drivers, DirectX, visual c++ runtimes etc), files corrupt or missing, etc.

Sorry, I should have added that it is with every game I have been playing today. I was playing perfectly fine yesterday. I have tried portal, and AC3 to confirm it wasn't just Arma. Here is one of the event viewer errors:

Faulting application name: arma3.exe, version: 0.5.102.571, time stamp: 0x512deb6a
Faulting module name: arma3.exe, version: 0.5.102.571, time stamp: 0x512deb6a
Exception code: 0xc0000005
Fault offset: 0x008f834c
Faulting process id: 0x15a0
Faulting application start time: 0x01ce1abff7816f77
Faulting application path: D:\Mas steam games\steamapps\common\Arma 3\arma3.exe
Faulting module path: D:\Mas steam games\steamapps\common\Arma 3\arma3.exe
Report Id: a31d20d5-86b3-11e2-908f-bc5ff45841ef

There was also this 40 seconds before:

Faulting application name: svchost.exe_WinDefend, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000410380
Faulting process id: 0x15e0
Faulting application start time: 0x01ce1ac00bcb84e5
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: unknown
Report Id: 714a08e2-86b3-11e2-908f-bc5ff45841ef

Any ideas?

[dirrtymartini]

connolly852 の投稿を引用：

Faulting application name: svchost.exe_WinDefend, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000410380
Faulting process id: 0x15e0
Faulting application start time: 0x01ce1ac00bcb84e5
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: unknown
Report Id: 714a08e2-86b3-11e2-908f-bc5ff45841ef

Any ideas?

I'd start with resolving whatever made Windows Defender throw up. Are your Windows Updates current? Can you run Windows Defender manually? Run scans? Does it interfere with any network communication needed by ARMA III?

[connolly852]

dirrtygsharp の投稿を引用：

connolly852 の投稿を引用：

Faulting application name: svchost.exe_WinDefend, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000410380
Faulting process id: 0x15e0
Faulting application start time: 0x01ce1ac00bcb84e5
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: unknown
Report Id: 714a08e2-86b3-11e2-908f-bc5ff45841ef

Any ideas?

I'd start with resolving whatever made Windows Defender throw up. Are your Windows Updates current? Can you run Windows Defender manually? Run scans? Does it interfere with any network communication needed by ARMA III?

I just ran the updates and then ran a scan that turned up fine. I don't think it is interfering with anything. I usually run avast, but I have that in gaming mode. I have never touched Windows Defender until right now, so I don't know why that would show up in anything. All other windows updates are all current.

[dirrtymartini]

connolly852 の投稿を引用：

dirrtygsharp の投稿を引用：

I'd start with resolving whatever made Windows Defender throw up. Are your Windows Updates current? Can you run Windows Defender manually? Run scans? Does it interfere with any network communication needed by ARMA III?

I just ran the updates and then ran a scan that turned up fine. I don't think it is interfering with anything. I usually run avast, but I have that in gaming mode. I have never touched Windows Defender until right now, so I don't know why that would show up in anything. All other windows updates are all current.

Ok, I'm assuming you installed ARMA III late yesterday or early today? And once you did, other games started having problems?

[connolly852]

dirrtygsharp の投稿を引用：

connolly852 の投稿を引用：

I just ran the updates and then ran a scan that turned up fine. I don't think it is interfering with anything. I usually run avast, but I have that in gaming mode. I have never touched Windows Defender until right now, so I don't know why that would show up in anything. All other windows updates are all current.

Ok, I'm assuming you installed ARMA III late yesterday or early today? And once you did, other games started having problems?

Yes early today. Yesterday I was playing just fine and today everything went to ♥♥♥♥. I sadly didn't play anything before Arma, so I couldn't tell you if it happened right after I installed it. This has happened before, but not to this extent. Before it seemed to have fixed itself, but now it won't stop no matter what. I reinstalled drivers, but no luck there.

[dirrtymartini]

connolly852 の投稿を引用：

dirrtygsharp の投稿を引用：

Ok, I'm assuming you installed ARMA III late yesterday or early today? And once you did, other games started having problems?

Yes early today. Yesterday I was playing just fine and today everything went to ♥♥♥♥. I sadly didn't play anything before Arma, so I couldn't tell you if it happened right after I installed it. This has happened before, but not to this extent. Before it seemed to have fixed itself, but now it won't stop no matter what. I reinstalled drivers, but no luck there.

A guess here -- maybe some of the pre-reqs (directX, dotnet runtime, whatever) for Arma III stepped on stuff you already had installed? Not sure what else would break your ability to run other games just by installing Arma III...

If nothing jumps out at you when poking around your system, I'd file a bug report with BI, send them a dxdiag report, and let them sort it out.

http://feedback.arma3.com/main_page.php

You'll need to create an account but it takes less than a minute to do -- provide email, get confirmation, set password, done.

[connolly852]

dirrtygsharp の投稿を引用：

connolly852 の投稿を引用：

Yes early today. Yesterday I was playing just fine and today everything went to ♥♥♥♥. I sadly didn't play anything before Arma, so I couldn't tell you if it happened right after I installed it. This has happened before, but not to this extent. Before it seemed to have fixed itself, but now it won't stop no matter what. I reinstalled drivers, but no luck there.

A guess here -- maybe some of the pre-reqs (directX, dotnet runtime, whatever) for Arma III stepped on stuff you already had installed? Not sure what else would break your ability to run other games just by installing Arma III...

If nothing jumps out at you when poking around your system, I'd file a bug report with BI, send them a dxdiag report, and let them sort it out.

http://feedback.arma3.com/main_page.php

You'll need to create an account but it takes less than a minute to do -- provide email, get confirmation, set password, done.

I'll do that, thanks. It looks like I bluescreened a couple of minutes ago when my computer froze.. Maybe it is related?

Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\021613-9406-01.dmp
C:\Users\Sean\AppData\Local\Temp\WER-25677-0.sysdata.xml
C:\Users\Sean\AppData\Local\Temp\WER40A7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Sean\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0bdd4cd7

Analysis symbol:
Rechecking for solution: 0
Report Id: 021613-9406-01
Report Status: 0

[dirrtymartini]

connolly852 の投稿を引用：

dirrtygsharp の投稿を引用：

A guess here -- maybe some of the pre-reqs (directX, dotnet runtime, whatever) for Arma III stepped on stuff you already had installed? Not sure what else would break your ability to run other games just by installing Arma III...

If nothing jumps out at you when poking around your system, I'd file a bug report with BI, send them a dxdiag report, and let them sort it out.

http://feedback.arma3.com/main_page.php

You'll need to create an account but it takes less than a minute to do -- provide email, get confirmation, set password, done.

I'll do that, thanks. It looks like I bluescreened a couple of minutes ago when my computer froze.. Maybe it is related?

Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\021613-9406-01.dmp
C:\Users\Sean\AppData\Local\Temp\WER-25677-0.sysdata.xml
C:\Users\Sean\AppData\Local\Temp\WER40A7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Sean\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0bdd4cd7

Analysis symbol:
Rechecking for solution: 0
Report Id: 021613-9406-01
Report Status: 0

Good God, man. You've got a handful of problems on that system. Roll up your sleeves and get to work.

A system freeze is usually...usually a hardware issue. Not entirely, but most of the time. Start testing your hardware. Check memory with Memtest86+. Check temps on system, cpu, and video card. If you're overclocking, stop doing that -- for testing purposes. Check your hard drive for physical or logical errors. Pop the cover on the case and give it a good shot of compressed air too just to be thorough.

If that .dmp file isn't too large, I'd be happy to run it through a debugger and see if it provides any clues about what happened.

Did you happen to catch any stop codes or the BSOD error msg?

[connolly852]

:) I built it 3 months ago too... I don't know what is wrong with it. I have suspected hardware issues before but couldn't really track it down. 5 hours of Memtest showed nothing.

dirrtygsharp の投稿を引用：

connolly852 の投稿を引用：

I'll do that, thanks. It looks like I bluescreened a couple of minutes ago when my computer froze.. Maybe it is related?

Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\021613-9406-01.dmp
C:\Users\Sean\AppData\Local\Temp\WER-25677-0.sysdata.xml
C:\Users\Sean\AppData\Local\Temp\WER40A7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Sean\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0bdd4cd7

Analysis symbol:
Rechecking for solution: 0
Report Id: 021613-9406-01
Report Status: 0

Good God, man. You've got a handful of problems on that system. Roll up your sleeves and get to work.

A system freeze is usually...usually a hardware issue. Not entirely, but most of the time. Start testing your hardware. Check memory with Memtest86+. Check temps on system, cpu, and video card. If you're overclocking, stop doing that -- for testing purposes. Check your hard drive for physical or logical errors. Pop the cover on the case and give it a good shot of compressed air too just to be thorough.

If that .dmp file isn't too large, I'd be happy to run it through a debugger and see if it provides any clues about what happened.

Did you happen to catch any stop codes or the BSOD error msg?

:) I built it 3 months ago too... I don't know what is wrong with it. I have suspected hardware issues before but couldn't really track it down. 5 hours of Memtest showed nothing. Temps have never been an issue. I have always kept track of them with nothing out of the ordinary.

My GPU has a factory OC, so should I roll that back?

That .dmp file is no where to be found for some reason. I do, however, have 6 .dmps from last month that may help. All are 274 KB . I feel horrible for not taking care of her like I should. I just don't know exactly what I am doing.

I didn't even see the actual blue screen. The game just froze, audio went stagnant. I left it for a minute after Ctrl alt dlt, and ended up restarting. Nothing ever came up.

[dirrtymartini]

connolly852 の投稿を引用：

(snip for space)

:) I built it 3 months ago too... I don't know what is wrong with it. I have suspected hardware issues before but couldn't really track it down. 5 hours of Memtest showed nothing. Temps have never been an issue. I have always kept track of them with nothing out of the ordinary.

My GPU has a factory OC, so should I roll that back?

That .dmp file is no where to be found for some reason. I do, however, have 6 .dmps from last month that may help. All are 274 KB . I feel horrible for not taking care of her like I should. I just don't know exactly what I am doing.

I didn't even see the actual blue screen. The game just froze, audio went stagnant. I left it for a minute after Ctrl alt dlt, and ended up restarting. Nothing ever came up.

Ok, don't mess with the GPU for now. Send me what you have for .dmps and your System and Application Event Logs. We can step through them and try to figure out wtf is happening.

What you might do, if this is feasible, is try uninstalling ARMA III and seeing if your system starts behaving again. Were you having these appcrashes and BSOD prior to ARMA III being installed? (not saying that ARMA III is the culrprit...just looking for clues)

Email is in my profile.

[xx-LiquidLight-xx]

If I were you I would reinstall windows. You got to many errors looks like ur computer is taking a dump. Stop procrastinating and reinstall Windows and everything will work.

[connolly852]

dirrtygsharp の投稿を引用：

connolly852 の投稿を引用：

(snip for space)

:) I built it 3 months ago too... I don't know what is wrong with it. I have suspected hardware issues before but couldn't really track it down. 5 hours of Memtest showed nothing. Temps have never been an issue. I have always kept track of them with nothing out of the ordinary.

My GPU has a factory OC, so should I roll that back?

That .dmp file is no where to be found for some reason. I do, however, have 6 .dmps from last month that may help. All are 274 KB . I feel horrible for not taking care of her like I should. I just don't know exactly what I am doing.

I didn't even see the actual blue screen. The game just froze, audio went stagnant. I left it for a minute after Ctrl alt dlt, and ended up restarting. Nothing ever came up.

Ok, don't mess with the GPU for now. Send me what you have for .dmps and your System and Application Event Logs. We can step through them and try to figure out wtf is happening.

What you might do, if this is feasible, is try uninstalling ARMA III and seeing if your system starts behaving again. Were you having these appcrashes and BSOD prior to ARMA III being installed? (not saying that ARMA III is the culrprit...just looking for clues)

Email is in my profile.

They happened before from time to time, but not nearly this often.

I'll have to get to the rest of this tomorrow afternoon.

.dmps are on their way.