Sign in with
Sign up | Sign in
Your question

Frequent Computer Freezes on homebuilt system. Help?

Last response: in Systems
Share
January 27, 2013 6:27:57 PM

Hello. I need help determining the problem with my computer. Before I get too far into my issues, here is my system build:

http://pcpartpicker.com/p/zV9d


Basically, here is the issue. My computer has been frequently either freezing up while I am using it (in which case, it is typically when I am watching a video on Youtube, and then the Audio freaks out, but it isn't always during that), or when it is in sleep mode and is inactive (in which case, when them monitor goes to sleep in activity, the monitor won't come back on because it isn't getting a signal, but my computer is on and it sounds like it is still working). I'm not sure where the problem lies, so I thought I would hand it over for you guys to help me. My suspicions lies with either my Video Card or my motherboard itself. I suspected the video card because my monitor would sometimes would get color squares on it, lock up, go black, come back on, and I got a bubble that the kernel of my driver has crashed. I tried updating my video card, but I don't think it helped, even though the colored square recovery issue has pretty much resolved, the freezing up of my computer issue has not.

Below, in the spoiler, are error messages / dump that WhoCrashed has picked up. Perhaps this can help you guys:
Quote:
System Information (local)
--------------------------------------------------------------------------------

computer name: SUPERCOMPUTER
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8477773824 total
VM: 2147352576, free: 1965785088




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 1/11/2013 5:23:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011013-27518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800B4B5200, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 1/11/2013 5:23:40 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1B39C9)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800B4B5200, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 310.70
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 310.70
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 310.70 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_VERIFIER_DETECTED_VIOLATION



On Tue 1/8/2013 5:23:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010713-16395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800AA45B60, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 11/8/2012 7:19:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110812-14898-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/2/2012 5:56:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110212-15943-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/2/2012 12:38:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-17378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Thanks for all and any help guys! I am willing to provide more information if needed. Everything to my knowledge is at its latest update, though I can confirm if needed.

EDIT: quick things I forgot to add. One, my computer uses the HDD for Windows currently. It is my primary driver. The issue is present on both drivers when windows files are on them, so I don't think that is what causes it. Additionally, this is not a recent problem, but an ongoing one that has been happening over several months.
January 27, 2013 7:52:45 PM

Crashes and freezes can either be hardware related or software related.

Are you overclocking? If so what are your temps? What is the overclock?

If not overclocking it is most likely the software. Sleep mode is a known problems with windows and I wouldn't use it.

I would question the quality of your windows install. Try a windows repair and see what you get.
January 27, 2013 8:18:14 PM




My friends set the overclocking stats for me. If they need to be fixed up, just let me know what to do.

I will disable sleep mode now, and then do a windows repair as well.
January 27, 2013 8:23:10 PM

jackattack923 said:
http://i.imgur.com/gdEkmip.png
http://i.imgur.com/dzkRHej.png

My friends set the overclocking stats for me. If they need to be fixed up, just let me know what to do.

I will disable sleep mode now, and then do a windows repair as well.


Don't bother with the windows repair. When you have an overclock that gives you stability issues you need to back down. Start again at default and see if your problems go away. Then increase the overclock slowly and see if you have issues. Once the issues return go back to the highest overclock that you have no problems.
!