Overclock.net › Forums › Intel › Intel CPUs › OC Help
New Posts  All Forums:Forum Nav:

OC Help - Page 7

post #61 of 72
Thread Starter 
Given all of your OC success. I think I got a bad chip in terms of overclockability frown.gif
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
post #62 of 72
Thread Starter 
I hunted down the .dmp file from my 5ghz/1.5v bsod
Here is the text in it's entirety:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\010812-8080-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03259e70
Debug session time: Sun Jan 8 22:56:19.905 2012 (UTC - 8:00)
System Uptime: 0 days 2:51:02.170
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880035d5180, 3}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe

Followup: MachineOwner

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880035d5180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

Debugging Details:

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff8000301c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0817bfd8 fffff800`0303a463 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`035d5180 : nt+0x705c0
fffff880`0817bfe0 00000000`00000101 : 00000000`00000031 00000000`00000000 fffff880`035d5180 00000000`00000003 : nt+0x1e463
fffff880`0817bfe8 00000000`00000031 : 00000000`00000000 fffff880`035d5180 00000000`00000003 fffff900`c1f144e0 : 0x101
fffff880`0817bff0 00000000`00000000 : fffff880`035d5180 00000000`00000003 fffff900`c1f144e0 00000003`00000000 : 0x31


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
post #63 of 72
Just call me Mr.comingintothethreadwithnorealusefulinfobutthis.

I am only stable at 4.8GHZ using 1.48-1.49 volts. Which is kind of ridiculous for 4.8GHZ but oh well.
post #64 of 72
The rounding error could be the RAM, try loosening the timings.

If it is the vcore then i just suggest trying 4.8 or 4.9. As said before 5.0Ghz requires a lot of juice and 1.5v is already over the limit without a proper WC set-up imo.
Keith.
(15 items)
 
Janet.
(13 items)
 
My PC.
(4 photos)
CPUMotherboardGraphicsRAM
Intel Core i7 2600K [5.0GHz@1.45v] Asus Maximus IV Extreme EVGA GTX 680 Classified 16GB Corsair Vengeance Red 1600Mhz 9-9-9-24 
Hard DriveHard DriveHard DriveCooling
60GB Corsair Force Series 3 SSD 160GB Samsung 7200RPM 1TB Samsung 7200RPM Corsair H100 
OSMonitorMonitorKeyboard
Windows 7 Professional 64Bit 27" Acer S273HLAbmii 19" Samsung SyncMaster 943SN Logitech diNovo Edge 
PowerCaseMouse
Antec High Current Gamer 900W Coolermaster HAF 932 Logitech G300 
CPUMotherboardGraphicsRAM
AMD Phenom II X4 965 @ 4.21Ghz ASUS M4A87TD/USB3 NVIDIA GeForce GTX 460 768MB Corsair 4x2GB DDR3 1333Mhz 
Hard DriveOSMonitorPower
Samsung 160GB, Samsung 1TB Windows 7 Ultimate 64Bit Samsung SyncMaster 943SN Corsair TX650W 
  hide details  
Reply
Keith.
(15 items)
 
Janet.
(13 items)
 
My PC.
(4 photos)
CPUMotherboardGraphicsRAM
Intel Core i7 2600K [5.0GHz@1.45v] Asus Maximus IV Extreme EVGA GTX 680 Classified 16GB Corsair Vengeance Red 1600Mhz 9-9-9-24 
Hard DriveHard DriveHard DriveCooling
60GB Corsair Force Series 3 SSD 160GB Samsung 7200RPM 1TB Samsung 7200RPM Corsair H100 
OSMonitorMonitorKeyboard
Windows 7 Professional 64Bit 27" Acer S273HLAbmii 19" Samsung SyncMaster 943SN Logitech diNovo Edge 
PowerCaseMouse
Antec High Current Gamer 900W Coolermaster HAF 932 Logitech G300 
CPUMotherboardGraphicsRAM
AMD Phenom II X4 965 @ 4.21Ghz ASUS M4A87TD/USB3 NVIDIA GeForce GTX 460 768MB Corsair 4x2GB DDR3 1333Mhz 
Hard DriveOSMonitorPower
Samsung 160GB, Samsung 1TB Windows 7 Ultimate 64Bit Samsung SyncMaster 943SN Corsair TX650W 
  hide details  
Reply
post #65 of 72
Thread Starter 
So my RAM's too crappy to handle 4.8ghz...
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
post #66 of 72
Thread Starter 
I loosened timings to 9-10-9-27. Is that a little drastic, or is that good? I was about to go 1.5v on the CPU...
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
post #67 of 72
Thread Starter 
I'm running 4.8 right now.
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
post #68 of 72
Thread Starter 
Loosened RAM timings, got illegal sumouts on core 1 and rounding errors on the rest...HELP my parts are absolute crap!
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
post #69 of 72

You need to bring the VCCIO back down below 1.2v. What is your ram voltage? Set VCCIO within .5v of your ram voltage. So if you have 1.65v ram set to 1.15v vccio.

 

Your parts are not crap BTW. It is just that your chip is kinda meh. 

 

 

Leave your ram alone and set them to stock values.

 

Change your LLC to very high

Leave VCCIO at .5v from DRAM voltage (DRAM at 1.65v, set VCCIO to 1.15v)

Try pulling your PLL down to 1.7v 

Set Phase Control to Extreme

Duty Control to T.Probe

VRM frequency to 350

 

 

 

Now start bumping the mutli till you cannot boot then upt he voltage till you can. Stop when either voltages or temps get out of hand (keep below 1.45v for 24/7 in my book).

 

 

If you cannot go any higher than tough luck.

 


Edited by Lord Xeb - 1/12/12 at 8:10pm
 
Gsvlip Dudyrm
(15 items)
 
Oda'maksv
(9 items)
 
CPUMotherboardGraphicsRAM
3770k @ 4.5 1.312 load Zotac Z77 ITX Wifi GTX 1070 Gaming 2126/2249 w/ Hybrid cooler TridentX 16GB 2400MHz 
Hard DriveHard DriveCoolingCooling
Samsung 850 Pro 1TB Seagate 2TB H105 EVGA Hybrid GPU cooler 
OSMonitorKeyboardPower
Windows 10 Asus MG279Q - 24" 144Hz 1080p Filco Majestic II w/ Cherry Reds Seasonic X 760W 
CaseMouseMouse PadAudio
Bitfelix Prodigy Logitech G400 Razer Goliath AKG A701 
AudioAudio
JDS Labs Objective 2 JDS Labs ODAC 
CPUMotherboardGraphicsRAM
Core i5 750 3.99 (190x21) 1.376v Load ASUS P7P55d-E Pro GTX 670 FTW <- Poor overclocker :( 8GB (4x2GB) G.Skill DDR3 1600 
Hard DriveHard DriveOptical DriveOS
Samsung 830 Evo 128GB 2x 2TB  Some DVD drive OSX 10.10.4 
MonitorPowerCaseMouse
Asus 1080P Crap TX 750 HAF 922 G400s 
Mouse PadOther
Apple Keyboard Xbox One controler 
CPURAMHard DriveHard Drive
C2D 2,26GHz under volted @ .978v 8GB  Crucial M4 64GB SSD 500GB Scorpio Black 
OSMonitorKeyboardMouse
OS X 10.0 1280x800 Built-in Trackpad 
Audio
Built-in 
  hide details  
Reply
 
Gsvlip Dudyrm
(15 items)
 
Oda'maksv
(9 items)
 
CPUMotherboardGraphicsRAM
3770k @ 4.5 1.312 load Zotac Z77 ITX Wifi GTX 1070 Gaming 2126/2249 w/ Hybrid cooler TridentX 16GB 2400MHz 
Hard DriveHard DriveCoolingCooling
Samsung 850 Pro 1TB Seagate 2TB H105 EVGA Hybrid GPU cooler 
OSMonitorKeyboardPower
Windows 10 Asus MG279Q - 24" 144Hz 1080p Filco Majestic II w/ Cherry Reds Seasonic X 760W 
CaseMouseMouse PadAudio
Bitfelix Prodigy Logitech G400 Razer Goliath AKG A701 
AudioAudio
JDS Labs Objective 2 JDS Labs ODAC 
CPUMotherboardGraphicsRAM
Core i5 750 3.99 (190x21) 1.376v Load ASUS P7P55d-E Pro GTX 670 FTW <- Poor overclocker :( 8GB (4x2GB) G.Skill DDR3 1600 
Hard DriveHard DriveOptical DriveOS
Samsung 830 Evo 128GB 2x 2TB  Some DVD drive OSX 10.10.4 
MonitorPowerCaseMouse
Asus 1080P Crap TX 750 HAF 922 G400s 
Mouse PadOther
Apple Keyboard Xbox One controler 
CPURAMHard DriveHard Drive
C2D 2,26GHz under volted @ .978v 8GB  Crucial M4 64GB SSD 500GB Scorpio Black 
OSMonitorKeyboardMouse
OS X 10.0 1280x800 Built-in Trackpad 
Audio
Built-in 
  hide details  
Reply
post #70 of 72
Thread Starter 
ok. I apologize to my parts lol. Is 1.15v god for vccsa voltage. Vcore at 1.43 and ram is set according to the values on the spreaders. Running prime blend now.
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i5 2500K Maximus IV Gene-Z GTX 570 Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Force GT ASUS 24x Black SATA Corsair H100 Windows 7 64-bit Ultimate 
PowerCase
Corsair TX750 V2 Corsair Carbide 400R 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › OC Help