I was running StarCraft 2 version 1. The earlier crash dump for 4th Jan shows a problem with nbdrv. It was fixed by downclocking my card in thundermaster. The issue turned out that the installer skipped out on installed a. We will be glad to help you.
What the fuck does this have to do with the thread? Believe it if you want. I've got a taiwan version also but that seems to work. Try to install the graphics drivers using compatibility mode and check if it helps. The issue turned out that the installer skipped out on installed a. If you're getting a frozen screen but can still hear audio you can Ctrl +alt + del and bring up the task manager, close it, and the game will resume as normal.
After these all failed, I decided to reinstall, which made the problem worse. Usually I can use the mouse, and Cmd+Q works albeit laggy as hell , but I can't type in my password, Cmd+M doesn't work. So as I said, I was just repeating what Blizzard has stated as the reason. There are a bazillion programs out there that can be installed on xp and 7 but won't work on 8. You have the right to have a functional card. What exactly is happening in your case? This will solve the crashing issue in most cases.
And, to comment on your previous post, the problem is not on my end. It's a well known issue. There are very few programs that don't work on 8 that work on 7, there are a lot more programs that wont work on 7 that work on xp your point is not only not helpful but just plain wrong. And look at me, here I am doing the same thing, look what you've done. Edit: And why the fuck are there always forum fighters trying to be smart and cursing around telling people not to reply to a one-day thread.
I'm stuck in this cycle. Anyways try disabling your sound devices and starting up sc2, try to isolate what is causing the issue. It would be nice if you could for example, upload your dxdiag information to pastebin. Hope this information helps, for further assistance please reply. If you don't believe me, take your factory overclocked card and turn it down to the reference speeds and see if it makes a difference. Hi, just an update: i have to put on rtss's black list this executable. Please follow the instructions in the tutorial carefully and especially the part about monitoring the temperatures and stopping if they get too hot.
Have you altered windows in any way? Then you decided to lump Blizzard in there too because why not? And why the fuck are you so mad? It was a fix designed to correct random flickering and crashes on those cards specifically. What the fuck does this have to do with the thread? We apologize for the inconvenience and we appreciate your patience while we get this issue resolved. Many thanks for leaving the additional fix idea in the comments. That is silly because that guy used it first but he's not warned? I just hope the fix is quick. I would try disabling or removing that software for now. People tend to make up crap like this using anecdotal evidence because they're having an issue that's almost certainly being caused by something else. My specs are Processor: intel i5-4690k 4x3.
Believe it if you want. Sometimes it crashes before the window comes up--the animated background of the ringed planet on the right freezes. I don't want to revert back to the former drivers because then I won't be able to play Crysis, not because I have a beta or cracked version of the game. Make sure security software hasn't prevented the part of the graphic card drivers installation software like Kaspersky will protect this area as it's high risk and will ask you while installing. Perhaps you should research your answers a little better before making suggestion that do not address the issue at all.
Parameter 1 identifies the type of error source that reported the error. Downclocking a card takes literally about 30 seconds. What the fuck does this have to do with the thread? Why bump a thread just to add on a comment that belongs to a luddite. I've had Virtualbox installed for months, without any updates recently. This will bring up System Information.
It turned out that lowering my graphics from ultra to high fixed the problem. I'll do a clean boot, and then upload the log files again. But after installing the newest drivers, my downclock gets instantly reset the moment I leave the thundermaster overclocker window. Also, I'm not about to downclock my video card just to wait and see if a problem that happens intermittently occurs. My information was troubleshooting based on the error message log provided. It was a great 2 for 1 deal.