Look forward to some pics and how you think the rig performs.
are these units compatiable?
#31
Posted 29 February 2012 - 04:11 PM
Look forward to some pics and how you think the rig performs.
#32
Posted 01 March 2012 - 04:52 PM
#33
Posted 04 March 2012 - 03:58 PM
#34
Posted 05 March 2012 - 07:45 PM
im thinking of installing a water cooler for my cpu. thoughts?
Not something I would use.
"Why not go with a liquid-cooling CPU Cooler, such as the Corsair H100?
There are a few reasons not to go with a liquid-cooling CPU Cooler:
- Similar cooling performance, but with a much higher noise level, compared to high-end air CPU coolers.
- Higher cost ($110 for Corsair H100 vs ~$90 for high-end air CPU Cooler)
- More possible points of failure (pump, tubing and fans vs only fans)
- Risk of a leak, which can damage many other components!
In the end, a high-end air CPU Cooler is less likely to fail, cannot possibly leak liquid/damage other components, offers similar cooling performance with less noise and costs less." source, Hardware RevolutioN.
What are your temps like when gaming?
Remember that where a CPU is provided with a stock cooler and you change it for an after-market one, you void the warranty, so you do so at your own risk.
#35
Posted 06 March 2012 - 08:51 PM
#36
Posted 08 March 2012 - 02:25 AM
Please download SpeedFan. Run the program and post a screenshot of the results.
http://www.almico.com/sfdownload.php
On your next post, use full Editor.
How to take a screenshot.
Click on the ALT key + PRT SCR key..its on the top row....now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload...
then after typing in any response you have... click on browse...desktop...find the screenshot..select it and click on the upload button...then on the lower left...after it says upload successful...click on add reply like you normally would.
<br style="color: rgb(13, 41, 117); font-size: 13px; line-height: 19px; text-align: left; background-color: rgb(242, 242, 242); "><br style="color: rgb(13, 41, 117); font-size: 13px; line-height: 19px; text-align: left; background-color: rgb(242, 242, 242); ">Screenshot instructions courtesy of
happyrock
Edited by iammykyl, 08 March 2012 - 03:14 PM.
#37
Posted 09 March 2012 - 04:30 AM
#38
Posted 09 March 2012 - 02:36 PM
#39
Posted 10 March 2012 - 02:52 PM
#40
Posted 10 March 2012 - 07:07 PM
See if we can find out why your are getting BSOD issues.
Can you remember what you were doing when the problem surfaced?
Go to the following page, scroll down to Crash Analysis, download, Who Crashed, install and run. http://www.resplendence.com/downloads
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashedbefore clicking Finish
Click Analyze
It will want to download the Debugger and install it Say YesWhoCrashed
will create report but you have to scroll down to see it
Copy and paste it into your next replyDownload
BlueScreenViewNo installation required.
Double click on
BlueScreenView.exe file to run the program.When scanning is done, go
Edit>Select AllGo
File>Save Selected Items, and save the report as BSOD.txt.Open
BSOD.txtin Notepad, copy all content, and paste it into your next reply.
Edited by iammykyl, 10 March 2012 - 07:26 PM.
#41
Posted 11 March 2012 - 11:23 PM
--------------------------------------------------------------------------------
computer name: ALLEN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8497143808 total
VM: 2147352576, free: 1983483904
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 3/12/2012 3:24:26 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x124 (0x0, 0xFFFFFA800AA4E028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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: Unknown .
Google query: Unknown WHEA_UNCORRECTABLE_ERROR
On Sun 3/11/2012 10:42:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031112-5460-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800AA3C028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 3/9/2012 8:32:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030912-4617-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 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 which cannot be identified at this time.
On Thu 3/8/2012 8:25:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-4524-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80001ED7C40)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800AA0E028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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: Unknown .
Google query: Unknown WHEA_UNCORRECTABLE_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
unknown
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
#42
Posted 11 March 2012 - 11:28 PM
Dump File : 031112-5460-01.dmp
Crash Time : 3/11/2012 3:43:21 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0aa3c028
Parameter 3 : 00000000`be200000
Parameter 4 : 00000000`0005110a
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031112-5460-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266,288
==================================================
==================================================
Dump File : 030912-4617-01.dmp
Crash Time : 3/9/2012 1:33:15 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000031
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`009c0180
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030912-4617-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
==================================================
Dump File : 030812-4524-01.dmp
Crash Time : 3/8/2012 1:26:56 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0aa0e028
Parameter 3 : 00000000`be200000
Parameter 4 : 00000000`0005110a
Caused By Driver : Unknown_Module_00000000`00000000
Caused By Address : Unknown_Module_00000000`00000000+124
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030812-4524-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
#43
Posted 12 March 2012 - 11:54 PM
Thanks for the info.
Indications are, 2 software problems and 1 hardware problem.
Can you remember what you were doing when you received the BS, gaming, browsing, playing music?
Have you added new hardware like headphones?
Did you have any external hardware plugged in, like HDD?
Did you recently update any drivers.
Have you made any alteration in the BIOS?
Have you over-clocked the PC in any way?
-------------------------------------------------------------------------------
Go to device manager,
Check the box , show hidden device.
If any flags, copy and paste into your next post.
Have a look at this page, then look in action centre to see any information.
http://www.vikitech....rotect-computer
Are there any actions to take?
#44
Posted 13 March 2012 - 03:11 AM
#45
Posted 13 March 2012 - 03:43 AM
Please keep going from
Did you recently update any drivers.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users