Win 8 keyboard freezes and comp crashes

[casperX]

My computer has been having an issue lately where my keyboard will flip out and spam a certain key, which does not stop even when I unplug and replugin the keyboard. After it does this for about 30 sec or less the computer crashes. I have copied the Dump file below..

Loading Dump File [C:\Windows\Minidump\011113-22526-01 - Copy.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'ImagePath'
WARNING: Inaccessible path: 'SymbolPath'
Symbol search path is: SymbolPath
Executable search path is: ImagePath
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9200 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
Machine Name:
Kernel base = 0xfffff803`4746e000 PsLoadedModuleList = 0xfffff803`47738a80
Debug session time: Fri Jan 11 13:30:21.020 2013 (UTC - 8:00)
System Uptime: 0 days 23:23:03.729
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, fffff8801e1214c0, fffff8801e121418, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Lycosa.sys ( Lycosa+5510 )

Followup: MachineOwner
---------

 

[Tmagic650]

This is caused by the Razer Tarantula keyboard driver... Go here:
http://www.razersupport.com/
See if you can find a driver update

 

[casperX]

This is caused by the Razer Tarantula keyboard driver... Go here:
http://www.razersupport.com/
See if you can find a driver update

I do not understand how it can be the Razer Tarantula drivers since I do not have that. I think you ment lycosa? We have upgraded and downgraded those drivers so many times because it still messes up. I will update them again if they need it and then post a new crash report if it happens. Thanks!

 

[Tmagic650]

Lycosa.sys is a Razer keyboard driver. Did you ever have one attached to this computer? You can attach "cleaner" minidumps by going to C:\windows\minidump. Minidump files have a .dmp extension. Select all the .dmp files. Right-click and send them to a compressed(zipped)folder. Upload that folder as a file here...

 

[casperX]

Ok that's what I thought you ment. Ya I currently am using a Lycosa. I updated the drivers so now so if it crashes ill post the new dump file

 

[Tmagic650]

Okay, good...

 

[casperX]

Hey I apologize, apparently I already had the latest drivers installed when I posted this. 3.0.2 is the latest drivers on the razer support site. I just reinstalled the drivers themselves. Should this have fixed it or should I be expecting a crash again?

 

[Tmagic650]

"Should this have fixed it or should I be expecting a crash again?" Time will tell