Loading...

Solved CPU Bug

Discussion in 'Help Desk' started by TrailBlazer, Jun 21, 2018.

Thread Status:
Not open for further replies.
  1. TrailBlazer

    TrailBlazer Member

    Joined:
    May 17, 2018
    Messages:
    20
    Likes Received:
    24
    Trophy Points:
    3
    Hiya!

    Long story short.
    I have an octa core CPU, so according to the D2 CPU bug approx. 12-13% of the cpu should be in use when the bug kicks in. This was not my case, it was oscillating around 30(!!)%.
    Did the D2Client.dll swap - CPU dropped to ~15-20%.

    Investigated running processes - turns out both core threads of D2 and Topaz Chat are good, its the GameGuard process that wreaks havoc, take a look:
    threads.PNG
    It's in Polish. Sorry. But you get the idea.

    What do I do? Is there anything that can be done with this? Anyone experienced it?
    Normally I do as much as I can by myself with such issues, but GameGuard log is not human-readable, so I don't really know where to begin and I am messing with protection software here so I decided to stand back and call for help.
     
    Tini likes this.
  2. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,544
    Likes Received:
    5,153
    Trophy Points:
    113

    Best Answer
    Hello! The D2 CPU bug values given here are aproximate so having the next cpu generation after quad core which is an octa core cpu doesn't mean you will get half of the quad core mentioned value due to the process being x86 (32bit) and the coding flaw within the game, although I get half of what you get and on a quad core cpu. The fix we provide on ou website is working but doesn't fix the bug entirely, it's way better than nothing though. Anyhow, seems there are some issues with the recent signed drivers by microsoft and I guess it all started few weeks ago when they attempted to fix this recent faulty update as it was fine before that and causes the gameguard shield to do extensive searching for unallowed processes due to a bug in the .NET framework similar to how the game misses the nosleep function thus causing the known cpu bug. Already informed the developer about that and the fix should be provided in the next few days so you don't need to do anything on your side. I'll update the thread once this happens, thank you.

    We received the new update together with the fix today so I'll have it tested for a few days during the coming week since a lot of coding improvements have been made in this update and we want to make sure everything is alright and there won't be any connection issues or so before releasing it to the public.

    The update should be pushed at the end of this weekend.


    Update completed and the bug has been fixed as well.
    "Thanks" microsoft for screwing us over in the first place.
     
    Last edited: Jul 9, 2018
    ameth, Tini, Atox and 3 others like this.
  3. TrailBlazer

    TrailBlazer Member

    Joined:
    May 17, 2018
    Messages:
    20
    Likes Received:
    24
    Trophy Points:
    3
    Gix to the rescue, as always. :tup:
    Really appreciate constructive replies like this one. 12/10.


    In the past I've worked in technical support field for nearly 6 years, I know what I'm talking about.
     
    Gix likes this.
Loading...
Similar Threads - CPU Bug
  1. da3mon
    Replies:
    1
    Views:
    1,278
  2. D2Addict
    Replies:
    6
    Views:
    1,802
  3. JmeN
    Replies:
    2
    Views:
    1,803
  4. Quinneczech
    Replies:
    2
    Views:
    1,208
  5. Killa_Kem
    Replies:
    3
    Views:
    1,693
Thread Status:
Not open for further replies.
Loading...