peckham Posted December 20, 2002 Share Posted December 20, 2002 Has anyone had a problem where they minimize CMBB, then click on the taskbar button to restore it, and the game screen goes completely black? This happens to me every time I drop out of CMBB with the windows key, or CTRL-ESC. No way to restore the game, as everything stays totally black...I have to switch to taskbar and forcibly end the program. I'm using an IBM A31p laptop with an ATI Mobility Radeon FireGL 7800 card w/64 MB of RAM, under Windows XP Pro. 0 Quote Link to comment Share on other sites More sharing options...
Madmatt Posted December 20, 2002 Share Posted December 20, 2002 Does this also happen if you Alt-Tab or just when you use Cntrl-Esc or use the Windows Key? Madmatt 0 Quote Link to comment Share on other sites More sharing options...
peckham Posted December 20, 2002 Author Share Posted December 20, 2002 I figured it out!!! Okay. This problem may affect other users, since it's related to an XP SP2 hotfix (post-SP1). Here's what I did to track it down. 1. First, to answer your question Matt, it happens whether I hit CTRL-ESC, the Windows key, or ALT-TAB. 2. After posting my error message here, I used an early system restore point to go back, pre-windows-updates, and noted that CMBB went back to working fine, i.e. the display did not "black out" after minimizing once. 3. On a hunch, I whipped out my original build discs and initiated an image restore back to factory defaults. 4. Upon completion, I installed and tested CMBB. No problems. 5. I proceeded to connect to IBM's website to download all the latest drivers, including the latest video driver. Installed and tested CMBB. No problems. 6. I connected to the Windows Update site and installed SP1 for XP Pro. Tested CMBB post-install. No problems. 7. I connected back to the Windows Update site and installed the following post-SP1 hot fixes: http://support.microsoft.com/default.aspx?scid=kb;en-us;329834 http://support.microsoft.com/default.aspx?scid=kb;en-us;329048 http://support.microsoft.com/default.aspx?scid=kb;en-us;328310 http://support.microsoft.com/default.aspx?scid=kb;en-us;810565 http://support.microsoft.com/default.aspx?scid=kb;en-us;329115 http://support.microsoft.com/default.aspx?scid=kb;en-us;329390 Tested CMBB. THE PROBLEM WAS BACK. 8. I recorded the hot fix numbers (the last number in each of those hyperlinks) and proceeded to uninstall them one at a time. The culprit was 328310. From MS's support site: MS02-071: Flaw in Windows WM_TIMER Message Handling Can Enable Privilege Elevation The information in this article applies to: Microsoft Windows XP 64-Bit Edition SP1 Microsoft Windows XP 64-Bit Edition Microsoft Windows XP Home Edition Microsoft Windows XP Home Edition SP1 Microsoft Windows XP Professional Microsoft Windows XP Professional SP1 Microsoft Windows 2000 Advanced Server Microsoft Windows 2000 Professional Microsoft Windows 2000 Server Microsoft Windows 2000 Professional SP1 Microsoft Windows 2000 Professional SP2 Microsoft Windows 2000 Professional SP3 Microsoft Windows 2000 Server SP1 Microsoft Windows 2000 Server SP2 Microsoft Windows 2000 Server SP3 Microsoft Windows 2000 Advanced Server SP1 Microsoft Windows 2000 Advanced Server SP2 Microsoft Windows 2000 Advanced Server SP3 Microsoft Windows NT Server 4.0 Microsoft Windows NT Server 4.0 SP1 Microsoft Windows NT Server 4.0 SP2 Microsoft Windows NT Server 4.0 SP3 Microsoft Windows NT Server 4.0 SP4 Microsoft Windows NT Server 4.0 SP5 Microsoft Windows NT Server 4.0 SP6a Microsoft Windows NT Server 4.0 Terminal Server Edition Microsoft Windows NT Server 4.0 Terminal Server Edition SP4 Microsoft Windows NT Server 4.0 Terminal Server Edition SP5 Microsoft Windows NT Server 4.0 Terminal Server Edition SP6 Microsoft Windows NT Workstation 4.0 Microsoft Windows NT Workstation 4.0 SP1 Microsoft Windows NT Workstation 4.0 SP2 Microsoft Windows NT Workstation 4.0 SP3 Microsoft Windows NT Workstation 4.0 SP4 Microsoft Windows NT Workstation 4.0 SP5 Microsoft Windows NT Workstation 4.0 SP6a This article was previously published under Q328310 SYMPTOMS Windows messages provide a way for interactive processes to react to user events (such as keystrokes or mouse movements) and communicate with other interactive processes. The WM_TIMER message is sent at the expiration of a timer, and it can be used to cause a process to run a timer callback function. This message may create a security vulnerability because it is possible for one process in the interactive desktop to use a WM_TIMER message to cause another process to run a callback function at the address of its choice, even if the second process did not set a timer. If that second process has higher privileges than the first process, this would provide the first process with a way of exercising the functions. By default, several of the processes that are running in the interactive desktop do so with LocalSystem privileges. As a result, an attacker who can log on to a system interactively can potentially run a program that would levy a WM_TIMER request upon such a process, causing it to take any action the attacker specified. In this scenario, the attacker can have complete control over the system. The security patch that is described in this article addresses this vulnerability, and it also makes changes to several processes that run on the interactive desktop with high privileges. Although none of these processes would allow an attacker to gain privileges on the system in the absence of the WM_TIMER vulnerability, we have included them in the patch to make the services more robust. RESOLUTION For more information about how to resolve this vulnerability, click any of the following links: Windows XP (all versions) Windows 2000 (all versions) Windows NT 4.0 (all versions) Windows XP (All Versions) Download Information The following files are available for download from the Microsoft Download Center: Windows XP Home Edition and Professional All languages: Download the 328310 package now Windows XP 64-bit Edition All languages: Download the 328310 package now Release Date: December 11, 2002 My guess? This "fix" will create problems for anyone running CMBB, that tends to drop out of CMBB for various reasons during a game. Matt, can you guys test this? Do you need any additional information from me? I'm totally cool now, since I don't care much about that particular hotfix, but it could be an issue when Microsoft releases SP2 for XP and bundles this in, in which case anyone with SP2 would have the problem. Thanks, Matt 0 Quote Link to comment Share on other sites More sharing options...
Harv Posted December 21, 2002 Share Posted December 21, 2002 I can confirm that this is an issue with my machine also. Sadly, I had System Restore turned off and had to reinstall Windows, but all is well now as long as I don't install 328310. Dell i8000 Laptop Geforce 4Go 64mb Video Harv 0 Quote Link to comment Share on other sites More sharing options...
MRoadster Posted December 21, 2002 Share Posted December 21, 2002 Peckham, Great job tracking that one down. I was using the 40 series drivers with Alt-Tab, but mysteriously got the "blackout" problem. Since this latest graphical glitch came up I've been using the 30 series drivers again. I did notice that if I Alt-Tab in the 30 series, for whatever reason, I'll still get the "blackout" effect. At least I can read the text again. I hope this issue gets worked out... 0 Quote Link to comment Share on other sites More sharing options...
Nick Schieben Posted December 21, 2002 Share Posted December 21, 2002 That was some great detective work! Mazin' ennit! how we have to continually trade off with Windows functionality and security. I'm very wary of the constant XP updates, as they sometimes fix and break things at the same time. Fortunately I've not updated since SP1, and I'm using the 41.07 drivers (which are dynamite with Il-2!). However I've not bothered with AA effects since AF looks very nice on its own, and there's always the chance that one ALT TAB too many can send that CMBx turn into the bit bucket! At least that sometimes happened when I was using Win2kPro. Regards 0 Quote Link to comment Share on other sites More sharing options...
PiggDogg Posted December 21, 2002 Share Posted December 21, 2002 Matt & Guys, In both CMBB & CMBO, I have had the same problem that Peckham has had. I have not solved the problem. However, I get around the problem by never minimizing either game. Further, before I load a new file, I close the game & then open it again. I have an AMDxp2100, Ti4200 w/128 meg, 1 gig PC2700 ram, WinXP Professional, Soyo KT333 Dragon Mobo. If you solve the problem, I would be pleased. I'll keep an eye on this thread. Cheers, Richard 0 Quote Link to comment Share on other sites More sharing options...
peckham Posted December 22, 2002 Author Share Posted December 22, 2002 All, Do note that you should be able to go back into your add/remove programs and remove 328310, which fixes the problem. I'm not particularly concerned about the security issue that this "fix" is supposed to fix. Matt 0 Quote Link to comment Share on other sites More sharing options...
KursruK Posted December 27, 2002 Share Posted December 27, 2002 I also have this problem. I get around it the same way Pigg-Dogg does. I just never minimize the game. Kind of inconvenient. Anyone of you techy-maestros figured this out yet? 0 Quote Link to comment Share on other sites More sharing options...
peckham Posted December 27, 2002 Author Share Posted December 27, 2002 That's certainly another solution, Tigger, but considering the fact that some MP games can take whole days to play, I need the option to hop in and out of the game to conduct other business simultaneously. Again, the permanent fix is really as simple as uninstalling the MS hotfix in your add/remove programs. I'm not sure whose "fault" this particular glitch is, i.e. Microsoft's or Battlefront's, but considering that the hotfix just came out on Microsoft's Windows Update site, 12/11/2002, I see no compelling reason to leave it on. Just remove it. Fixes the problem, guaranteed, 100%. Matt [ December 27, 2002, 08:19 AM: Message edited by: peckham ] 0 Quote Link to comment Share on other sites More sharing options...
KursruK Posted December 27, 2002 Share Posted December 27, 2002 Matt, I got it to work thanks to your help. Greatly appreciated! 0 Quote Link to comment Share on other sites More sharing options...
LtCol.05 Posted December 28, 2002 Share Posted December 28, 2002 I have 328310 loaded on my XP Home OS and do not have this problem. I'm guessing then that it is exclusive to XP Pro.... 0 Quote Link to comment Share on other sites More sharing options...
peckham Posted December 28, 2002 Author Share Posted December 28, 2002 Could well be limited to XP Pro, which is what I'm running on both a desktop and laptop that had the problem. If so, that's good news for anyone running XP Home. 0 Quote Link to comment Share on other sites More sharing options...
Belaja smert Posted December 29, 2002 Share Posted December 29, 2002 I confirm the bug and the solution for it. I have XP Pro installed and had the same problem. Removing Q328310 solved my problems too. Excellent work tracking down this bug. Here's my setup: - Win XP Pro - Athlon XP 2000 - nVidia G4 Ti 4200 - Asus A7V333 - 512mb RAM 0 Quote Link to comment Share on other sites More sharing options...
easytarget Posted December 29, 2002 Share Posted December 29, 2002 strange - i have 328310 installed on my xp pro and i drop in and out of the game w/o any issues 0 Quote Link to comment Share on other sites More sharing options...
walpurgis nacht Posted December 29, 2002 Share Posted December 29, 2002 Originally posted by easytarget: strange - i have 328310 installed on my xp pro and i drop in and out of the game w/o any issuesI think this is only a problem on a laptop. 0 Quote Link to comment Share on other sites More sharing options...
peckham Posted December 31, 2002 Author Share Posted December 31, 2002 That's odd easytarget, because Belaja smert's configuration is a desktop (not a laptop), so the problem's not limited to just laptops (or video cards, since I was having the problem with an ATI Mobility Radeon FireGL 7800, while Belaja smert's having it with an Nvidia Geforce 4 Ti4200). Could be some subtle variation in the mainboard chipset architecture? The "bug" introduced by Microsoft's "fix" has something to do with system processes and runtime prioritization. Perhaps there's something unique to certain chipsets and bridge drivers that don't play well with the SP2 hotfix installed. In any case, laptop or desktop, and whatever chipset you're running, I have yet to hear from someone having this problem who's been unable to fix it by uninstalling 328310 (and enough have succeeded in fixing the problem by removing it that I'm certain it's the catalyst). [ December 30, 2002, 11:55 PM: Message edited by: peckham ] 0 Quote Link to comment Share on other sites More sharing options...
Belaja smert Posted January 5, 2003 Share Posted January 5, 2003 *BUMP* It would be nice to have this problem addressed... 0 Quote Link to comment Share on other sites More sharing options...
Japper Posted January 29, 2003 Share Posted January 29, 2003 This advice deserves a nice bump because it helped me get ridd of that damn black screen. Microsoft :mad: :mad: 0 Quote Link to comment Share on other sites More sharing options...
Warren Peace Posted January 30, 2003 Share Posted January 30, 2003 Thanks for the great detective work! This totally fixed my problem on my Dell Inspiron 8100. 0 Quote Link to comment Share on other sites More sharing options...
Uedel Posted January 31, 2003 Share Posted January 31, 2003 Ok WinXP HOME here this was also my failure, i first mentioned it after i upgraded to new catalyst drivers, but didnt also play cmbb lot before for some reasons. i descriped my problem here My Message on this Board But this fix here helped me !!! 0 Quote Link to comment Share on other sites More sharing options...
PaleRider Posted February 6, 2003 Share Posted February 6, 2003 Good call guys... Removing the Microsoft "fix" solved the problem I was having with black screens when trying to play CMBB on my notebook. Thanks, PR [ February 05, 2003, 10:56 PM: Message edited by: PaleRider ] 0 Quote Link to comment Share on other sites More sharing options...
Holman Posted February 14, 2003 Share Posted February 14, 2003 Looks like I'm the new guinea pig... As of today, I'm the proud owner of a brand new computer running Windows XP Home. The first thing I did when I got everything plugged in was to download the latest (41.09) NVIDIA drivers and then install CMBB and the 1.01 patch (I don't yet have 1.02). When I try to run CMBB, my monitor goes black and can only be restored by alt-tabbing to the desktop. Switching back into CMBB means a black screen again, every time. This video card and these drivers were great for CMBB on my old machine, which ran Win 98se. I haven't downloaded any Windows XP updates, and none are listed in my Add/Remove Programs list. Control Panel says I have "Windows XP Home Edition, 2002 version, Service Pack 1." [edit: I should add that I get the same black screen whether I have FSAA or Anisotropowhatever enabled or not...] What can I do? Is there a way to eliminate this mysterious 328310 from my system? Or is there a generation of NVIDIA drivers that I should go back to? (Say it ain't so! I'm waiting to run IL2: Forgotten Battles on this machine!) My specs: Pentium 4 2.4 GHz CPU 256MB RAM (more on the way) Windows XP Home edition GeForce4 Ti4400 128MB RAM vid card NVIDIA 41.09 drivers Thanks! [ February 13, 2003, 11:06 PM: Message edited by: Martyr ] 0 Quote Link to comment Share on other sites More sharing options...
Schrullenhaft Posted February 14, 2003 Share Posted February 14, 2003 You have to go back to the 30.82/30.87 drivers. Windows XP Service Pack 1 includes the WM_TIMER patch that causes this problem (so you'll be unable to install it). You're only solution for CMBB is to go back to an earlier NVidia driver, but this won't work if you also upgraded to DirectX 9.0 (which is not necessary for CMBB or almost any other game currently available for that matter). Windows 98SE worked because the OS doesn't have the WM_TIMER vulnerability that Win2K/XP does and thus it doesn't have the patch that is the root of this problem. Hopefully NVidia sees this as a problem (I don't konw which other games may be experiencing this problem) and they may be able to correct it with some future driver. [ February 14, 2003, 01:10 PM: Message edited by: Schrullenhaft ] 0 Quote Link to comment Share on other sites More sharing options...
Holman Posted February 15, 2003 Share Posted February 15, 2003 Thanks for the advice. I've gone back to 30.82, and everything is now OK. However, graphics are a little murkier than under the 40 series drivers, probably because 30.82 doesn't have the "texture sharpening" option. Is there a benefit to using 30.87 over 30.82? And is there a way to get texture sharpening under 30.xx drivers (a tweak utility perhaps)? Again, this is for a GeForce4 Ti4400 128MB card. Thanks! [ February 15, 2003, 03:24 PM: Message edited by: Martyr ] 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.