Hello,

I've been getting this stop error after, predominantly since I enabled Driver Verifier.  I have a Logitech T650 touch pad and a Logitech cordless mouse.  It seems that whenever I use the touchpad, I get this error.  All my drivers are up to date and AV/Anti-Malware shows no issues.  Memtest also shows no issues.  System is Win8 64-bit, 128GB SSD, 16GB RAM, AMD FX8350

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

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

Symbol search path is: SRV*C:\My\Sym*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
Machine Name:
Kernel base = 0xfffff802`7e215000 PsLoadedModuleList = 0xfffff802`7e4e1a20
Debug session time: Fri Jun 28 10:49:58.943 2013 (UTC - 4:00)
System Uptime: 0 days 0:25:08.729
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {20003, fffff880010d3050, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for LMouFilt.Sys
Probably caused by : mouclass.sys ( mouclass!MouseClassServiceCallback+5f )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000020003, ID of the 'IrqlDispatch' rule that was violated.
Arg2: fffff880010d3050, A pointer to the string describing the violated rule condition.
Arg3: 0000000000000000, An optional pointer to the rule state variable(s).
Arg4: 0000000000000000, Reserved (unused)

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

DV_VIOLATED_CONDITION:  KeAcquireSpinLockAtDpcLevel should only be called at IRQL >= DISPATCH_LEVEL.

DV_RULE_INFO: !ruleinfo 0x20003

BUGCHECK_STR:  0xc4_IrqlDispatch_XDV

IMAGE_NAME:  mouclass.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ab5f

MODULE_NAME: mouclass

FAULTING_MODULE: fffff880010c5000 VerifierExt

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  KHALMNPR.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880010cf21f to fffff8027e26f440

STACK_TEXT: 
fffff880`0f0850f8 fffff880`010cf21f : 00000000`000000c4 00000000`00020003 fffff880`010d3050 00000000`00000000 : nt!KeBugCheckEx
fffff880`0f085100 fffff880`010c89ae : fffffa80`0f131780 fffff802`7e6446c7 00000000`00000000 fffff802`7e855d76 : VerifierExt!SLIC_abort+0x47
fffff880`0f085140 fffff880`010c89d6 : 00000000`00000000 00000000`00000003 fffffa80`0f6b3000 fffff880`0f085210 : VerifierExt!KeAcquireSpinLockRaiseToDpc_wrapper+0x5a
fffff880`0f085170 fffff802`7e8682db : 00000000`00000000 fffff880`012d2d66 00000000`00000000 00000000`00000000 : VerifierExt!KeAcquireSpinLockAtDpcLevel_wrapper+0x1a
fffff880`0f0851a0 fffff880`012e67f3 : fffffa80`0f1315a0 fffff980`1149ce40 00000000`00000000 fffff880`012d3453 : nt!VerifierKeAcquireSpinLockAtDpcLevel+0xa4
fffff880`0f0851e0 fffff880`012d3f75 : fffff880`0f085390 fffff980`78592e70 fffff980`1149ce40 fffff980`12ca4c50 : mouclass!MouseClassServiceCallback+0x5f
fffff880`0f085240 fffff880`012d408b : fffff980`12c36df0 00000000`00000001 fffff880`012d3280 fffff980`12ca4c50 : LMouFilt+0x3f75
fffff880`0f0852a0 fffff880`012d1e81 : fffff980`12c36df0 fffff980`484a8ff0 00000000`00000c30 fffff980`6eceeff4 : LMouFilt+0x408b
fffff880`0f0852d0 fffff880`012d1858 : fffff980`12c36df0 fffff980`484a8ff0 fffff980`00000c30 fffff980`6eceeff4 : LMouFilt+0x1e81
fffff880`0f085330 fffff880`012d74f7 : 0000067f`b65150d8 0000067f`87a6d188 fffff980`00220414 0000067f`ed3c94b8 : LMouFilt+0x1858
fffff880`0f085490 fffff880`01110f88 : 0000067f`ed35b3a8 0000067f`87a6d188 00000000`00000000 00000000`00000008 : LMouFilt+0x74f7
fffff880`0f085560 fffff880`0111042f : fffff980`12ca4c00 fffff980`00000008 fffff980`12ca4c50 00000000`00000001 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x488
fffff880`0f0855e0 fffff880`0111bfbb : fffff980`1149ce40 fffff980`78592e00 00000000`00000000 fffff980`78592e70 : Wdf01000!FxIoQueue::DispatchEvents+0x66f
fffff880`0f085660 fffff880`0111530a : fffff980`1149ce00 fffff980`78592e70 fffff980`76552ea0 fffff880`0f085740 : Wdf01000!FxIoQueue::QueueRequest+0x2ab
fffff880`0f0856d0 fffff880`011149da : fffff980`78592e70 00000000`0000002a fffffa80`0f131b00 fffff980`76552ea0 : Wdf01000!FxPkgIo::Dispatch+0x4da
fffff880`0f085740 fffff880`01114aa6 : fffff980`76552ea0 fffffa80`0f131be0 fffffa80`0f131be0 fffffa80`0d80a7a0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`0f085780 fffff802`7e855d76 : fffff980`76552ea0 fffffa80`0f131be0 00000000`00000002 fffffa80`0ce2c218 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`0f0857c0 fffff802`7e6446c7 : fffff980`76552ea0 fffff880`0f085b00 00000000`00000001 fffffa80`0d80a7a0 : nt!IovCallDriver+0x3e6
fffff880`0f085810 fffff802`7e6598a6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`042efc00 : nt!IopXxxControlFile+0x7e5
fffff880`0f0859a0 fffff802`7e26e453 : fffffa80`10d88b30 fffff880`0f085b00 fffffa80`10d88b30 fffff802`7e653e7d : nt!NtDeviceIoControlFile+0x56
fffff880`0f085a10 000007fa`65c22c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`042efac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fa`65c22c5a

STACK_COMMAND:  kb

FOLLOWUP_IP:
mouclass!MouseClassServiceCallback+5f
fffff880`012e67f3 488d45f0        lea     rax,[rbp-10h]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  mouclass!MouseClassServiceCallback+5f

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID_FUNC_OFFSET:  5f

FAILURE_BUCKET_ID:  0xc4_IrqlDispatch_XDV_VRF_mouclass!MouseClassServiceCallback

BUCKET_ID:  0xc4_IrqlDispatch_XDV_VRF_mouclass!MouseClassServiceCallback

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

 Any ideas?

 

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS. You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking. If you are overclocking stop.  (chances are if you dont know if you are, you are not)a To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm The procedure: * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine. * Zip up the copy. * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)  *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply. Link for how to  upload below. http://www.wikihow.com/Use-SkyDrive To ensure minidumps are enabled: * Go to Start, in the Search Box type: sysdm.cpl, press Enter. * Under the Advanced tab, click on the Startup and Recovery Settings... button. * Ensure that Automatically restart is unchecked. * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies). * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump. * OK your way out. * Reboot if changes have been made. Please also run MSinfo32 and upload the output as well. To run MSinfo32 please go to start>run>MSinfo32 Go to "file" "save" and upload the saved file with the DMPS System specs are extremely useful so please include whatever you know. Team Zigzag3143.com

Thanks for the response.  I have the files you need uploaded to my SkyDrive, but I keep getting an error trying to post the link here saying I can't post any links until my account is verified.  How do I get my account verified? I didn't receive an email when establishing my profile

Derrick

You should get your account validated (for future issues) but it will let you post a link if you leave off the https:// at the beginning and just post the rest.

If you are being told you cant post a link, or embed a picture (or any other restriction) you just need to post to this thread saying your account has not been validated http://social.msdn.microsoft.com/Forums/en-US/reportabug/thread/812eb24a-ecbd-46e8-936b-8ae40da72ec3 http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/e82268c3-d5a3-48c7-a711-3a7fb44abf4e http://social.msdn.microsoft.com/Forums/en-US/reportabug/thread/6673b7ac-4c8e-4e55-80f2-ebfdb2e2b43e

Try this....

sdrv.ms/11SzHKI

Thanks

Derrick

These were Related to LMouFilt.Sys Logitech SetPoint KMDF Mouse Filter Driver.  I would check to see if there is a newer driver (yours 01/2013) and if so re-install using the newer driver.  If there isnt re-install the current driver in compatibility mode (see below).  Also of note,  KHALMNPR.exe was the running process when the crash occured (Part of the Logitech Setpoint software for their wired and wireless mice and trackballs) so I would be inclined to remove it as well

If I were you I would remove Avast and use the built in defender.

To Run in compatibility mode do the following:

Right click the installer>properties>compatibility>choose OS

http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1

Avast  can be a  contributing cause of BSOD'S in win 8.

http://files.avast.com/files/eng/aswclear5.exe

BugCheck C4, {20003, fffff880010d3050, 0, 0}
*** WARNING: Unable to verify timestamp for LMouFilt.Sys
*** ERROR: Module load completed but symbols could not be l

Sorry for the confusion, it's regular http, no "s"

Derrick

My mistake not yours, sorry. Figured it out see above.

It looks like Logitech is the culprit.  I removed Avast (even ran the cleaner in safe mode) and enabled Defender.  There are no newer Logitech drivers, so I re-ran the latest Logitech install in Win7 compatibility mode and I still crashed with the same stack output.  It appears that the Logitech software is using mouclass.sys for something related to the touch pad only, because operation of the mouse produces no bugcheck.  I uninstalled Logitech and there was no Bugcheck while I was using the touchpad (although functionality of the touchpad has been reduced to next-to-nothing).  I then reinstalled the Logitech drivers, tried the touchpad and it Budchecked instantly with the same output. 

Guess I'll see what Logitech has to say.... :-(

Thanks for the help

Derrick

At least you know what it is.  You can contact Logitech but I suspect it is something local as I ran it on win 8 and am now running it on 8.1

That's quite possible that it's local.  I was running it fine until I enabled Driver Verifier, actually.  Perhaps DV is a little too sensitive?

Derrick

It is supposed to be that sensitive to "catch" the mis-behaving drivers but sometimes it is not sensitive enough and sometimes too sensitive.  After all its just a tool for when all else fails.

BSODS are almost always a combination of things.  Logitech will work perfectly in the vast majority of cases but combine it with something else that is also working fine and you get grief.

Glad to see the issue is resolved.