BSOD unplugging USB mouse

There is a lot of info missing needed to analyse your issue:

Please follow these instructions for posting:

https://www.sevenforums.com/crashes-d...tructions.html

   Tip

Ensure you click the "GRAB ALL" button and then wait for each window to appear in turn and then click OK

Cheers

Dave

Those are fine, thanks

Hi,
From your logs:

Code:

 
STOP 0x0000010D: WDF_VIOLATION 
Usual causes:  Device driver, ?Memory
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {a, fffff80000b9c8a0, 0, fffffa8005e1fae0}
Probably caused by : Wdf01000.sys ( Wdf01000!FxIoQueue::FatalError+5b )
Followup: MachineOwner
---------
0: 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.

Run SFC to check the integrity of all Windows 7 system files:
Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt
(Note: there is a space between SFC and /scannow)

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight

These drivers are contributing to your BSOD'S:

Code:

Faulting Driver: iaStor.sys
Dated: Sat Nov 06 07:44:52 2010
Refers To: Intel Storage drivers

Uninstall Intel Rapid storage Program, reboot and then download and install this stable version:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=21730

You want file: iata_enu.exe
Version: 11.2.0.1006
Date: 06/07/2012

Code:

Faulting Driver: Apfiltr.sys
Dated: Fri Dec 03 05:32:20 2010
Refers to: Alps Touch Pad Filter Driver for Windows x64

Update from OEM manufacturer's website or from device manager:
https://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html

Code:

Faulting Driver: mousim.sys
Dated: Mon May 16 21:16:58 2011

I cannot find any reference to this driver anywhere and suspect your computer maybe infected.

Run these programs to check for virus infection and post back any results:
http://kaspersky-tdsskiller.en.softonic.com/
Windows Defender Offline

Problem devices:

Code:

Antilog32 
Refers to: Zemana Antilogger or any other program with antilogger in the name.

Navigate to:
Start>Click Control Panel>change to icon view.
Click on Device manager>Click the View Tab>Click show hidden devices
locate non -plug & play devices> and then expand
Is there an AntiLog32 entry?

Cheers
Dave

Yes, there is an Antilog32 driver when I click show hidden drivers. It has a yellow warning at the corner and says "This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)"

I want to say that Mousim.sys is a virtual mouse driver. It is provided by the Macro Program "Blue Eye Macro". (Mousim is short form for Mouse Image)

Also, After completing the scans you told me to do, I found no memory issues or malware issues.

Glad to help
thanks for the info on Mousim.sys as it may help others in the future.

Antilog32 - Monitor the situation and see if any issues arise.

cheers

Dave