BSOD due to overclock?

apone2000

apone2000

apone2000

Associate
Joined
28 Apr 2011
Posts
14
Hi,

I have just got some new components and rebuilt my PC (Windows 7 home premium 64bit).

I am having problems with is blue screening though, and not sure if it is because its an overclocked problem or something else, the dump analysis didnt show and specific driver issues.

It can do it at random times - i.e. no when under load. Sometimes it will do it when using MS Word, sometimes when Im not at the pc. If I run Prime95 for 2-3 hours it works fine (albeit at 75degrees), but none of the crashes have occured under and more then 5% cpu load. I have just put it down to 4.5 from 4.6 to see if it helps at all. Idle and low usage temps are 35-37degrees.

I have also been through each driver and made sure each is updated to the lates. It has crashed about 6-7 times yesterday, only 2 dumps though as it didnt store the first 4 as I had virtual memory off (by default it took 12gb for hibernate and 12gig swap file off my nice new 120gb SSD, so I disabled both to get free space back!)

Windows is patched to all the latest patches, including SP1

The spec is:

Asus P8P67 Intel P67
i7 2600K 3.40GHz @ 4.50GHz
A50 Cooler
Corsair XMS3 16GB (4x4GB) DDR3 PC3-12800C9 1600MHz
OCZ Vertex 3 120GB 2.5" SATA-3 Solid State Hard Drive (VTX3-25SAT3-120G)
Coolermaster Silent Pro Gold 700W Power Supply
Western Digital Caviar Black 750GB SATA 6Gb/s 64MB Cache - OEM (WD7502AAEX)
ATI Radeon HD 5850 (not overclocked)

The 2 dump files are at:
http://www.megaupload.com/?d=DHP41ITF
http://www.megaupload.com/?d=OB6ZH31Q

Output from windbg:
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

Any help apprediated!

Regards,
Graham
 
took the overclock off at about 10am this morning, and so far its been running prime95 all day with no issues, 55degree temp too.

I took the overclock off using the "optimized profile" on the motherboard, with the overclockers shipped one still saved in the oc profiles.

As the overclocked BSOD occus when there is not high load, but can handle 3hrs of oc95 fine, does that help point to what values need tweaking, is it likely to just be a voltage thing or just querk of overclocking and could be one of a number of values? I only understand the basics of overclocking so bought one of the overclockers bundles, but happy navigating around the bios to chnge values, or is it best just to call the support line when they are next open to walk through changing settings?
 
Sounds like needs a little bit more juice try overclocking using off set voltages

I had same problem turns out there was not enough volts going through the chip at 1600 but will prime away for hours

Personally if it primes for an hour it's stable enough for me I have never used a programme or game yet that loads the CPU 100% for any lenth of time

Post your bios settings for the overclock see if can tweak ya settings
 
Last edited:
Think these are the main settings, let me know if there are any other specific ones.

Turbo by all cores @46
Internal PLL overvoltage Enabled
CPU Manual 1.35v
CPU PLL 1.9v
CPU Spread Spectrum disables
Lode-line calibration extreme
VRM Frequency Manual
VRM Fixed Freq 400
Phase Control Extreme
Duty Control T.Probe
CPU Current Capability 120%
CPU C1E/C3/C6 Auto
Speedstep Enabled

Couple of CPUID and core temp shots when idle and at load
http://www.megaupload.com/?d=SNYQC53B

http://www.megaupload.com/?d=UBKY8XDR
 
I think the BSOD error you are getting is #124, meaning that you need to play with your vcore/vtt. I had the same issue with that board. The problem is small ffts / Lynx / IBT are not effective for testing Sandy (at least in my experience). The only true way to test these chips IMO is Prime Blend. I think if your 4hrs stable then you shouldn't get any BSOD when not under load.
 
Last edited:
Thanks for the links, some interesting bits in there!

I have upped my core voltage s smidge, and gone to 4.5 rather than 4.6 to see if that stabalises. If it does then I might go back up to 4.6 and tweak a couple of other settings they have in there too.

strangely now with a higher core voltage cpuid shows the core speed at 4500 always, even though the bios shows speedstep is enabled, not sure if after a certain voltage it always sticks at the higher core speed. My original problem was when it was not at the max speed by at 1600mhz, so not sure if I have done something else now to remove speedstep!
 
apone2000 said:
Thanks for the links, some interesting bits in there!

I have upped my core voltage s smidge, and gone to 4.5 rather than 4.6 to see if that stabalises. If it does then I might go back up to 4.6 and tweak a couple of other settings they have in there too.

strangely now with a higher core voltage cpuid shows the core speed at 4500 always, even though the bios shows speedstep is enabled, not sure if after a certain voltage it always sticks at the higher core speed. My original problem was when it was not at the max speed by at 1600mhz, so not sure if I have done something else now to remove speedstep!
Click to expand...

No, no matter how high your voltage if you have speedstep enabled, it should always reduce your clock down to 16*100.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom