Crashing a lot Info includes Dxdiag + crash errors

same proablom i cant stand it tis drive me crazy!!! nad its onyl since the last update

ggg save us ? ?

I promise you I tried everything suggested and not suggested. Yes I'm glad it works for you and guess what? It worked for a lot of my friends but at the same time just because it doesn't work for the 10% doesn't mean we should be ignored right?

Do me a favour and look on Reddit as well as here since the start of 3.1 on how many people who have similar crash and if you count less than a hundred I will send you a stash tab gift. That's how bad it is and not even one response from GGG. It sucks to be honest and the only response I get from them on email was "did the latest patches fix it?"

Nothing else and it sucks. But it is what it is,I won't lose sleep over it but I support a company who treats me well and doesn't ignore me.

"

SlippyCheeze wrote:

"

edys007 wrote:

RIP so you have 6k PC and a beastly video card I bet. Well that shits on my plans buying a new one. Yeah it sucks because other games work no problem I swear. Skyrim with mods, Fifa 15, warband with mods as well as gta v with police mods just to name very few and I don't crash ever on them .

Inb4 they don't have the same budget :P

It is worth noting that I have had no similar problems on either a mid-2013 system, or a right-now system; I'm absolutely not saying that the problem does not exist. I am, though, saying that it is not a universe issue.

Buying a new system may solve your problem. It also may do nothing useful for you. Without knowing the exact cause we can't predict that. :(

I'd start looking at anything that runs in the graphics pipeline (eg: overwolf, steam overlay, riva stats server, etc), or pokes the graphics card (eg: hardware monitoring), as well as checking that the files on disk were not corrupted (eg: packcheck.exe or steam "verify local files")

I'd also give a shot at reinstalling the upstream drivers for my graphics card, and DirectX 9/11 from the redistributables supplied by Microsoft, just in case it was something there.

I'd probably also make sure that any "internet security" software that might inject code into the executable at runtime was disabled or removed, because I have seen that cause random memory corruption in the past. (No doubt due to the excellent code quality of those "security" software.)

"

edys007 wrote:

I promise you I tried everything suggested and not suggested. Yes I'm glad it works for you and guess what? It worked for a lot of my friends but at the same time just because it doesn't work for the 10% doesn't mean we should be ignored right?

Nope. I'm glad you tried all that stuff, and I'm sorry the problem persists. I hope that GGG can find a solution that fixes it for you. (and please remember, I can't know what you have or have not tried before.)

"

edys007 wrote:

Do me a favour and look on Reddit as well as here since the start of 3.1 on how many people who have similar crash and if you count less than a hundred I will send you a stash tab gift. That's how bad it is and not even one response from GGG. It sucks to be honest and the only response I get from them on email was "did the latest patches fix it?"

So, fun fact: when I got into the queue at the 3.1 launch, 42,000 people were ahead of me at 3PM Friday in NYC, which makes it even earlier in the workday in the rest of the US. That strongly suggests that number is significantly lower than the final count of people playing at 3.1 launch, but we can definitely know that there were at least that many.

If I find 100 people reporting a similar crash, that would be 0.24 percent of players having problems that, frankly, could be caused by any number of hardware or driver issues. In fact, they could be caused by a wide range of different hardware or driver issues, manifesting in the same problem.

The errors most commonly shown are basically "oh, gosh, this thing failed to load". Not "failed for this specific reason", just a generic "ugh, didn't work." So, yeah, they might all be the same, or there might be thirty different reasons hidden in there.

So, no, I absolutely don't think that the people with these problems should be ignored. I also don't think they are a sign the game is nearly as bad as people suggest; using extremely generous numbers we could maybe argue that one percent of players, not ten percent, are having problems.

(and I'd wager that there should be an extra zero ahead in there to account for people who didn't queue on day one, or closer to 0.025 percent of players having bugs like this. don't forget, pretty much nobody comes to the bug report forum to say "yeah, works just dandy for me")

I guess it's too bad for us then, I just recieved an email from GGG

"

Hello there,

Thanks for getting back to us about this, and for letting us know.

I am truly sorry, but I'm afraid we're unable to assist further with this issue at this time, as our Customer Support department is currently overwhelmed with several thousand requests for support.

I'm sorry we can't be of further assistance at this time.

Kind regards,
Rachel

Hopefully 3.2 ...

Started happening for me aswell ever since 3.1.. If i run dx11 i will 100% crash every time i try to run Blood Aqueduct in act9, most times as soon as i try to load into the zone, sometimes i get to run 10-30 seconds before it crashes.. If i go down to dx9 i can run the zone over and over with no problem.. Dx11 related issue?

"

Sneakyjones wrote:

Started happening for me aswell ever since 3.1.. If i run dx11 i will 100% crash every time i try to run Blood Aqueduct in act9, most times as soon as i try to load into the zone, sometimes i get to run 10-30 seconds before it crashes.. If i go down to dx9 i can run the zone over and over with no problem.. Dx11 related issue?

For you, it sounds like it is, yes. Sadly, it probably isn't just one issue, but hey.

Given that, and that DX11 works for many people, I'd look at the question, "what could be different about my computer to theirs", and start with things like hardware issues (eg: check fans, ensure card is seated correctly, etc), and ensuring that drivers and DirectX software is good.

Installing the DirectX redistributable package from Microsoft helps with the later, ensure the latest driver from the vendor, or perhaps try and older one, and see if any of that helps.

Oh, and run stock clocks, if you overclock, and ensure that nothing like afterburner, or whatever, that might be poking at the GPU or driver at the same time is happening.

I know for at least some people updating to the latest afterburner (or, specifically, latest Riva Statistics Server, which it uses) stopped crashes; the software that was injected into the game client rendering pipeline by that software was breaking PoE.

So it's always our fault because it works for most and doesn't work for us right?

Other games work heck fuckin GTA v works still on mid and high and the minimum requirements is way more than GGG'S yet and GGG'S doesn't work.

"

Sneakyjones wrote:

Started happening for me aswell ever since 3.1.. If i run dx11 i will 100% crash every time i try to run Blood Aqueduct in act9, most times as soon as i try to load into the zone, sometimes i get to run 10-30 seconds before it crashes.. If i go down to dx9 i can run the zone over and over with no problem.. Dx11 related issue?

I would like to +1 this.

W7 Ultimate playing on DX11
770GTX 4gb with 388.71 drivers (latest)
i5 4670k

I get the "display driver has stopped working" coupled with the ~50+ error message popups on top of black screen that look like the ones posted on the first page of the thread in the a9 blood aqueducts, sometimes seconds after entering, sometimes while clearing it.
Haven't gotten it in any other zone yet.

I can barely play the game but every patch performance is poorer. I suppose my mid end pc will not be able to play the game even on 768p monitor( I have old monitor but decent specs for games like fifa 16, dota 2 on medium-high with particle effects). I am thinking of upgrading but reading how everyone is having issues doesn't seem worth it.