Crashes and reboots, again

[Hickory]

Hi thanks for the reply,

I’ve done as suggested and reset BIOS to default. Would it be OK to go back in and set my fan curve? These are really loud! If not I can live with it for now.

Top of the memory list was Antimalware Service Executable and iCue, they changed places constantly even after a few minutes, both using roughly the same amount.

[Hickory]

Just to add, about half an hour after reboot and iCue 4 is using almost 400mb of memory, which seems a lot to me? I don’t know what you make of that.

[phillpower2]

No problem and by all means sort your fans out to how you had them.

Leave any other settings alone for now and see how things go.

How much memory were each of those two programs using, the anti malware service would be expected to use a fair amount but you don`t want a third party program like iCue using too much, as an asides and just so you know programs like iCue and Razer are the bane of a techs life, they cause no end of grief and have only gotten worse with the advent of RGB lighting

Edit to add, just seen your follow up post, as if by coincidence, already mentioned above.

Calling it a day now as up at 5am, will check back PM UK tomorrow after tea.

[Hickory]

Morning.
Just to update I’ve had one power off event and another lock up this morning. It sure if it’s a coincidence but the first happened the moment I switched on my corsair headset.

I have tried turning off icue, but then the system locked up in the same game a short time later. But didn’t reboot. It did have a few corsair processes running in the background.

Not sure if this is coincidence or not but I’m starting to wonder if icue is causing issues.

[phillpower2]

A new MTB log would help.

Not sure if this is coincidence or not but I’m starting to wonder if icue is causing issues.

The ICue software was mentioned by myself previously but you dismissed it as being the cause, likewise your Corsair wireless headset drivers could be involved.

I have also reinstalled iCue. I doubt that’s causing system instability but figured it was worth a try,

Your MTB log suggests that it has been giving you serious issues for the past thirteen days (does almost two weeks sound familiar) and rather than reinstalling it completely uninstalling it as part of the troubleshooting steps may be required.

[Hickory]

Hello again

I wasn’t intentionally being dismissive but I should have been more open there. I’ll defer to your better judgement and uninstall iCue completely and the Corsair drivers to see if that helps.

I still can’t seem to attach the MTB but it is here.

[phillpower2]

I would not uninstall anything for now, give me five minutes to go through the latest MTB log after which I will come back and edit this reply with a follow up.

[COLOR=rgb(44, 130, 201)]Edit to add: Corsair software and Windows issues again, the former most likely the drivers for your wireless headset.

Disconnect the Corsair headset and then do a clean boot the steps for which you will find here[/COLOR]

[Hickory]

Done

[phillpower2]

Sorry but that is not all that there is to it, you need to use the computer as best you can with just the most basics running.

Reboot and see if the PC runs better.

If yes then use msconfig to enable several items at a time till you find the culprit.

If no, start msconfig and click on the Services tab.

Check the Hide All Microsoft Services box, record what is currently starting then click the Disable All button.
Again, do a regular boot, see if it runs normal.

If yes then use msconfig to enable services until you find the culprit.

Once you’ve found the culprit, uninstall it or find out how to eliminate it from your system. Simply disabling it in msconfig is a temporary fix at best.

Enable everything else you disabled.

[Hickory]

I think my PC failed step 1, so with everything disabled and the headset unplugged I left a game running and came back to the login screen, and nothing running. So I didn’t see it reboot but I can only assume it did.

[phillpower2]

Did the PC re start ok after you first did the clean boot.

What was the game you left playing.

Can we have a new MTB log, repetitive I know but needs must.

[Hickory]

Thanks again for the reply.

Yeah the PC started up fine, no issues that I noticed
I was running Satisfactory which has been triggering the crashing etc on and off but isn’t the only game doing it.

Don’t worry about being repetition, at this stage I’m just desperate to fix it

MTB here.

[phillpower2]

Looking like hardware and because we know that you have a good quality, more than adequate spec of PSU the GPU looks to be the most likely candidate, your latest MTB only has the one error and that is the to be expected Windows one below.
[HEADING=1]System errors:[/HEADING]
Error: (04/28/2021 07:13:00 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 18:35:27 on 28/04/2021 was unexpected.

The following requires you to be in attendance throughout the test;

Use the free version at the following link;

Stress test your GPU with Furmark

[Hickory]

I’m currently running the furmark stress test at default settings, 1280x720 - it’s been running for about 20 minutes.
Should I run it at my default monitor res or is it fine like this?

And how long should I run it for?

Thanks

[phillpower2]

Run the test on the settings that you normally use, 20 minutes is enough as a flaky GPU will normally fall over before that.

That time again so will need to catch up tomorrow.