1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Help with Mini-Dump

Discussion in 'Windows Home Server' started by TimV, Sep 22, 2009.

  1. TimV

    TimV Guest

    Hi All,

    I need some help with this minidump. I cant find anything..

    Code:
    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: b1981250, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on 
chips which support this level of status)
Arg4: 80837604, address which referenced memory

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


WRITE_ADDRESS:  b1981250 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiComputeWaitInterval+1e
80837604 f00fba2900      lock bts dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b99f31b0 to 80837604

STACK_TEXT:  
f78b2c7c b99f31b0 89e83398 b99f34bc f7737a40 nt!KiComputeWaitInterval+0x1e
f78b2ce8 b99f34cb b9a5e940 00000000 f78b2d50 tcpip!MdpFree+0xec
f78b2cf8 8083d99a b9a5e950 b9a5e940 0172808a tcpip!TCBTimeout+0x9ff
f78b2d50 80839b3f 00000000 0000000e f05f7fbf nt!FsRtlInitializeLargeMcb+0x2f
f78b2d74 7fffabfd f03ffb1f fdefdf6f dafbfbfd nt!KeQueryValuesProcess+0x92
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78b2d80 dafbfbfd ffdfff7f ffff9fbb fffeffff 0x7fffabfd
f78b2d84 ffdfff7f ffff9fbb fffeffff efbfffff 0xdafbfbfd
f78b2d88 ffff9fbb fffeffff efbfffff affffffd 0xffdfff7f
f78b2d8c fffeffff efbfffff affffffd dfff7d5f 0xffff9fbb
f78b2d90 efbfffff affffffd dfff7d5f f74ffc7e 0xfffeffff
f78b2d94 affffffd dfff7d5f f74ffc7e fb779bf0 0xefbfffff
f78b2d98 dfff7d5f f74ffc7e fb779bf0 fb6ff4ee 0xaffffffd
f78b2d9c f74ffc7e fb779bf0 fb6ff4ee abd59bf7 0xdfff7d5f
f78b2dbc fffff7ff b7b7fff7 dfbfffdb ffffffff 
Dfs!DfsRemoveFromPrefixTableLockedEx+0x30
f78b2dd0 ffffffff 00000001 8083fe89 00000000 0xfffff7ff
f78b2dd4 00000000 8083fe89 00000000 00000000 0xffffffff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Dfs!DfsRemoveFromPrefixTableLockedEx+30
f74ffc7e ??              ???

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  Dfs!DfsRemoveFromPrefixTableLockedEx+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Dfs

IMAGE_NAME:  Dfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45d697d5

FAILURE_BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30

BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30

Followup: MachineOwner
---------
[\code]


-- 
Thnx,
Tim
     
    TimV, Sep 22, 2009
    #1
  3. Dusko Savatovic

    Dusko Savatovic Guest

    Hi TimV,

    IRQL_NOT_LESS_OR_EQUAL is almost always related to hardware failure.
    If you can, save your data to external drive or another computer. Reboot
    from Vista DVD.
    When booted from Vista DVD, you can run a memory check.
    If memory check is OK, do a clean install.
    If everything is OK, you are lucky. If not, you will have to do more
    hardware checks.

    You can do the usual hardware checks:
    - check fans, specially one on the processor
    - reseat and rotate memory modules. Start with one module, then add
    remaining modules one by one.
    - reseat graphics adapter.
    - reseat all other cards (NIC, sound, wireless, etc).

    If that doesn't help, you will need to swap components with known good ones
    (this is usually done in the proper service shop).

    If your PC is still covered by waranty, it is best to do a clean install
    (possibly using manufacturer's recovery procedures) and if that doesn't
    help, return the computer to your dealer or authorized service center.

    Good luck


    "TimV" <TimV@discussions.microsoft.com> wrote in message
    news:5BC511C8-B15F-4DA2-A693-A53FBD27DF4B@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hi All,
    >
    > I need some help with this minidump. I cant find anything..
    >
    >
    Code:
    > 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: b1981250, memory referenced
> Arg2: d0000002, IRQL
> Arg3: 00000001, bitfield :
> bit 0 : value 0 = read operation, 1 = write operation
> bit 3 : value 0 = not an execute operation, 1 = execute operation (only on
> chips which support this level of status)
> Arg4: 80837604, address which referenced memory
>
> Debugging Details:
> ------------------
>
>
> WRITE_ADDRESS:  b1981250
>
> CURRENT_IRQL:  2
>
> FAULTING_IP:
> nt!KiComputeWaitInterval+1e
> 80837604 f00fba2900      lock bts dword ptr [ecx],0
>
> CUSTOMER_CRASH_COUNT:  2
>
> DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
>
> BUGCHECK_STR:  0xA
>
> PROCESS_NAME:  Idle
>
> LAST_CONTROL_TRANSFER:  from b99f31b0 to 80837604
>
> STACK_TEXT:
> f78b2c7c b99f31b0 89e83398 b99f34bc f7737a40 nt!KiComputeWaitInterval+0x1e
> f78b2ce8 b99f34cb b9a5e940 00000000 f78b2d50 tcpip!MdpFree+0xec
> f78b2cf8 8083d99a b9a5e950 b9a5e940 0172808a tcpip!TCBTimeout+0x9ff
> f78b2d50 80839b3f 00000000 0000000e f05f7fbf 
> nt!FsRtlInitializeLargeMcb+0x2f
> f78b2d74 7fffabfd f03ffb1f fdefdf6f dafbfbfd nt!KeQueryValuesProcess+0x92
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> f78b2d80 dafbfbfd ffdfff7f ffff9fbb fffeffff 0x7fffabfd
> f78b2d84 ffdfff7f ffff9fbb fffeffff efbfffff 0xdafbfbfd
> f78b2d88 ffff9fbb fffeffff efbfffff affffffd 0xffdfff7f
> f78b2d8c fffeffff efbfffff affffffd dfff7d5f 0xffff9fbb
> f78b2d90 efbfffff affffffd dfff7d5f f74ffc7e 0xfffeffff
> f78b2d94 affffffd dfff7d5f f74ffc7e fb779bf0 0xefbfffff
> f78b2d98 dfff7d5f f74ffc7e fb779bf0 fb6ff4ee 0xaffffffd
> f78b2d9c f74ffc7e fb779bf0 fb6ff4ee abd59bf7 0xdfff7d5f
> f78b2dbc fffff7ff b7b7fff7 dfbfffdb ffffffff
> Dfs!DfsRemoveFromPrefixTableLockedEx+0x30
> f78b2dd0 ffffffff 00000001 8083fe89 00000000 0xfffff7ff
> f78b2dd4 00000000 8083fe89 00000000 00000000 0xffffffff
>
>
> STACK_COMMAND:  kb
>
> FOLLOWUP_IP:
> Dfs!DfsRemoveFromPrefixTableLockedEx+30
> f74ffc7e ??              ???
>
> SYMBOL_STACK_INDEX:  d
>
> SYMBOL_NAME:  Dfs!DfsRemoveFromPrefixTableLockedEx+30
>
> FOLLOWUP_NAME:  MachineOwner
>
> MODULE_NAME: Dfs
>
> IMAGE_NAME:  Dfs.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP:  45d697d5
>
> FAILURE_BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30
>
> BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30
>
> Followup: MachineOwner
> ---------
> [code]
>
>
> -- 
> Thnx,
> Tim <!--colorc--><!--/colorc-->
     
    Dusko Savatovic, Sep 22, 2009
    #2
  4. Peter Foldes

    Peter Foldes Guest

    Tim

    Aside from hardware failure as Dusko posted this issue can also be attributed to a
    bad or an incompatible driver.

    Use the verifier tool to examine the drivers and see which one if any is at fault

    Start\Run verifier



    --
    Peter

    Please Reply to Newsgroup for the benefit of others
    Requests for assistance by email can not and will not be acknowledged.

    "TimV" <TimV@discussions.microsoft.com> wrote in message
    news:5BC511C8-B15F-4DA2-A693-A53FBD27DF4B@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hi All,
    >
    > I need some help with this minidump. I cant find anything..
    >
    >
    Code:
    > 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: b1981250, memory referenced
> Arg2: d0000002, IRQL
> Arg3: 00000001, bitfield :
> bit 0 : value 0 = read operation, 1 = write operation
> bit 3 : value 0 = not an execute operation, 1 = execute operation (only on
> chips which support this level of status)
> Arg4: 80837604, address which referenced memory
>
> Debugging Details:
> ------------------
>
>
> WRITE_ADDRESS:  b1981250
>
> CURRENT_IRQL:  2
>
> FAULTING_IP:
> nt!KiComputeWaitInterval+1e
> 80837604 f00fba2900      lock bts dword ptr [ecx],0
>
> CUSTOMER_CRASH_COUNT:  2
>
> DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
>
> BUGCHECK_STR:  0xA
>
> PROCESS_NAME:  Idle
>
> LAST_CONTROL_TRANSFER:  from b99f31b0 to 80837604
>
> STACK_TEXT:
> f78b2c7c b99f31b0 89e83398 b99f34bc f7737a40 nt!KiComputeWaitInterval+0x1e
> f78b2ce8 b99f34cb b9a5e940 00000000 f78b2d50 tcpip!MdpFree+0xec
> f78b2cf8 8083d99a b9a5e950 b9a5e940 0172808a tcpip!TCBTimeout+0x9ff
> f78b2d50 80839b3f 00000000 0000000e f05f7fbf nt!FsRtlInitializeLargeMcb+0x2f
> f78b2d74 7fffabfd f03ffb1f fdefdf6f dafbfbfd nt!KeQueryValuesProcess+0x92
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> f78b2d80 dafbfbfd ffdfff7f ffff9fbb fffeffff 0x7fffabfd
> f78b2d84 ffdfff7f ffff9fbb fffeffff efbfffff 0xdafbfbfd
> f78b2d88 ffff9fbb fffeffff efbfffff affffffd 0xffdfff7f
> f78b2d8c fffeffff efbfffff affffffd dfff7d5f 0xffff9fbb
> f78b2d90 efbfffff affffffd dfff7d5f f74ffc7e 0xfffeffff
> f78b2d94 affffffd dfff7d5f f74ffc7e fb779bf0 0xefbfffff
> f78b2d98 dfff7d5f f74ffc7e fb779bf0 fb6ff4ee 0xaffffffd
> f78b2d9c f74ffc7e fb779bf0 fb6ff4ee abd59bf7 0xdfff7d5f
> f78b2dbc fffff7ff b7b7fff7 dfbfffdb ffffffff
> Dfs!DfsRemoveFromPrefixTableLockedEx+0x30
> f78b2dd0 ffffffff 00000001 8083fe89 00000000 0xfffff7ff
> f78b2dd4 00000000 8083fe89 00000000 00000000 0xffffffff
>
>
> STACK_COMMAND:  kb
>
> FOLLOWUP_IP:
> Dfs!DfsRemoveFromPrefixTableLockedEx+30
> f74ffc7e ??              ???
>
> SYMBOL_STACK_INDEX:  d
>
> SYMBOL_NAME:  Dfs!DfsRemoveFromPrefixTableLockedEx+30
>
> FOLLOWUP_NAME:  MachineOwner
>
> MODULE_NAME: Dfs
>
> IMAGE_NAME:  Dfs.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP:  45d697d5
>
> FAILURE_BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30
>
> BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30
>
> Followup: MachineOwner
> ---------
> [code]
>
>
> -- 
> Thnx,
> Tim <!--colorc--><!--/colorc-->
     
    Peter Foldes, Sep 22, 2009
    #3
  5. TimV

    TimV Guest

    Thanks for the replys...


    I'm gonne start with a fresh installatie on a new server. Done with the old,
    in with the new!


    --
    Thnx,
    Tim


    "Peter Foldes" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Tim
    >
    > Aside from hardware failure as Dusko posted this issue can also be attributed to a
    > bad or an incompatible driver.
    >
    > Use the verifier tool to examine the drivers and see which one if any is at fault
    >
    > StartRun verifier
    >
    >
    >
    > --
    > Peter
    >
    > Please Reply to Newsgroup for the benefit of others
    > Requests for assistance by email can not and will not be acknowledged.
    >
    > "TimV" <TimV@discussions.microsoft.com> wrote in message
    > news:5BC511C8-B15F-4DA2-A693-A53FBD27DF4B@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    > > Hi All,
    > >
    > > I need some help with this minidump. I cant find anything..
    > >
    > >
    Code:
    > > 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: b1981250, memory referenced
> > Arg2: d0000002, IRQL
> > Arg3: 00000001, bitfield :
> > bit 0 : value 0 = read operation, 1 = write operation
> > bit 3 : value 0 = not an execute operation, 1 = execute operation (only on
> > chips which support this level of status)
> > Arg4: 80837604, address which referenced memory
> >
> > Debugging Details:
> > ------------------
> >
> >
> > WRITE_ADDRESS:  b1981250
> >
> > CURRENT_IRQL:  2
> >
> > FAULTING_IP:
> > nt!KiComputeWaitInterval+1e
> > 80837604 f00fba2900      lock bts dword ptr [ecx],0
> >
> > CUSTOMER_CRASH_COUNT:  2
> >
> > DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
> >
> > BUGCHECK_STR:  0xA
> >
> > PROCESS_NAME:  Idle
> >
> > LAST_CONTROL_TRANSFER:  from b99f31b0 to 80837604
> >
> > STACK_TEXT:
> > f78b2c7c b99f31b0 89e83398 b99f34bc f7737a40 nt!KiComputeWaitInterval+0x1e
> > f78b2ce8 b99f34cb b9a5e940 00000000 f78b2d50 tcpip!MdpFree+0xec
> > f78b2cf8 8083d99a b9a5e950 b9a5e940 0172808a tcpip!TCBTimeout+0x9ff
> > f78b2d50 80839b3f 00000000 0000000e f05f7fbf nt!FsRtlInitializeLargeMcb+0x2f
> > f78b2d74 7fffabfd f03ffb1f fdefdf6f dafbfbfd nt!KeQueryValuesProcess+0x92
> > WARNING: Frame IP not in any known module. Following frames may be wrong.
> > f78b2d80 dafbfbfd ffdfff7f ffff9fbb fffeffff 0x7fffabfd
> > f78b2d84 ffdfff7f ffff9fbb fffeffff efbfffff 0xdafbfbfd
> > f78b2d88 ffff9fbb fffeffff efbfffff affffffd 0xffdfff7f
> > f78b2d8c fffeffff efbfffff affffffd dfff7d5f 0xffff9fbb
> > f78b2d90 efbfffff affffffd dfff7d5f f74ffc7e 0xfffeffff
> > f78b2d94 affffffd dfff7d5f f74ffc7e fb779bf0 0xefbfffff
> > f78b2d98 dfff7d5f f74ffc7e fb779bf0 fb6ff4ee 0xaffffffd
> > f78b2d9c f74ffc7e fb779bf0 fb6ff4ee abd59bf7 0xdfff7d5f
> > f78b2dbc fffff7ff b7b7fff7 dfbfffdb ffffffff
> > Dfs!DfsRemoveFromPrefixTableLockedEx+0x30
> > f78b2dd0 ffffffff 00000001 8083fe89 00000000 0xfffff7ff
> > f78b2dd4 00000000 8083fe89 00000000 00000000 0xffffffff
> >
> >
> > STACK_COMMAND:  kb
> >
> > FOLLOWUP_IP:
> > Dfs!DfsRemoveFromPrefixTableLockedEx+30
> > f74ffc7e ??              ???
> >
> > SYMBOL_STACK_INDEX:  d
> >
> > SYMBOL_NAME:  Dfs!DfsRemoveFromPrefixTableLockedEx+30
> >
> > FOLLOWUP_NAME:  MachineOwner
> >
> > MODULE_NAME: Dfs
> >
> > IMAGE_NAME:  Dfs.sys
> >
> > DEBUG_FLR_IMAGE_TIMESTAMP:  45d697d5
> >
> > FAILURE_BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30
> >
> > BUCKET_ID:  0xA_Dfs!DfsRemoveFromPrefixTableLockedEx+30
> >
> > Followup: MachineOwner
> > ---------
> > [code]
> >
> >
> > -- 
> > Thnx,
> > Tim <!--colorc--><!--/colorc-->
> 
> <!--colorc--><!--/colorc-->
     
    TimV, Sep 23, 2009
    #4

Share This Page