Soldato
- Joined
- 28 Dec 2017
- Posts
- 9,205
- Location
- Beds
I think so!
Overclocking when I don't want to.
- Thread starter MoridinUK
- Start date
XMP in that list is just the profiles available for you to select. The memory is running at stock speeds.
The CPU appears to have enabled everything in the BIOS that it is required for it to downclock.
Last edited:
Yeah but it doesn'tsigh
Have you checked the Power Plan?
Control Panel/System and Security/Power Options/
Select Balanced and click on Change Plan Settings and then Change Advanced Power Settings on the next screen.
In the Power Options window make sure Minimum Processor State is set to 5%.
Yes ok so I'm an idiot! Thank you!Have you checked the Power Plan?
Control Panel/System and Security/Power Options/
Select Balanced and click on Change Plan Settings and then Change Advanced Power Settings on the next screen.
In the Power Options window make sure Minimum Processor State is set to 5%.
Last edited:
Can you restate the problems again please?
You have fixed the CPU downclocking, right?
Yeah I thought the failure to down clock may have been because of a overclocking setting inthe bios.
The actual problem is system stability, I get crashes occasionally and prime95 can not run any test for long before either a broken blue screen is displayed (I can read that it was trying to build a report to send to microsoft but it's repeated a few times and has coloured distorted boxes underneath) Or the workers stop due to rounding errors.
I've tried with two different sets of ram and the cpu and ram are running at stock (not even XMP). I even gave the ram at stock speeds some extra voltage as I've only seen rounding errors once and that was the only time I've ever experienced bad ram.
The mainboard is an old Asus ROG Maximus VIII Gene.
Not sure what else to try next
Last edited:
Hmm, quite hard to diagnose from what you described.
Sorry if I'm repeating, but have you totally ruled out software issues by using a fresh install with nothing installed?
RAM is in the slots suggested by the motherboard?
Do you have any significant errors being reported in the event viewer (especially WHEA)?
Your temps look fine in the pictures, power use looks fine. Only other thing I can think of is your PSU, is it known good?
You can download a CPU diagnostic test from Intel (I think yours would use a legacy version, but not 100% sure), though I don't think it is a particularly thorough test.
You could try turning off the turbo and seeing if the CPU runs stable at the base speed.
I can't imagine what would break on the motherboard to show those symptoms, but I suppose can't rule it out either.
I have not tried a fresh windows install because I can't really wipe my drive. I could maybe try to install on a fresh ssd though I guess.
Ram is in the slots the MB wants
Errors: apart from the critical ones for an unexpected shutdown not really. I see this error around the time of the crashes :
The System Guard Runtime Monitor Broker service terminated with the following error:
%%3489660935
And some issues with permission on every start up
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
And some service always seems to fail:
The Freemake Improver service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
No idea what the heck that is to be honest.
I may try to find the cpu diagnostics. I did swap out the cpu a month or so back, (i5-6600k out i7-7700k in) and there were occasional crashes but very rare and nothing I could replicate. I know I shouldn't but I always feel like that's almost normal with windows.
PSU was replaced only 6 months ago when I swapped out a 1080 gtx for the radeon 6800 xt (which the 8 year old 600 w psu seemed to struggle with)
If the install is very old, I'd recommend it, because you could easily have picked up some problems over the years. Obviously make sure you have back ups before you mess with it, blahblah.
None of those sound important. WHEA errors are the ones I usually pay attention to for hardware related issues.
It is a quick and simple tool to run, so worth a pop.
Hmm, depends on what exactly you mean by crashes. BSODs and CTDs should be very rare on a stable system, outside of specific driver or app issues. Black screens should never or very rarely happen. Resets, the same (never or very rarely). I'm familiar with PCs that are left on for weeks, or even months and the only crashes during that time are related to the apps crashing within Windows and having to be restarted, due to bugs in their code.
I'll girde up my loins for an reinstall. It's at least 7 years old I think,
I'm downloading the tool.
Mostly they have been screen lock ups or BSOD. :thinking: I think it's not been well for a while
That should be a decent PSU so failure unlikely.
I’ve no idea if UBCD is the latest and greatest anymore (probably not) but you can get a USB version that runs prime95, memtest and lots of other tools to rule out some of the hardware.
Another unlikely cause could be peripherals plugged in or other hardware. Try testing with as much removed or unplugged as you can to eliminate more variables.
I’ve no idea if UBCD is the latest and greatest anymore (probably not) but you can get a USB version that runs prime95, memtest and lots of other tools to rule out some of the hardware.
Another unlikely cause could be peripherals plugged in or other hardware. Try testing with as much removed or unplugged as you can to eliminate more variables.
Hmm, not looking good there for the CPU!
Did you do a full CMOS reset/clear when you swapped the CPUs out?
Edit: noticed that my PCs have usually defaulted to SST = off / OS-control instead of hardware control (for speed shift). You may want to try that, though realistically I can't see why it would make a difference.
Last edited: