Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The ROOT CAUSE is explained as such:This issue occurs because of a timing issue in the Server service driver. This timing issue involves the operation that adds a new SMB session to the global session table and the operation that closes an SMB session. In this timing issue, the Server service driver synchronizes these operations incorrectly. When this behavior occurs, an SMB session is added to the global session table after the session is deleted. Therefore, an entry in the global session table references freed memory. When the freed memory is accessed, you receive the Stop error message that is mentioned in the "Symptoms" section.
Which basically means a server you are acessing is incorrectly handling the passing of information via Windows server message block protocols. Probably by the hackshield they are using. Just saying.
Hotfix here (Windows Vista & 7) if you want to try it:
http://support.microsoft.com/kb/951418
Heed the warnings and good luck. I ran it and noticed no change system wide except that my game stopped hard crashing and doesn't force my system to restart. I can play the game smooth now.
This topic is two years old, no need to bring up the past. :)
Indeed, besides it wasn't a hardware problem, but a software incompatibility thing. Cheers for trying though. ;)