The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    random BSOD w/ Windows + Warcraft 3: FT (Bootcamp 1.3)

    Discussion in 'Apple and Mac OS X' started by demenion, Aug 3, 2007.

  1. demenion

    demenion Notebook Consultant

    Reputations:
    35
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    30
    This is the ONLY game I have problems with.

    I am running on a SR MBP, 256 mb 8600 GT, etc.

    I am trying to play Warcraft 3 (DOTA) but it's very unstable. Usually about 20-30 mins in I will just get a blue screen of death.

    I do not think its my temps because I forced my fans at 6k RPM with inputremapper, and it's only unstable on War3.

    I have played Quake 4 / ET: Quake Wars and they run perfectly.

    Has anyone tried playing Warcraft 3 on a SR MBP in Windows via Bootcamp?
     
  2. althanis

    althanis Notebook Enthusiast

    Reputations:
    0
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    15
    I'm about to purchase my MBP when I get to NYC tomorrow, and I'm a little worried about your problem, because the only game I play right now is TFT DOTA (master.db8r is my account name).

    How come you're running it in Bootcamp though? I thought all Blizzard games could run natively on a Mac?
     
  3. imMACulate

    imMACulate Notebook Evangelist

    Reputations:
    14
    Messages:
    386
    Likes Received:
    0
    Trophy Points:
    30
    they do he doesn't have to use Boot Camp...Actually, I can't think of a reason of why he would want to play on Boot Camp it's not any faster since all Blizzard games are compatible with both Mac OS X and Windows so I'm not sure why he's using Boot camp. Maybe you should try running it natively, and let us know what happens then
     
  4. Zero2007

    Zero2007 Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Hey demenion,

    My name is Andrew and I'm new to the forums.
    A little background info on me:
    I'm a freshmen in college (University of Hawaii) and have worked with computers for the past 8 years (WinME was my first case-- woo hoo)
    Anyways, I currently run a business of my own, 808 Geniuses LLC.

    K so aside from that...
    I recently had several of my high school classmates purchase the santa rosa MBP's (15.4 in model); the higher equipped version (similar specs to your's).
    And yeah, they play Dota (so do I) a lot and we ran into the problem before they left for college. Now they're gone but I'm still trying to help them remotely. And this is my report on the problem so far.

    I don't remember the exact BSOD details, but I remember looking into it and it was a faulty sound driver that caused the problem. If you google this kind of problem, there are other problems not related to games-- for instance, a fellow had an iMac (different, yes I know-- but the boot camp files are all similar) and had the BSOD after tinkering around with the iSight-- but get this-- It was a faulty sound driver as well.

    Back to our case. All of the specs work out wonderfully, and I can say with 99.9% confidence that the problem is only occurring under certain circumstances, in which WCIII can produce. I say this because other than the iSight problem listed above, this is the only game I've seen and have record of BSOD'ing on the user. My friends play WOW, which is much more of a burden on the CPU and GPU (more memory for this game, but you get the point) than WCIII, and WCIII is several generations old of a game.

    The last time I looked into the problem, the file listed on their BSOD's was a sound driver, and when I looked into it, it points at the Realtek integrated audio, particularly a file in the driver package itself.
    The audio driver would cause the memory fault problem, which results in the BSOD because of an overflow of audio commands, which I think can be reproduced through WCIII. My look at it is that older audio commands aren't cleared out of the memory (the RAM specifically, since my research showed that the RAM was somewhat included in the BSOD-- references not available since I'm free-writing this) and eventually "stack or pile up," causing the BSOD to occur within a similar and common time frame (from what I've seen and noted, anywhere between 20 minutes to 70 minutes). In theory, this does make sense, since the faulty sound driver has been identified.

    Now I started them off with bootcamp 1.3, and yes, their iSight, along with the backlit keyboard functions, worked under windows (even though it wasn't supported). Not sure on the stats on that, but bootcamp 1.4 is currently out, and apparently can be upgraded without re-partitioning the hard drive.

    The next steps on my things-to-do-list for them is to do the following:
    1. Make sure OS X is totally updated.
    2. Update to Bootcamp 1.4 (which contains video driver upgrades-- can't remember if sound was upgraded)
    3. If problems persist, upgrade the sound driver (a new version was released recently)
    4. If the problems still persist, then I may have to create an account on the bootcamp forum (if it exists, and I'm sure it does because I remember seeing something like that before).

    I'll try stay up to date on this forum, and hopefully, we can get this sorted out, because quite frankly, the machine's a beauty.

    If there are any questions, please feel free to email me at [email protected] and I'll try get back to you via email, OR the forum as soon as I can (mid-terms are up so I may take a few days).

    Good luck, and I hope to work with you guys some more in the near future.