Computer crashing when connecting to specific game platforms

Jocarrian · 08 Nov 2014

Hello all,

I bought Valiant Hearts a couple of weeks ago. I installed it and was ready to play it. But when you install and play it on steam, you also have to go through Ubisofts own gaming platform called "Uplay". Everytime my computer tries to connect to Uplay, it freezes and I have to pull the plug to the computer.

I've been in contact with ubisoft support but I'm just getting generic responses that doesn't do any good. They have said that I should update the drivers on my MOBO though. But it had never happened with any other gaming platform. So I assumed that it was Uplays fault and not my computers fault (because my computer is working like a dream atm)

2 days ago I got the Heroes of the Storm technical alpha. I installed it, but when I ran it, my computer froze, just like with the Uplay application. I've been trying to fix this with the help of blizzard community and I managed to get the game running and I got to see the cinematic trailer in the begining of the game. But when Battle.net was going to "Authenticate" my account, my computer froze.
The same thing happened to day when I was going to "connect" to battle.net so I could use the Starcraft 2 Map editor.
Now I've realized that there is something wrong with my computer.

To sum things up, I get the computer freeze when I'm trying to connect to the gaming applications servers.
Might there be something wrong with my network drivers?

I would really, really appreciate help on this.

I will insert the DM log collector files.

Thanks in advance,
Joachim

Arc · 15 Nov 2014

Hi Jocarrian.

The crash dumps are of September. And those are reporting versatile issues including display failure. So what is the source of the issue is not determined specifically.

You do some tests first.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Update the display driver to 14.9 WHQL from Desktop

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.
______________________________________

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8800f4e1dbb, fffff88002be4228, fffff88002be3a80}

Probably caused by : atikmdag.sys ( atikmdag+c7dbb )

Followup: MachineOwner
---------

Code:

BugCheck 4E, {99, 176a70, 4, 1}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------