Deathadder driver causing BSOD
The past week I've been getting random BSOD's. It doesn't happen when I'm playing a game. It usually happens when I'm just surfing the internet. I'll be clicking on a page and sometimes a link will stop letting me click it (happens on the links in the Steam store alot lately) as if the hyperlink went away or something. Then occasionally I'll just click on a link and BAM! the screen goes blue.
When the screen goes blue it's only there for a split second before the MOBO goes into it's boot cycle. The machine reboots just fine and works completely normal beyond that.
When the windows error report runs it says it's due to a device driver.
Brand new 8800GT with the newest driver installed. Everything else is brand new on this machine with the most current drivers I can find.
Is there a way to pull up the text from a BSOD when I'm in windows? I'm hoping that I can glean some more conclusive information from that - it just goes by to quick for me to see it normally.
Edit: Found the culprit. Any suggestions how to solve the issue with the Razer Deathadder driver?
"Fault always lies in the same place...with those foolish enough to lay blame"*
-Cort
*Unless you're Amazon or Funcom, in which case, SCREW YOU.
There may be some information logged in the event viewer in your control panel, under administrative tools, however sometimes the BSOD hits the system so hard that it can't capture the data in the logs. If that's the case, then go to the control panel, open the system applet, click on advanced, then startup and recovery settings. Uncheck the "automatically restart" option under the system failure heading and your BSODs will now stay on the screen until you manually reboot, allowing you time to copy down the necessary details.
-- My Biking Team --
Generally there is a code in the first line, sort of looks like a serial number. Write that down and check it from Microsoft, they have a big archive of them.
Serengeti's tip to turn off the automatic reboot configured on some boxes is a good one.
If you have the time/energy following the directions in this article will also let you find the culprit.
Do you ever walk alone like a drifter in the dark?
This was Awesome advice! I read through the article and used the Windbg gui.
It nailed a driver issue I was having with my Mouse, on the dadder.sys file.
I haven't really figured out how to fix the problem yet though. I'm using a Razer Deathadder mouse. I've updated to the latest driver/firmware from the site but the crash has still occured. I uninstalled the mouse completely and the dadder.sys file was still in the driver folder.
I'd rather not get a new mouse but I can't decide how to work around the driver issue here. Should I try an older driver perhaps?
"Fault always lies in the same place...with those foolish enough to lay blame"*
-Cort
*Unless you're Amazon or Funcom, in which case, SCREW YOU.
I was having the same issue with my new Deathadder.
I just removed the Razer drivers and use it with the standard Windows drivers. The sensitivity is still there, so I'm happy.
I with Razer would get their sh*t together with their drivers, though.
xbox live: Lester King 17