The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Can someone debug this minidump for me?

    Discussion in 'Windows OS and Software' started by Nvidia, Mar 4, 2009.

  1. Nvidia

    Nvidia Notebook Consultant

    Reputations:
    15
    Messages:
    242
    Likes Received:
    0
    Trophy Points:
    30
    Can someone please debug this minidump for me?

    Thanks. There are two. Can you tell me the cause of my BSOD?
     

    Attached Files:

  2. entropy.cz

    entropy.cz Notebook Evangelist

    Reputations:
    110
    Messages:
    386
    Likes Received:
    0
    Trophy Points:
    30
    both minidumps point to e100b325.sys driver

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 87400000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8885bfb4, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 819275a0
    Unable to read MiSystemVaType memory at 819086a0
     87400000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    e100b325+bfb4
    8885bfb4 ??              ???
    
    CUSTOMER_CRASH_COUNT:  2
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  Idle
    
    TRAP_FRAME:  818e9aac -- (.trap 0xffffffff818e9aac)
    ErrCode = 00000000
    eax=87400000 ebx=00000000 ecx=fd27590e edx=874002b0 esi=8384faf4 edi=00000000
    eip=8885bfb4 esp=818e9b20 ebp=818e9b30 iopl=0         nv up ei ng nz na pe cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
    e100b325+0xbfb4:
    8885bfb4 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 8885bfb4 to 81849354
    
    STACK_TEXT:  
    818e9aac 8885bfb4 badb0d00 874002b0 841af0e4 nt!KiTrap0E+0x2ac
    WARNING: Stack unwind information not available. Following frames may be wrong.
    818e9b1c 84e4668a 84675c1a 84675bc6 00000000 e100b325+0xbfb4
    818e9b30 8885c3c7 00006028 84e4666e 84e3e660 0x84e4668a
    818e9b74 88867ef3 84e46600 8384f008 0000004e e100b325+0xc3c7
    818e9ba4 88869ea4 c0010017 00000000 8384f008 e100b325+0x17ef3
    818e9c00 88869f4b 00000000 84e3ae28 00000000 e100b325+0x19ea4
    818e9c24 8886a20b 8384f008 8384f048 8384f04c e100b325+0x19f4b
    818e9c74 8885b569 8384f008 00000000 00000000 e100b325+0x1a20b
    818e9ca4 822cfd91 0084f008 8384f3f0 84e04488 e100b325+0xb569
    818e9cc8 82239d18 8384f404 0084f3f0 00000000 ndis!ndisMDpcX+0x7c
    818e9ce8 8186aed6 8384f404 8384f3f0 00000000 ndis!ndis5InterruptDpc+0x95
    818e9d50 818379de 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
    818e9d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    e100b325+bfb4
    8885bfb4 ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  e100b325+bfb4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: e100b325
    
    IMAGE_NAME:  e100b325.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4342e147
    
    FAILURE_BUCKET_ID:  0xD1_e100b325+bfb4
    
    BUCKET_ID:  0xD1_e100b325+bfb4
    
    Followup: MachineOwner
    ---------
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 86c00000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 87fd4082, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 8193f6d8
    Unable to read MiSystemVaType memory at 819202e0
     86c00000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    e100b325+c082
    87fd4082 ??              ???
    
    CUSTOMER_CRASH_COUNT:  10
    
    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  818ffaac -- (.trap 0xffffffff818ffaac)
    ErrCode = 00000000
    eax=86c00000 ebx=00000001 ecx=fdcc46da edx=86c005cc esi=854a5c8c edi=00000037
    eip=87fd4082 esp=818ffb20 ebp=818ffb30 iopl=0         nv up ei ng nz ac po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
    e100b325+0xc082:
    87fd4082 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 87fd4082 to 8186dc84
    
    STACK_TEXT:  
    818ffaac 87fd4082 badb0d00 86c005cc 00000048 nt!KiTrap0E+0x2ac
    WARNING: Stack unwind information not available. Following frames may be wrong.
    818ffb1c 8553237e 848c4cf6 848c4cae 00000001 e100b325+0xc082
    818ffb30 87fd4495 0005995a 8553236e 854ba360 0x8553237e
    818ffb74 87fe0213 85532300 854a5198 0000004e e100b325+0xc495
    818ffba4 87fe21da c0010017 00000000 854a5198 e100b325+0x18213
    818ffc00 87fe2281 00000000 847bdef8 00000000 e100b325+0x1a1da
    818ffc24 87fe2549 854a5198 854a51d8 854a51dc e100b325+0x1a281
    818ffc74 87fd3637 854a5198 00000000 00000000 e100b325+0x1a549
    818ffca4 87946af5 004a5198 854a558c 853b9438 e100b325+0xb637
    818ffcc8 878ac829 854a55a0 004a558c 00000000 ndis!ndisMDpcX+0x7c
    818ffce8 8187dab0 854a55a0 854a558c 00000000 ndis!ndis5InterruptDpc+0x95
    818ffd50 8187c55d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
    818ffd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    e100b325+c082
    87fd4082 ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  e100b325+c082
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: e100b325
    
    IMAGE_NAME:  e100b325.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  473de72c
    
    FAILURE_BUCKET_ID:  0xD1_e100b325+c082
    
    BUCKET_ID:  0xD1_e100b325+c082
    
    Followup: MachineOwner
    ---------