Blue Screens started out of the blue.

[Gussi]

All of a sudden when I was playing Black Ops I got a Blue Screen and ever since I've been getting random BS's once in a while and I have no idea why and would highly appreciate any help I can get. I was googling around and found this site and saw you had helped a lot of people so I thought why not try. Anyways attached are the .dmp files and the System Health Report. It's been a while since I reinstalled Windows 7. It's the Ultimate edition and it's x64. My basic specs are:
AMD Athlon 7750 Dual Core at 2,7 GHz.
ATi Radeon HD 4670
4GB DDR2 ram at 800MHz
Gigabyte motherboard.

Greetings from Iceland, Brynjar!(No pun intended in the title by the way)

 

[richc46]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp5_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\061811-20092-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`03257650
Debug session time: Sat Jun 18 16:21:18.730 2011 (GMT-4)
System Uptime: 1 days 7:56:42.290
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
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 : Lycosa.sys ( Lycosa+1c23 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+0
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  BlackOpsMP.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800030896be to fffff80003091cd0
STACK_TEXT:  
fffff880`03121dd8 fffff800`030896be : fffffa80`050e7bd0 fffffa80`0483bb00 fffff880`031225e0 fffff800`030bd890 : nt!KeBugCheck
fffff880`03121de0 fffff800`030bd55d : fffff800`03298968 fffff800`031d5cbc fffff800`03012000 fffff880`03122540 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03121e10 fffff800`030bc335 : fffff800`031d9028 fffff880`03121e88 fffff880`03122540 fffff800`03012000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03121e40 fffff800`030bf632 : fffff880`03122540 fffff880`031225e0 fffff880`00000001 00000000`00000001 : nt!RtlDispatchException+0x415
fffff880`03122520 fffff800`0304c6ea : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0512d500 : nt!RtlRaiseStatus+0x4e
fffff880`03122ac0 fffff880`08afbc23 : fffffa80`05100600 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff880`03122b40 fffffa80`05100600 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000007 : Lycosa+0x1c23
fffff880`03122b48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000007 00000000`00000000 : 0xfffffa80`05100600
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
Lycosa+1c23
fffff880`08afbc23 ??              ???
SYMBOL_STACK_INDEX:  6
SYMBOL_NAME:  Lycosa+1c23
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Lycosa
IMAGE_NAME:  Lycosa.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4c86fc86
FAILURE_BUCKET_ID:  X64_0x1E_Lycosa+1c23
BUCKET_ID:  X64_0x1E_Lycosa+1c23
Followup: MachineOwner
---------

You gave us three dumps, one indicated memory. Take a memory test after updating this driver, which was shown as the cause on the other two.
After you update drivers, test. If no more BSODs your done. If you get others, test memory.
Lycosa.sys file description
Productname:Razer Tarantula
Description:Razer Tarantula Keyboard Driver
Company:Razer USA Ltd.

Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If it passes try a good stick in each slot for 3 passes
If it fails do the same for 8 passes.

If you still get BSODs after memory, we have other possible remedies. This will get done.

 

[zigzag3143]

All of a sudden when I was playing Black Ops I got a Blue Screen and ever since I've been getting random BS's once in a while and I have no idea why and would highly appreciate any help I can get. I was googling around and found this site and saw you had helped a lot of people so I thought why not try. Anyways attached are the .dmp files and the System Health Report. It's been a while since I reinstalled Windows 7. It's the Ultimate edition and it's x64. My basic specs are:
AMD Athlon 7750 Dual Core at 2,7 GHz.
ATi Radeon HD 4670
4GB DDR2 ram at 800MHz
Gigabyte motherboard.

Greetings from Iceland, Brynjar!(No pun intended in the title by the way)

Memory corruption caused by a driver. Please run these two tests


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff 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/Win7 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" (without the quotes) 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.

 

[Gussi]

Thanks I'll try that.