Crash Problem

Discussion in 'Software' started by TheDudez, Mar 6, 2006.

  1. TheDudez

    TheDudez Private E-2

    Recently when I play WoW(World of Warcraft) the computer crashs.

    This is the minidump I got:


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


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

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 UP Free x86 compatible
    Product: WinNt
    Built by: 2600.xpclient.010817-1148
    Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
    Debug session time: Mon Mar 6 16:14:07.748 2006 (GMT-8)
    System Uptime: 0 days 0:14:00.334
    Loading Kernel Symbols
    ............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {e, 2, 0, e}

    Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmArm+2a )

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

    kd> !analyze -v
    *******************************************************************************
    * *
    * 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: 0000000e, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 0000000e, address which referenced memory

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


    READ_ADDRESS: 0000000e

    CURRENT_IRQL: 2

    FAULTING_IP:
    +e
    0000000e ?? ???

    PROCESS_NAME: WoW.exe

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 804d7c50 to 804fc1bb

    FAILED_INSTRUCTION_ADDRESS:
    +e
    0000000e ?? ???

    STACK_TEXT:
    f794aa90 804d7c50 0000000a 0000000e 00000002 nt!KeBugCheckEx+0x19
    f794aa90 0000000e 0000000a 0000000e 00000002 nt!KiTrap0E+0x2ad
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    f794ab1c 0252bf00 00000012 0252bd40 00000012 0xe
    f794ab8c f77afbbe f763f6b0 00000010 82af0580 0x252bf00
    f794abac f73cd0d4 82a77d08 82a79af0 82a90a01 PCIIDEX!BmArm+0x2a
    f794abec f71941b7 82a90ad8 82a77d08 00000103 NDIS!ndisMProcessDeferred+0x37
    f794ac20 f73b8c6d 827dadb0 82a77d08 00000082 psched!MpSend+0xab1
    f794ac40 f2fbf6b5 82ac6eb0 82a77d08 829bfbe0 NDIS!ndisMSendX+0x125
    f794ac68 f2fbf757 829bfbe0 82a77d08 823fb280 tcpip!ARPSendData+0x181
    f794ac90 f2fbe13f 829bfb02 823fb294 00000001 tcpip!ARPTransmit+0x72
    f794ada0 f2fc20ff f2ff53b8 023d81e8 823d8180 tcpip!IPTransmit+0x59d
    f794ae08 f2fc0f73 000005b4 00000002 00000000 tcpip!TCPSend+0x57a
    f794ae2c f2fc0767 00000002 00000002 00000000 tcpip!ProcessPerCpuTCBDelayQ+0x91
    f794aea4 f2fbf2f0 f2ffd860 00000000 804ebc14 tcpip!TCBTimeout+0xad6
    f794aeb0 804ebc14 f2ffd870 f2ffd860 0d0f27c8 tcpip!TCBTimeoutdpc+0xb
    f794afb4 804eaa97 f4e0f06a 00000001 ffdff000 nt!KiTimerListExpire+0xf3
    f794afe0 804f02eb 80544a20 00000000 0000d215 nt!KiTimerExpiration+0xb0
    f794aff4 804effd3 f0354d44 00000000 00000000 nt!KiRetireDpcList+0x30
    f794aff8 f0354d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
    804effd3 00000000 00000009 bb835675 00000128 0xf0354d44


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    PCIIDEX!BmArm+2a
    f77afbbe 5f pop edi

    FAULTING_SOURCE_CODE:


    SYMBOL_STACK_INDEX: 4

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: PCIIDEX!BmArm+2a

    MODULE_NAME: PCIIDEX

    IMAGE_NAME: PCIIDEX.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d83e2

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_PCIIDEX!BmArm+2a

    BUCKET_ID: 0xD1_CODE_AV_BAD_IP_PCIIDEX!BmArm+2a

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

    I will really appreciate if anyone can tell me whats causing this problem.
    Thanks
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds