1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Constant BSOD

Discussion in 'Windows 7' started by EvilSmoothie, 2009/06/01.

  1. 2009/06/01
    EvilSmoothie

    EvilSmoothie Inactive Thread Starter

    Joined:
    2009/06/01
    Messages:
    4
    Likes Received:
    0
    Ok so summerise I am receiving the BSOD mulitple times a day.

    System Rundown:

    Windows 7 X86 RC Build: 7100
    Asus Crosshair AM2, nForce 590 SLI Chipset
    AMD Athlon 64x2 Dual Core 6400+ ~3.2GHz
    4GB DDR2 RAM
    Nvidia GeForce 8400GS

    - I have ran MemTest overnight with 0 errors returned.
    - I previously had same problem on x64 version of Win7RC, so tried installing x64 version.
    - I have got two monitors setup, issue can usually be provoked by watching full screen flash videos of youtube for example, and occasionally whilst switching monitor setup (Via use of Win + P) - However often occurs when PC is idle or via general use.
    - Have downloaded most up to date video card drivers for Windows 7.
    - Also happened on every occurance of attempting to install Nero 9.

    --------

    Memory Dumps - Here are the result of WinDBG on a number of my dumps.


    Loading Dump File [C:\Windows\Minidump\060109-26161-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    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 7100 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0x82841000 PsLoadedModuleList = 0x82989810
    Debug session time: Mon Jun 1 13:23:15.497 2009 (GMT+1)
    System Uptime: 0 days 0:23:44.168
    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
    .....
    Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {2167ae0, 2, 0, 8c484c27}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : tcpip.sys ( tcpip+5bc27 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 02167ae0, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8c484c27, address which referenced memory

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: tcpip

    FAULTING_MODULE: 82841000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a0a314f

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    02167ae0

    CURRENT_IRQL: 0

    FAULTING_IP:
    tcpip+5bc27
    8c484c27 037dfc add edi,dword ptr [ebp-4]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 8c484c27 to 8287c7bb

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    82967a60 8c484c27 badb0d00 00000019 82810cee nt+0x3b7bb
    82967ac4 8c484c27 00000008 00010286 00022c65 tcpip+0x5bc27
    00000000 00000000 00000000 00000000 00000000 tcpip+0x5bc27


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    tcpip+5bc27
    8c484c27 037dfc add edi,dword ptr [ebp-4]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: tcpip+5bc27

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: tcpip.sys

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ---------


    Loading Dump File [C:\Windows\Minidump\060109-39686-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    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 7100 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0x8283b000 PsLoadedModuleList = 0x82983810
    Debug session time: Mon Jun 1 12:58:20.454 2009 (GMT+1)
    System Uptime: 0 days 14:26:54.124
    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
    .............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D3, {8216660c, ff, 0, 82893a36}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : ntkrnlpa.exe ( nt+58a36 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_PORTION_MUST_BE_NONPAGED (d3)
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers marking code or data as pageable when it should be
    marked nonpaged.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 8216660c, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 82893a36, address which referenced memory

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: 8283b000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8b4e

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    8216660c

    CURRENT_IRQL: 0

    FAULTING_IP:
    nt+58a36
    82893a36 8b430c mov eax,dword ptr [ebx+0Ch]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD3

    LAST_CONTROL_TRANSFER: from 82893a36 to 828767bb

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    82961c20 82893a36 badb0d00 00002710 badb0d00 nt+0x3b7bb
    82961cd4 82893978 82164d20 8296e280 00000000 nt+0x58a36
    82961d20 82893798 00000000 0000000e 00000000 nt+0x58978
    82961d24 00000000 0000000e 00000000 00000000 nt+0x58798


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+58a36
    82893a36 8b430c mov eax,dword ptr [ebx+0Ch]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt+58a36

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntkrnlpa.exe

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ---------
     
  2. 2009/06/14
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Format & reinstall.

    Did you get the Win7 ISO download from Microsoft?
     
    Arie,
    #2

  3. to hide this advert.

  4. 2009/07/09
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    As you have had this issue with 2 different copies of Win7, I'd suspect that it's a compatibility problem - most likely with a driver due to the BSOD.

    First, try running the Windows 7 Upgrade Advisor to see if it identifies any compatibility issues: http://www.microsoft.com/downloads/...90-7659-4BD9-9E51-2497C146AF15&displaylang=en

    Second, in the debugger, run the memory dump again.
    Then type "lmtsmn" (without the quotes) in the box at the bottom of the debugger and press Enter.
    This will list your drivers (in alphanumeric order) that were loaded when the dump was created. Check for any drivers from 2008 or earlier. Then research those drivers to see if there's any that have updates available - and update them. You can safely disregard any older Windows files as Windows Update takes care of those.

    You may also want to run Driver Verifier. Please read these instructions BEFORE using it as it can cause a BSOD loop that won't let you into Windows:
    I hang out in a lot of forums (and will be away until Monday afternoon - with limited internet access). I've subscribed to email notification of this thread so I'll be notified when you respond.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.