Help with my crash dump

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by daiwuff, Jul 18, 2012.

  1. daiwuff

    daiwuff New Member

    Joined:
    Jul 18, 2012
    Messages:
    4
    Likes Received:
    0
    Okay it's been enough of a pain for me trying to figure out how to open the dump file, got that sorted and now I'm trying to understand it. :confused: I get it's obviously a hardware issue, lol, but any ideas beyond that??

    Any help is appreciated, thanks in advance~

    ****************************************************************************

    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: 0000000006b19220, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88006b3569e, address which referenced memory

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


    WRITE_ADDRESS: 0000000006b19220

    CURRENT_IRQL: 2

    FAULTING_IP:
    WmXlCore+669e
    fffff880`06b3569e 0100 add dword ptr [rax],eax

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffff80000ba2280 -- (.trap 0xfffff80000ba2280)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000006b19220 rbx=0000000000000000 rcx=fffff88006b2f000
    rdx=fffffa8006c1eeb0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88006b3569e rsp=fffff80000ba2410 rbp=0000000000000000
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=fffff88006b3c240 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    WmXlCore+0x669e:
    fffff880`06b3569e 0100 add dword ptr [rax],eax ds:00000000`06b19220=????????
    Resetting default scope

    EXCEPTION_RECORD: fffff880009ebec0 -- (.exr 0xfffff880009ebec0)
    ExceptionAddress: 0000000000000000
    ExceptionCode: 00000000
    ExceptionFlags: 0ad8bdb0
    NumberParameters: 0

    MISALIGNED_IP:
    WmXlCore+669e
    fffff880`06b3569e 0100 add dword ptr [rax],eax

    LAST_CONTROL_TRANSFER: from fffff8000448d769 to fffff8000448e1c0

    STACK_TEXT:
    fffff800`00ba2138 fffff800`0448d769 : 00000000`0000000a 00000000`06b19220 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff800`00ba2140 fffff800`0448c3e0 : fffff800`04498085 fffff880`009e7180 00000000`00000005 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba2280 fffff880`06b3569e : 00000000`06b19220 00000000`00000246 fffffa80`061e0984 fffff800`00ba254c : nt!KiPageFault+0x260
    fffff800`00ba2410 00000000`00000001 : fffff800`00ba2720 fffff880`06b364c6 fffffa80`00000000 fffff800`00ba2720 : WmXlCore+0x669e
    fffff800`00ba26b0 fffff800`00ba2720 : fffff880`06b364c6 fffffa80`00000000 fffff800`00ba2720 fffff800`00ba2720 : 0x1
    fffff800`00ba26b8 fffff880`06b364c6 : fffffa80`00000000 fffff800`00ba2720 fffff800`00ba2720 fffffa80`00000001 : 0xfffff800`00ba2720
    fffff800`00ba26c0 fffff880`06b37947 : fffffa80`06b19470 00000000`1b35c31c fffffa80`06b19510 fffffa80`06b19220 : WmXlCore+0x74c6
    fffff800`00ba2700 fffff800`04498e3c : fffff800`00ba2830 00000000`00000000 00000000`00000001 00000000`00000000 : WmXlCore+0x8947
    fffff800`00ba27a0 fffff800`04498cd6 : fffffa80`0480e358 fffffa80`0480e358 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba2810 fffff800`04498bbe : 00000426`e4157de9 fffff800`00ba2e88 00000000`01be8535 fffff800`04603928 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`044989a7 : fffffa80`0528dcc2 fffffa80`01be8535 fffffa80`05287000 00000000`00000035 : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`04491305 : 00000000`00000000 fffffa80`05e16760 00000000`00000000 fffff880`0696d480 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`0449111c : fffffa80`05df2370 fffff800`04a01895 fffff800`04a27460 fffff880`07a8dbc0 : nt!KyRetireDpcList+0x5
    fffff880`07a8db00 fffff800`044d9193 : fffff800`0448a740 fffff800`0448a7ac fffff880`07a8db80 00000000`000000f4 : nt!KiDispatchInterruptContinue
    fffff880`07a8db30 fffff800`0448a7ac : fffff880`07a8db80 00000000`000000f4 00000000`00000001 00000000`00000000 : nt!KiDpcInterruptBypass+0x13
    fffff880`07a8db40 fffff880`06950363 : fffff880`009ebec0 fffff880`0694fdc0 fffffa80`05df2370 fffffa80`05df2370 : nt!KiInterruptDispatchNoLock+0x1fc
    fffff880`07a8dcd0 fffff880`0694fe96 : 00000000`00000000 fffffa80`03f00010 00000000`00000080 fffffa80`05df2370 : dxgmms1!VidSchiSubmitQueueCommand+0x1b
    fffff880`07a8dd00 fffff800`04724e6a : 00000000`06ba6da1 fffffa80`05e16760 fffffa80`039e89e0 fffffa80`05e16760 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`07a8dd40 fffff800`0447eec6 : fffff880`009e7180 fffffa80`05e16760 fffff880`009f1f40 fffffa80`04960e70 : nt!PspSystemThreadStartup+0x5a
    fffff880`07a8dd80 00000000`00000000 : fffff880`07a8e000 fffff880`07a88000 fffff880`07a8cf30 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    WmXlCore+669e
    fffff880`06b3569e 0100 add dword ptr [rax],eax

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: WmXlCore+669e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_IP_MISALIGNED_WmXlCore.sys

    BUCKET_ID: X64_IP_MISALIGNED_WmXlCore.sys

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

    0: kd> lmvm hardware
    start end module name
     
  2. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Do you still need assistance with this topic?

    Looks like hardware to me - maybe video. Start with these free diagnostics (start with the video tests): Hardware Diagnostics
     
  3. daiwuff

    daiwuff New Member

    Joined:
    Jul 18, 2012
    Messages:
    4
    Likes Received:
    0
    Yeah.. thanks! Video made sense, it only happens while I'm playing a game (a particular mmorpg I play). So I'd updated my graphics driver after the above crash, and it's still blue screened three times since. Though the debugging info is always different. :/ I'm wondering if it might have something to do with the power the fan on my card is drawing...
     
  4. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    If you can't isolate anything with the video, then start looking at your Logitech Wingman - both the software and the device itself. This driver belongs to it: WmXlCore.sys. It's actually more likely to be the problem than your video is.

    Un-install the software for the device, then download and install a fresh copy of the latest Win7 compatible software for the device.
    If the BSOD's continue, then un-install the Logitech software and physically remove the device from your system - see if that stops the BSOD's

    Then, if that doesn't work, please run Driver Verifier according to these instructions: Driver Verifier Settings

    Also, please generate and upload these reports so we can get a bit more information: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html
     

Share This Page

Loading...