TechSpot

Just another BSOD.Please HELP!

By DemRaziel
Nov 22, 2006
  1. Hi I have this problem when playing NFS Carbon
    and it happens at the same spot every time.
    I have newest drivers installed.
    Memtest shows no memory errors.

    Here is my Bugcheck Analysis report:


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini112206-05.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: symsrv*symsrv.dll*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Wed Nov 22 19:21:37.121 2006 (GMT+1)
    System Uptime: 0 days 1:07:42.704
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Loading Kernel Symbols
    ...............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {d, 0, 0, 0}

    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

    *** WARNING: Unable to verify timestamp for nv4_disp.dll
    *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
    Probably caused by : nv4_disp.dll ( nv4_disp+29c000 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

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

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

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


    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 421dfc18

    BUGCHECK_STR: 0x7f_d

    CUSTOMER_CRASH_COUNT: 5

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER: from e3759c4e to 804e1ff1

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f5bf68f8 e3759c4e badb0d00 00000002 0025d73c nt!KiCoprocessorError+0xf4
    f5bf690c 804e1718 00000001 e284f000 00000000 0xe3759c4e
    f5bf6924 bfc70000 badb0023 00000023 00000002 nt!Kei386EoiHelper+0x26bc
    f5bf6928 badb0023 00000023 00000002 00000002 nv4_disp+0x29c000
    f5bf692c 00000000 00000002 00000002 00000002 0xbadb0023


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nv4_disp+29c000
    bfc70000 ?? ???

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nv4_disp+29c000

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nv4_disp

    IMAGE_NAME: nv4_disp.dll

    BUCKET_ID: WRONG_SYMBOLS

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



    And my latest minidumps: View attachment 10831

    Thanx in advance to anyone! :D

    P.S.
    Sorry if this is not the right place 4 the post! :(

    Edit: Removed bold type. It`s fine to use bold type to highlight something important, but it`s not nice for almost an entire post.
     
  2. tpfagan

    tpfagan TS Rookie Posts: 43

    DemRaziel,

    I'm a bit of a novice when looking at minidump files, but all four of the minidumps that you posted had issues with nv4_disp.dll - which are for your NVidia graphics card.

    Historical posts usually indicate that:

    - either your not running the latest drivers.
    - your running beta drivers.
    - your running new drivers and did not uninstall the old drivers. (NVidia is pretty picky about removing the old drivers).

    It appears (based on some other postings) that the best way to correct this problem is to boot into safemode, uninstall your video drivers (add/remove programs), uninstall your video adapter (device manager) and reinstall with the correct drivers.

    Now you might be able to do this outside of safemode.

    I little google-fu on NV4_disp.dll will provide you with a ton of information from other people who have had this same problem.

    I suppose this would also explain why it happens when your playing a game (pushing the graphics card).

    Hope this helps - if not, let us know.
     
  3. DemRaziel

    DemRaziel TS Rookie Topic Starter

    Nothing!

    Well that didn't help (i used driver cleaner for nVidia drivers) :(
    If it helps:
    At that "crashing" spot in the game changing resolution to 640x480 helps (no BSOD) but any resolution higher than that causes BSOD
    Entire game works great at 1280x1024 except that point and it' kinda sucky when you need to change resolution every time i get there!

    So if anyone can help, HELP!

    @tpfagan: thanx man :) anyway!
    Hope my english is ok!
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Try nVidia Display Driver 81.98

    Hi,

    Your version of nVidia Display Card is same as this problem. Install nVidia Display Driver 81.98 may resolve the problem. If it still crashes, probably your video card is bad.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...