Battle.net

No ideas? :(

You will have to ask your laptop manufacturer for help. This is something related to hardware, something goes wrong somewhere.

There is a limit on how much we can help over the forum.

I'm sorry:(

Be sure to link to this thread when you ask for their help.

Well, Droy, you said you installed without drivers, to make sure they aren't the problem, but maybe you had the wrong ones all along?

Since you use VAIO you are in need of mobile drivers, so please download the GPU/Chipset drivers for your VAIO model, however not from ATI/nVidia and chipset manufacturer, but from Sony, if they released any.

Note that VAIO is not really meant for gaming. There's also a risk, that Moonshadow is right about this being a hardware issue. If you always played SC2 on your VAIO and didn't keep track of the temperatures you developed, your hardware may have been damaged.

Thanks for ur answers. But I did it too. Im asked for help from SONY support and have no answer. I downloaded drivers from officialy site and have same problem. I have no problem with similar model of VAIO (eb2z1r) but in (ea1s1r) I have. :(

14/06/2012 22:02Posted by RuuNa

Itself a division by zero is only telling you, why the program crashes. The question is what makes it possible for a division by zero to occur.

Yeah, just like any excpetion. What makes it possible to appear is obviously a lack of check for certain value, or assert. More important question is where it apears; in blizzards software, windows, or drivers.

As ruuna said, try to install drivers from either ATI or nvidia, whatever you have. I would also try to run the laptop with only one stick of ram; and test each separately. I know it si pain in the a.. to take out ram from laptop, but it is not impossible.

It might be even sound or network drivers.

14/06/2012 22:02Posted by RuuNa

As I said, the problem isn't widely known, so if he receives it everytime he wants to play and he already redownloaded and installed other instances of the client it leaves his system to be the troublemaker.

At the time when I asked, he didn't posted when it happends; and that was reason why I asking. Stop taking the quarell to other people threads.

13/06/2012 11:06Posted by nooby

You get a debugger like softice or IDA, run game in the debugger and than find the spott where they do division with 0 and patch it by adding jump or by changing 0 to somehing like 1 :).

try
{
buggy block of code
}
catch(DivissionByZeroException* e)
{
e->show();
exit(1);
}

Which is what actually happens in there.

As I said, the problem isn't widely known, so if he receives it everytime he wants to play and he already redownloaded and installed other instances of the client it leaves his system to be the troublemaker.

At the time when I asked, he didn't posted when it happends; and that was reason why I asking. Stop taking the quarell to other people threads.

No offense, but based on your performance in the general discussion forums I prefer to neglect your input in future.
This comment you quoted, however, was before our "conversation".

Also I'm glad that all of us know, how try+catch works with exceptions, but I hope no one seriously thinks a debugger is appropriate here.

First of all I'd like to see a 64Bit dxdiag of the system as it is now. Also again since VAIO is not meant for gaming an error due to overheating cannot be excluded. Going on a bughunt will be difficult like this. So we may as well check system and hardware first, which has already been done partially, especially by the tests suggested by Moonshadow.

18/06/2012 22:40Posted by RuuNa

Also I'm glad that all of us know, how try+catch works with exceptions, but I hope no one seriously thinks a debugger is appropriate here.

no. I just said what is actually happening in the code.

If they didn't catch the DivisionByZero exception, there wouldn't have been a message displayed.