Sign in with
Sign up | Sign in
Your question

Cant run my cpu at full power (stock) without getting blue screen

Last response: in CPUs
Share
February 3, 2013 12:35:51 PM

I can only run my FX 8350 at 3400 mhz via the catalyst control center, if I try to run at 4000 mhz (full power stock) my computer blue screens. What am I doing wrong?
February 3, 2013 1:13:30 PM

It may be caused by overheating or overspeed protection in the BIOS
February 5, 2013 6:47:08 PM

cant find a way to adjust that in the bios...any other possibilitys?
Related resources
a b à CPUs
April 12, 2013 5:40:00 PM

Download HWMonitor, CPU-Z and maybe CoreTemp.

These programs will monitor cou usage, activity and temperatures.
Run anything demanding benchmark (game, intel burn in etc.) and monitor the above. Keep an eye on the temps in particular.

If at full load it only goes up to 3.4 Ghz, then there;s something wrong. I suspect you are manually adjusting the clock when it is not needed (i.e. increasing clocks when the CPU is idle.)

Hope this helps. :) 
April 12, 2013 6:44:46 PM

If you are running AMD's software to overclock in Windows take the software off, it is trash.

Enter BIOS and slowly bump up the speed manually, enter Windows and check to see if it is stable. If so, re-boot and bump the speed up a little more. Remember to increase voltage a little at around 3.8GHz, and slightly use more aggressive settings on the CPU MOSFITs, VTT and so on. Drop RAM speed or increase RAM timing a little with each step past 3.7GHz, just to make sure RAM is not the problem.

Once everything is stable at 4GHz enter BIOS and slowly increase RAM speed and reduce timing - slowly, entering Windows and check stability; do this until you are at the rated RAM speed.
April 13, 2013 9:48:29 AM

I haven't adjusted any clocks, or even really tampered with the bios( because Im a newb) and Im not using any overclock software, really im just trying to get it to run full power out of the box . I did a bench mark test and it will run 4020, when I adjust it to full power in the catalyst control center. But if I leave it at full power it becomes unstable. Usually when I am gaming, that does it the fastest and it will blue screen after a short time. when I adjust it to 3/4 power in the catalyst control center it is stable. I just can't seem to get it stable at full power.
April 13, 2013 9:38:02 PM

Your case is probably too hot inside and/or the fan on your video card is running too slow. If you have an AMD HD 5000 series or newer, you can easily preset video card fan speeds.

Download and install HWMonitor to check temperatures, among other things. Get the free version here:
http://www.cpuid.com/downloads/hwmonitor/1.21-setup.exe

I forgot to ask what you are using for video, sorry. Please tell me what you use for video.
April 14, 2013 6:31:24 AM

I'm running one gtx 680
April 14, 2013 6:45:05 PM

Got it,now what do I do with it?
a b à CPUs
April 15, 2013 11:49:23 AM

Ok people, simple question here: Why is the system crashing? Find that out BEFORE you try and solve the issue.

Download BluescreenView, and report the Bug_Check_Strings (Should be all caps, something like MEMORY_MANAGEMENT or VIDEO_TDR_ERROR). That should give a good idea where the problem lies.
April 15, 2013 6:51:51 PM

all kinds of other info but the bug check string is blank
a b à CPUs
April 16, 2013 4:46:49 AM

joshua44 said:
all kinds of other info but the bug check string is blank


...not promising. How about the Bug_Check_Code (Something like: 0x0000001A)? You can derive the Bug Check String from that.
April 16, 2013 5:07:28 AM

One possibility is that your powersupply is not giving out enough power. What powersupply are you using?
April 16, 2013 2:42:10 PM

Bug string check code: 0x00000101
April 16, 2013 2:42:58 PM

Power supply 850 watt thermaltake
a b à CPUs
April 17, 2013 5:20:41 AM

joshua44 said:
Bug string check code: 0x00000101


Quote:
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT

The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.


This is a rare one. The only time I've ever seen this thrown is an underpowered CPU, or overheating. You generally get some other BSOD if its some other hardware problem.

So I'd check temps, voltages, and the like. If everything checks out, PSU/Motherboard are the most likely culprits.
!