none
BSOD Lenovo T61 XP SP3 related to nvidia drivers RRS feed

  • Question

  • I've been getting increasingly frequent BSOD while my computer is running.  Particularly, when performing anything that requires intensive use of the graphics card (such as streaming video or playing a game). My computer is a Lenovo T61, 2500Mhz Intel Core 2 Duo, nVidia Quadro NVS 140M with 512 mb Dedicated.  At first I thought it may have to do with upgrading the driver to the latest nvidia released version, but then I decided to downgrade back to the version last released by Lenovo.  Still getting the BSODs.  I've also ran memory check and passed.  Anything else I can check?

    Below is a copy of the crash dump that I usually get.

       *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {e0000001, b4c0b925, a297a8b4, 0}

    *** 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+11cda5 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: e0000001, The exception code that was not handled
    Arg2: b4c0b925, The address that the exception occurred at
    Arg3: a297a8b4, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>

    FAULTING_IP:
    watchdog!RaiseExceptionInThread+b
    b4c0b925 c3              ret

    TRAP_FRAME:  a297a8b4 -- (.trap 0xffffffffa297a8b4)
    ESP EDITED! New esp=a297ac64
    ErrCode = 00000000
    eax=e1d3a800 ebx=00000001 ecx=00000776 edx=000008d4 esi=e29a6878 edi=0000ffff
    eip=b4c0b925 esp=a297a928 ebp=a297ac78 iopl=0         nv up ei pl nz na po nc
    cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000202
    watchdog!RaiseExceptionInThread+0xb:
    b4c0b925 c3              ret
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  plugin-containe

    LAST_CONTROL_TRANSFER:  from b4c0b622 to b4c0b925

    STACK_TEXT:  
    a297acd4 b4c0b622 e1c15714 e100c408 bf905ed4 watchdog!RaiseExceptionInThread+0xb
    a297ace8 bd12eda5 bd0040b5 e1d3a800 e520c4f0 watchdog!WdEnterMonitoredSection+0x10
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a297acec bd0040b5 e1d3a800 e520c4f0 e1c15724 nv4_disp+0x11cda5
    a297ad08 bd006e55 e520c4f0 a297ad64 0012f15c dxg!DdDisableMotionCompObject+0x39
    a297ad1c bd007426 e1c15008 a297ad38 a297ad64 dxg!bDdDeleteMotionCompObject+0x43
    a297ad54 805417e8 30a00020 0012f15c 0012f168 dxg!DxDdDestroyMoComp+0x18
    a297ad54 7c90e514 30a00020 0012f15c 0012f168 nt!KiSystemServicePostCall
    0012f168 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nv4_disp+11cda5
    bd12eda5 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  nv4_disp+11cda5

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nv4_disp

    IMAGE_NAME:  nv4_disp.dll

    DEBUG_FLR_IMAGE_TIMESTAMP:  496e9c75

    FAILURE_BUCKET_ID:  0x8E_nv4_disp+11cda5

    BUCKET_ID:  0x8E_nv4_disp+11cda5

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

    Monday, January 6, 2014 5:46 AM

Answers

  • Jsfh

    As JMH3143 suggests 4 of 6 of the original and these two all point to your video driver.  The two newest aren't driver verified but the evidence is accumulating that it is the video driver.

    There newer drivers available that you should update to.

    The Nv4_disp.dll file is used by Nvidia graphics card drivers. It is used to increase the performance of Nvidia components

    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\Mini010614-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jan  6 22:36:49.656 2014 (UTC - 5:00)
    System Uptime: 0 days 0:34:00.390
    Loading Kernel Symbols
    
    BugCheck 1000008E, {e0000001, b4248925, a16ae850, 0}
    
    *** 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+11cda5 )
    
    
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>
    
    
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  plugin-containe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from b4248622 to b4248925
    
    STACK_TEXT:  
    a16aecd4 b4248622 e1c56714 e2e27240 bf905ed4 watchdog!RaiseExceptionInThread+0xb
    a16aece8 bd12eda5 bd0040b5 e1cbd800 e1bf9238 watchdog!WdEnterMonitoredSection+0x10
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a16aecec bd0040b5 e1cbd800 e1bf9238 e1c56724 nv4_disp+0x11cda5
    a16aed08 bd006e55 e1bf9238 a16aed64 0515efb8 dxg!DdDisableMotionCompObject+0x39
    a16aed1c bd007426 e1c56008 a16aed38 a16aed64 dxg!bDdDeleteMotionCompObject+0x43
    a16aed54 805417e8 06a02509 0515efb8 0515efc4 dxg!DxDdDestroyMoComp+0x18
    a16aed54 7c90e514 06a02509 0515efb8 0515efc4 nt!KiSystemServicePostCall
    0515efc4 00000000 00000000 00000000 00000000 0x7c90e514
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nv4_disp+11cda5
    bd12eda5 ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nv4_disp+11cda5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nv4_disp
    
    IMAGE_NAME:  nv4_disp.dll
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  496e9c75
    
    FAILURE_BUCKET_ID:  0x8E_nv4_disp+11cda5
    
    BUCKET_ID:  0x8E_nv4_disp+11cda5
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x8e_nv4_disp+11cda5
    
    FAILURE_ID_HASH:  {ccbcf5ab-6ce5-75fe-0112-f4801f590d76}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag


    Tuesday, January 7, 2014 3:53 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.


    Please follow our instructions for finding and uploading the files we need to help you fix your computer.

    They can be found here

    If you have any questions about the procedure please ask

    Advice offered in good faith. It is your decision to implement same. Wanikiya and Dyami - Team ZigZag

    Monday, January 6, 2014 6:24 AM
  • Ok here are the most recent DMP files generated by the BSOD. Thanks for your help.

    http://sdrv.ms/JZGdwk

    Monday, January 6, 2014 11:40 PM
  • Hello again,

    5 different causes are seen in 7 Dmp files.

    The one DMP that appeared to have verifier enabled did not catch the driver. If the next crash does not we can change the set of drivers it is examining to “all.”  This will slow the computer down a bit but will give us a far greater chance of catching the driver.

    To enable us to find the underlying cause please run Driver Verifier again.

    Instructions are here

    The instructions are generic so you may have to adjust them slightly. 

    To run verifier you will need to launch an elevated cmd prompt.

    Test that verifier is indeed running, type verifier /query . 

    If it is running it should display a list of drivers that are being verified.

    Please upload the new DMP files after the computer crashes. 

    It is possible your video driver may be the underlying cause. If that is the case you may have to install a much older driver as the current ones have a known issue.

     
    BugCheck 1000008E, {e0000001, b4c0b925, a297a8b4, 0}
    Probably caused by : nv4_disp.dll ( nv4_disp+11cda5 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 1000007E, {c0000005, bd1222dc, 9c823c48, 9c823944}
    Probably caused by : nv4_disp.dll ( nv4_disp+1102dc )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 1000008E, {e0000001, b8380925, a037a6f8, 0}
    Probably caused by : nv4_disp.dll ( nv4_disp+3ca468 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck C9, {20e, b79cd52f, 919a2f48, 0}
    Probably caused by : wmiacpi.sys ( wmiacpi!WmiAcpiFunctionControl+4f )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 96, {8a3b1400, 8056485c, 80564820, 80576ae0}
    Probably caused by : ntkrpamp.exe ( nt!IopProcessWorkItem+0 )
    


    Advice offered in good faith. It is your decision to implement same. Wanikiya and Dyami - Team ZigZag


    Tuesday, January 7, 2014 2:19 AM
  • Ok so I've added all non microsoft drivers to verifier and got my computer to crash once more by running a bunch of flash video on web browser and running a game.  Here is the link to the DMP file generated.  Let me know if there is more info you have on this. 

    http://sdrv.ms/1dLKVcG

    Tuesday, January 7, 2014 3:45 AM
  • Jsfh

    As JMH3143 suggests 4 of 6 of the original and these two all point to your video driver.  The two newest aren't driver verified but the evidence is accumulating that it is the video driver.

    There newer drivers available that you should update to.

    The Nv4_disp.dll file is used by Nvidia graphics card drivers. It is used to increase the performance of Nvidia components

    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\Mini010614-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_qfe.130704-0421
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jan  6 22:36:49.656 2014 (UTC - 5:00)
    System Uptime: 0 days 0:34:00.390
    Loading Kernel Symbols
    
    BugCheck 1000008E, {e0000001, b4248925, a16ae850, 0}
    
    *** 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+11cda5 )
    
    
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>
    
    
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  plugin-containe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from b4248622 to b4248925
    
    STACK_TEXT:  
    a16aecd4 b4248622 e1c56714 e2e27240 bf905ed4 watchdog!RaiseExceptionInThread+0xb
    a16aece8 bd12eda5 bd0040b5 e1cbd800 e1bf9238 watchdog!WdEnterMonitoredSection+0x10
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a16aecec bd0040b5 e1cbd800 e1bf9238 e1c56724 nv4_disp+0x11cda5
    a16aed08 bd006e55 e1bf9238 a16aed64 0515efb8 dxg!DdDisableMotionCompObject+0x39
    a16aed1c bd007426 e1c56008 a16aed38 a16aed64 dxg!bDdDeleteMotionCompObject+0x43
    a16aed54 805417e8 06a02509 0515efb8 0515efc4 dxg!DxDdDestroyMoComp+0x18
    a16aed54 7c90e514 06a02509 0515efb8 0515efc4 nt!KiSystemServicePostCall
    0515efc4 00000000 00000000 00000000 00000000 0x7c90e514
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nv4_disp+11cda5
    bd12eda5 ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nv4_disp+11cda5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nv4_disp
    
    IMAGE_NAME:  nv4_disp.dll
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  496e9c75
    
    FAILURE_BUCKET_ID:  0x8E_nv4_disp+11cda5
    
    BUCKET_ID:  0x8E_nv4_disp+11cda5
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x8e_nv4_disp+11cda5
    
    FAILURE_ID_HASH:  {ccbcf5ab-6ce5-75fe-0112-f4801f590d76}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag


    Tuesday, January 7, 2014 3:53 AM
  • Same problem here... 

    How to create a dump file ?

    Tuesday, March 8, 2016 4:08 PM
  • Read JMH3143 post on DMP files from Jan 06 2014.  You do realize you are replying to a 2+ year old thread, right?

    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Tuesday, March 8, 2016 5:38 PM