Computer hard locks -

[meuqsaco]

Hello,

I thought my issues were solved, but I was wrong. Before I tell what the problem is, here are the specs:

CPU: Intel I7 2600
GPU: EVGA GTX 570
Memory: 2x4gb Kingston Hyperx 1600 mhz
Mobo: Asus P8P67 PRO
Power Supply: FSP Aurum Gold 700
Audio: Onboard

My computer freezes during gaming, when iddle in Windows, when installing Windows and even inside BIOS(latest version). It can happen 5 times in 30 minutes or once every 12 hours. This computer is 7 months old, and I believe after 2-3 months the freezing started. At start it would freeze maybe once ever 3 days or so. Then it started freezing almost daily and now it freezes 1-7 times a day.

- So far, I've tried switching my GTX 570 for 2 other weaker cards and the freezing continued.

- Then I tried both sticks of RAM separately and on different slots. I even tried another monitor, as I had visual problems because of a bad HDMI cable, in the past. This also did not work. Also, my memory is set to run at a lower frequency and voltage(1333mhz/1.5v). This is automatically set by the mobo, altough the memory has a XMP profile to run at 1600mhz and 1.65V. Both configurations did not work.

- I cleaned my entire case and all it's components of dust(barely had any) and reseated every component and replugged every cable twice.

- I've run several 15 minutes sessions of furmark. This did not cause any artifacts or shutdowns.

- I've run memtest(boot version) several times. I've seen at least 20 passes so far, altough not sequential and not a single error.

- I've run Prime95 for over 8 hours. This did return a error on one of the workers, saying "rounding was 0.5 expected less than 0.4". The error occurred after 7 hours.

- I've run CHKDSK and it did not return a single bad sector.

- In any of the previous steps, my computer did freeze at least once, but the pattern makes me believe the following:
1 - It is not memory because memtest did not return a single error after 20 or so passes. Also, if it was memory, it would probably be a single stick of it and not both of them at the same time.
2 - It is not the power supply because my system would most likely shutdown or restart and my motherboard would also most likely beep telling my there is not enough power. Additionally, this is a very good power supply and I've monitored the voltages and they are all correct with barely any percentage of fluctuation.
3 - It is not the GPU. Running furmark for several sessions without artifacts or shutdowns and also trying different GPUs on different slots did not seize the freezing.
4 - It is not temperature. The case is very well ventilated and the temps of every component is below the average reported by the manufacturers.
5 - It is not software. I had most recent drivers for everything inside my computer and it still froze. Stock drivers that were running fine during the first months of my PC also did not work. Reinstalling Windows did not work. The biggest proof though is that it froze inside BIOS.
6 - It is not the Hard Disk. The proof is that it froze inside BIOS, with the HD cables unplugged.

I believe the issue is either the motherboard or the CPU, most likely the first. I don't think there is anything else to do, as I have no spare mobo or CPU to test. I'm thinking of buying a new motherboard, but before that, I wanted to know what is everyone's opinion about this and if there is something else that can solve the problem.

Thank you

 

[askavatar]

Well, RAM would have been my first guess, but you seem to have covered that pretty well. I would lean more towards the motherboard before the processor, I can't remember the last time I had a problem with an Intel processor. I have had many ASUS mobo problems recently, a lot of the symptoms that you report, in addition to BIOS being screwed up (the screen is askew when in BIOS, totally strange, and ASUS unsuccessfully tried to repair it, hellooooo Intel Motherboard).

 

[meuqsaco]

Yeah, I also think it's the motherboard. I talked to an Asus engineer and he thinks the motherboard is the cause. I've never even heard of an Intel processor causing issues. It's quality is incredible.

Unfortunally I moved to Brazil and will stay here for 2 years and Asus refuses to approve an RMA, even after I stated that I will pay shipping both ways. I am never buying an Asus product again as it sold me a bad product and does not want to put any effort to help me. I already selected the MSI P67A-C45 ATX to replace it.

 

[writhziden]

Could be the motherboard or CPU, could also still be memory if it is incompatible with the motherboard. Sometimes that will not show up through Memtest86+. In case Memtest86+ missed anything, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. This you may want to run overnight since it takes a long time to complete (run an hour before bed and check before going to sleep that it is still running).

You may also try the following steps.
Note: backup any files if you are using a RAID controller of any kind.
1. Go into your BIOS and load default settings to clear the CMOS memory (this will reset your RAID configuration resulting in loss of data, so if you have RAID and want to proceed from step 3, that is fine).
2. Save Settings and exit the BIOS.
3. Shut down and turn off the computer.
4. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
5. Hold down the power button for 30 seconds to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory. This closes the circuit and ensures all power from components is drained.
6. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall.
7. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back your results.

 

[meuqsaco]

Could be the motherboard or CPU, could also still be memory if it is incompatible with the motherboard. Sometimes that will not show up through Memtest86+. In case Memtest86+ missed anything, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. This you may want to run overnight since it takes a long time to complete (run an hour before bed and check before going to sleep that it is still running).

You may also try the following steps.
Note: backup any files if you are using a RAID controller of any kind.
1. Go into your BIOS and load default settings to clear the CMOS memory (this will reset your RAID configuration resulting in loss of data, so if you have RAID and want to proceed from step 3, that is fine).
2. Save Settings and exit the BIOS.
3. Shut down and turn off the computer.
4. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
5. Hold down the power button for 30 seconds to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory. This closes the circuit and ensures all power from components is drained.
6. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall.
7. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back your results.

Thanks, but I already did all that. Windows memory diagnostic tool takes too long to get a single pass though, and the computer always freezes before it can finish.

 

[writhziden]

Did you try resetting the BIOS and its software connections? Same problem?

 

[meuqsaco]

Yeah, I tried. I just turned off bluetooth and other unused controller on the BIOS. Also something about CPU4 and CPU reports, but told me it solved for them. So far it hasn't crashed, bu it's been 2 hours

 

[writhziden]

Yeah, I tried. I just turned off bluetooth and other unused controller on the BIOS. Also something about CPU4 and CPU reports, but told me it solved for them. So far it hasn't crashed, bu it's been 2 hours

That sounds like a motherboard/cpu problem, most likely the motherboard since CPU failure is rare. It's too bad you cannot RMA it to narrow down possible problems. Have you tried re-seating components (including the CPU) in the motherboard? Careful, things may be hot. Make sure you re-apply any thermal paste before putting heat sinks back, too. Also, have you made sure all components have power linkages in the correct place and the power plugs are securely connected?

If you do anything with the computer internals, make sure you follow good electrostatic discharge safety techniques. Keep yourself grounded. Before you open the case up, turn the computer off, unplug the power, hold down the power button for 30 seconds to close the circuit and drain all residual power (for your safety as well as for the components). Then it is safe to open the case.

 

[meuqsaco]

Yeah, I tried re seating and I did use thermal paste. So far after my last changes, I haven't had any freeze issue. I'm shooting myself in the feet by saying this, but I hope it keeps going like this.

 

[writhziden]

Keep us posted. Best wishes!

 

[meuqsaco]

Yeah, almost half a day and no freezing. It's beating the record so far. It looks like it solved. I'll wait at least a couple days and if it is solved, I'll return the mobo I ordered and let you guys know which options helped me with the freezing

 

[meuqsaco]

So I got a BSOD today, but this time it did not freeze like all other times. The minidump was saved. I believe the freezing issue is solved and this is related to something else. My memory was in it's XMP profile so I set it back to stock(1333mhz, 1.5v). I believe this was the problem, but just in case, could someone take a look at the minidump and see what triggered it?

Thank you!

 

[writhziden]

While your .dmp file is informative, it is not the best information for helping with crashing/freezing problems. If you follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, it provides us with more information than just the .dmp file. The information may be helpful if you continue to have problems so we know more about your system and can determine possible conflicts, application errors, system errors, etc. existing on the system.

Your blue screen crash (seen below) was due to Stop 0x101, and may be resolved using http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html. It may be the RAM, as you said, but there are other possibilities outlined in that thread by usasma, who is one of the best hardware debuggers on here.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\meuqsaco\012112-15163-01\012112-15163-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe70
Debug session time: Sat Jan 21 08:24:06.373 2012 (UTC - 7:00)
System Uptime: 0 days 1:16:52.294
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880032f9180, 6}

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880032f9180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0a2e1498 fffff800`02e70463 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`032f9180 : nt!KeBugCheckEx
fffff880`0a2e14a0 fffff800`02ecac87 : 00000000`00000000 fffff800`00000006 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`0a2e1530 fffff800`02e13895 : fffff800`02e38460 fffff880`0a2e16e0 fffff800`02e38460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a2e1630 fffff800`02ebeab3 : 00000000`83cfc1fa fffff800`0303ce80 00000000`00001000 fffff800`02ff6bfe : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a2e1660 fffff800`02ef3621 : 00000003`00000000 fffffa80`00000000 00000000`00000001 c5f00001`83ac3025 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a2e17f0 fffff800`02ef5cc9 : 00000000`00000000 00000000`0bd90fff fffff880`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x7d8
fffff880`0a2e19b0 fffff800`031d8050 : fffffa80`06a31160 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0a2e1ad0 fffff800`031d845b : 00000980`00000000 00000000`0bd90000 fffffa80`00000001 00000000`0fe2eb01 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0a2e1b90 fffff800`02ec1813 : 00000000`00000000 00000000`77081a75 fffffa80`06838060 fffffa80`0c767900 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a2e1be0 00000000`7762f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0fe2e208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7762f95a


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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

 

[meuqsaco]

While your .dmp file is informative, it is not the best information for helping with crashing/freezing problems. If you follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, it provides us with more information than just the .dmp file. The information may be helpful if you continue to have problems so we know more about your system and can determine possible conflicts, application errors, system errors, etc. existing on the system.

Your blue screen crash (seen below) was due to Stop 0x101, and may be resolved using http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html. It may be the RAM, as you said, but there are other possibilities outlined in that thread by usasma, who is one of the best hardware debuggers on here.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\meuqsaco\012112-15163-01\012112-15163-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe70
Debug session time: Sat Jan 21 08:24:06.373 2012 (UTC - 7:00)
System Uptime: 0 days 1:16:52.294
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880032f9180, 6}

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880032f9180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0a2e1498 fffff800`02e70463 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`032f9180 : nt!KeBugCheckEx
fffff880`0a2e14a0 fffff800`02ecac87 : 00000000`00000000 fffff800`00000006 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`0a2e1530 fffff800`02e13895 : fffff800`02e38460 fffff880`0a2e16e0 fffff800`02e38460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a2e1630 fffff800`02ebeab3 : 00000000`83cfc1fa fffff800`0303ce80 00000000`00001000 fffff800`02ff6bfe : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a2e1660 fffff800`02ef3621 : 00000003`00000000 fffffa80`00000000 00000000`00000001 c5f00001`83ac3025 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a2e17f0 fffff800`02ef5cc9 : 00000000`00000000 00000000`0bd90fff fffff880`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x7d8
fffff880`0a2e19b0 fffff800`031d8050 : fffffa80`06a31160 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0a2e1ad0 fffff800`031d845b : 00000980`00000000 00000000`0bd90000 fffffa80`00000001 00000000`0fe2eb01 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0a2e1b90 fffff800`02ec1813 : 00000000`00000000 00000000`77081a75 fffffa80`06838060 fffffa80`0c767900 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a2e1be0 00000000`7762f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0fe2e208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7762f95a


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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

Thanks, I'll get more info of my system as you said and read the topic.

 

[writhziden]

Thanks, I'll get more info of my system as you said and read the topic.

You are welcome. Let us know how things go with the tests (in the linked thread) if you run them.

 

[meuqsaco]

The pc froze 3 times just now, damn. I read the topic and people say it is most likely the CPU that causes it. Forget the minidump. My new mobo just arrived and I installed everything and formatted windows with updated drivers. I am now going to test it and if it freezes, then I will return the mobo and contact Intel to request an RMA.

 

[writhziden]

The pc froze 3 times just now, damn. I read the topic and people say it is most likely the CPU that causes it. Forget the minidump. My new mobo just arrived and I installed everything and formatted windows with updated drivers. I am now going to test it and if it freezes, then I will return the mobo and contact Intel to request an RMA.

Probably a good troubleshooting step to see if it is the CPU. Is your RAM compatible with the new board?

 

[meuqsaco]

The pc froze 3 times just now, damn. I read the topic and people say it is most likely the CPU that causes it. Forget the minidump. My new mobo just arrived and I installed everything and formatted windows with updated drivers. I am now going to test it and if it freezes, then I will return the mobo and contact Intel to request an RMA.

Probably a good troubleshooting step to see if it is the CPU. Is your RAM compatible with the new board?

Yeah, it is. I've checked the compatibility list of manufacturer(MSI). If it is not the mobo, it must be the CPU. Anyway, I'll keep doing my tests and update you guys about the results. Maybe someone else is having this issue.

 

[writhziden]

Yeah, it is. I've checked the compatibility list of manufacturer(MSI). If it is not the mobo, it must be the CPU. Anyway, I'll keep doing my tests and update you guys about the results. Maybe someone else is having this issue.

Appreciate that you are thinking of fellow users with similar issues. Good luck!

 

[meuqsaco]

One thing I noticed is that the GPU temprature is higher on this board. I'm not sure how the mobo could affect it, maybe the size of the heatsink? On the Asus mobo, the one close to the GPU is bigger.