Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Windows 7 Computer Freezes Randomly

27 Apr 2012   #31
iMarioo

Windows 7 Home Premium 64-Bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
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.


My System SpecsSystem Spec
.
28 Apr 2012   #32
iMarioo

Windows 7 Home Premium 64-Bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
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.
My System SpecsSystem Spec
28 Apr 2012   #33
writhziden

Windows 7 Home Premium 64 Bit
 
 

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
My System SpecsSystem Spec
.

28 Apr 2012   #34
iMarioo

Windows 7 Home Premium 64-Bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
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.
My System SpecsSystem Spec
28 Apr 2012   #35
iMarioo

Windows 7 Home Premium 64-Bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
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?
My System SpecsSystem Spec
28 Apr 2012   #36
writhziden

Windows 7 Home Premium 64 Bit
 
 

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.
My System SpecsSystem Spec
28 Apr 2012   #37
iMarioo

Windows 7 Home Premium 64-Bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
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.
My System SpecsSystem Spec
29 Apr 2012   #38
iMarioo

Windows 7 Home Premium 64-Bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
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.
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.
My System SpecsSystem Spec
29 Apr 2012   #39
iMarioo

Windows 7 Home Premium 64-Bit
 
 

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.
My System SpecsSystem Spec
29 Apr 2012   #40
Dorian182

Windows 7 Home Premium 64bit
 
 

I have this exact same problem, especially when I play League of Legends. I really hope you find a solution.
My System SpecsSystem Spec
Closed Thread

 Windows 7 Computer Freezes Randomly




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Computer Randomly Freezes
So for the past month or so my computer has been periodically freezing, sometimes half an hour after start up and other times it can be fine for a full day of use. The freezing leaves my computer in a fully unresponsive state (pressing caps locks on my keyboard does not light up the LED) and the...
General Discussion
Windows 7: Windows 7 Computer Freezes Randomly
Hello, Ive been searching for a problem thats bothered me for quiet a while and i just cant seem to fix it, My problem is that when im using my computer it will randomly freeze whether im watching youtube videos, browsing the net or just playing games (Starcraft 2, League of Legends) My music...
General Discussion
Computer freezes randomly
First time posting here...over the last couple of days my computer randomly freezes and i have to force reboot it happens at random...so i checked the event viewer and it said The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding,...
BSOD Help and Support
Hard drive light stays on and computer freezes randomly in windows 7
I am little bit worried about my harddrive. Previously I had 80 gb harddrive and then I upgraded it to 320 gb. I have dell latitude d630 laptop with two operating system. Windows 7 and XP. When I use Windows 7 then my computer specially hard drive light stays on and mouse is busy and I have to...
General Discussion
Hard drive light stays on and computer freezes randomly in windows 7
I am little bit worried about my harddrive. Previously I had 80 gb harddrive and then I upgraded it to 320 gb. I have dell latitude d630 laptop with two operating system. Windows 7 and XP. When I use Windows 7 then my computer specially hard drive light stays on and mouse is busy and I have to...
Hardware & Devices
Computer freezes randomly
Hey! I created this account and posted this thread because I've encountered a disturbing problem on my expensive gaming/school laptop that drastically affects my life. I am currently unable to work on assignments on my own computer or enjoy games because it freezes completely sporadically...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:01.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App