2010-07-12, 03:37 PM
I believe Zakum boss stage(s) has a coding error in it, that cause memory overwrite, but because window 7 & vista handles processes (ms) bleaching their process space (memory) differently than XP. (As ms was developed and tested when XP was the latest windows version) When parts of zakum starts to disappear or funny graphic appears, suggests a memory overwritten and windows will detect it and perform preventative shutdown of the process to prevent a total system crash (BSOD). Just XP is less restricted about how much it allows a process to fail before it shutdown it.
The nature of a memory over write behaves is quite random depending on a lot of factors, in zakum's case it probably depends on number of attackers, skills used by the attacker (and non attackers), combine that with zakum's attack timing and that is the reason some people have window 7 & vista doesn't see that glitch and can finish without getting disconnected. Also it could got to do with the amount of video memory on your video card too.
There has been suggestion that if once you see the glitch, you need to go into windows mode (if you are not already in it) then click outside of ms on the desktop then press f5 to refresh will help getting around that d/c issue.
Here is a simple bat script that will do automate refresh every ~5 seconds for those that want to try it. I have XP and I never D/C as zakum yet, so I haven't tried the script while zaking, you can adjust the refresh rate by changing the number in the pings (2 and/or 5).
:START
rundll32.exe user32.dll,UpdatePerUserSystemParameters
@ping 127.0.0.1 -n 2 -w 1000 > nul
@ping 127.0.0.1 -n 5 -w 1000 > nul
GOTO START
The nature of a memory over write behaves is quite random depending on a lot of factors, in zakum's case it probably depends on number of attackers, skills used by the attacker (and non attackers), combine that with zakum's attack timing and that is the reason some people have window 7 & vista doesn't see that glitch and can finish without getting disconnected. Also it could got to do with the amount of video memory on your video card too.
There has been suggestion that if once you see the glitch, you need to go into windows mode (if you are not already in it) then click outside of ms on the desktop then press f5 to refresh will help getting around that d/c issue.
Here is a simple bat script that will do automate refresh every ~5 seconds for those that want to try it. I have XP and I never D/C as zakum yet, so I haven't tried the script while zaking, you can adjust the refresh rate by changing the number in the pings (2 and/or 5).
:START
rundll32.exe user32.dll,UpdatePerUserSystemParameters
@ping 127.0.0.1 -n 2 -w 1000 > nul
@ping 127.0.0.1 -n 5 -w 1000 > nul
GOTO START