post #11 of 11
Quite often when your system returns \\windows\\system32\\config\\system errors it is a voltage dip. This is where the crunch of your dynamic link libraries occur in the Virtial Memory Manager Kernel and is shown by an immediate stop upon initialization of Windows. In such a case, you will always attain boot but not number crunching load. You will also very likely pass a DOS memtest86 which will show that memory is not the problem but the voltage to the processor registers upon number crunching.

I would take a look at your CPU voltage and if you are able to state a termination on the voltage do so. If not then raise your voltage .1 steps and retry. What is your voltage at? For testing purposes you can take your voltage up to 1.55V (1.36V is default with the multiple VID being 1.25 - 1.525V) to find your maximal overclock. I would not keep it that high for 24/7 use but you should be able to make ~3.8 - 3.9GHz

R
Roped In
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 2600k P8P67 Pro Rev (3.1) @ B3 XFX Radeon HD 6950 XXX 16GB G.SKILL Ripjaws 9-11-9-28 
Hard DriveOptical DriveOSMonitor
2 X Callisto Deluxe 25nm 60GB Plextor PX-B910SA 4x Blu-ray DVD-RW Win7 64 2 x Samsung 275T+ 
KeyboardPowerCaseMouse
Logitech G15 Corsair HX10000 Antec 1200 Logitech G7 
Mouse Pad
Splatter Game Pad 
  hide details  
Reply
Roped In
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 2600k P8P67 Pro Rev (3.1) @ B3 XFX Radeon HD 6950 XXX 16GB G.SKILL Ripjaws 9-11-9-28 
Hard DriveOptical DriveOSMonitor
2 X Callisto Deluxe 25nm 60GB Plextor PX-B910SA 4x Blu-ray DVD-RW Win7 64 2 x Samsung 275T+ 
KeyboardPowerCaseMouse
Logitech G15 Corsair HX10000 Antec 1200 Logitech G7 
Mouse Pad
Splatter Game Pad 
  hide details  
Reply