Windows 7 BSOD with some info..

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by fratleyslaye, Jan 29, 2010.

  1. fratleyslaye

    fratleyslaye New Member

    Joined:
    Jan 29, 2010
    Messages:
    12
    Likes Received:
    0
    While gaming today, I got a blue screen of death.(mass effect 2, by the way) Well, it actually crashed the game for a moment, and windows told me there was a problem with game. this isn't unheard of for a game to have a problem, so i checked temps on computer just verifying this new game wasn't overheating anything, and I was fine. re-ran the game, and 30seconds into the game it crashed again, but instead of giving me a windows notification that the game has stopped working, it blue screened.

    i ran perfmon /rel (an old command i remembered from problems with vista) and got this from the crash.

    Code:
    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7600.2.0.0.256.1
    Locale ID:    1033
    
    Extra information about the problem
    BCCode:    101
    BCP1:    00000031
    BCP2:    00000000
    BCP3:    807C3120
    BCP4:    00000001
    OS Version:    6_1_7600
    Service Pack:    0_0
    Product:    256_1
    Bucket ID:    CLOCK_WATCHDOG_TIMEOUT_4_PROC
    Server information:    9d6623e0-92b3-404d-86be-db937d8c4e93
    

    Read stickies, followed all of the guidelines. resource and performance monitor gave back one driver error, but i couldn't find any information about this on google.

    Symptom: [​IMG]
    Device is not present, not working properly, or does not have all of its drivers installed.
    Cause: A device has a configuration problem that prevents it from working properly. Details: The device, adfs, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_ADFS\0000. Resolution: 1. Verify the correct driver is installed.
    2. Try updating the drivers using Windows Update.
    3. Check with the manufacturer for an updated driver.
    4. Attempt to uninstall and then reinstall the device using Device Manager. Related: Explanation of Error Codes Generated by Device Manager
    Manage Devices in Windows

    Tried using windows debug tools and couldn't get it to work. installed, and said symbol path is not initialized. but just for the sake of it, i'll post the info it gave back.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\012910-21730-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0x85c4c000 PsLoadedModuleList = 0x85d94810
    Debug session time: Fri Jan 29 04:58:09.236 2010 (GMT-6)
    System Uptime: 1 days 1:39:12.405
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    .....
    

    any help is greatly appreciated, and anything else that I may need to do to further assess my situation, please let me know and I'll get right on it. Thanks!

    ~Bobby
     
  2. Blunts

    Blunts New Member

    Joined:
    Dec 5, 2009
    Messages:
    22
    Likes Received:
    2
    Have you overclocked your processor, or GPU?
     
  3. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    to get debugger to load symbols you need to open debugger then click on the File menu item, then on Symbol File Path.
    then In the window that opens, insert the exact text on the next line in the Symbol File Path box. This is a critical step, and if done incorrectly you'll end up with symbol errors:

    SRV*c:\symbols*hZtp://msdl.microsoft.com/download/symbols (replace the Z for a t ;) )

    I also suggest you upload your minidump and it can be run through debugger ;)
     
  4. fratleyslaye

    fratleyslaye New Member

    Joined:
    Jan 29, 2010
    Messages:
    12
    Likes Received:
    0
    012910-21730-01.dmp
    here is my most recent one.

    012010-18642-01.dmp
    about a week older.

    011710-18954-01.dmp
    about 2 weeks.

    these are only 3 i've ever had, to be honest. i'd upload my dump.dmp but it's massive, like 250mb. O_O

    I played around with overclocking awhile back, but didn't save any changes at all i'm about 99% positive. and even then i was trying to underclock my card, when I used to think my computer was overheating. Turns out it's a driver error between windows7/nvidia/another video game I play :p

    I'd love for both problems to be solved, but i'll stay on topic.

    Oh, also about the windows toolset... i used this line exactly:

    SRV*c:\symbols*hZtp://msdl.microsoft.com/download/symbols

    without the z, obviously ;) but it still doesn't seem to read it correctly. says the debugee is not connected.
     
  5. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    change your setting to small memory dump ?
     
  6. fratleyslaye

    fratleyslaye New Member

    Joined:
    Jan 29, 2010
    Messages:
    12
    Likes Received:
    0
    not sure how to do that... isn't the minidump more than enough info though?
     
  7. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    the newest dump file wont run through windows debugger it says it's corrupted and blue screenview didn't come up with anything helpful, although you do have some drivers which need updating or removing
    I would suggest research those drivers with google and update them, then remove your old dump files and setup your pc to record small memory dump files :)

    when you next get a blue screen go to the dump file normally found C:\Windows\Minidump and copy it to an easily accesible folder or to desktop then zip it and attach it to your post here :D
     

Share This Page

Loading...