Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Intermittent BSOD After Changing Mouse

11 Jun 2015   #1

Windows 7 Home Premium x64
Intermittent BSOD After Changing Mouse

After my Microsoft wireless mouse clicked it's last clack, I changed to a Logitech Marathon M705. I still use the MS wireless keyboard, so now I have two USB transceivers-- one for the keyboard, one for the mouse. Don't know if this is the source of the problem, but I do know that no other system changes were made since the BSOD's began.

I logged a support call with Logitech with this: "Windows 7 system crashes occasionally since I started using the Marathon M705. No other changes have been made to the system. My mouse drivers are Microsoft's HID-compliant Mouse version 6.1.7600.16385 and USB Dual Receiver Wireless Mouse Should I be using some other drivers?", and they, not answering my question, responded with the following:

Please perform the following troubleshooting steps:

1. Download Unifying Software
2. Click Advance
3. Check if the device is on the left side of the screen
4. Highlight the device name
5. Unpair/Uninstall device
6. Wait for 10-15 seconds
7. Click Add/Pair New Device
8. Check if the device is now working
1. Remove Battery
2. Press each buttons for 30 seconds
3. Place battery back inside the battery compartment
4. Turn off the mouse and turn it back on
5. Test mouse if it still not clicking
1. Try another port
1. Try another computer

I've tried the 1st and 2nd recommendations to no avail. Then I found this forum and thought maybe one of you nice people could help.

My DM Log Collection file is attached.

Thanks so much for your time!

My System SpecsSystem Spec
14 Jun 2015   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

 Clean boot
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\YUSSIKAT\Downloads\HERCULES-Thu_06_11_2015_173006_22\061115-17113-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*
Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`03266000 PsLoadedModuleList = 0xfffff800`034ab890
Debug session time: Thu Jun 11 23:17:13.851 2015 (UTC + 6:00)
System Uptime: 1 days 1:55:20.084
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800897a620, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33da4 )

Followup: MachineOwner

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

    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800897a620
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:

BUGCHECK_STR:  0x1a_41790



PROCESS_NAME:  svchost.exe


ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003349630 to fffff800032d8a40

fffff880`0d76b818 fffff800`03349630 : 00000000`0000001a 00000000`00041790 fffffa80`0897a620 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0d76b820 fffff800`032c5f1f : fffffa80`00000000 00000000`2fa1ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33da4
fffff880`0d76b9e0 fffff800`032d7cd3 : ffffffff`ffffffff 00000000`0f1ff108 00000000`0f1ff100 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0d76bae0 00000000`773bddba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0f1ff0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773bddba


nt! ?? ::FNODOBFM::`string'+33da4
fffff800`03349630 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33da4

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


IMAGE_VERSION:  6.1.7601.18798

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33da4

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33da4


FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+33da4

FAILURE_ID_HASH:  {df764026-faf7-d682-0d92-b9895c2e6adf}

Followup: MachineOwner
Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

  • Double click and open my computer.
  • Right click on desired drive and hit properties.
  • Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Memtest should be done overnight.
My System SpecsSystem Spec

 Intermittent BSOD After Changing Mouse

Thread Tools

Similar help and support threads
Thread Forum
Intermittent Freezes; Keyboard and Mouse stop working Windows 7
Good Morning all! I am writing this post asking for help on my newly upgraded custom computer has been giving me crap for the past week since the upgrade... The issue so far: Every so often, randomly, my computer will "freeze". The reason I put "" around freeze is because I am not sure if...
Hardware & Devices
BSOD after changing wireless mouse batteries
Im back once again. I have an HP Pavilion G series and it has bsod on me twice recently. It started happening when I added new batteries to my wireless mouse. Seems strange right?? Other than than I would get random shutdowns while not doing anything in particular. Same old story except for the...
BSOD Help and Support
Win 7 64 - Intermittent - When Waking has no Video/Mouse, KB Control
This is a fresh install of Ultimate on a newly built Computer. Asus Z97, 16 Gig, Asus 240 Gig SSD, Seagate 2 TByte HD, Asus Ge Force GT-640 running 3 Samsung monitors. Win Experience Index of 7.1. 9 out of 10 times the system wakes up just fine. Every 10th time or so, the system seems to be...
General Discussion
Gigabyte GA-Z87X-UD4H Intermittent USB failure with mouse and keyboard
I upgraded my system at the beginning of January with an i7-4770K in a Gigabyte GA-Z87X-UD4H with 16GB of G.Skill Trident X memory. Almost immediately after build, I started running into a problem with my USB ports. The primary problem is that my mouse will often stop responding for a few seconds,...
Hardware & Devices
Baffling intermittent mouse lag problem Razer Abyssus
I have searched help forums far and wide without finding a solution to this problem, or even a similar description. Every 10 minutes or so, my mouse will lag for 4-7 seconds, and then correct itself. What I mean by lag is that it will suddenly appear to me moving more slowly than before, but will...
General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:43.
Twitter Facebook Google+