New
#31
Ok I tried that:
Ok I tried that:
Well froze again, so it seems that the firmware update and the bios update didn't manage to solve the problem. Neither did the intel drivers that came with the motherboard. Nothing relevant in the event viewer other than the problems I've already posted.
One thing I have noticed though is that if the reset button works I tend to get a crash dump. If it doesn't then nothing. At the moment I'm going to try a different sata port for the ssd to see if that has any effect.
With the 101 bugchecks, I would start recommending some stress tests of the components:
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
Is the system overclocked at all?
Golden, its not overclocked in any way. I'll have a look at the thread you posted.
As Golden said, it is a stop 0x101 BSOD. Your post #19.
Can you post it following the Blue Screen of Death (BSOD) Posting Instructions ?
I've uploaded the file Arc.
OK, let us do some changes here:
Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.
- Right click on "my computer" icon and click "manage" on the context menu.
- It will open the "computer management" window.
- Select "Device Manager" in the left pane, It will list all the existing devices up.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, uninstall.
- Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
- Now restart the computer. At restart, windows will auto configure the appropriate native system driver.
Make it sure that the 250GB Samsung SSD 840 EVO is running with the latest firmware.
Samsung SSD (Solid State Drive) 840 series | Samsung SSD Website
Open the computer. Make it sure that both the HDD and SSD is properly seated. Re-seat the sata and power cables. If possible, change them and replace with known good cables.
The latest BIOS version available is F11 (the installed one is F9), though that is old, too. Better you install it from GIGABYTE - Motherboard - Socket 1156 - GA-H55M-UD2H (rev. 1.0)
Install the NVIDIA DRIVERS 314.22WHQL only.
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).- Now follow Drivers - Clean Left over Files after Uninstalling
- Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
Update your network drivers:
- Drivers for Atheros AR9285 and Windows 7
- Realtek : Win7 and WinServer 2008 R2 Driver
Follow Driver Install - Device Manager to install the drivers.
Finally, when ataport.sys is failing, it may be a rootkit infection with all the other possible alternatives. So better take no chance. Scan the system for possible virus infection with the following programs.
Let us know the results. Will decide out further course of action depending on the results.
_______________________________________________________________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff880009e8180, 1} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009e8180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffff880`031a0d78 fffff800`02edea4a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx fffff880`031a0d80 fffff800`02e916f7 : 00000000`00000000 fffff800`00000001 00000000`000186a1 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`031a0e10 fffff800`03401895 : fffff800`03427460 fffff880`031a0fc0 fffff800`03427460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`031a0f10 fffff800`02e84113 : fffff800`03002e80 00000000`00000001 00000000`00000000 fffff800`02e6e8ba : hal!HalpHpetClockInterrupt+0x8d fffff880`031a0f40 fffff800`02e5c93f : fffff880`02f64180 fffffa80`06729b50 01cef6ef`3f3f33db fffffa80`06801048 : nt!KiInterruptDispatchNoLock+0x163 fffff880`031a10d0 fffff800`0314434f : 00000000`00000000 fffff880`031a1700 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b fffff880`031a1140 fffff800`03192956 : fffff8a0`142b60a8 00000000`0001ff58 fffff880`031a12d0 00000000`00000000 : nt!ExpGetProcessInformation+0x7f fffff880`031a1290 fffff800`031933ad : fffff8a0`142b60a8 fffffa80`6365734b 00000000`00000000 fffff880`031a1c20 : nt!ExpQuerySystemInformation+0xfb4 fffff880`031a1640 fffff800`02e86e53 : fffff880`031a1710 fffff800`02e85dfd 00000000`00000001 fffff8a0`142b6000 : nt!NtQuerySystemInformation+0x4d fffff880`031a1680 fffff800`02e83410 : fffff880`014761dc fffff880`0a72b005 fffff880`031a1844 00000000`0c4100a1 : nt!KiSystemServiceCopyEnd+0x13 fffff880`031a1818 fffff880`014761dc : fffff880`0a72b005 fffff880`031a1844 00000000`0c4100a1 00000000`00000000 : nt!KiServiceLinkage fffff880`031a1820 fffff880`0147673d : fffffa80`06d93db0 fffff800`02e8f1e3 fffff880`20206f49 fffff880`031a1bf0 : cng!GatherRandomKey+0x22c fffff880`031a1be0 fffff800`0317e1ed : 00000000`00000001 00000000`00000001 00000000`80000000 fffffa80`06729b50 : cng!scavengingWorkItemRoutine+0x3d fffff880`031a1c80 fffff800`02e91261 : fffff800`00000000 fffff800`00000001 fffff800`02e40200 fffff800`00000000 : nt!IopProcessWorkItem+0x3d fffff880`031a1cb0 fffff800`031242ea : 00000000`00000000 fffffa80`06729b50 00000000`00000080 fffffa80`06707040 : nt!ExpWorkerThread+0x111 fffff880`031a1d40 fffff800`02e788e6 : fffff880`02f64180 fffffa80`06729b50 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a19e0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
Arc - I already posted that I updated the firmware of the ssd and am running the latest version of the bios earlier. These haven't solved the issue.
As for the intel rapid storage, this isn't the cause of the problem. Previously I ran the ssd with windows own drivers and I still got random freezes. I only installed intel rapid storage in the hope that it may solve the problem. It hasn't.
As for the sata cable and power cable to the ssd, yes I have checked these numerous times. I also checked the RAM to make sure it has not become unseated.
I run Microsoft security essentials which I believe is pretty comprehensive when comes to viruses etc. This is updated regularly and I am careful about what I install on my PC so I don't think it's a virus or root kit.
@Golden - I ran hot cpu tester 4 last night and that tested the cpu for 6 hours under high loads, there were no errors. I try running the other stress tests when I have time.
It appears that you know what the issue is. Goo :) Do it then.
I dont know. Nobody knows, for a stop 0x101. We can search in possible areas, but cannot pinpoint the issue.
Troubleshooting will not go with your thinking, at any chance.
Sorry for consuming your time in vein. I dont have a fix button.