Windows 7 Computer Freezes Randomly

writhziden said:

Just do your normal routine and see if the freezing stops; no need to run Verifier at this time. Corrupted keyboard or mouse drivers can cause freezes, so hopefully that was it. :)

Hopefully, Thank You VERY much. Ill report back if there's any problems.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042812-15756-01\042812-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309e650
Debug session time: Sat Apr 28 02:33:02.969 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:29.701
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 7777777700000148, fffffa800b123b30, fffff88006be3eb8}

Unable to load image 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+1eb8 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 7777777700000148, Handle value being referenced.
Arg3: fffffa800b123b30, Address of the current process.
Arg4: fffff88006be3eb8, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000335f3dc to fffff80002ed6c80

STACK_TEXT:  
fffff880`0a8cb518 fffff800`0335f3dc : 00000000`000000c4 00000000`000000f6 77777777`00000148 fffffa80`0b123b30 : nt!KeBugCheckEx
fffff880`0a8cb520 fffff800`03374ae4 : fffffa80`0b123b30 77777777`c0000022 fffffa80`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a8cb560 fffff800`0312d1f0 : 00000000`00000000 fffff880`0a8cb790 00000000`00000000 fffffa80`07affe00 : nt!VfCheckUserHandle+0x1b4
fffff880`0a8cb640 fffff800`031b00e5 : 00000202`00180000 00000000`00100000 00000000`00000000 fffff800`031b0000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a8cb710 fffff800`03374878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a8cb760 fffff880`06be3eb8 : fffff980`16df2ee0 00000000`00000002 fffffa80`07affe20 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a8cb7b0 fffff980`16df2ee0 : 00000000`00000002 fffffa80`07affe20 00000000`00000000 fffff880`06be7128 : Lycosa+0x1eb8
fffff880`0a8cb7b8 00000000`00000002 : fffffa80`07affe20 00000000`00000000 fffff880`06be7128 00000000`00000000 : 0xfffff980`16df2ee0
fffff880`0a8cb7c0 fffffa80`07affe20 : 00000000`00000000 fffff880`06be7128 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a8cb7c8 00000000`00000000 : fffff880`06be7128 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07affe20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+1eb8
fffff880`06be3eb8 89842498000000  mov     dword ptr [rsp+98h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+1eb8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c86fc86

FAILURE_BUCKET_ID:  X64_0xc4_f6_Lycosa+1eb8

BUCKET_ID:  X64_0xc4_f6_Lycosa+1eb8

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

Your crashes still indicate your keyboard. I would recommend trying a different keyboard to test whether the freezes are due to your current keyboard. Borrow one from a friend if you do not have a spare. Uninstall the current drivers before connecting another keyboard.


In the meantime, you could try to clean up your USB devices through Windows and reset the USB ports.

• Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
  
  1. Shut down and turn off the computer.
     
  2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
     
  3. "Remove the computer from any port replicator or docking station, disconnect
     cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
     
  4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
     power from components is drained to clear the software connections between the BIOS
     and hardware and clear any corruption in the temporary memory.
     
  5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
     and mouse should suffice and be the only peripherals reconnected.
     
  6. Turn it on to reinitialize the software connections between the BIOS and hardware
     

writhziden said:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042812-15756-01\042812-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309e650
Debug session time: Sat Apr 28 02:33:02.969 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:29.701
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 7777777700000148, fffffa800b123b30, fffff88006be3eb8}

Unable to load image 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+1eb8 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 7777777700000148, Handle value being referenced.
Arg3: fffffa800b123b30, Address of the current process.
Arg4: fffff88006be3eb8, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000335f3dc to fffff80002ed6c80

STACK_TEXT:  
fffff880`0a8cb518 fffff800`0335f3dc : 00000000`000000c4 00000000`000000f6 77777777`00000148 fffffa80`0b123b30 : nt!KeBugCheckEx
fffff880`0a8cb520 fffff800`03374ae4 : fffffa80`0b123b30 77777777`c0000022 fffffa80`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a8cb560 fffff800`0312d1f0 : 00000000`00000000 fffff880`0a8cb790 00000000`00000000 fffffa80`07affe00 : nt!VfCheckUserHandle+0x1b4
fffff880`0a8cb640 fffff800`031b00e5 : 00000202`00180000 00000000`00100000 00000000`00000000 fffff800`031b0000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a8cb710 fffff800`03374878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a8cb760 fffff880`06be3eb8 : fffff980`16df2ee0 00000000`00000002 fffffa80`07affe20 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a8cb7b0 fffff980`16df2ee0 : 00000000`00000002 fffffa80`07affe20 00000000`00000000 fffff880`06be7128 : Lycosa+0x1eb8
fffff880`0a8cb7b8 00000000`00000002 : fffffa80`07affe20 00000000`00000000 fffff880`06be7128 00000000`00000000 : 0xfffff980`16df2ee0
fffff880`0a8cb7c0 fffffa80`07affe20 : 00000000`00000000 fffff880`06be7128 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a8cb7c8 00000000`00000000 : fffff880`06be7128 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07affe20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+1eb8
fffff880`06be3eb8 89842498000000  mov     dword ptr [rsp+98h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+1eb8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c86fc86

FAILURE_BUCKET_ID:  X64_0xc4_f6_Lycosa+1eb8

BUCKET_ID:  X64_0xc4_f6_Lycosa+1eb8

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

Your crashes still indicate your keyboard. I would recommend trying a different keyboard to test whether the freezes are due to your current keyboard. Borrow one from a friend if you do not have a spare. Uninstall the current drivers before connecting another keyboard.


In the meantime, you could try to clean up your USB devices through Windows and reset the USB ports.

• Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
  
  1. Shut down and turn off the computer.
     
  2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
     
  3. "Remove the computer from any port replicator or docking station, disconnect
     cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
     
  4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
     power from components is drained to clear the software connections between the BIOS
     and hardware and clear any corruption in the temporary memory.
     
  5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
     and mouse should suffice and be the only peripherals reconnected.
     
  6. Turn it on to reinitialize the software connections between the BIOS and hardware
     

OK I have done everything you said, i switched keyboards, drained the power and i reset my USB ports. Now ill just wait and see if it crashes.

writhziden said:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042812-15756-01\042812-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309e650
Debug session time: Sat Apr 28 02:33:02.969 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:29.701
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 7777777700000148, fffffa800b123b30, fffff88006be3eb8}

Unable to load image 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+1eb8 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 7777777700000148, Handle value being referenced.
Arg3: fffffa800b123b30, Address of the current process.
Arg4: fffff88006be3eb8, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000335f3dc to fffff80002ed6c80

STACK_TEXT:  
fffff880`0a8cb518 fffff800`0335f3dc : 00000000`000000c4 00000000`000000f6 77777777`00000148 fffffa80`0b123b30 : nt!KeBugCheckEx
fffff880`0a8cb520 fffff800`03374ae4 : fffffa80`0b123b30 77777777`c0000022 fffffa80`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a8cb560 fffff800`0312d1f0 : 00000000`00000000 fffff880`0a8cb790 00000000`00000000 fffffa80`07affe00 : nt!VfCheckUserHandle+0x1b4
fffff880`0a8cb640 fffff800`031b00e5 : 00000202`00180000 00000000`00100000 00000000`00000000 fffff800`031b0000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a8cb710 fffff800`03374878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a8cb760 fffff880`06be3eb8 : fffff980`16df2ee0 00000000`00000002 fffffa80`07affe20 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a8cb7b0 fffff980`16df2ee0 : 00000000`00000002 fffffa80`07affe20 00000000`00000000 fffff880`06be7128 : Lycosa+0x1eb8
fffff880`0a8cb7b8 00000000`00000002 : fffffa80`07affe20 00000000`00000000 fffff880`06be7128 00000000`00000000 : 0xfffff980`16df2ee0
fffff880`0a8cb7c0 fffffa80`07affe20 : 00000000`00000000 fffff880`06be7128 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a8cb7c8 00000000`00000000 : fffff880`06be7128 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07affe20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+1eb8
fffff880`06be3eb8 89842498000000  mov     dword ptr [rsp+98h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+1eb8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c86fc86

FAILURE_BUCKET_ID:  X64_0xc4_f6_Lycosa+1eb8

BUCKET_ID:  X64_0xc4_f6_Lycosa+1eb8

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

Your crashes still indicate your keyboard. I would recommend trying a different keyboard to test whether the freezes are due to your current keyboard. Borrow one from a friend if you do not have a spare. Uninstall the current drivers before connecting another keyboard.


In the meantime, you could try to clean up your USB devices through Windows and reset the USB ports.

• Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
  
  1. Shut down and turn off the computer.
     
  2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
     
  3. "Remove the computer from any port replicator or docking station, disconnect
     cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
     
  4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
     power from components is drained to clear the software connections between the BIOS
     and hardware and clear any corruption in the temporary memory.
     
  5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
     and mouse should suffice and be the only peripherals reconnected.
     
  6. Turn it on to reinitialize the software connections between the BIOS and hardware
     

I was Writing Up a post to say that it froze again even though i changed keyboards and followed all your instructions when suddenly half way through it BSOD and i caught a glimpse of it and it said "adequate Disk Space" Heres the dump file, So now it makes me think, Maybe its the HDD?

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042912-33649-01\042912-33649-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`03054650
Debug session time: Sat Apr 28 22:24:16.000 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:58.343
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 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
---------

3: 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:
------------------


OVERLAPPED_MODULE: Address regions for 'WudfPf' and 'RtsUStor.sys' overlap

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6332313838646365
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e8467e to fffff80002e8cc50

STACK_TEXT:  
fffff880`02ffcb98 fffff800`02e8467e : ffffffff`ffffffff fffff880`02fd5180 fffff880`02ffd3a0 fffff800`02eb7c80 : nt!KeBugCheck
fffff880`02ffcba0 fffff800`02eb794d : fffff800`0309571c fffff800`02fd2078 fffff800`02e10000 fffff880`02ffd300 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffcbd0 fffff800`02eb6725 : fffff800`02fd5fac fffff880`02ffcc48 fffff880`02ffd300 fffff800`02e10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffcc00 fffff800`02eb9a16 : fffff880`02ffd300 fffff880`02ffd3a0 fffffa80`00000001 fffff880`03e16ef8 : nt!RtlDispatchException+0x415
fffff880`02ffd2e0 fffff800`02e46a9a : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0753f900 : nt!RtlRaiseStatus+0x4e
fffff880`02ffd880 fffff880`05f8dc23 : fffffa80`068fedc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff880`02ffd900 fffffa80`068fedc0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Lycosa+0x1c23
fffff880`02ffd908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000000 : 0xfffffa80`068fedc0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+1c23
fffff880`05f8dc23 ??              ???

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_0_Lycosa+1c23

BUCKET_ID:  X64_0x1E_0_Lycosa+1c23

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

The crash is still blaming the same driver for your other keyboard. Have you shown hidden USB/HID devices and uninstalled the driver?

In this case, you may have information that we do not, so it may be worth investigating the hard drive.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the Hitachi Drive Fitness Test to make sure the drive is not faulty. You may also want to run SeaTools short and long tests on the drive to double check.

writhziden said:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042912-33649-01\042912-33649-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`03054650
Debug session time: Sat Apr 28 22:24:16.000 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:58.343
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 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
---------

3: 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:
------------------


OVERLAPPED_MODULE: Address regions for 'WudfPf' and 'RtsUStor.sys' overlap

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6332313838646365
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e8467e to fffff80002e8cc50

STACK_TEXT:  
fffff880`02ffcb98 fffff800`02e8467e : ffffffff`ffffffff fffff880`02fd5180 fffff880`02ffd3a0 fffff800`02eb7c80 : nt!KeBugCheck
fffff880`02ffcba0 fffff800`02eb794d : fffff800`0309571c fffff800`02fd2078 fffff800`02e10000 fffff880`02ffd300 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffcbd0 fffff800`02eb6725 : fffff800`02fd5fac fffff880`02ffcc48 fffff880`02ffd300 fffff800`02e10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffcc00 fffff800`02eb9a16 : fffff880`02ffd300 fffff880`02ffd3a0 fffffa80`00000001 fffff880`03e16ef8 : nt!RtlDispatchException+0x415
fffff880`02ffd2e0 fffff800`02e46a9a : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0753f900 : nt!RtlRaiseStatus+0x4e
fffff880`02ffd880 fffff880`05f8dc23 : fffffa80`068fedc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff880`02ffd900 fffffa80`068fedc0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Lycosa+0x1c23
fffff880`02ffd908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000000 : 0xfffffa80`068fedc0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+1c23
fffff880`05f8dc23 ??              ???

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_0_Lycosa+1c23

BUCKET_ID:  X64_0x1E_0_Lycosa+1c23

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

The crash is still blaming the same driver for your other keyboard. Have you shown hidden USB/HID devices and uninstalled the driver?

In this case, you may have information that we do not, so it may be worth investigating the hard drive.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the Hitachi Drive Fitness Test to make sure the drive is not faulty. You may also want to run SeaTools short and long tests on the drive to double check.

OK i am 100% SURE that the driver is NOW uninstalled. I will report back with errors if any.

I also have 2 sound devices High Definition Audio Device and Realtek High Definition Audio. I Forgot To mention and its not a 1TB HDD its actually 2 500gb HDD. Again I dont know if this could be a problem or if this will contain the solution but, I just need this problem fixed its annoying the shit out of me so much.

I have this exact same problem, especially when I play League of Legends. I really hope you find a solution.