Windows 10: BSOD while trying to Eject a USB Thumb Drive

I was trying to remove a USB Thumb Drive, and that's when it crashed. Also, when it booted back up after the crash, it said there was a problem with my antivirus. My antivirus is working though. If this crash pertains to a driver, please note that I installed the latest Graphics Driver and it was really buggy. So I reverted back to my old Graphics driver. I have not had a problem in a while, except for the Windows Mail app. This is the first time it has crashed in a while.

Attachment 76392

:)

 

Windows 10 cannot "Safe Eject" USB drive

Open task manager performance tab & click on Resource Monitor on the bottom - might find what is using the usb drive.

I had the cant eject usb drive in use, it was a simple stand alone program, core temp, running from the thumb drive.

 

Start Menu, Search, Notifications not working. When is Patch coming?

Also, calendar on the toolbar isn't working. And USB thumb drive eject is not working.

So, that's Start Menu, Search, Notifications, Volume Control, External Drive Eject/Dismount and Calendar. All not working.

All of these are basic OS functions that should be rock solid. It is absurd that these basic functions don't operate on a major Windows upgrade.

This problem should have been patched yesterday. Or weeks ago.

 

The zip file you uploaded is empty, nothing in it. Try again but right click on dm_log_collector and select RUn as Administrator, see if that helps. Upload the zip file again then please.

 

That one should work.

Attachment 76409

 

Looks like it's caused by your mouse driver which is very old.

Code: SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: NMgamingms+1cbb FOLLOWUP_NAME: MachineOwner MODULE_NAME: NMgamingms IMAGE_NAME: NMgamingms.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a6976ec FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb BUCKET_ID: 0x139_3_NMgamingms+1cbb ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x139_3_nmgamingms+1cbb FAILURE_ID_HASH: {177edb92-9b1b-58b9-1136-1a7e08f6eada} Followup: MachineOwner --------- 1: kd> lmvm NMgamingms start end module name fffff801`dad00000 fffff801`dad02c00 NMgamingms T (no symbols) Loaded symbol image file: NMgamingms.sys Image path: \SystemRoot\system32\drivers\NMgamingms.sys Image name: NMgamingms.sys Timestamp: Fri Jul 24 04:55:08 2009 (4A6976EC) CheckSum: 0000EC2F ImageSize: 00002C00 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] You need to update the mouse driver. Is this the one you have?

If no newer driver it's time to get a new mouse.

 

You need to update the mouse driver. Is this the one you have?



If no newer driver it's time to get a new mouse.[/quote] So I need to go to the Primax website and see if there is a new version for the mouse?

 

I'm not really sure. My mouse is Gear Head. I looked up Primax and couldn't find a website for them.

 

See if you can find an updated driver for the Gear Hear Optical Mouse.

 

Okay. Let me see. It let me download the software for it, but it didn't get to finish it because it crashed again. So I turned the mouse off.

 

It's not letting me load the software configuration for the mouse.

 

If it's the same place I just tried, those drivers were pretty old (2007)

PC Gearhead

Can you post the hardware ID's like this,

Attachment 76415

It doesn't look good for that mouse though.

 

Attachment 76416

 

Yeah, I don't get any vendor with that, I just thought it was worth a try.

May just have to get a different mouse Jesse.

 

Is it possible to find a mouse that when the drivers expire, you can always update them so that this won't happen again? I found another Gear Head for $12 to $13.