Question / Help Frequent crashing

Velyse

New Member
Getting this texture map error that has been hard-locking my system when I attempt to stream dota to twitch.

Specs:
intel 4770k, radeon 290x (x2), 16gb of ram, 256gb ssd main drive, that's about all the pertinents...

Sometimes it happens immediately when I click preview or start stream, sometimes 15 minutes, sometimes I get an entire match. I have since lowered the framerate, switched to x64, killed the preview window, killed msi afterburner... still crashes.

I am using the Catalyst 14.4 drivers, I had two 770 GTX's in my system about 5 months ago and I dont recall ever having a problem with them, I just recently got the urge to start streaming but it just crashes and I don't really know where to begin, I've attached a log file.

Any pointers would be greatly appreciated.
 

Attachments

  • 2014-05-18-1219-37.log
    59.3 KB · Views: 26

Jack0r

The Helping Squad
Have you tested, does this also happen if you only use one 290x? I would think the crossfire setup could potentially be the cause of your problem. So that would be an easy test to rule this out.
 

VooDoo

Member
It's likely a crossfire problem or you're cooking the top card. It's actually not suggested or even smart to have 2 R9 290x's in CFX the power is great but they already run hotter than hell. Then considering even at a load of even low end gaming like Moba's you end up baking the top card, then I'll bet the added temps from streaming are just pushing it over the edge and its crashing out.

Also you didn't list the most important parts of the build.

#1 Intel i7-4770k is great information but worthless if you don't specify @ what clocking and voltage

#2 R9 290x says a lot but doesn't say what clocking, factory overclocked? What brand and what cooler?

#3 Wheres the power supply...its likely the most important thing you could possibly tell us. If you don't have like 1000 watt or higher PSU Id you could be causing this crash because you cannot provide the power needed. This gets worse if that i7 and 2 gpu's are overclocked. That build in my hands would need roughly 1200 watts to run efficiently. The 2 r9's alone can soak up 800w

Keep in mind for the next time you need help that when you list a build pushing roughly $2000~ in parts alone that another PC enthusiast would expect you to know how important Clock speeds and power delivery are actually the most important information about your hardware we could ever get to assist you.
 

Velyse

New Member
Have you tested, does this also happen if you only use one 290x? I would think the crossfire setup could potentially be the cause of your problem. So that would be an easy test to rule this out.
Dota doesn't run crossfire so the second card just sits idle. It's a factory OC card, a gigabyte windforce3 card, they run about 72-74c in dota, which is pretty low compared to other games with no problems.

I do have a 1000w power supply and literally everything is stable, I can run Arma3 for hours on end which taxes the hell out of both card, and my CPU, problem free.

4770k is at 4.5ghz and 1.29v iirc, it's also p95 stable and benches at about 65-70c, never above 58c in any game I have thrown at it.

I guess I was silly for thinking you folks would assume my machine was stable in literally everything else I throw at it.
 

Krazy

Town drunk
Why on earth would we assume that? We regularly have people come here with issues where the root cause is system instability, so we have to ask and clarify these kinds of things.

Anyway, have you tried capping the framerate in DotA so that your game and OBS aren't competing for GPU time? This sort of error almost always happens when the GPU drivers crash due to instability or overheating. Even though Arma 3 "taxes the hell" out of your system, OBS uses your system in different ways than a game.

You can also experiment with downgrading drivers, or maybe trying any available beta drivers. The root cause of your issue is some sort of instability, somewhere with your GPU or the drivers, that's exactly what the error message says is the problem. Maybe it's a combination of the way DotA needs to use your GPU + OBS running that exposes the instability or something, it's really hard to say for sure. I'd also recommend swapping out which GPU is the "main" one.
 

Velyse

New Member
Why on earth would we assume that? We regularly have people come here with issues where the root cause is system instability, so we have to ask and clarify these kinds of things.

Anyway, have you tried capping the framerate in DotA so that your game and OBS aren't competing for GPU time? This sort of error almost always happens when the GPU drivers crash due to instability or overheating. Even though Arma 3 "taxes the hell" out of your system, OBS uses your system in different ways than a game.

You can also experiment with downgrading drivers, or maybe trying any available beta drivers. The root cause of your issue is some sort of instability, somewhere with your GPU or the drivers, that's exactly what the error message says is the problem. Maybe it's a combination of the way DotA needs to use your GPU + OBS running that exposes the instability or something, it's really hard to say for sure. I'd also recommend swapping out which GPU is the "main" one.

I don't know why, I am sure you do, it's just going out of my way to make an account here to ask a question, I would probably look at fixing my system instability if there was any first and attribute OBS crashing to that lol.

I really can't go too far back in drivers as I think 13.11's are the earliest that support the R290 series chipsets.

I am going to dial the framerate back to 30fps and see what that does, I don't think I have the upload to really push much quality past 30fps anyway, cue south park local cable company skit.

I was hoping maybe there was simply something I was missing, or perhaps the 14.4 drivers and 290x's were having issues with OBS in general and there was a better combination to work with.
 

Krazy

Town drunk
Good lord, I just realized you were streaming at 90FPS in that log, no wonder everything exploded. Try again with settings that aren't insane.
 
Top