locked
Warcraft Causing Vista Bluescreen RRS feed

  • Question

  • So I've been trying to deal with this for months and Vista keeps bluescreening/locking up when I play this game. This is the only reason I pretty much have this computer and it appears to be the only thing locking it up. I've been trying to find accurate information for troubleshooting this issue. The event log is pretty useless but the only errors I see are 6008, and another involving kerebros. I have installed the lastest drivers from Nvidia for the 8600GT, I have also installed all the windows updates to this point.

    Any particular area I can look for a more informative troubleshoot? I've never seen so many bluescreens except when I updated to vista, very poor software.
    Thursday, December 25, 2008 5:04 PM

Answers

  •  

    Hi George, to troubleshoot BSOD crash issues, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     


    Sean Zhu - MSFT
    Monday, December 29, 2008 1:42 AM
    Moderator

All replies

  • Hi

    One thing to remember is that a BlueScreen is almost always the result of a hardware/driver error.

    What will help in troubleshooting the BSOD is information from the blue screen itself.

    See the following website for an image and description of the important parts of a typical blue screen. The information in the sections with the red outline can be helpful.

    http://i196.photobucket.com/albums/aa86/rvmv/BSODDetails.jpg

    *NOTE: If the blue screen disappears too fast to write down the information, perform the following.

    Open Control Panel, on the Tasks menu, select the Classic View.
    Double click System, select the Advanced System Settings on the Tasks menu.
    In the Startup and Recovery section, click the Settings button.
    Finally, under System Failure, remove the check mark from Automatically Restart option.
    This will allow the bsod to stay on the screen until you manually shut the system down.

    In addition, open Problem Reports and Solutions in Control Panel.
     
    Select View Problem History in the Tasks Pane.

    Look in the Windows section for Shutdown Unexpectedly in the Problem Column that corresponds to the date and time that the BSOD appeared. Double click that error to see the details. At the bottom of the details window, click the Copy to clipboard button and paste the results, along with the other information,  in a reply to this thread.

    Let us know what you find.



    Ronnie Vernon MVP
    Friday, December 26, 2008 9:09 PM
    Moderator
  • Thank you for the reply I have found several hang ups (as stated)

    Here's one below: I didn't know if you wanted any of the dump information. From the memory analysis I did on the dump file, it doesn't appear like a lot of memory is being consumed (4 megs). But when I looked at the analysis file I get: DebugDiag failed to locate the PEB (Process Environment Block) in Mini122508-01.dmp, and as a result, debug analysis for this dump may be incomplete or inaccurate.


    Problem signature

    Problem Event Name: BlueScreen

    OS Version: 6.0.6001.2.1.0.768.2

    Locale ID: 1033

    Files that help describe the problem

    Mini122408-02.dmp

    sysdata.xml

    Version.txt

    View a temporary copy of these files

    Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

    Extra information about the problem

    BCCode: 101

    BCP1: 0000000000000061

    BCP2: 0000000000000000

    BCP3: FFFFFA60005EC180

    BCP4: 0000000000000001

    OS Version: 6_0_6001

    Service Pack: 1_0

    Product: 768_1

    I will write down the details on the next blue screen to see if you have any recommendations based on what's thrown back. I appreciate your help with this frustrating issue!

    Sunday, December 28, 2008 7:55 PM
  •  

    Hi George, to troubleshoot BSOD crash issues, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     


    Sean Zhu - MSFT
    Monday, December 29, 2008 1:42 AM
    Moderator