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.

BSOD on two machines

Discussion in 'Windows XP' started by smokepole, 2008/12/10.

  1. 2008/12/10
    smokepole

    smokepole Inactive Thread Starter

    Joined:
    2008/11/30
    Messages:
    1
    Likes Received:
    0
    Hello,

    I have 2 friends machines that are getting BSOD errors frequently.

    Here are the dmp's. Anyone who recognizes or knows what this might be their comments would be appreciated.

    **********
    first machine:
    **********

    System:
    Microsoft Windows XP
    Professional
    Version 2002
    Service Pack 3

    HP dv9017TX
    Genuine Intel(R) CPU
    T2250 @ 1.73GHz
    1.73 GHz, 1.00 GB of RAM




    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Gef\Desktop\Mini113008-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\Windows\symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun Nov 30 21:08:19.327 2008 (GMT+13)
    System Uptime: 0 days 0:43:40.582
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    ...........
    Unable to load image nv4_disp.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nv4_disp.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, bfaa9db5, b6fd2a5c, 0}

    Probably caused by : nv4_disp.dll ( nv4_disp!CDerivedPShader::ComputeFogWeightPlacement+a65 )

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





    *************
    second machine:
    *************

    type: not known


    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Gef\Desktop\Mini121008-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\Windows\symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c720
    Debug session time: Wed Dec 10 20:48:42.062 2008 (GMT+13)
    System Uptime: 0 days 0:39:29.759
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ..............
    Unable to load image tcpip.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {ff8000b3, 2, 0, aa2e1e6b}

    *** WARNING: Unable to verify timestamp for SYMTDI.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
    *** WARNING: Unable to verify timestamp for afd.sys
    Probably caused by : SYMTDI.SYS ( SYMTDI+365a )

    Followup: MachineOwner
    ---------
     
    smokepole,
    #1
  2. 2008/12/10
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    Welcome to WindowsBBS;)

    While you're waiting for someone who can read those - check this out:

    Introduction to Stop Errors

    "Stop errors in a nutshell are errors that are serious enough to cause Windows to stop. They are similar to the blue screen errors that were present on Windows 9x, however there is no option to try and resume the session in a Windows NT Stop Error (Windows 2000 and all XP members included). "

    Continued:

    http://mvps.org/marksxp/WindowsXP/bsod.php

    Go here to search for the error message:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;kbhowto&sd=GN&ln=EN-US&FR=0
     
    Steve R Jones,
    #2


  3. to hide this advert.

  4. 2008/12/10
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Unfortunately these logs require expert knowledge to analyze and there are only a few members (who occasionally visit WindowsBBS.com) that have the depth of knowledge necessary. Other members can make observations and suggestions as to how you might proceed toward finding the cause ....

    Your first dump indicates a problem with your nVidia graphics driver .....
    I suggest you uninstall the graphics driver through Add/Remove Programs and reinstall a fresh or updated copy.

    Your second dump indicates a problem with Norton Security Suite .....
    Not a user of Norton products, but this Google may help ....

    http://www.google.com/search?q=SYMT...UTF-8&oe=UTF-8&sourceid=ie7&rlz=1I7GGLG_en-GB
     
    PeteC,
    #3
  5. 2008/12/19
    bdesmond

    bdesmond Inactive

    Joined:
    2008/05/19
    Messages:
    36
    Likes Received:
    0
    Given the lack of info I'd tend to agree on the two bad drivers. As a side note, your second machine needs to be upgraded to XP SP3.
     
    bdesmond,
    #4

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.
    Accept Learn More...