Overclock.net › Forums › Intel › Intel CPUs › Possible damaged CPU? BSOD and other issues.
New Posts  All Forums:Forum Nav:

Possible damaged CPU? BSOD and other issues. - Page 3

post #21 of 32
Quote:
Originally Posted by Bearybear View Post

1.36v. I'm currently in safemode running the same benchmark but I don't think it's a software problem.

1.36v for 5.0 OC? Ive had the same BSOD and it was vcore related. I upped my voltage by .01v to 1.37v and avoided BSOD's for a good year or so, before i had to up it again to 1.38v; then again a year later.... to 1.39v (where its at)

I use 1.39v for a 4.8 OC on my i5-2500k. Over time, your CPU will need more voltage to keep the same OC its at, normal chip degredation.

If your CPU was "damaged" per se, or "broken"... you wont even POST or see any display on the screen even if all your parts are working fine. No beep no thing. So if you can still log on, im sure your CPU is still fine.

Have you tried upping your voltage by a bit and running 12-24 hours of P95? Just to see and rule out if its just an unstable OC thats requiring a little bit more voltage over time...

It may or may not be your PSU. 700W is completely overkill for your build (if its your sig rig 3770k + 670). I suggest going with a 450W or 500W PSU that has at least gold/plat certification with good OEM parts. Sometimes Corsair is known to rebrand very cheap OEM PSU's and slap their logo on it.

First test out your CPU OC stability by running P95, if you run into a BSOD; try upping your voltage by .01 and run P95 again. Most of the time these BSOD errors are just from an unstable OC asking for a little more voltage.

From your Original Post,
Quote:
"[snip]

A clock interrupt was not received on a secondary processor within the allocated time interval.

[snip]

Technical information:

*** STOP: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xFFFFF8800233B180, 0x0000000000000004)

[snip]"

The 0x00000101 points to BSOD 101. On Sandy Bridge CPU's it points to upping your vcore a bit. Not sure if it applies to Ivy Bridge the same way; but you should try it.
post #22 of 32
Quote:
Originally Posted by Bearybear View Post

I disabled everything I could in msconfig, with no success. I've also just had another BSOD whilst trying to update drivers with slimdrivers:

"*** STOP: 0x000000C4 (0x00000000000000F6, 0x000000000000005C, 0xFFFFFA80135C3060, 0xFFFFF8800AA37171)

*** SWDMON.SYS Address FFFFF8800AA37171 base at FFFFF8800AA36000, Date Stamp 51570FA7"

(swdmon.sys is part of the slimdrivers program)

The only time I have seen a 0C4 is when trying to force a device that was not digitally signed for my XBCD controller (Xbox controller rewired to a USB). I am not familiar with slimdrivers, but it sounds like it has something to do with drivers...if it is not a necessary program try uninstalling it.
Blue540
(14 items)
 
x99
(18 items)
 
B.M.O.
(10 items)
 
CPUMotherboardGraphicsGraphics
6800k ASUS X99-A EVGA 980 FTW ACX 2.0 EVGA 980 FTW ACX2.0 
RAMHard DriveHard DriveCooling
Corsair Vengeance CMK32GX4M4B3200C16W Crucial MX100 WD Blue 1TB EK Supremacy EVO 
CoolingCoolingCoolingOS
EK 480 PE EK 240 PE EK D5 Vario Windows 10 
MonitorKeyboardPowerCase
Samsung 49KU7500 (curved 4k) Corsair K65 NZXT Hale 90 V2 1000W Thermaltake X9 
MouseMouse Pad
Logitch G100S X-Trac Ripper 
CPUMotherboardGraphicsRAM
6400k msi A75MA-P33 Sapphire 6670 passive hynix 2 GB dual channel 
Hard DriveOSMonitorKeyboard
WD  windows 8.1 e-machine wireless 
PowerCase
king win 600w custom built 
  hide details  
Reply
Blue540
(14 items)
 
x99
(18 items)
 
B.M.O.
(10 items)
 
CPUMotherboardGraphicsGraphics
6800k ASUS X99-A EVGA 980 FTW ACX 2.0 EVGA 980 FTW ACX2.0 
RAMHard DriveHard DriveCooling
Corsair Vengeance CMK32GX4M4B3200C16W Crucial MX100 WD Blue 1TB EK Supremacy EVO 
CoolingCoolingCoolingOS
EK 480 PE EK 240 PE EK D5 Vario Windows 10 
MonitorKeyboardPowerCase
Samsung 49KU7500 (curved 4k) Corsair K65 NZXT Hale 90 V2 1000W Thermaltake X9 
MouseMouse Pad
Logitch G100S X-Trac Ripper 
CPUMotherboardGraphicsRAM
6400k msi A75MA-P33 Sapphire 6670 passive hynix 2 GB dual channel 
Hard DriveOSMonitorKeyboard
WD  windows 8.1 e-machine wireless 
PowerCase
king win 600w custom built 
  hide details  
Reply
post #23 of 32
Bluescreenview should show you something atleast. Is your pc set to not make the dump files? If so, enable it.
Without knowing what the dump has to say our answers will just be a blind shot.

Remove your "IDE ATA/ATAPI controllers" from device manager, reboot pc and let windows install them again.
0xc4 is driver relates.
0x101 is entirely different.
Sexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 - 4770 MSI Z87 GD65 - Gaming Palit GTX 760 G.Skill 8gb DDR3 @ 1600mhz 
Hard DriveHard DriveCoolingOS
Seagate 7200rpm 250GB Samsung 850 EVO SSD Cooler Master Hyper 212X and 6 case fans. Windows 7 Ultimate x64 
MonitorKeyboardPowerCase
Samsung SyncMaster 2033sw  Dragon War Seasonic M12ii - 650w Cooler Master HAF 912 Combat 
MouseMouse PadAudio
steelseries Sims4 Edition steelseries Sims4 Edition + QCK++ Philips Explode - 2.1 
  hide details  
Reply
Sexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 - 4770 MSI Z87 GD65 - Gaming Palit GTX 760 G.Skill 8gb DDR3 @ 1600mhz 
Hard DriveHard DriveCoolingOS
Seagate 7200rpm 250GB Samsung 850 EVO SSD Cooler Master Hyper 212X and 6 case fans. Windows 7 Ultimate x64 
MonitorKeyboardPowerCase
Samsung SyncMaster 2033sw  Dragon War Seasonic M12ii - 650w Cooler Master HAF 912 Combat 
MouseMouse PadAudio
steelseries Sims4 Edition steelseries Sims4 Edition + QCK++ Philips Explode - 2.1 
  hide details  
Reply
post #24 of 32
Thread Starter 
@ineden; I installed it so I could update my drivers to try to solve the problem, so it isn't the cause

@Ken; Okay, not sure what I'm supposed to be doing with BSV but screens below, and I'll try that.

post #25 of 32
Thread Starter 
Just had another: (Reinstalling the "IDE ATA/ATAPI controllers" made no difference.)
post #26 of 32
Is your driver veriffier running? You have quite a few driver problems or maybe a serious registry problems.

storport.sys is SCSI Port driver. Get auslogic disk defrag. and degrag your drives.

Later maybe you'll get 0x3B: SYSTEM_SERVICE_EXCEPTION. But first lets solve the two above. So check driver verifier, defrag disks, if it doesnt solve then repair windows for registry issues.
Sexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 - 4770 MSI Z87 GD65 - Gaming Palit GTX 760 G.Skill 8gb DDR3 @ 1600mhz 
Hard DriveHard DriveCoolingOS
Seagate 7200rpm 250GB Samsung 850 EVO SSD Cooler Master Hyper 212X and 6 case fans. Windows 7 Ultimate x64 
MonitorKeyboardPowerCase
Samsung SyncMaster 2033sw  Dragon War Seasonic M12ii - 650w Cooler Master HAF 912 Combat 
MouseMouse PadAudio
steelseries Sims4 Edition steelseries Sims4 Edition + QCK++ Philips Explode - 2.1 
  hide details  
Reply
Sexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 - 4770 MSI Z87 GD65 - Gaming Palit GTX 760 G.Skill 8gb DDR3 @ 1600mhz 
Hard DriveHard DriveCoolingOS
Seagate 7200rpm 250GB Samsung 850 EVO SSD Cooler Master Hyper 212X and 6 case fans. Windows 7 Ultimate x64 
MonitorKeyboardPowerCase
Samsung SyncMaster 2033sw  Dragon War Seasonic M12ii - 650w Cooler Master HAF 912 Combat 
MouseMouse PadAudio
steelseries Sims4 Edition steelseries Sims4 Edition + QCK++ Philips Explode - 2.1 
  hide details  
Reply
post #27 of 32
Thread Starter 
The Above BSOD was caused by trying to install a marvel sata driver with the same result every time, but it just installed perfectly fine now from safe mode.

I have no idea what you mean by "Is your driver verifier running?".

I'm using an SSD via SATA, I don't even have any SCSI ports AFAIK.
post #28 of 32
BSOD's are a pain to track down, the bad pool bsod mentions storport.sys being the cause.

What about your windows updates? is it updated?

Driver Verifier runs in background to check for buggy drivers and when it finds one, it bsod's or restarts sometimes. It might be causing these. Click start > verifier.exe
check "delete existing settings" and click finish, this will disable it if its running.

EDIT: I asked for windows update because "2816159" fixes the issue ""0x000000C4" Stop error after you restart a Windows 7-based, Windows 8-based, Windows Server 2008 R2-based or Windows Server 2012-based computer that has the Driver Verifier tool enabled "
Sexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 - 4770 MSI Z87 GD65 - Gaming Palit GTX 760 G.Skill 8gb DDR3 @ 1600mhz 
Hard DriveHard DriveCoolingOS
Seagate 7200rpm 250GB Samsung 850 EVO SSD Cooler Master Hyper 212X and 6 case fans. Windows 7 Ultimate x64 
MonitorKeyboardPowerCase
Samsung SyncMaster 2033sw  Dragon War Seasonic M12ii - 650w Cooler Master HAF 912 Combat 
MouseMouse PadAudio
steelseries Sims4 Edition steelseries Sims4 Edition + QCK++ Philips Explode - 2.1 
  hide details  
Reply
Sexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 - 4770 MSI Z87 GD65 - Gaming Palit GTX 760 G.Skill 8gb DDR3 @ 1600mhz 
Hard DriveHard DriveCoolingOS
Seagate 7200rpm 250GB Samsung 850 EVO SSD Cooler Master Hyper 212X and 6 case fans. Windows 7 Ultimate x64 
MonitorKeyboardPowerCase
Samsung SyncMaster 2033sw  Dragon War Seasonic M12ii - 650w Cooler Master HAF 912 Combat 
MouseMouse PadAudio
steelseries Sims4 Edition steelseries Sims4 Edition + QCK++ Philips Explode - 2.1 
  hide details  
Reply
post #29 of 32
Step 1: Revert back to AUTO cpu clock / volt
Step 2: Reinstall windows
Step 3: Start the overclocking process again, your cpu is degrading and isn't stable
Step 4: Check your OC with Prime95 and enjoy your computer

It doesn't matter what your cpu used to do but what it can do now. It seems you have two problems here, your OC isn't stable and driver / OS issue.

Do you also diagnose your cars at the rev-limiter? rolleyes.gif Listen to your fellow peers, they are trying to help you. Revert back to Auto and then try to troubleshoot and i don't mean by revert as going back to 4.5ghz @1.13v because it used to do 1.12 rolleyes.gif

Just an FYI 101 BSOD = more Vcore.
post #30 of 32
Thread Starter 
Disabled verifier and it's let me install newer drivers etc. Windows is always fully up to date. I'm back to auto but I don't think I have the time or energy for a full wipe and reinstall yet. The chip still seems to do the same OCs with the same voltages as it always used to, with the same results in benchmarks and "stability" tests; so that's frustrating.

Edit: I think disabling verifier seems to have stopped the hanging and SSD IOPS are closer where they should be, this is both on stock speeds and over-clocked.
Edited by Bearybear - 10/6/13 at 7:13am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Possible damaged CPU? BSOD and other issues.