Homebuilt desktop freezes and blue-screens when playing gmaes

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Hi, guys my computer's got the case of the blues. I have lots of information so please read it all. Thanks.
My PC:
Budget home-build
CPU: AMD FX-4350 4.2 Ghz 4 core (says it's at 4.5 will talk more about this later)
MB: ASUS M5A97 r2.0
GPU: EVGA Nvidia GTX 750 1GB
PSU: Corsair CX500M (80+ Bronze class, Semi Modular 500W)
RAM 2X4GB Crucial Ballistix CL9@1.5v 1600 (set to something else in bios will talk about later)
SSD: Samsung 840 EVO 120G (120GB OS drive)
HDD: Toshiba 500GB (I think 7400 rpm?)
Windows 7 Home Premium 64bit
Fans: thee intake (two of which are filtered (the effectiveness is questionable) two molex exhaust

My Problem and its History:
My computer randomly blue-screens, freezes and becomes unresponsive (Hard Hang?), or if I'm lucky, the game crashes when playing steam games. (Which is what I use it for 90% of the time).
It wasn't always this way. I have used it happily for many months, but a month or two ago (I'm not good with time) it blue-screened. At first it rarely happened, but looking back I now see a trend in which, it happened more and more frequently as time progressed, to the point where now, when I play any game, it is only a matter of time before one of the things mentioned above occurs.

All the information I got:

  • ■ Okay so although the processor is 4.2ghz, and the memory is 1600mhz, it seems to be clocked at around 4.5 ghz and the memory is clocked at less then 1600. I took the computer into micro-center for an unrelated issue before I began gaming on it so maybe they made these changes.
    ■ I repeat, over time, I have noticed a trend in which the crashes, (game or whole pc) became more and more frequent as time progressed. They were tolerable before but now unbearable.
    ■ In past sometimes the just game would crash.
    ■ Thus far this only happens when gaming (but I don't do much else). (I'm using the computer to type this).
    ■ The games I usually play are TF2, Robocraft, and Rust; All are susceptible to this.
    ■ The critical events in the event log all say kernal-power Event ID 41. Meaning the system stopped responding, crashed, or lost power unexpectedly. Most of them say bug check:0 but some say 209 (I have photos) and the information saved.
    ■ Microsoft's support page I think attributes this to insufficient power (weak power-supply, over clocking etc. (I'm scenario 3) Here's the link: http://support.microsoft.com/kb/2028504/nl
    ■ If it means anything, I have multiple times in past done a forced shut-down of my computer (long press power button) (for unrelated reasons)
    ■ For a period of time I only had my ssd in my computer, then later I added the HDD, it is unlikely but possible that this problem started after that.
    ■ The time varies, but usually I can get 5-15+ minutes of game play out of robocraft before it crashes.
    ■ Recently, it has happened once or twice that audio will not play for a short period or will be lowered and then rise back up all on its own
    ■ I don't know how hot my cpu was when my pc crashes, but to test my temps I would play a game and periodically check the temperature (using AiSuiteII). The heat was around 44C°, perfectly normal for my cpu..unless my sources are wrong.
    ■ More often I get a blue-screen when something goes wrong; freezes and solely game crashes are less often.
    ■ I usually play at low or second lowest quality settings, on a 1440x900 monitor (I have a really small budget).
Crash logs:
Here's the link to the screenshots:
https://drive.google.com/open?id=0By-_-MkCV5h1fjluMUM5cTkzWGNKX1V2T2wxdGNYTTRIUk50R2h0RkNZc1QtVU9TV0RPSDg&authuser=0
Thanks for reading it all, hope this helps you help me help myself! :)
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640

Thus far I really only understand how do to what tradesman said. Also I wouldn't know how to decipher the the mini-dump files. I can however give you the xml codes for each error if that helps.

 
just copy the memory dump file (.dmp) to a cloud server like microsoft one drive or mediafire and post a link to it.
I can take a quick look in the windows debugger and see if I can see something useful.



 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Ok I'm sorry I have been away this weekend and will not be free until the weekend. Thank you for your time and patience. My plan is to 1. first check the actual clock speeds and voltages of my cpu and ram
2. I will convert the crash logs into plain text and post it on media fire or something. (Can you use google drive with a shared link?)
Thanks again
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Tested it for a couple days and then played fine, Problem seems to have resolved itself, no issues whatsoever for hours of play time. I am keeping this thread open for another two weeks in case it happens again (which it may as I did NOTHING) if it does I will run the xml through whocrashed and post that and readjust the ram in the interim. Thanks for your help, and sorry for opening a thread and not answering it. Peace and all hail the facist apple overlords.
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
It happened again after using many many tabs of chrome for many hours while writing a paper. Less frequent though. I am very busy wont be at the end of this week (next Saturday) will post crash info and ram voltages and timings.
Sorry, work sucks.
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Okay, I'm back. Thanks for waiting.
First, I am pretty sure my cpu has been overclocked as it is targeted at 4.5gz but it should be at 4.2. I am using the stock cooler, and I think I used too much thermal paste (this is my first build). And admittedly I have not dusted my computer...period. (My case is mesh though and my fans have filters)
I have my cpu cooler stocked to a very high setting too.
When I play tf2 and have it open my cpu load skyrockets to more or less 50%; when I minimize it, it falls.

I am having issues using action center's "solutions" tool as it says I cannot connect to the internet...which is obviously not true.

Okay, now back to what you asked; I am downloading whocrashed, (and trusting a total stranger on the internet by downloading this program I know nothing of :) ) Will report back momentarily. Again, I have xml info and other stuff if you want it.
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
It says:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

No valid crash dumps have been found on your computer


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

Crash dumps are enabled but no valid crash dumps have been found. In case you are experiencing system crashes, it may be that crash dumps are prevented from being written out. Check out the following article for possible causes: If crash dumps are not written out.



Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Are you sure you dont want the saved crashlogs and xm data?
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Im confused by what you just said.
I seems to sometimes crash sometimes not but I found two things

1. It crashed recently and it saved the minidump so here ya go.
2. I think it may be an overheating issue as tf2 often crashes after awhile and my cpu load sky rockets to 61%, I probably used too much thermal paste.
-----------------------------------------------------------------------
Crash Log
-----------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 3/15/2015 1:28:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031415-10452-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x5 (0xFFFFFA8006CDD890, 0xFFFFFA8006CDD890, 0x0, 0xFFFFFA8006D0BB50)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 3/15/2015 1:28:03 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x5 (0xFFFFFA8006CDD890, 0xFFFFFA8006CDD890, 0x0, 0xFFFFFA8006D0BB50)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
It is really sporadic, I often can get hours or days of game play before something happens, often my sessions go off without a hitch. The issue isn't limited to tf2, it has happened with robocraft (which is much less resource intensive, my cpu load hovers around 15% cpu and 40% ram) (albeit much less frequently) (although it used to (like most other games) make the computer hard hang) once during chrome when I had way too many tabs open (but again, it took a very long time for it to crash, and I had the same amount of tabs open another time and nothing happened) and once when I left my computer for a second and had nothing open. It is much less rare than it was before, but still has issues. Again I can go a couple of days before something happens (I use it mostly on weekends in roughly five hour sessions either playing work or doing games.)

I will get back to you on the memtest, I had suspicions too but the cpu load thing is what made me unsure. Will get back to you when I have the time to mem-test each stick of ram with the highest detail (and then them both together for good measure). Also, can you explain what the oxoooo5 bug is and why it caused the computer to bsod? Do you think it would be worth my time to remove and reapply the thermal paste? Since this was my first build I likely used too much, to be honest.
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Sorry SAT prep and SAT itself = won't be able to get back to you until next week during spring break. I'm getting my wisdom teeth taken out then, too, so I probably won't have much motivation to do work anyway so I'll be able to work with you.

Thanks!
 

joebro865

Reputable
Feb 13, 2015
50
0
4,640
Sorry it took me so long to get back, I haven't tested the memory. I was about to close the thread as I haven't had issues...until today. Got another bluescreen, I wasn't gaming, I was closing chrome. (After finishing a dissertation) (The reason why it took so long to get back) (Can't describe how bummed I felt when I got that BSOD) :(

I'm not memory testing this today, I don't have the patience to deal with this, will get back on Sunday.

Here's the who crashed for this time:

System Information (local)
--------------------------------------------------------------------------------

computer name: JOSEPHDESKTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-4350 Quad-Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 8482082816 total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 4/11/2015 12:24:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041015-10545-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xB337)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800532D337, 0xFFFFF880059B6878, 0xFFFFF880059B60D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Sat 4/11/2015 12:24:00 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xB337)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800532D337, 0xFFFFF880059B6878, 0xFFFFF880059B60D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.