Windows 7 Computer Freezes Randomly

iMarioo · Apr 22, 2012

JMH said:
*Did you run a Full System Scan with Malwarebytes as requested?
Results?

* Re your past Anti Virus programs.
You may indeed have remnants of both McAfee & Norton still on your System that may be contributing to your current glitches / freezes.
Our recommendation is to use the appropriate Uninstall Tool to remove all traces of same.
Reboot after using each.

http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

* Run DiskCleanup
http://www.sevenforums.com/tutorials/818-disk-cleanup-open-use.html

* Repair Windows 7 System Files with System File Checker.{Option 2}
It may need to be run up to three times before successful.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

* Won't hurt to run CheckDisk so we can rule out corruption as much as possible.
How to Run Disk Check in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html

* Have you SP1 installed?

I Done EVERYTHING you said and yes i have Service Pack 1 Installed, And yet It STILL freezes. I dont understand what the problem could be. I have also uninstalled AVG and installed Microsoft Security Essentials.

writhziden · Apr 22, 2012

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the latest crash/freeze reports and logs. Those instructions help with more than just blue screens but also can help with determining causes of freezing.

iMarioo · Apr 24, 2012

writhziden said:
Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the latest crash/freeze reports and logs. Those instructions help with more than just blue screens but also can help with determining causes of freezing.

This Machine Came Pre-installed with Windows 7 Home Premium 64 Bit, but it was freezing so i Re-installed Windows 7 Ultimate hoping To Fix the problem But Not LucK

Windows 7 Ultimate
6GB DDR3 Ram
AMD Athlon II X4 610e Qaud Core Processor
1TB HDD
AMD Radeon 6570 1024MB

There Is The System Health Report and BSOD Dumps and System File Collector.

writhziden · Apr 24, 2012

Nothing to indicate the cause in terms of software, so it is likely hardware related. Run some hardware tests.

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing a CPU stress test using IntelBurnTest

iMarioo · Apr 27, 2012

writhziden said:
Nothing to indicate the cause in terms of software, so it is likely hardware related. Run some hardware tests.

If you are overclocking any hardware, please stop.

Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.

Real Temp is a good CPU temperature monitor.

Speccy - System Information - Free Download will monitor all hardware temperatures.

HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.

Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Follow the steps for doing a CPU stress test using IntelBurnTest

I Followed Everything you said, I wasn't overclocking so there was nothing to stop. The Tests ALL CAME back positive. There was no Problems with any of them AND im STILL freezing. I also went and redone verifier again twice. Here are the DMP files.

writhziden · Apr 27, 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042712-16411-01\042712-16411-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`02e50000 PsLoadedModuleList = 0xfffff800`03094650
Debug session time: Fri Apr 27 04:33:43.378 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:56.736
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 3535353500000148, fffffa800b5c0b30, fffff880066724c2}

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+14c2 )

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

0: 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: 3535353500000148, Handle value being referenced.
Arg3: fffffa800b5c0b30, Address of the current process.
Arg4: fffff880066724c2, 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 fffff800033553dc to fffff80002eccc80

STACK_TEXT:  
fffff880`0a6e5538 fffff800`033553dc : 00000000`000000c4 00000000`000000f6 35353535`00000148 fffffa80`0b5c0b30 : nt!KeBugCheckEx
fffff880`0a6e5540 fffff800`0336aae4 : fffffa80`0b5c0b30 35353535`c0000022 fffffa80`00000000 fffff880`0a6de000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a6e5580 fffff800`031231f0 : 00000000`00000000 fffff880`0a6e57b0 00000000`00000000 fffffa80`07be4900 : nt!VfCheckUserHandle+0x1b4
fffff880`0a6e5660 fffff800`031a60e5 : 00000000`00000000 00000000`00100000 00000000`00000000 fffff800`031a6000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a6e5730 fffff800`0336a878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a6e5780 fffff880`066724c2 : fffff980`13fbeee0 00000000`00000002 fffffa80`07be4990 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a6e57d0 fffff980`13fbeee0 : 00000000`00000002 fffffa80`07be4990 00000000`00000000 fffff880`06674828 : Lycosa+0x14c2
fffff880`0a6e57d8 00000000`00000002 : fffffa80`07be4990 00000000`00000000 fffff880`06674828 00000000`00000000 : 0xfffff980`13fbeee0
fffff880`0a6e57e0 fffffa80`07be4990 : 00000000`00000000 fffff880`06674828 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a6e57e8 00000000`00000000 : fffff880`06674828 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07be4990


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+14c2
fffff880`066724c2 89442478        mov     dword ptr [rsp+78h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+14c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac2e27e

FAILURE_BUCKET_ID:  X64_0xc4_f6_Lycosa+14c2

BUCKET_ID:  X64_0xc4_f6_Lycosa+14c2

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

Appears to be related to your Razer Tarantula Keyboard Driver which is corrupted. Disable Verifier for now. Try re-installing the driver for the keyboard. First, download the latest driver for the keyboard from the keyboard site: Razer Support

Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand Keyboards
Right click the Razer Keyboard
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device and hit OK
Restart your computer
Install the downloaded driver for the keyboard device.

Alternatively:

Login as an adminstrative user.
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand Keyboards
Right click the Razer Keyboard
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device and hit OK
Restart your computer
Install the downloaded driver for the keyboard device.

iMarioo · Apr 27, 2012

writhziden said:

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\iMarioo\042712-16411-01\042712-16411-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`02e50000 PsLoadedModuleList = 0xfffff800`03094650
Debug session time: Fri Apr 27 04:33:43.378 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:56.736
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 3535353500000148, fffffa800b5c0b30, fffff880066724c2}

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+14c2 )

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

0: 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: 3535353500000148, Handle value being referenced.
Arg3: fffffa800b5c0b30, Address of the current process.
Arg4: fffff880066724c2, 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 fffff800033553dc to fffff80002eccc80

STACK_TEXT:  
fffff880`0a6e5538 fffff800`033553dc : 00000000`000000c4 00000000`000000f6 35353535`00000148 fffffa80`0b5c0b30 : nt!KeBugCheckEx
fffff880`0a6e5540 fffff800`0336aae4 : fffffa80`0b5c0b30 35353535`c0000022 fffffa80`00000000 fffff880`0a6de000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a6e5580 fffff800`031231f0 : 00000000`00000000 fffff880`0a6e57b0 00000000`00000000 fffffa80`07be4900 : nt!VfCheckUserHandle+0x1b4
fffff880`0a6e5660 fffff800`031a60e5 : 00000000`00000000 00000000`00100000 00000000`00000000 fffff800`031a6000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a6e5730 fffff800`0336a878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a6e5780 fffff880`066724c2 : fffff980`13fbeee0 00000000`00000002 fffffa80`07be4990 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a6e57d0 fffff980`13fbeee0 : 00000000`00000002 fffffa80`07be4990 00000000`00000000 fffff880`06674828 : Lycosa+0x14c2
fffff880`0a6e57d8 00000000`00000002 : fffffa80`07be4990 00000000`00000000 fffff880`06674828 00000000`00000000 : 0xfffff980`13fbeee0
fffff880`0a6e57e0 fffffa80`07be4990 : 00000000`00000000 fffff880`06674828 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a6e57e8 00000000`00000000 : fffff880`06674828 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07be4990


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+14c2
fffff880`066724c2 89442478        mov     dword ptr [rsp+78h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+14c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac2e27e

FAILURE_BUCKET_ID:  X64_0xc4_f6_Lycosa+14c2

BUCKET_ID:  X64_0xc4_f6_Lycosa+14c2

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

Appears to be related to your Razer Tarantula Keyboard Driver which is corrupted. Disable Verifier for now. Try re-installing the driver for the keyboard. First, download the latest driver for the keyboard from the keyboard site: Razer Support

Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand Keyboards
Right click the Razer Keyboard
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device and hit OK
Restart your computer
Install the downloaded driver for the keyboard device.

Alternatively:

Login as an adminstrative user.
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand Keyboards
Right click the Razer Keyboard
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device and hit OK
Restart your computer
Install the downloaded driver for the keyboard device.

When i expand the keyboard section its not there? Instead Its in Human Interface Devices.

writhziden · Apr 27, 2012

That's fine and not entirely unexpected. Most keyboards show up under the keyboards devices, but those that have extra functionality will show up as HIDs. The steps I laid out are the same, just expand HIDs instead of Keyboards.

iMarioo · Apr 27, 2012

writhziden said:
That's fine and not entirely unexpected. Most keyboards show up under the keyboards devices, but those that have extra functionality will show up as HIDs. The steps I laid out are the same, just expand HIDs instead of Keyboards.

Thought So, So i completed that task done everything re-installed correct driver. Now Do i just wait to see if it freezes again or should i run Verifier to test it?

writhziden · Apr 27, 2012

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.

iMarioo · Apr 28, 2012

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.

iMarioo · Apr 28, 2012

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.

It Happened Again. I froze whilst watching a Youtube Video.

*EDIT*

Here are MORE DMP files.

writhziden · Apr 28, 2012

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 http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html 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

iMarioo · Apr 28, 2012

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 http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html 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.

iMarioo · Apr 29, 2012

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 http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html 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?

writhziden · Apr 29, 2012

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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
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.

iMarioo · Apr 29, 2012

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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
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.

iMarioo · Apr 29, 2012

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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
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.

It froze Again, I even uninstalled the driver for my keyboard.\

Chkdsk Log

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
364800 file records processed. File verification completed.
644 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
456964 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
364800 file SDs/SIDs processed. Cleaning up 3575 unused index entries from index $SII of file 0x9.
Cleaning up 3575 unused index entries from index $SDH of file 0x9.
Cleaning up 3575 unused security descriptors.
Security descriptor verification completed.
46083 data files processed. CHKDSK is verifying Usn Journal...
36027344 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

479110143 KB total disk space.
146482404 KB in 231147 files.
139656 KB in 46084 indexes.
0 KB in bad sectors.
485827 KB in use by the system.
65536 KB occupied by the log file.
332002256 KB available on disk.

4096 bytes in each allocation unit.
119777535 total allocation units on disk.
83000564 allocation units available on disk.

Internal Info:
00 91 05 00 f9 3a 04 00 c8 9e 07 00 00 00 00 00 .....:..........
a5 9b 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

*EDIT*

I guess this problem is unsolvable, Verifier Doesnt BSOD anymore at least.

iMarioo · Apr 29, 2012

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.

Dorian182 · Apr 29, 2012

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

Windows 7 Computer Freezes Randomly

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer