TechSpot

Hi All BSOD lol need help checking the minidump

By eckng
Oct 15, 2006
  1. Hi All,

    I have not experienced a blue screen for ages till I installed my new drivers for mobo and grahpic card.

    I have used driver cleaner (in safe mode) before installing the new device drivers.

    From the looks of it, it seems to point to the graphic driver Forceware 91.47
    (the mobo drivers are 6.86, did not install the IDE / sata drivers and nam and firewall).

    Below is the minidump
    *********************************************************

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


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

    Symbol search path is: http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp.050928-1517
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sat Oct 14 18:48:57.984 2006 (GMT+8)
    System Uptime: 0 days 3:12:22.681
    Loading Kernel Symbols
    ......................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {ffdf, 2, 1, 806e4a8e}

    *** WARNING: Unable to verify timestamp for nv4_mini.sys
    *** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
    Probably caused by : nv4_mini.sys ( nv4_mini+55df3 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000ffdf, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 806e4a8e, address which referenced memory

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


    WRITE_ADDRESS: 0000ffdf

    CURRENT_IRQL: 2

    FAULTING_IP:
    hal!KeAcquireQueuedSpinLock+42
    806e4a8e 8902 mov dword ptr [edx],eax

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: PPStream.exe

    LAST_CONTROL_TRANSFER: from 806e4a41 to 806e4a8e

    STACK_TEXT:
    b52a8b30 806e4a41 804fccdf 00000002 89add778 hal!KeAcquireQueuedSpinLock+0x42
    b52a8b34 804fccdf 00000002 89add778 89c29cc0 hal!KeAcquireQueuedSpinLockRaiseToSynch+0x5
    b52a8b4c b9f69df3 89c29cc0 00000000 00000001 nt!KeReleaseSemaphore+0x11
    WARNING: Stack unwind information not available. Following frames may be wrong.
    00000000 00000000 00000000 00000000 00000000 nv4_mini+0x55df3


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nv4_mini+55df3
    b9f69df3 ?? ???

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nv4_mini+55df3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nv4_mini

    IMAGE_NAME: nv4_mini.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 44dd49d8

    FAILURE_BUCKET_ID: 0xA_W_nv4_mini+55df3

    BUCKET_ID: 0xA_W_nv4_mini+55df3

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

    1: kd> lmvm nv4_mini
    start end module name
    b9f14000 ba2da6e0 nv4_mini T (no symbols)
    Loaded symbol image file: nv4_mini.sys
    Image path: nv4_mini.sys
    Image name: nv4_mini.sys
    Timestamp: Sat Aug 12 11:24:08 2006 (44DD49D8)
    CheckSum: 003C90B0
    ImageSize: 003C66E0
    Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
     
  2. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    I can confirm your minidump crashes at your video card drivers. I suggest you rollback to the driver version you were using before.

    Regards Howard :)
     
  3. eckng

    eckng TS Rookie Topic Starter

    Cheers mate!!! But which area do u look at? at the n4_mini.dll?
     
  4. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    Do you know what version of the video card drivers you were using before you updated?

    If you do, go to add remove programmes in your control panel and uninstall your current video card drivers. Then, go to the Nvidia website and download the version of the drivers you were using before and install them.

    Another possibility is to do a system restore to before you installed the new drivers.

    Regards Howard :)
     
  5. eckng

    eckng TS Rookie Topic Starter

    Yes mate I do what was my previous version. Sorry my mistake, hmmm I was asking how did u read the minidump and that from that you can say that it was the video card driver?

    I believe you, just want to learn how to do it :D

    Cheers Mate!!!!

    P.S
    But these drivers are the latest offical Nvidia ones... dunno I would have though they would be fine..
     
  6. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    First some versions of the Nvidia card drivers aren`t stable. Once you find a version that is stable with your video card, you should stick with them. I don`t see the point in updating drivers, unless there`s a good reason to do so.

    Your minidump crashed at nv4_mini.sys. This is part of your video card drivers. The owning process was PPStream.exe. I believe this is the ppStream P2P programme.

    If you would like to learn to read minidumps, take a look at this short tutorial HERE.

    Regards Howard :)

    Edit: Unfortunately the link I gave you above on how to read minidumps isn`t working.

    Edit: The link above is now working. Must have been a problem with the site.
     
  7. eckng

    eckng TS Rookie Topic Starter

    Cheers mate! thanks again!
     
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...