Overclock.net › Forums › AMD › AMD CPUs › X4 955 C3 OCCT core error
New Posts  All Forums:Forum Nav:

X4 955 C3 OCCT core error

post #1 of 3
Thread Starter 
I built a rig for my friend with these parts
955 X4 C3 w/ OCZ Vendetta 2
MSI 790XT-G45 latest BIOS
Patriot Extreme Performance Gaming 2X2GB
Corsair CX430
EVGA 9800GT 1GB
Kingston SSDNow! V+ SSD 30GB
Hitachi 1TB
Windows 7 Ultimate

It gave me 4 BSODs all regarding 4e ntoskrnl.exe memory corruption before I am able to get all the updates/drivers and finally, the AMD chipset (southbridge I recalled where I do not think there's driver for the north bridge) seems to fix the BSOD for now.

Problem now is, whenever I run OCCT "stock clock", it gives me error within 8 to 12 mins. I ran 5 times and all of them gave me errors within this time frame. Strangely, 2 of them are error on Core 2, and one time each on core 0 and core 3. I pumped the voltage a notch on Vcore and NB, still the same. Googled it and not much came out, but also read that if the errors are not always the same core, it may not be the CPU?!

Need some help here, this has been the worst rig I have ever worked with.
Main Rig V 6.8
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6850K @ 4.4Ghz Asus Rog Rampage V Extreme U3.1 GTX 1080 Ti @ 2050/6000 Corsair Vengance LPX 16GB DDR4-2800 
Hard DriveHard DriveHard DriveHard Drive
Intel 600P 512GB NVMe Samsung 850 PRO 256GB Samsung 850 EVO 500GB WD Caviar Black 640GB X2 
CoolingOSMonitorKeyboard
Corsair H115i AIO Windows 10 Pro x64 Philips BDM4350UC 4K Monitor 10bit + LG IPS231P Corsair K70 LUX CherryMX Brown 
PowerCaseMouseAudio
Corsair AX1200 80Plus Gold Thermaltake Core P3 Logitech G502 Proteus Core  ALC1150 Optical Out to Pioneer VSX-824-K 
  hide details  
Reply
Main Rig V 6.8
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6850K @ 4.4Ghz Asus Rog Rampage V Extreme U3.1 GTX 1080 Ti @ 2050/6000 Corsair Vengance LPX 16GB DDR4-2800 
Hard DriveHard DriveHard DriveHard Drive
Intel 600P 512GB NVMe Samsung 850 PRO 256GB Samsung 850 EVO 500GB WD Caviar Black 640GB X2 
CoolingOSMonitorKeyboard
Corsair H115i AIO Windows 10 Pro x64 Philips BDM4350UC 4K Monitor 10bit + LG IPS231P Corsair K70 LUX CherryMX Brown 
PowerCaseMouseAudio
Corsair AX1200 80Plus Gold Thermaltake Core P3 Logitech G502 Proteus Core  ALC1150 Optical Out to Pioneer VSX-824-K 
  hide details  
Reply
post #2 of 3
Thread Starter 
Temp was perfectly good, topped at 53C.
Hope this may help.
Main Rig V 6.8
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6850K @ 4.4Ghz Asus Rog Rampage V Extreme U3.1 GTX 1080 Ti @ 2050/6000 Corsair Vengance LPX 16GB DDR4-2800 
Hard DriveHard DriveHard DriveHard Drive
Intel 600P 512GB NVMe Samsung 850 PRO 256GB Samsung 850 EVO 500GB WD Caviar Black 640GB X2 
CoolingOSMonitorKeyboard
Corsair H115i AIO Windows 10 Pro x64 Philips BDM4350UC 4K Monitor 10bit + LG IPS231P Corsair K70 LUX CherryMX Brown 
PowerCaseMouseAudio
Corsair AX1200 80Plus Gold Thermaltake Core P3 Logitech G502 Proteus Core  ALC1150 Optical Out to Pioneer VSX-824-K 
  hide details  
Reply
Main Rig V 6.8
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6850K @ 4.4Ghz Asus Rog Rampage V Extreme U3.1 GTX 1080 Ti @ 2050/6000 Corsair Vengance LPX 16GB DDR4-2800 
Hard DriveHard DriveHard DriveHard Drive
Intel 600P 512GB NVMe Samsung 850 PRO 256GB Samsung 850 EVO 500GB WD Caviar Black 640GB X2 
CoolingOSMonitorKeyboard
Corsair H115i AIO Windows 10 Pro x64 Philips BDM4350UC 4K Monitor 10bit + LG IPS231P Corsair K70 LUX CherryMX Brown 
PowerCaseMouseAudio
Corsair AX1200 80Plus Gold Thermaltake Core P3 Logitech G502 Proteus Core  ALC1150 Optical Out to Pioneer VSX-824-K 
  hide details  
Reply
post #3 of 3
OCCT may very well blow up your PC due to the unstable MOSFETs.... though the instability may not necessarily be the MOSFETs I don't recommend running the 955 or any 125W processor on that board at all, most especially with the tower cooling
(Sig for details)
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD CPUs
Overclock.net › Forums › AMD › AMD CPUs › X4 955 C3 OCCT core error