Overclock.net › Forums › Intel › Intel CPUs › The Intel Devil's Canyon Owners Club
New Posts  All Forums:Forum Nav:

The Intel Devil's Canyon Owners Club - Page 2104

post #21031 of 22487
Quote:
Originally Posted by Kamikaze-X View Post

Booted my machine last night and my processor, on a custom loop, was hitting 80C! I was like '***?!' until i checked the voltages and I had somehow managed to set the core V to 1.9v...... :O

oops!

And it's alive? You sure it was really running at 1.9V? That scared me just thinking about it! What the hell...?

I remember one time when Asus' AISuite tried to set my core voltage to 1.92V and as soon as I saw it, I just pressed the reset button hastily. Didn't risk it for a moment. I spent a week running at bone stock settings just to make sure it was running correctly. A year and a half later and it's alive, so I guess it either didn't apply the setting or it didn't run like that long enough. Needless to say AISuite is my enemy since then.
post #21032 of 22487
Ram tweaking above 2500mhz is very annoying. I can't get anything above 2500 stable anymore. But i've made some intresting discoveries. The ram is capable, the problem is somewhere else i think. 2666 Cl11 1T usually rebootloops before getting into windows. But i tried having vccsa and the io voltages at auto and it booted without any problems! It added +0.100 vccsa (0.940) and nothing to the io voltages. So it seems like it prefers certain values, +200 worked too. I tried 2600 at the same timings, but it produced errors even quicker than 2666 and looser timings didn't help at all.
post #21033 of 22487
No point pushing things this far on this platform. Stability will be too limited
post #21034 of 22487
Quote:
Originally Posted by GeneO View Post

? Not sure what you are trying to say here. Windows will apply patches to the OS that will load newer microcode. It is recorded in the registry as you say. All AIDA64 does is report that. If your BIOS microcode revision is less than the OS revision, the OS revision will be loaded in the microprocessor at boot. All I am asking you is to verify that the OS hasn't overloaded the microcode in the BIOS.

What you say about a new CPU maybe needing a new BIOS with the correct microcode is correct, but I think not for the reason you re thinking. The BIOS of course needs a working processor to execute its code. You have to have a revision of the microcode for that processor in the BIOS in order to bootstrap the BIOS (you also need a version of IME that supports the processor). Once it is booted, if windows has a newer version, it will get loaded.

Hello GeneO, sorry for late reply but i was involved in a long work that totally absorbed me... redface.gif
Things you said are correct but in reality there are some differences and i'll try to explain with a fact that i've encountered.
This is a little PC that i have assembled to handle administratives stuff in the lab where i work and is based on an ASRock Z97M Pro4, a Pentium G3258 AE@4.500 Mhz (Fixed Mode, Speedstep and C-States disabled, VCore applied in override mode), 16GB of Crucial DDR3 PC3 12800:




As you can see CPU micro-code is Rev. 19 and CPU is in OC




From OS info are these:




As you can see the CPU micro-code is Rev. 1E and the information is updated by the "mcupdate_GenuineIntel.dll" that is located in "c:\Windows\System32\"

If you exclude the DLL taking ownership (http://www.askvg.com/guide-how-to-take-ownership-permission-of-a-file-or-folder-manually-in-windows/) and renaming it, you'll have this info:




and CPU micro-code correspond to Rev. 19 that is "stored" into BIOS.

The possibility that CPU microcode present in BIOS prevails to the one introduced with OS can be "explained" with some tests done by modding the same version of BIOS with different CPU micro-code revisions like i've done when i've encountered this issue:

http://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-upgrade-fails-with-0xc1900101-0x20017/db224756-027e-4a5c-83a8-0c8edd156e55?page=1

As stated by some users in the above discussion, it seems that after the moment where discussion has started (August 2015) CPU micro-codes released have disabled OC for Pentium G3258 and as can be seen in UBU CPU Micro-code choice menu the Rev. 1E and subsequent are theoretically to be avoided:




Infact this is the working OC with Rev. 1D and mcupdate_GenuineIntel.dll disabled:




and this is the OC set into BIOS but not working with CPU micro-code Rev. 1E (13-08-2015) (see the CPU Turbo frequency @ 4.500 Mhz but not applied):




valid up to the latest CPU micro-code recently released (Rev. 20):




So, if the CPU micro-code updated by OS would have highest priority than the one implemented by BIOS this situation couldn't be possible e.g. CPU micro-code 1E with an OCed CPU:






That's all folks! thumb.gif

Cheers,

KK
post #21035 of 22487
Quote:
Originally Posted by tolis626 View Post

And it's alive? You sure it was really running at 1.9V? That scared me just thinking about it! What the hell...?

I remember one time when Asus' AISuite tried to set my core voltage to 1.92V and as soon as I saw it, I just pressed the reset button hastily. Didn't risk it for a moment. I spent a week running at bone stock settings just to make sure it was running correctly. A year and a half later and it's alive, so I guess it either didn't apply the setting or it didn't run like that long enough. Needless to say AISuite is my enemy since then.

yeah it was definitely 1.9V... I think in my sleep deprived state I mistook the Core V for the Input V, or I miskeyed 1.29V for the core.

She's been up and running fine since so touch wood its ok!
post #21036 of 22487
There was a guy...on a forum somewhere...with a devils canyon chip who accidentally typed in 1.91V instead of 1.19V. He said the first time he tried to boot it froze shortly into the boot. Second time it froze even faster and would never work again. Total chip death supposedly. Not sure how he knew it was 1.91V though if the CPU was dead at that point (and if he knew earlier, obviously he wouldn't have booted), so I guess it was a partial guess.

Another story...on a forum somewhere...was of a skylake CPU with 2.5V entered. It drooped down a lot so ended up at like 1.7 or something. He ran it for a few minutes or hours and got significant degredation (wasn't quite stable at stock settings).

Both of these I read first hand, but, now it's second hand so...no way to really be sure.

It's pretty hard to hurt these chips. I've run my computer (4690k) for about 6 months at 1.25V, 12 months at 1.3V, and 6 months at 1.36V. Pretty sure it runs better (lower voltage) now than when I got it. I'm only under load for a few hours a day at most.
Dorje
(12 items)
 
  
CPUMotherboardGraphicsRAM
4690k Gigabyte z97x-sli MSI TF 280 G Skill Sniper 1600/9 
Hard DriveCoolingOSMonitor
Seagate 4 tb hybrid Corsair h80i Windows 8.1 SE39UY04 
PowerCaseMouseAudio
EVGA NEX-G 750W S340 (white) Bloody ZL5A Razer Blackshark 
  hide details  
Reply
Dorje
(12 items)
 
  
CPUMotherboardGraphicsRAM
4690k Gigabyte z97x-sli MSI TF 280 G Skill Sniper 1600/9 
Hard DriveCoolingOSMonitor
Seagate 4 tb hybrid Corsair h80i Windows 8.1 SE39UY04 
PowerCaseMouseAudio
EVGA NEX-G 750W S340 (white) Bloody ZL5A Razer Blackshark 
  hide details  
Reply
post #21037 of 22487
Quote:
Originally Posted by fat4l View Post

My 5.1G 4790K is finally getting what it deserves..... a proper Mobo!
Asus Maximus VII Formula biggrin.gif



CPU: 5.1G 4790K


Warning: 5.1G 4790K Stress tests 100% stable!!! (Click to show)
1Hour


4Hours


8Hours




5.4G for the lolz biggrin.gif



thumb.gif

Thats more like it biggrin.gif

Nice chip! thumb.gif
post #21038 of 22487
Hey guys.

Anyone using HWiNFO? For some reason, the sensor for CPU voltage is always reading 1.002V, even when system is idle and CPU is downclocked. CPU-Z on the other hand report's voltage is changing depending on the load. I'm assuming HWiNFO is reading the sensor incorrectly? Using latest versions of both apps..
PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 4690k MSI Z97 Gaming 3 MSI Radeon R9 380 Gaming 2GB Kingston HyperX Fury 8GB DDR3 1600MHz 
Hard DriveHard DriveCoolingCooling
Crucial MX100 256GB WD10EZEX Scythe Kotetsu CPU Cooler Master Silencio FP 120 PWM intake 
CoolingOSMonitorPower
Akasa exhaust Windows 7 Pro x64 LG Flatron IPS235 Corsair CX550M 
CaseMouseMouse PadAudio
CoolerMaster Elite 334U SteelSeries Rival 100 SteelSeries QcK Vector Kingston HyperX Cloud 
Audio
Logitech z333 DEAD/RMA 
  hide details  
Reply
PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 4690k MSI Z97 Gaming 3 MSI Radeon R9 380 Gaming 2GB Kingston HyperX Fury 8GB DDR3 1600MHz 
Hard DriveHard DriveCoolingCooling
Crucial MX100 256GB WD10EZEX Scythe Kotetsu CPU Cooler Master Silencio FP 120 PWM intake 
CoolingOSMonitorPower
Akasa exhaust Windows 7 Pro x64 LG Flatron IPS235 Corsair CX550M 
CaseMouseMouse PadAudio
CoolerMaster Elite 334U SteelSeries Rival 100 SteelSeries QcK Vector Kingston HyperX Cloud 
Audio
Logitech z333 DEAD/RMA 
  hide details  
Reply
post #21039 of 22487
Quote:
Originally Posted by blue.dot View Post

Hey guys.

Anyone using HWiNFO? For some reason, the sensor for CPU voltage is always reading 1.002V, even when system is idle and CPU is downclocked. CPU-Z on the other hand report's voltage is changing depending on the load. I'm assuming HWiNFO is reading the sensor incorrectly? Using latest versions of both apps..

http://www.overclock.net/t/1235672/official-hwinfo-32-64-thread

This guy should be able to help you out. Not sure why it would do that, mine seems to work fine. You are using the beta version?
Intel Overclocker
(12 items)
 
Media PC
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel i7 4790k Delidded + Lapped ASRock Z97 Extreme4 MSI Twin Frozr GTX 660  Corsair Vengeance Pro 2400mhz DDR3 
Hard DriveHard DriveOptical DriveCooling
OCZ Deneva 2 R series 400GB SSD WD Green 4TB HDD Asus DRW-24B1ST Phanteks PH-TC14PE_RD 
OSPowerCaseMouse
Windows 10 Seasonic 650w M12II Phanteks Enthoo Pro M with Acrylic side Cobra e-blue 
CPUMotherboardRAMHard Drive
intel core 2 quad q8200 Dell studio stock Dell studio Stock Corsair Force 3 SSD 
Hard DriveOptical DriveCoolingOS
External powered Seagate expansion desk Dell studio stock Stock Windows 10 
CPUMotherboardGraphicsRAM
FX-8350 GA-990FXA-UD5 MSI 7870 Hawk Edition Gskill 1600 2x4 GB 
Hard DriveOptical DriveCoolingOS
Corsair Force Series 3 22x Samsung w/ lightscribe dvd/cd burner Noctua NH-D14 Win 7 pro x64 
MonitorPowerCase
Acer x173w Seasonic M12II 650watt Semi-Modular PSU Apevia x-dreamer4 (with side window and red) 
  hide details  
Reply
Intel Overclocker
(12 items)
 
Media PC
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel i7 4790k Delidded + Lapped ASRock Z97 Extreme4 MSI Twin Frozr GTX 660  Corsair Vengeance Pro 2400mhz DDR3 
Hard DriveHard DriveOptical DriveCooling
OCZ Deneva 2 R series 400GB SSD WD Green 4TB HDD Asus DRW-24B1ST Phanteks PH-TC14PE_RD 
OSPowerCaseMouse
Windows 10 Seasonic 650w M12II Phanteks Enthoo Pro M with Acrylic side Cobra e-blue 
CPUMotherboardRAMHard Drive
intel core 2 quad q8200 Dell studio stock Dell studio Stock Corsair Force 3 SSD 
Hard DriveOptical DriveCoolingOS
External powered Seagate expansion desk Dell studio stock Stock Windows 10 
CPUMotherboardGraphicsRAM
FX-8350 GA-990FXA-UD5 MSI 7870 Hawk Edition Gskill 1600 2x4 GB 
Hard DriveOptical DriveCoolingOS
Corsair Force Series 3 22x Samsung w/ lightscribe dvd/cd burner Noctua NH-D14 Win 7 pro x64 
MonitorPowerCase
Acer x173w Seasonic M12II 650watt Semi-Modular PSU Apevia x-dreamer4 (with side window and red) 
  hide details  
Reply
post #21040 of 22487
Latest stable.

But looking at it I think I'm reading it wrong.



What is the difference between sensor from CPU - Core VIDs and motherboard sensor - Vcore?

I'm confused. I'd like to overclock my 4690k but I'm scared that setting Vcore manually in BIOS to 1V is not undervolting the CPU like on auto. I have all the power efficiency features enabled.

Right now I have all OC settings on optimized defaults (auto). HWiNFO now reports VIDs from 0.7V to 1V. If I manually enter 1V for Vcore in BIOS, VIDs stay always at 1V.
PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 4690k MSI Z97 Gaming 3 MSI Radeon R9 380 Gaming 2GB Kingston HyperX Fury 8GB DDR3 1600MHz 
Hard DriveHard DriveCoolingCooling
Crucial MX100 256GB WD10EZEX Scythe Kotetsu CPU Cooler Master Silencio FP 120 PWM intake 
CoolingOSMonitorPower
Akasa exhaust Windows 7 Pro x64 LG Flatron IPS235 Corsair CX550M 
CaseMouseMouse PadAudio
CoolerMaster Elite 334U SteelSeries Rival 100 SteelSeries QcK Vector Kingston HyperX Cloud 
Audio
Logitech z333 DEAD/RMA 
  hide details  
Reply
PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 4690k MSI Z97 Gaming 3 MSI Radeon R9 380 Gaming 2GB Kingston HyperX Fury 8GB DDR3 1600MHz 
Hard DriveHard DriveCoolingCooling
Crucial MX100 256GB WD10EZEX Scythe Kotetsu CPU Cooler Master Silencio FP 120 PWM intake 
CoolingOSMonitorPower
Akasa exhaust Windows 7 Pro x64 LG Flatron IPS235 Corsair CX550M 
CaseMouseMouse PadAudio
CoolerMaster Elite 334U SteelSeries Rival 100 SteelSeries QcK Vector Kingston HyperX Cloud 
Audio
Logitech z333 DEAD/RMA 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › The Intel Devil's Canyon Owners Club