New
#1
Bugcheck 0x0000003b While using a new mouse
Using a rather old PC right now. Gateway FX6840-15e. The mouse I'm currently using has been in the same USB slot for as long as I can remember, and the scroll wheel is driving me crazy. I decided to replace it today, and about ten minutes later I got a BSOD while clicking to close out Chrome. I've switched back to the old mouse and I haven't crashed in the past few hours. Reliability Monitor claims that it's 0x0000003b, which is apparently a graphics-driver thing so I'm not entirely certain that it's the mouse, however, I hadn't been gaming or anything at the time, and after rebooting I tested New Vegas for a few minutes with no issues.
Reliability Monitor:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000096, 0xfffff80002ee0875, 0xfffff8800998df20, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120915-36972-01.
I think the USB port may be damaged or otherwise messed up somehow, but I'll post the Graphics information just in case it was a coincidence. The PC runs a Radeon HD 5750, and it's using the driver version 8.711.0.0 from 2/25/2010. I have had other issues in the past; including BSODs when coming out of hibernation and the PC's blatant refusal to install DirectX and Microsoft .NET frameworks. These problems still persist to this day. I've attached the dump files, as instructed.
EDIT: I should probably clarify that I don't think the actual USB mouse that I had in when it crashed was the problem, but that it's the USB port that I plugged the mouse in to. I've had issues with it before when it wouldn't accept anything EXCEPT the mouse that had been plugged in to it for years already. It wouldn't even register that the mouse was removed. This last time I did it, when it BSOD'd, it took a good four or five seconds for the PC to make the "you unplugged the thing" chime.
Last edited by TheZman; 09 Dec 2015 at 22:45.
Quote