Seemingly random BSODs, often during shutdown

[potti15]

I've been getting BSODs randomly while using my computer. They happen a few times a week, and I don't know why. They seem to happen most often while why my computer is closing programs while it's shutting down, but they also happen occasionally while I'm playing Starcraft 2.

 

[koolkat77]

Welcome

One of your blue screen is related to your keyboard, check for a possible driver update.
Source Lycosa.sys Razer Tarantula Keyboard Driver Razer Support

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000047, fffff80003507ec8, fffff8800341f240, fffff8800341f2e0}

Unable to load image \SystemRoot\system32\drivers\Lycosa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : [B][COLOR=DarkRed]Lycosa.sys ( Lycosa+1051 )[/COLOR][/B]

Followup: MachineOwner
---------
1: kd> lmvm Lycosa
start             end                 module name
fffff880`05e00000 fffff880`05e07100   Lycosa   T (no symbols)           
    Loaded symbol image file: Lycosa.sys
    Image path: \SystemRoot\system32\drivers\Lycosa.sys
    Image name: Lycosa.sys
    Timestamp:        [B][COLOR=DarkRed]Wed Sep 08 09:01:26 2010 (4C86FC86)[/COLOR][/B]
    CheckSum:         0001462D
    ImageSize:        00007100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

STOP 0x000000C2: BAD_POOL_CALLER (go to top of page)

Usual causes: Device driver, Memory

To make sure that hard drive is good run disk check following this tutorial:
:ar: http://www.sevenforums.com/tutorials/433-disk-check.html
Run memtest86+ on each stick for 8 passes preferably overnight:
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Norton is also a known cause to bsods, I and many members on this forum recommend
MSE. The most compatible (+Free) antivirus for windows 7.
:ar: Microsoft Security Essentials - Free Antivirus for Windows

Post back results

 

[potti15]

I've done a disk check on both of my drives and that was all fine. I'll run the memtest tonight and will post results of that tomorrow. I've also checked the drivers for my keyboard, and they're up to date

 

[koolkat77]

Alright
Let us know if you're having more bsods

 

[potti15]

I had one more BSOD yesterday, which was Bad_Pool_Caller. Let me know if you would like me to upload the dump of that one. Also, after 8 passes of memtest I had one error:
Tst
Pass
Failing Address
Good
Bad
Err- Bits
Count
Chan
6
0
00194eb4088c-6478.7MB
40000000
40008000
00008000
1

 

[koolkat77]

I had one more BSOD yesterday, which was Bad_Pool_Caller. Let me know if you would like me to upload the dump of that one. Also, after 8 passes of memtest I had one error:
Tst
Pass
Failing Address
Good
Bad
Err- Bits
Count
Chan
6
0
00194eb4088c-6478.7MB
40000000
40008000
00008000
1

Thanks for the update
Even one error on ram means its bad. Can you get your ram replaced?

 

[potti15]

I can probably get a replacement if it's needed.

 

[koolkat77]

Go ahead, but if you want to reconfirm..You can lend sticks from a friend/neighbor (that matches with your board etc)
Also see how your computer performs without the damaged stick

 

[potti15]

I'm now getting blue screens during startup saying that a driver is trying to corrupt my the system. I have tried to start my computer with my keyboard drivers uninstalled, but that has not helped.

 

[koolkat77]

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[potti15]

I have done all of that now. How do I now whether it's worked or not?

 

[koolkat77]

How long did you keep verifier on for? 36 hours?

 

[potti15]

Oops, I didn't make that clear, I set up the verifier and re-booted my computer, but how do I know that it's running?

 

[koolkat77]

If you're system is laggy you'll understand

 

[potti15]

I had a blue screen which said that the driver verifier had found something

 

[koolkat77]

Yup. Update this driver its old:

Source: Lycosa.sys
Razer Tarantula Keyboard Driver
Razer Support

Driver Reference Table

3: kd> lmvm Lycosa
start             end                 module name
fffff880`05cda000 fffff880`05cde980   Lycosa   T (no symbols)           
    Loaded symbol image file: Lycosa.sys
    Image path: \SystemRoot\system32\drivers\Lycosa.sys
    Image name: [COLOR="Blue"]Lycosa.sys[/COLOR]
    Timestamp:        [COLOR="blue"]Fri Jan 18 14:51:42 2008[/COLOR] (4790689E)
    CheckSum:         0000E99D
    ImageSize:        00004980
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Don't disable verifier yet.

 

[potti15]

While trying to update the driver, my computer blue screened with the same error message about lycosa.sys. Also, I have the latest drivers already.

 

[koolkat77]

Okay, so are you having more blue screens now?

 

[potti15]

no blue screens since the driver update yet

 

[koolkat77]

Okay, keep verifier on for few more hours and observe for more blue screens.
If you get one, upload the dump.