Overclock.net banner
141 - 160 of 504 Posts
Glad to hear it. Maybe I should change kits.

I noticed that with the NPU, too. I didn't look at the version. Just clicked. Yes, the GCC updates are more frequent than what is posted. My .3717 installed ok. I will watch for the next GCC update.
You don't have to wait, just look at Neural processors under Device Manager....

Text Screenshot Number Font Software


If the Driver is still 3053, the 3717 update hasn't taken. Why, is the question 🤷‍♂️

Im having the same issue with the NPU driver. I've installed it 3 times now
Same here, 3 times. It simply won't take. All that said, I've not noticed any issues, so.... 🤷‍♂️
 
Discussion starter · #143 ·
Do you guys have a issue when you change network adapter settings you have to restart you computer to get the ethernet to come back? It happens anytime I change a setting or update/install the driver.
It happens to me only when I get a stability crash and it reboots. I have to reboot to get the Ethernet back. Doesn't happen to me with driver installs - yet.
 
Discussion starter · #144 ·
You don't have to wait, just look at Neural processors under Device Manager....

View attachment 2704655

If the Driver is still 3053, the 3717 update hasn't taken. Why, is the question 🤷‍♂️



Same here, 3 times. It simply won't take. All that said, I've not noticed any issues, so.... 🤷‍♂️
My .3717 took. Maybe there is an order of install issue? Flakey.
 
Discussion starter · #146 ·
Yes, I am using a CPU Frame from thermalright it is just barely snug I did not crank it down super tight haha!! I will try a different BIOS version I still think I have F16c.. I also tried to change the different speed rate it still started like it has been..

I thought I fixed it when I turned off the Power limits and set them at auto instead of maxing them out.. it did boot fine for a day then I was adjusting the NGU and D2D and tried OC the ram a bit and it came back where it starts turns off the restarts in one press of the button..
OK I set the BIOS to Optimised settings and when I turned my PC off and restarted it booted right up. and the only thing I changes was the OC to the P/E Cores, XMP PRofile and the e core voltages set too 1.225v.. so it has to be the OC settings.

I was wondering should maybe I adjust the voltages on the E cores?? I have the P cores an Auto..
 
Discussion starter · #148 ·
OK I set the BIOS to Optimised settings and when I turned my PC off and restarted it booted right up. and the only thing I changes was the OC to the P/E Cores, XMP PRofile and the e core voltages set too 1.225v.. so it has to be the OC settings.

I was wondering should maybe I adjust the voltages on the E cores?? I have the P cores an Auto..
E-core voltage should be fine - shouldn't be the issue. My P cores are auto and E cores @ 5.0 are 2.45v if my P cores are 5.5 or 2.75v if my P cores are 5.6 (they need more juice if your P core ratio is higher - will still run at the lower voltage but will score less in benchmarks)

I think the XMP is being difficult.
 
My .3717 took. Maybe there is an order of install issue? Flakey.
You say that but what does Device Manager say??? Mine "took" too, until Device Manager shows it didn't.

tried the latest driver from the Intel hompage (3967)?

View attachment 2704661
Sounds like a good idea. Link?

EDIT:

Got it sorted, but was weird. Going to Intel’s site I came across this tutorial: How To Install or Update the Intel® NPU Driver. (nothing new as I’ve used that in the past for other driver issues) but still…

Anyway, when you uninstall a device with its drivers and do a Scan for Hardware Changes, the item you just removed would just normally show up as an Other devices with a yellow Triangle” indicating the device is unknown and needs a driver. Simply install the driver and “other Devices” will change to the named device with a driver, and the yellow triangle gone. That’s usually the normal way.

Weird was I uninstalled the Neural Processor (NPU) and driver, and clicked Scan for Hardware Changes, the NPU not only showed up, but the driver was updated to 3717. Here simply uninstalling the device (with driver) and doing a hardware changes scan fixed the issue without ever having to install the driver (not typical). Given that I suspect the driver was already in the system, but simply refused to update until that uninstall was done. Weird.

Anyway, now the new driver is installed and all is good now. Even shows in GCC as 3717. Haven’t installed the latest one (3967) yet. Will wait to see if it’s offered first.

Anyway, Issue now solved. All good.

Text Screenshot Font Software Number


BTW, if yours doesn't do what mine did, simply continue following the tutorial to manually install the driver. Also, not necessarily required, but I always do a reboot just to be sure all is good.

Good luck.
 
  • Rep+
Reactions: igor_kavinski
E-core voltage should be fine - shouldn't be the issue. My P cores are auto and E cores @ 5.0 are 2.45v if my P cores are 5.5 or 2.75v if my P cores are 5.6 (they need more juice if your P core ratio is higher - will still run at the lower voltage but will score less in benchmarks)

I think the XMP is being difficult.
OK, so if we did the OC and not run the XMP PRofile if what your saying is true it should not have the boot issue?

EDIT: Well I just tried setting back to optimised then set just the XMP Profile it had the bootup issue. I then removed the XMP PRofile and put just an OC on the P/E Cores and set the volts too 1.225v for e cores and it did the same thing..

So maybe both as when I just do the optimised profile IT boots just fine.. I will try this set to optimised and then see how it boots over a day or two.. I will report back on what happened unless you find the same thing..
 
Discussion starter · #151 ·
OK, so if we did the OC and not run the XMP PRofile if what your saying is true it should not have the boot issue?

EDIT: Well I just tried setting back to optimised then set just the XMP Profile it had the bootup issue. I then removed the XMP PRofile and put just an OC on the P/E Cores and set the volts too 1.225v for e cores and it did the same thing..

So maybe both as when I just do the optimised profile IT boots just fine.. I will try this set to optimised and then see how it boots over a day or two.. I will report back on what happened unless you find the same thing..
Did you set your loadline?

Advance Voltage Settings
in CPU/VRM Settings
- CPU DLVRin Vcore Loadline Calibration - Ultra Extreme
(You may get away with a lessor setting than Ultra Extreme but higher than the auto or lower ones - I have not tested each)

Not sure if that may be it.
 
Just a reminder but some of those BIOS changes in and of themselves are going to cause a double boot, so I wouldn't count on that as an indication the issue is still present. I would at least give a day to see what happens.

That said, I'm not clear on what @The_Nephilim issue is.
 
Just a reminder but some of those BIOS changes in and of themselves are going to cause a double boot, so I wouldn't count on that as an indication the issue is still present. I would at least give a day to see what happens.

That said, I'm not clear on what @The_Nephilim issue is.
Yes I am aware of that the BIOS changes causes a double boot. my issue is when I do a coldboot when I click the power button it starts up for like 2 seconds then turns off it then turns back on without me doing anything and boots like normal..

I currently loaded optimised defaults and it boots as normal, it is when I put an OC and the XMP PRofile I get the boot issue on a cold boot..
 
Discussion starter · #154 ·
Between March 3 and tonight, I tweaked my P Cores, so I finally cleared 72K in CPU Mark. Also OC'd my videocard.
Bios changes and issues with XMP profiles took my Memory score down.

Not the best benchmark from what I hear - but rerunning while playing with core ratios in XTU helps identify the best ratio for each core. Set Active-Core Tuning to all 57 to push max on the cores.

I found that one of my cores likes to stay at 55, 4 like 56 and 3 like 57. Corresponds to the auto voltages. ~295v = 56, <300v = 55, >345v = 57, I think. For this bench at least.


Technology Display device Electronics Screenshot Software
Technology Display device Electronics Screenshot Multimedia
 
Discussion starter · #156 ·
Between March 3 and tonight, I tweaked my P Cores, so I finally cleared 72K in CPU Mark. Also OC'd my videocard.
Bios changes and issues with XMP profiles took my Memory score down.

Not the best benchmark from what I hear - but rerunning while playing with core ratios in XTU helps identify the best ratio for each core. Set Active-Core Tuning to all 57 to push max on the cores.

I found that one of my cores likes to stay at 55, 4 like 56 and 3 like 57. Corresponds to the auto voltages. ~295v = 56, <300v = 55, >345v = 57, I think. For this bench at least.


View attachment 2704719 View attachment 2704720
...and if you apply those ratios while running CPU Profile in 3DMark it will stutter.

Max threads - stutters if E Core voltage too low when P Core ratios are higher.
8 threads - stutters if your P Core ratios are odd number stepped and/or ratio doesn't have enough voltage.

So each bench has a different ratio/voltage config to produce the best score.
 
  • Rep+
Reactions: sygnus21
Yes I am aware of that the BIOS changes causes a double boot. my issue is when I do a coldboot when I click the power button it starts up for like 2 seconds then turns off it then turns back on without me doing anything and boots like normal..

I currently loaded optimised defaults and it boots as normal, it is when I put an OC and the XMP PRofile I get the boot issue on a cold boot..
Yeah, I don't have that issue here, and I do have XMP enabled, but I use the XMP profile that doesn't OC past the RAM's rated capacity. My RAM is rated at 6400MHz so the profile I use.

With that, I rarely power off my machines, instead letting them sleep while not in use. I'll power off every now and then just to reset things, but for the most part it's sleep.

Also be aware "Load Optimized" defaults is just a base to get the PC booted, not necessarily to best settings for the system. The only time I use Optimized defaults is right after I do a BIOS update - I load the defaults, restart the machine, boot into the BIOS and tweak my settings to include making sure XMP is enabled.

Suggest you Enable XMP to your RAM profile 6400MHz and hold off on the OCs to see what the system does. That said, I'm not an overclocker so I've no suggestions there.

Anyway, I was getting hard crashes when I pushed my RAM past their rated speed of 6400 to 6600. System just wasn't stable at those speeds. I run 4 x 16gig sticks. Sticking to 6400, no more hard crashes and thus my Time Spy score here. Yeah, I could possibly do better, but I was doing worse pushing 6600MHz.

And again, the system isn't OC'd. And for the record, I personally don't see using XMP to push RAM to its rated spec'd speed as "overclocking", but I know many do, so....

Good luck.
 
  • Rep+
Reactions: ArrogantHair
Well when I booted up this morning it seemed to have booted just fine. I do have my OC on and XMP Profile enabled but I did enable the load line calibration too extreme. so maybe that was it or I have an intermintent issue that could come back.\

I will continue to test over the next day or so and see what happens.

EDIT: Well I just booted up after the PC was off for 2 hours it had the bootup issue.. so maybe something wrong with the memory controller or similar??
 
  • Rep+
Reactions: ArrogantHair
Yeah, I don't have that issue here, and I do have XMP enabled, but I use the XMP profile that doesn't OC past the RAM's rated capacity. My RAM is rated at 6400MHz so the profile I use.

With that, I rarely power off my machines, instead letting them sleep while not in use. I'll power off every now and then just to reset things, but for the most part it's sleep.

Also be aware "Load Optimized" defaults is just a base to get the PC booted, not necessarily to best settings for the system. The only time I use Optimized defaults is right after I do a BIOS update - I load the defaults, restart the machine, boot into the BIOS and tweak my settings to include making sure XMP is enabled.

Suggest you Enable XMP to your RAM profile 6400MHz and hold off on the OCs to see what the system does. That said, I'm not an overclocker so I've no suggestions there.

Anyway, I was getting hard crashes when I pushed my RAM past their rated speed of 6400 to 6600. System just wasn't stable at those speeds. I run 4 x 16gig sticks. Sticking to 6400, no more hard crashes and thus my Time Spy score here. Yeah, I could possibly do better, but I was doing worse pushing 6600MHz.

And again, the system isn't OC'd. And for the record, I personally don't see using XMP to push RAM to its rated spec'd speed as "overclocking", but I know many do, so....

Good luck.
Well besides having the BIOS settings at default where it works fine, I am at a loss as to what the issue is.. I just tried setting BIOS to the Previous one F15 and I get the same behavior with the bootup sequence..

Either something is bad or broke and maybe time to send the board for an RMA..
 
  • Sad
Reactions: ArrogantHair
Well besides having the BIOS settings at default where it works fine, I am at a loss as to what the issue is.. I just tried setting BIOS to the Previous one F15 and I get the same behavior with the bootup sequence..

Either something is bad or broke and maybe time to send the board for an RMA..
Hey Guys, I think I narrowed it down to being the RAM slots.. I put the memory into slots A1, B1 and it booted normally. I put them back in slots A2,B2 and I get the boot issue.. so it looks like I might need to RMA the board..
 
  • Rep+
Reactions: ArrogantHair
141 - 160 of 504 Posts