Quantcast

Maximum PC

It is currently Sat May 25, 2013 6:54 am

All times are UTC - 8 hours




Post new topic Reply to topic  [ 52 posts ]  Go to page 1, 2, 3  Next
Author Message
 Post subject: First Build - Constant Crashing
PostPosted: Mon Dec 26, 2011 12:17 pm 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
Hi guys, I have recently decided to build a gaming computer for myself for the first time. On Sat 10th Dec my parts all arrived and I put the comp together, installed windows ect. Since then I have been having a ton of problems when playing games. When I'm playing games such as Empire: Total War, Starcraft 2, Shogun 2, Just Cause 2, the screen will go black/dark blue and the audio will loop, then the computer will either restart itself or I will have to hard reset it by holding down the on/off button on the front of my case. I have completely no idea as to what could be causing the problem. I have tried downloading and installing Catalyst 11.11, 11.5 and the newest 11.12. I've contacted AMD Support and their support hasn't been great, the best thing they have done is shown me how to uninstall all my drivers properly, which I have done and reinstalled the latest catalyst to no avail. I have also tried re-installing Windows, updated my BIOS to the latest version and downloaded the latest chipset driver. I'm completely stumped on what the problem could be. Sometimes I get a "The AMD Display Driver has stopped responding and has recovered successfully" message. Any help would be greatly appreciated, I've tried posting on other forums but have got no replies. I can attach my DxDiag and MSINFO if needed. I also did a clean re-install of Windows 7 on the 23rd.

My system specs are;

Spoiler: show
AMD FX-4100 Quad Core Processor @ 3.6GHz
Powercolor Radeon 6870 1GB
8GB Corsair DDR3 RAM
320GB Samsung SpinPoint HDD
ASUS M5A78L-MLX m-ATX Motherboard
OCZ Fatal1ty 750W Power Supply


I have tried running Memtest86, I ran two tests and it came out fine. I also then tried Windows Memory Diagnostics Tool, which also came out fine with zero errors. I've also ran Furmark at 1920x1080 (FS), the scores are below in the spoiler.

Spoiler: show
AA:0 samples. My score was 1689 points (28FPS, 60000 ms) Max GPU Temp: 70degrees C. FPS: Min: 29, max: 30, avg: 28.
Renderer : AMD Radeon HD 6870
Drivers: Catalyst 11.12 - 8.92.111109a-129966C-ATI (11-9-2011)
Clocks: core: 900MHz, mem:1050MHz
CPU: AMD FX™-4100 Quad Core Processor
CPU Speed: 3616MHz
System Memory: 8174MB
OS: Windows 7 64-bit build 7601 [Service Pack 1]


I have also ran Prime95 for 4hours, the temps throughout the testing are below in the spoiler

Spoiler: show
Test started at 10.02, finished at 14.02
10:10:
CPU : 34C min 37C Max
HDD : 26C min 27C Max
GFX : 31C Min 37C Max
10.30:
Temps remained same as above.
11.00:
Temps remained same as above.
12:00
CPU : 33min 40max
HDD : 25min 28Max
GPU ; 31min 56max
12.30:
Temps stayed same
1.00:
CPU : 33min 40max
HDD : 25min 29max
GPU : 31min 57max
1.30:
Temps remained same as above.
2.00:
Temps remained same as above. All temps are in degrees C


Whenever I try run Shogun 2, I blue screen, I know I do this because Windows makes the computer reboot. Once I log back on, I get a "Windows has recovered from an unexpected shutdown" error message. I then used Windows Debugging Tools to check the .dmp file it referred to in the error message. The result for the error message is below in the spoiler.

Spoiler: show
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007e8a8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031a85b0 fffff800`02d1fc59 : fffffa80`07e8a8d0 fffffa80`06a91040 00000000`00000011 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8ad0 fffff800`02bfff57 : fffffa80`07e8a8d0 fffff800`02c7a2b8 fffffa80`06a91040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8b00 fffff800`02b675d5 : fffff800`02cdbae0 00000000`00000001 fffffa80`07eeca40 fffffa80`06a91040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8b40 fffff800`02ae4001 : fffff880`010cfe00 fffff800`02b675b0 fffffa80`06a91000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8b70 fffff800`02d74fee : 00000000`00000000 fffffa80`06a91040 00000000`00000080 fffffa80`069f4040 : nt!ExpWorkerThread+0x111
fffff880`031a8c00 fffff800`02acb5e6 : fffff880`02f65180 fffffa80`06a91040 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8c40 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037ed400 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner


I then tried using BlueScreenViewer at the recommendation of someone on another forum I have posted on. (I'm not sure if I'm allowed to post the link to it, so I haven't.) The results from BlueScreenViewer for all 10 of my .dmp files are below in the spoiler.

Spoiler: show
==================================================
Dump File : 122411-16395-01.dmp
Crash Time : 24/12/2011 00:21:24
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e7c038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122411-16395-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-18376-01.dmp
Crash Time : 23/12/2011 23:26:50
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e0e038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-18376-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-17518-01.dmp
Crash Time : 23/12/2011 21:32:36
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e8a8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-17518-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-17612-01.dmp
Crash Time : 23/12/2011 19:33:42
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07dcd038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-17612-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-19219-01.dmp
Crash Time : 23/12/2011 15:59:46
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e0d038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-19219-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-19656-01.dmp
Crash Time : 23/12/2011 15:56:16
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e25038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-19656-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-22963-01.dmp
Crash Time : 23/12/2011 14:55:16
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07b268f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-22963-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-18236-01.dmp
Crash Time : 23/12/2011 14:27:34
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07dbc038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : crashdmp.sys
Caused By Address : crashdmp.sys+1b3c5f0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-18236-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-17206-01.dmp
Crash Time : 23/12/2011 14:23:49
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e4c178
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-17206-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-22261-01.dmp
Crash Time : 23/12/2011 09:34:14
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e518f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
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+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-22261-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================


All but one of the .dmp files refer to ntoskrnl.exe as the problem. However I don't know how to fix that driver if it is the cause.

Any help would be a godsend. Thanks for reading this all.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 10:57 am 
Thoroughbred
Thoroughbred
User avatar

Joined: Sat May 07, 2011 12:30 pm
Posts: 1922
Location: A place not actively occupied by something else.
The exe you are having trouble with is not a driver, it is the main kernel, the little bit that makes the computer run. I personally would suggest a full reinstall, because it appears that an important system file is acting up.
The one error report that does not refer to ntoskrnl.exe seems to be the file dump program dying.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 11:22 am 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
noghiri_x wrote:
The exe you are having trouble with is not a driver, it is the main kernel, the little bit that makes the computer run. I personally would suggest a full reinstall, because it appears that an important system file is acting up.
The one error report that does not refer to ntoskrnl.exe seems to be the file dump program dying.


I've reinstalled Windows twice, I'm RMA'ing the processor tomorrow.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 11:31 am 
Team Member
Team Member
User avatar

Joined: Sat Apr 21, 2007 6:57 am
Posts: 1061
Looks to me like a bad video card driver or video card. Do you have another card to try, or can you return the current card that you have and try a new/different one?

Did you install the latest chipset drivers for your motherboard?
When you removed the video drivers did you use driver sweeper to make sure that you got rid of all the old drivers?


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 11:34 am 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
nsvander wrote:
Looks to me like a bad video card driver or video card. Do you have another card to try, or can you return the current card that you have and try a new/different one?

Did you install the latest chipset drivers for your motherboard?
When you removed the video drivers did you use driver sweeper to make sure that you got rid of all the old drivers?


I didn't use driversweeper because I read on AMD forums that driver cleaners can mess up Windows registry files. I followed the steps AMD told me on how to fully remove the drivers and I did that. Then I re-installed 11.12 and I still crashed. I have the latest BIOS and Chipset driver for my motherboard and I still crash.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 12:01 pm 
Willamette
Willamette

Joined: Thu Aug 12, 2004 9:04 am
Posts: 1015
I see that your card has 2 6-pin auxiliary power connectors on it, and that your OCZ PSU has three +12v rails, each of which are rated at a maximum current capacity of 18A. It could be a power-balancing issue that is a result of these two factors. Do you have a spare PSU (or can you borrow one to swap out the OCZ PSU) that has a single +12V rail on it (I see that the minimum PSU requirement for the video card is 500W) that you can use to test this theory?





=


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 12:03 pm 
Million Club - 2 Plus
Million Club - 2 Plus

Joined: Thu Aug 02, 2007 11:07 pm
Posts: 2622
Location: NC
Don't list to noghiri_x, he's a noob and actually thinks that OS's are built upon popcorn.

As listed by the OP, he did a clean install of win7 64 bit and all drivers/chipset/firware/bios updated. Unfortunately, any failures with the ntoskrnl program generally comes back as a some form of OS corruption caused by an unknown hardware failure, which is like a general fault code for the OS. Lots of reasons that could do this, but with your specs and specific problem its most likely an actual hardware problem and not a driver or firmware issue.

I'm going to bet my money on the gpu is bad, a few others have had the exact same issue that you describe when using the 6870 and a friend of mine is having hard rebooting issues after putting his 6870 last week as well. He just submitted his RMA today, but to note, putting his old 9800 back in the system and it's rock solid.

You can test this theory by running Furmark to test the load of the gpu. If it fails then it's probably the gpu. Then try to take the gpu completely out of the system and use the onboard radeon 3000, but since its an old design, it might not be able to run furmark; try running an old game like Team Fortress 2. It won't stress the onboard too much but should see if your system is stable to open up a graphics app if anything is actually a firmware/driver issue. If you have another video card laying around, you could try that instead.

Another note is that the same error code comes up with people having issues with a failed cpu under load, but since it passed prime95 and memtest86, that's discounted.

The only other issue could be with the motherboard itself. Unless its something simple as forgetting to plug in the two 6pin 12v connectors on the card... but it couldn't be that... could it? (I've had 1 or 2 friends forget this step)


Oh and see if disabling async crossfire hybrid helps in the driver. I had to do this on my A6 AMD laptop to get the discrete to work properly.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Wed Dec 28, 2011 3:37 pm 
Thoroughbred
Thoroughbred
User avatar

Joined: Sat May 07, 2011 12:30 pm
Posts: 1922
Location: A place not actively occupied by something else.
No jbaz, everyone knows they are built on asparagus. :wink:
My reasoning for the reinstall was because installation of new drivers on top of the old ones can cause major problems, ones that sometimes are fixed with nv's solution (drive sweeper).


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Thu Dec 29, 2011 2:14 am 
Million Club - 2 Plus
Million Club - 2 Plus

Joined: Thu Aug 02, 2007 11:07 pm
Posts: 2622
Location: NC
Quote:
I have also tried re-installing Windows,

your said resolution has been nixed


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Thu Dec 29, 2011 9:00 am 
Thoroughbred
Thoroughbred
User avatar

Joined: Sat May 07, 2011 12:30 pm
Posts: 1922
Location: A place not actively occupied by something else.
JBaz wrote:
Quote:
I have also tried re-installing Windows,

your said resolution has been nixed

Didn't see that.
Also, double check the contacts in the PCI-e slot are clean. dust in the contacts will cause all sorts of problems, such as not booting and other problems. I managed to fry two GPUs before I used canned air to clean the thing, and then everything worked fine. The 5450s didn't work, but my old 210 did just fine. After cleaning, everything worked.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 3:25 pm 
Coppermine
Coppermine
User avatar

Joined: Thu Apr 16, 2009 1:45 pm
Posts: 610
Location: Richmond, Va.
At 18a on the rails, you are a bit short. I wouldn't begin to use todays cards with less than 25a on the rails. Yeah, 18a will run the card, but when things start ramping up in the graphics dept., you are going to come up short with the resulting headaches as you will not have enough.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 3:39 pm 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
I dont have another graphics card/computer which I can switch with. I've had laptops for the past 5 or so years. The only desktop I have is one I got in 2006.

So it could possibly be a problem with my power supply? I dont understand how though because it says that it is optimized for SLI so surely it should provide enough power two cards at a minimum?

I'll RMA the graphics card if once I get my processor back it turns out that I still have the crashing.

All of my parts were delivered on the 9th Dec so I dont think dust is an issue as the parts are only just hitting their 1month mark.

If it is the power supply rail like you've suggested, how would I go about fixing that? New power supply?

Thank you all for the replies.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 3:59 pm 
Million Club - 2 Plus
Million Club - 2 Plus

Joined: Thu Aug 02, 2007 11:07 pm
Posts: 2622
Location: NC
coastie65 wrote:
At 18a on the rails, you are a bit short. I wouldn't begin to use todays cards with less than 25a on the rails. Yeah, 18a will run the card, but when things start ramping up in the graphics dept., you are going to come up short with the resulting headaches as you will not have enough.

Short?!? WTF really? That's per rail and there's four for a max of 216w per rail although his psu only allows for 650w on the 12v's. More than enough to power one lonely 127w 6870. Even then, most high end cards are going to have 2 or maybe 3 12v rails so it really doesn't matter if its 18a.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 4:18 pm 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
So PSU is out of the question then?

Like I've said, my processor arrived at Ebuyer (guys I bought all my parts off) on Friday so I'll probably have it back by Thursday at the latest. If it turns out that I still get crashes, what would be the next probable cause? A friend of mine seems to think its either the graphics card or the processor, which is an idea I'm leaning towards agreeing with.

I dont think its the RAM as I've ran memtest for 5hours without a single hiccup. I also dont think its the HDD as if it was then I would be BSOD'ing when not running games as well. The only other thing I can think of is the motherboard, but after speaking with the tech guys at Ebuyer, they told me that a mobo would only cause BSOD's if it is a bad socket - Which is also something I dont think is the problem because if it was then I would also be BSOD'ing when not in game too?

It's just gone midnight here so Happy New Year guys :)


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 5:13 pm 
Thoroughbred
Thoroughbred
User avatar

Joined: Sat May 07, 2011 12:30 pm
Posts: 1922
Location: A place not actively occupied by something else.
A mobo can also bsod with blown caps and other problems.
You're right about the HDD, though, and the GPU, but I'd hesitate to point a finger at the processor unless you overclocked it, and even then, being able to do P95 for 4 hours should show that it's probably not the CPU, as it stresses the part more than a game usually would.

EDIT: CPU, not PSU.


Last edited by noghiri_x on Sat Dec 31, 2011 6:10 pm, edited 1 time in total.

Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 5:20 pm 
Million Club - 2 Plus
Million Club - 2 Plus

Joined: Thu Aug 02, 2007 11:07 pm
Posts: 2622
Location: NC
it shouldn't be cpu since you stress tested it and the temps look good.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 5:25 pm 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
So would you guys suggest its the GPU/Mobo?


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 6:14 pm 
Thoroughbred
Thoroughbred
User avatar

Joined: Sat May 07, 2011 12:30 pm
Posts: 1922
Location: A place not actively occupied by something else.
Joey129 wrote:
So would you guys suggest its the GPU/Mobo?

Not the mobo, that would bsod on other things, too. It seems to only bsod on GPU-intensive stuff, so it's either the GPU or (debatably) the PSU.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Sat Dec 31, 2011 6:23 pm 
Million Club - 2 Plus
Million Club - 2 Plus

Joined: Thu Aug 02, 2007 11:07 pm
Posts: 2622
Location: NC
try more cpu intensive stress tests, still could be it. Others with FX cpu's have noted similar constant gaming crashes was due to the cpu and not the gpu even though they booted up just fine.


Top
  Profile  
 
 Post subject: Re: First Build - Constant Crashing
PostPosted: Tue Jan 03, 2012 9:54 am 
8086
8086

Joined: Mon Dec 26, 2011 10:10 am
Posts: 25
Ok so I just got an email back from Ebuyer saying my processor is fine. Next on the list to RMA is Graphics card, what do you guys think?


Top
  Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 52 posts ]  Go to page 1, 2, 3  Next

All times are UTC - 8 hours


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group