Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

REEQUEST HELP WITH DEBUGGING INFO ON MEMORY DUMP FILE


  • Please log in to reply
1 reply to this topic

#1 HunterL

HunterL

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:29 AM

Posted 12 October 2009 - 05:36 AM

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02649000 PsLoadedModuleList = 0xfffff800`0280ddd0
Debug session time: Mon Oct 12 04:40:55.052 2009 (GMT-5)
System Uptime: 0 days 6:01:08.003
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {37fe, 2, 1, fffff8000266c84b}

Probably caused by : hardware ( mouclass!MouseClassServiceCallback+49 )

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

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: 00000000000037fe, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8000266c84b, address which referenced memory

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


WRITE_ADDRESS: 00000000000037fe

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiIdleSchedule+137
fffff800`0266c84b 018bf8370000 add dword ptr [rbx+37F8h],ecx

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffffa600211b5f0 -- (.trap 0xfffffa600211b5f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa60005ec180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000266c84b rsp=fffffa600211b780 rbp=fffff800027b8a00
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiIdleSchedule+0x137:
fffff800`0266c84b 018bf8370000 add dword ptr [rbx+37F8h],ecx ds:0004:37f8=????????
Resetting default scope

MISALIGNED_IP:
nt!KiIdleSchedule+137
fffff800`0266c84b 018bf8370000 add dword ptr [rbx+37F8h],ecx

LAST_CONTROL_TRANSFER: from fffff800026a31ee to fffff800026a3450

STACK_TEXT:
fffffa60`0211b4a8 fffff800`026a31ee : 00000000`0000000a 00000000`000037fe 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`0211b4b0 fffff800`026a20cb : 00000000`00000001 fffffa80`071d7e17 00000000`00000000 00000000`00000006 : nt!KiBugCheckDispatch+0x6e
fffffa60`0211b5f0 fffff800`0266c84b : 00000000`00000080 00000000`00000001 fffffa80`06170560 fffffa60`134527a1 : nt!KiPageFault+0x20b
fffffa60`0211b780 fffffa60`133d6ac1 : fffffa80`060b0100 fffffa60`14b701ef fffffa80`06809c50 fffffa60`14b6f937 : nt!KiIdleSchedule+0x137
fffffa60`0211b7e0 fffffa60`14b81b17 : 00000000`00000002 fffffa80`067ef300 fffffa80`067ec750 fffffa80`067ec7f0 : mouclass!MouseClassServiceCallback+0x49
fffffa60`0211b840 fffff800`026ac5c2 : fffffa80`06874c60 fffffa80`00000000 fffffa80`00000000 fffffa80`00000000 : mouhid!MouHid_ReadComplete+0x637
fffffa60`0211b8c0 fffffa60`14b5e45d : fffffa80`06874c60 fffffa80`06d18706 fffffa80`06874ee0 fffffa80`068081d0 : nt!IopfCompleteRequest+0x302
fffffa60`0211b970 fffffa60`14b5e63e : fffffa80`06874202 fffffa80`0669d410 00000000`00000006 00000000`00000000 : HIDCLASS!HidpDistributeInterruptReport+0x245
fffffa60`0211ba00 fffff800`026ac5c2 : fffffa80`067ec840 fffffa80`06808060 fffffa80`05e2ad01 fffffa80`067e92d0 : HIDCLASS!HidpInterruptReadComplete+0x1ba
fffffa60`0211ba70 fffffa60`135a1e27 : fffffa80`05f09050 fffffa80`05f09000 fffffa80`05f091a0 fffffa80`05f09050 : nt!IopfCompleteRequest+0x302
fffffa60`0211bb20 fffffa60`135a24e0 : fffffa80`54546b63 fffffa80`067ec840 fffffa80`05f091a0 fffffa80`00000000 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x8d7
fffffa60`0211bc00 fffffa60`1359fb02 : fffffa80`39585043 fffffa80`05f091a0 fffffa80`05f0a088 fffffa80`05f091a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514
fffffa60`0211bc70 fffffa60`1358c1a7 : fffffa80`31636f49 fffffa80`05f0a088 00000000`00000002 fffffa80`05f091a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a
fffffa60`0211bcc0 fffff800`026a7667 : fffffa80`05f0a0a0 00000000`34776478 00000000`00000000 fffffa60`005ef580 : USBPORT!USBPORT_Xdpc_Worker+0x26f
fffffa60`0211bd10 fffff800`026a78e2 : fffffa60`1358bf38 fffffa60`005ec180 00000000`00000000 fffffa60`005f5d40 : nt!KiRetireDpcList+0x117
fffffa60`0211bd80 fffff800`02874860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffffa60`0211bdb0 00000000`fffffa60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
fffffa60`005efd00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00680000`00000000 : 0xfffffa60


STACK_COMMAND: kb

FOLLOWUP_IP:
mouclass!MouseClassServiceCallback+49
fffffa60`133d6ac1 488dbe90000000 lea rdi,[rsi+90h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: mouclass!MouseClassServiceCallback+49

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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

BC AdBot (Login to Remove)

 


#2 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:07:29 AM

Posted 12 October 2009 - 10:28 AM

If you have not already done it, I would recommend updating your Touchpad driver.

That driver can be located here.

Hope this helps,
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users