New
#21
Please follow the https://www.sevenforums.com/crashes-d...tructions.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.
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 Hardware - Stress Test With Prime95 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
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 SupportCode: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 ---------
- 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.
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.
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. :)