Blue Screen

[BamaCeltic]

I have started getting a blue screen on restart and shut down usually when I have my keyboard mess up. I am using a Razer Lycosa keyboard and the problem I am referring to is some of the keys will stop working. I actually already got a replacement keyboard from Razer and am still having the same problem(totally different keyboard). The blue screen doesn't only occur when the keyboad messes up so I'm not sure if it is the problem. I also have trouble like I cannot get Adobe Photoshop to install on my computer. Wondering if I may have a bad hardware component but not sure how to figure it out. I have reinstalled Windows numerous times trying to work out the problem but it doesnt help. I even tried by-passing the HP software and JUST installing Windows directly but for some reason it doesnt pick up as a boot cd if I try that. Can anyone tell me where to go from here?

I am attaching the minidump files I have to give added help to anyone that knows how to read them.

 

[usasma]

More problems with the Razer components - I'm seeing a lot of these recently!

Please uninstall the software and drivers for your Razer Tarantula Keyboard (the memory dump blames the Lycosa.sys driver)
Then monitor for further BSOD's.
Then download the latest Win7 drivers for your keyboard and install them - and monitor for further BSOD's

If this doesn't stop the problems, then try another keyboard. All 4 memory dumps blame the same driver - so it's gotta be either the drivers or the keyboard itself.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2008 or earlier:

fnetm64.SYS  Thu Mar 27 14:03:03 2008 - Panda Security - http://www.carrona.org/dvrref.html#fnetm64.SYS
Prot6Flt.sys Wed Jul 09 06:27:18 2008 - Panda Security - http://www.carrona.org/dvrref.html#Prot6Flt.sys
ShldFlt.sys  Thu Feb 28 07:22:30 2008 - Panda Security - http://www.carrona.org/dvrref.html#ShldFlt.sys

Summary of the BSOD's:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 00:19:19.336 2010 (GMT-4)
System Uptime: 0 days 0:07:08.990
BugCheck 1E, {0, 0, 0, 0}
*** 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+1267 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 23:06:59.348 2010 (GMT-4)
System Uptime: 1 days 0:20:50.002
BugCheck 1E, {0, 0, 0, 0}
*** 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+1267 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 20:02:30.261 2010 (GMT-4)
System Uptime: 0 days 2:45:06.916
BugCheck 1E, {0, 0, 0, 0}
*** 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+1267 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 26 20:04:57.068 2010 (GMT-4)
System Uptime: 0 days 0:04:54.722
BugCheck 1E, {0, 0, 0, 0}
*** 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+1267 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System