Solved Crashes and reboots, again

[Hickory]

Hi all,
After about two weeks of no issues this has started happening again. And again I am at a loss as to why, as I was pretty sure Phil had solved it!
I've copied in the original post below

Solved - PC rebooting/crashing irregularly in games

Hi there, I'm having a few crash issues on my PC and need a little help. It happens inconsistently, and only in games, mostly the PC will power off, then straight back on again and a couple of times it will lock-up and I'll need to hold the power button down to restart. I've checked the...

pchelpforum.net

 

[Hickory]

I've run fresh Speccy and Sysnative checks.

http://speccy.piriform.com/results/ayE1w6WXCcW8VhAVnlW3qac

 

[phillpower2]

Hello Hickory,

Is there any pattern to the behaviour such as only when gaming, online or does it happen regardless of what the PC is being used for and no matter how long that the PC has been in use for.

Only thing that we can see in the info provided is that Windows is having problems updating.

Download MiniToolBox and save the file to the Desktop.

Close the browser and run the tool, check the following options;

List last 10 Event Viewer Errors
List Installed Programs
List Devices (Only Problems)
List Users, Partitions and Memory size

Click on Go.

Post the resulting log in your next reply for us if you will.

 

[Hickory]

Hey, thanks for the reply and the ongoing help

Is there any pattern to the behaviour such as only when gaming, online or does it happen regardless of what the PC is being used for and no matter how long that the PC has been in use for.

It only seems to happen when gaming, and is irregular, I've yet to be able to find a pattern. So far it has only happened twice (since I reported in that it was fixed) last night, one lockup, one power off then on cycle, after about 2 hours, then 30 minutes in game respectively. By comparison I've been on one game 4 hours this afternoon without issue. The PC is normally on 5-6 hours at a time when I'm using it.

Not sure if this is related but just now, I tried to power on from Sleep and it wouldn't respond, I had to hold the power button down to power off to restart. It came up with this error code: "Windows failed to resume from hibernate with error status 0xC0000411" which seems to relate to hibernate which I do not have enabled.

 

[phillpower2]

Quick reply as rather busy for a while but will come back and edit this reply when I get back, no need to reply meanwhile.

Speccy shows that Hibernation is enabled;

Power Profile
Active power scheme: Balanced
Hibernation: Enabled


To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)"
2. Type in "powercfg.exe /h off" without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input
3. Now just exit out of command prompt

Edit to add

The only problem today is Windows related as you mentioned so let`s see if the steps above help any.

Previous problems that are consistent right up until yesterday are Corsair icue software related.

 

[Hickory]

Quick reply as rather busy for a while but will come back and edit this reply when I get back, no need to reply meanwhile.

Speccy shows that Hibernation is enabled;

Power Profile
Active power scheme: Balanced
Hibernation: Enabled


To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)"
2. Type in "powercfg.exe /h off" without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input
3. Now just exit out of command prompt

Edit to add

The only problem today is Windows related as you mentioned so let`s see if the steps above help any.

Previous problems that are consistent right up until yesterday are Corsair icue software related.

Just a quick update, I have disabled hibernation and had another lockup last night. I have also reinstalled iCue. I doubt that's causing system instability but figured it was worth a try,

 

[phillpower2]

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.

Windows/Defender does not like certain other software that you have on your computer, Java which the hackers love to exploit and a mod install launcher.

See if you are able to get Windows fully up to date then grab a screenshot of the latest update history and upload it for us.

Can we also have a new Speccy url and MTB log.

 

[Hickory]

Hi Phill,
Thanks again for the reply.
I've updated Windows again, it now says it is up to date. Here is my screenprint

Here is also new Speccy: http://speccy.piriform.com/results/bUFz5PYMtQBSuCYFe8wkKE0

I have uninstalled Java & the Mod launcher as suggested. I am using iCue4 now, instead of iCue 3, that might help solve some issues with the errors.

I also did a little digging on the z490 board and disabled MCE (in MSI this is known as Turbo Enhanced and Intel C state in BIOS. I did this as the MCE was know to clock the CPU above Intel's own recommended boost settings for longer to make the board look better to consumers - which apparently can cause stability issues.

I also found that C state for some reason kept the CPU clocked at 4.7GHZ pretty much the whole time, even at idle, it was supposed to reduce power consumption at idle. Disabling it means the CPU runs lower at idle, 800mhz and up, and also has reduced core temps significantly.

No idea if this was contributing to the lock ups but it can't hurt.

 

[phillpower2]

Hello Hickory,

See the second update down in your screenshot (KB5001330) this has been causing issues the world over and so much so that Microsoft has released an emergency patch, see PCHF feed here and BC info here deal with this above all else for now.

I also did a little digging on the z490 board and disabled MCE (in MSI this is known as Turbo Enhanced and Intel C state in BIOS. I did this as the MCE was know to clock the CPU above Intel's own recommended boost settings for longer to make the board look better to consumers - which apparently can cause stability issues.

I also found that C state for some reason kept the CPU clocked at 4.7GHZ pretty much the whole time, even at idle, it was supposed to reduce power consumption at idle. Disabling it means the CPU runs lower at idle, 800mhz and up, and also has reduced core temps significantly.

No idea if this was contributing to the lock ups but it can't hurt.

On the contrary. it is not helpful when receiving assistance on any tech forum if you go off and do your own thing, helpers will not know if their suggestions have helped and worse case scenario should you damage your computer a blame game could ensue and I for one will not put myself at risk of that.

 

[Hickory]

Hello Hickory,

See the second update down in your screenshot (KB5001330) this has been causing issues the world over and so much so that Microsoft has released an emergency patch, see PCHF feed here and BC info here deal with this above all else for now.


On the contrary. it is not helpful when receiving assistance on any tech forum if you go off and do your own thing, helpers will not know if their suggestions have helped and worse case scenario should you damage your computer a blame game could ensue and I for one will not put myself at risk of that.

Thanks again for the help, I've checked the links you sent me and if I am understanding things correctly the KIR has been successful as I have the registry entry mentioned in the article.

As for going off and making changes off my own back, I appreciate your position and I can only apologise. I'm used to trying to fix things myself and admittedly hadn't considered impacts on your advice etc. I am happy to undo the changes that I made if you would prefer as I certainly don't want to muddy the waters or make you feel at risk after all the help you've given me so far.

Edit: noticed the MTB file did not attach to my previous post.

 

[phillpower2]

Nothing wrong with troubleshooting on your own ** but it is always best to be done first, the steps made a note of and the info then provided to any tech forum you post on should you not be able to resolve the issue yourself.

Any repeat of the issue can you post a new MTB log and Speccy url so that we can start afresh.

You are welcome btw

** One of the reasons people should conclude their threads when they are resolved is so that people with the same issue can more easily find a solution to their problem using a Google search.

 

[Hickory]

Nothing wrong with troubleshooting on your own ** but it is always best to be done first, the steps made a note of and the info then provided to any tech forum you post on should you not be able to resolve the issue yourself.

Any repeat of the issue can you post a new MTB log and Speccy url so that we can start afresh.

You are welcome btw

** One of the reasons people should conclude their threads when they are resolved is so that people with the same issue can more easily find a solution to their problem using a Google search.

Understood I would always report back any fixes I find but will run any suggestions past here before I make any other changes on my own.

New Speccy: http://speccy.piriform.com/results/6QgcuCEtpDdjWRRnHE11XCH

Edit: It doesn't seem to be letting me attach the MTB log.

 

[phillpower2]

By posting the new Speccy url and trying to attach a MTB log does that mean that the issue has happened since my reply #9.

Not sure what is going on with you not being able to attach the log but have gone back to your previous thread and deleted the Sysnative file to see if it frees up you upload amount limit, push comes to shove you could either upload the MTB log to another source or copy/past the info into a reply.

 

[Hickory]

By posting the new Speccy url and trying to attach a MTB log does that mean that the issue has happened since my reply #9.

Not sure what is going on with you not being able to attach the log but have gone back to your previous thread and deleted the Sysnative file to see if it frees up you upload amount limit, push comes to shove you could either upload the MTB log to another source or copy/past the info into a reply.

Unfortunately yes, I had another power off/on last night.

I've uploaded the MTB here. Hopefully that works.

 

[phillpower2]

Your latest problems software wise are with Windows and those problems are as a result of the computer turning off before Windows has been shutdown properly, this indicates either a hardware issue or bad settings.

Try restoring the MBs default factory settings in the BIOS, they are sometimes listed as one of the following " factory defaults" "most stable" or on newer boards "optimized" please note that if you have both the "most stable" and the "optimized" options in the BIOS you should choose the most stable" option as in this instance the "optimized" settings are a form of overclocking that can cause instability.

Speccy has been showing high memory usage so once the above has been done, go into Task Manager, click on the Memory tab, click on the Processes tab, leave the computer for a minute or so to let things settle down then check what is shown to be using the most memory.

Note that when you check the memory usage you should not have anything open other than Windows and Windows Defender.

Physical Memory
Memory Usage: 36 %
Total Physical: 16 GB

Can I ask that you do not quote every reply as we have to read the full post to make sure nothing gets missed,, thanks.

 

[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.