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

Window Framework driver error


  • Please log in to reply
2 replies to this topic

#1 Renogen

Renogen

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:06 AM

Posted 24 October 2011 - 09:32 PM

Hi,

Recently, I've been getting BSOD by this error. Below is the memory.dmp analysis from WinDbg. Any help to solve this will be appreciated.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03299670
Debug session time: Tue Oct 25 10:06:38.175 2011 (UTC + 8:00)
System Uptime: 2 days 8:38:37.766
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {a, fffff88003393cb0, 0, fffffa8006be69e0}

*** ERROR: Module load completed but symbols could not be loaded for mousim.sys
Probably caused by : mousim.sys ( mousim+19df )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 000000000000000a, A fatal error has occurred while processing a request on the
	queue.
Arg2: fffff88003393cb0, Pointer to a WDF_QUEUE_FATAL_ERROR_DATA structure.
Arg3: 0000000000000000, Reserved.
Arg4: fffffa8006be69e0, Reserved.

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


BUGCHECK_STR:  0x10D_a

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  mpc-hc.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000e6c1fb to fffff800030d0c40

STACK_TEXT:  
fffff880`03393c78 fffff880`00e6c1fb : 00000000`0000010d 00000000`0000000a fffff880`03393cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`03393c80 fffff880`00e6439b : 0b380b58`0b580b02 00000000`00000000 fffffa80`072fc030 fffff880`057ccdd2 : Wdf01000!FxIoQueue::FatalError+0x5b
fffff880`03393ce0 fffff880`01d789df : fffffa80`07fd2460 fffffa80`07068b40 fffffa80`07068d01 fffffa80`07068d01 : Wdf01000!imp_WdfIoQueueStop+0xab
fffff880`03393d20 fffff880`01d795ff : 0000057f`f802db98 00000000`00000000 00000000`00000000 fffff880`00000146 : mousim+0x19df
fffff880`03393d50 fffff880`01d79bf6 : fffffa80`077bdc58 fffff880`00020000 0000057f`f802db98 fffffa80`077bdc58 : mousim+0x25ff
fffff880`03393de0 fffff880`057b12ea : fffffa80`070687d0 fffffa80`077bdc58 fffffa80`077bdc70 fffff880`03393f08 : mousim+0x2bf6
fffff880`03393e30 fffff800`030dc0ac : fffff880`03364180 fffffa80`00000000 fffffa80`070689f0 fffffa80`07068d90 : i8042prt!I8042MouseIsrDpc+0x28e
fffff880`03393f00 fffff800`030d3765 : 00000000`00000000 fffffa80`0c5d69a0 00000000`00000000 fffff880`057b105c : nt!KiRetireDpcList+0x1bc
fffff880`03393fb0 fffff800`030d357c : 00000000`74c02450 00000000`0098c120 00000000`0098fd20 00000000`fffdb000 : nt!KyRetireDpcList+0x5
fffff880`0aa5d320 fffff800`0311c993 : fffff800`030ccab6 fffff800`030ccb22 00000000`0964e160 fffff880`00000001 : nt!KiDispatchInterruptContinue
fffff880`0aa5d350 fffff800`030ccb22 : 00000000`0964e160 fffff880`00000001 fffffa80`04d6f0c0 00000000`00000001 : nt!KiDpcInterruptBypass+0x13
fffff880`0aa5d360 00000000`74c0271e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x212
00000000`001ce654 fffff800`030c8210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c0271e
fffff880`0aa5d760 00000000`00000000 : fffff800`03012b7f 00000000`00000000 fffff880`009e9180 00000000`00000000 : nt!KiCallUserMode


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mousim+19df
fffff880`01d789df 4883c428        add     rsp,28h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mousim+19df

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mousim

IMAGE_NAME:  mousim.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd1863a

FAILURE_BUCKET_ID:  X64_0x10D_a_mousim+19df

BUCKET_ID:  X64_0x10D_a_mousim+19df

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 000000000000000a, A fatal error has occurred while processing a request on the
	queue.
Arg2: fffff88003393cb0, Pointer to a WDF_QUEUE_FATAL_ERROR_DATA structure.
Arg3: 0000000000000000, Reserved.
Arg4: fffffa8006be69e0, Reserved.

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


BUGCHECK_STR:  0x10D_a

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  mpc-hc.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000e6c1fb to fffff800030d0c40

STACK_TEXT:  
fffff880`03393c78 fffff880`00e6c1fb : 00000000`0000010d 00000000`0000000a fffff880`03393cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`03393c80 fffff880`00e6439b : 0b380b58`0b580b02 00000000`00000000 fffffa80`072fc030 fffff880`057ccdd2 : Wdf01000!FxIoQueue::FatalError+0x5b
fffff880`03393ce0 fffff880`01d789df : fffffa80`07fd2460 fffffa80`07068b40 fffffa80`07068d01 fffffa80`07068d01 : Wdf01000!imp_WdfIoQueueStop+0xab
fffff880`03393d20 fffff880`01d795ff : 0000057f`f802db98 00000000`00000000 00000000`00000000 fffff880`00000146 : mousim+0x19df
fffff880`03393d50 fffff880`01d79bf6 : fffffa80`077bdc58 fffff880`00020000 0000057f`f802db98 fffffa80`077bdc58 : mousim+0x25ff
fffff880`03393de0 fffff880`057b12ea : fffffa80`070687d0 fffffa80`077bdc58 fffffa80`077bdc70 fffff880`03393f08 : mousim+0x2bf6
fffff880`03393e30 fffff800`030dc0ac : fffff880`03364180 fffffa80`00000000 fffffa80`070689f0 fffffa80`07068d90 : i8042prt!I8042MouseIsrDpc+0x28e
fffff880`03393f00 fffff800`030d3765 : 00000000`00000000 fffffa80`0c5d69a0 00000000`00000000 fffff880`057b105c : nt!KiRetireDpcList+0x1bc
fffff880`03393fb0 fffff800`030d357c : 00000000`74c02450 00000000`0098c120 00000000`0098fd20 00000000`fffdb000 : nt!KyRetireDpcList+0x5
fffff880`0aa5d320 fffff800`0311c993 : fffff800`030ccab6 fffff800`030ccb22 00000000`0964e160 fffff880`00000001 : nt!KiDispatchInterruptContinue
fffff880`0aa5d350 fffff800`030ccb22 : 00000000`0964e160 fffff880`00000001 fffffa80`04d6f0c0 00000000`00000001 : nt!KiDpcInterruptBypass+0x13
fffff880`0aa5d360 00000000`74c0271e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x212
00000000`001ce654 fffff800`030c8210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c0271e
fffff880`0aa5d760 00000000`00000000 : fffff800`03012b7f 00000000`00000000 fffff880`009e9180 00000000`00000000 : nt!KiCallUserMode


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mousim+19df
fffff880`01d789df 4883c428        add     rsp,28h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mousim+19df

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mousim

IMAGE_NAME:  mousim.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd1863a

FAILURE_BUCKET_ID:  X64_0x10D_a_mousim+19df

BUCKET_ID:  X64_0x10D_a_mousim+19df

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


I realised that mousesim.sys seems to be from a macro program called Blue Eye Macro. But I wasn't running the program at the point of the BSOD.

Edited by Renogen, 24 October 2011 - 09:34 PM.


BC AdBot (Login to Remove)

 


#2 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:06 AM

Posted 24 October 2011 - 10:13 PM

Removing the program would know if the bluescreen would still occur.

Tekken
 


#3 Renogen

Renogen
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:06 AM

Posted 28 October 2011 - 04:45 AM

removed but still BSOD.

mousim.sys seems to affect any mouse control in windows 7. putting it in recycle bin will make all mouse control useless, mouse or touchpad.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users