Windows 7: Random "Special Pool" BSOD's During General Use

Hi all,

I have a long history of BSOD's with this computer during startup but I eventually discovered (also with the help of this forum) that they were caused by my DeathAdder mouse. BSOD's during startup have vanished.

Instead, they have been replaced with BSOD's during the use of Skype, Microsoft Word, LOTRO or anything else I might have running. There's no pattern that I can discern except the BSOD's originate under the Special Pool flag. I have previously turned on Driver Verifier to help get some additional detail in my dump files.

At this point, the best I can tell the BSODs point to my Webcam and NVIDIA drivers both of which are absolutely current and have been so for some time. I've reached the point where I need some assistance from someone with a lot more expertise in parsing out system info.



Thanks in advance for the help!

Welcome
Your reports seem to point to your webcam. Go to the corporate website and update the driver
Lvrs64.sys file descriptionProductname:Logitech Webcam Software Description:Logitech Kernel Audio Improvement Filter Driver Company:Logitech Inc.
If the drivers are current as you say, try to roll them back.

Hi Rich,

Thanks for your note. I went to Logitech and found that I am on their most current driver package. The LVRS64 is a sub-component of that driver package - it's the audio improvement filter.

However, in my Device Manager under Sound, Video, & Game Controllers, I have 8 "NVIDIA High Definition Audio", 1 Realtek High Definition Audio, and 1 Webcam 600 entry. So that's my video cards trying to control audio, my actual sound card (Realtek) and my webcam. Is there a chance that's where the collision is happening?

I dont know the precise purpose for that driver other than its for the webcam. I think that you should go to the device manager and roll back the driver from the webcam. The previous version may work better than the current. That is something that happens many times. It happened to me with my graphics.
You could probably find where the driver is located via device manager. Just start to bring down the various trees.