-
Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.
Why not Click Here To Sign Up and start enjoying great FREE Tech Support.
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Solved Crashes and reboots, again
- Thread starter Hickory
- Start date
- Status
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.
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
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
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.
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.
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.
System errors:
=============
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
System errors:
=============
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
Hello again, quick update.
I ran memtest86 again for 3 hours overnight and furmark this morning for almost 2 hours, no issues with either.
I've been leaving other games idle (as this seems to be the only thing which causes the issue) as I realised I'd literally only been testing since the KIR by MS and using optimised BIOS settings, with Satisfactory which had two power cycles last night. So far in different games today, for over two hours a time each, there have been no repeats.
And in case of any confusion I've described the behaviour as reboots a couple of times, which isn't quite right. More a power cycle - power off for about a second then it powers up again. Either that or the system will completely lock up, but mostly it has been the power cycles.
I ran memtest86 again for 3 hours overnight and furmark this morning for almost 2 hours, no issues with either.
I've been leaving other games idle (as this seems to be the only thing which causes the issue) as I realised I'd literally only been testing since the KIR by MS and using optimised BIOS settings, with Satisfactory which had two power cycles last night. So far in different games today, for over two hours a time each, there have been no repeats.
And in case of any confusion I've described the behaviour as reboots a couple of times, which isn't quite right. More a power cycle - power off for about a second then it powers up again. Either that or the system will completely lock up, but mostly it has been the power cycles.
Thanks for the clarification but in all honesty how you described it did give the impression that you meant the PC powered off and then back on, the Windows error that is being reported also suggests that it was power related, for now we will have to wait and see if it happens again I`m afraid.
Hello again and thanks for the continuing input. It's been issue free since my last update. Including games prone to the power cycles /freezes before.
It's a little confusing but I'll take it. I will start to re-enable services etc as per your suggestion previously, but this is likely to be very slow paced as I'm paranoid of further issues
I'll report back any further crashes and how I'm getting on.
It's a little confusing but I'll take it. I will start to re-enable services etc as per your suggestion previously, but this is likely to be very slow paced as I'm paranoid of further issues
I'll report back any further crashes and how I'm getting on.
Happy Bank Holiday
Update of sorts, since Friday I have had zero power cycle events but just had my third lockup.
I've enabled Steam services yesterday and Nvidia services today.
I had a lockup on Saturday, before I enabled either that I was hoping I could put down to an isolated event (in denial basically) It has been less often and more stable, but is still clearly happening. The only other thing I've changed is using the headset again.
I've attached a new Speccy and MTB. Any help you can offer I'd be incredibly grateful
Speccy
MTB
Update of sorts, since Friday I have had zero power cycle events but just had my third lockup.
I've enabled Steam services yesterday and Nvidia services today.
I had a lockup on Saturday, before I enabled either that I was hoping I could put down to an isolated event (in denial basically) It has been less often and more stable, but is still clearly happening. The only other thing I've changed is using the headset again.
I've attached a new Speccy and MTB. Any help you can offer I'd be incredibly grateful
Speccy
MTB
Your first of the latest events was caused by a problem between Google Drive and Windows, something that you have as it is reported "did not meet the Microsoft signing level requirements." this has been a consistent problem for you and is most likely Windows Defender or even Windows itself not trusting something that you are attempting to access.
A bit of Deja Vu for the latest problems by the looks of it;
RAM
16.0GB Dual-Channel Unknown @ 1066MHz This should have been manually clocked to 2933MHz after you had restored the MBs default factory settings, a small oversight that will most likely only of impacted performance but not caused the PC to behave as you describe.
Power Profile
Active power scheme: High performance Guaranteed to cause issues, any idea as to how this got changed from Balanced to High performance in Windows.
A bit of Deja Vu for the latest problems by the looks of it;
RAM
16.0GB Dual-Channel Unknown @ 1066MHz This should have been manually clocked to 2933MHz after you had restored the MBs default factory settings, a small oversight that will most likely only of impacted performance but not caused the PC to behave as you describe.
Power Profile
Active power scheme: High performance Guaranteed to cause issues, any idea as to how this got changed from Balanced to High performance in Windows.
Hello again, thanks for the ongoing help.
Honestly I've no idea what's going on with Google Drive, everything but what I mentioned above is disabled, aside from Windows services, so I'm not sure what is trying to access it, I've been unable to access it myself with the services disabled. I can uninstall this for now if you think that might help?
I didn't reset the memory speed after I reset the BIOS to factory, not so much as an oversight I was just focussed on sorting the power cycle/freezing issues first. I will go in and fix that now though.
I've no idea how the power profile ended up on High Performance but I have reset that to Balanced now.
From my end, since my previous post I've gone back into the PC to check connections and things; I noticed the PSU was only secured with one thumb screw so was loose inside the case, clearly a massive oversight on my part, there was also a power cable that may not have been all the way in, though everything was powered so that may mean nothing and a SATA power cable that could potentially have been touching the inside of the case and possibly causing shorting (a bit of a long shot) which I've tidied away.
It's been stable since my last post but I was wondering if maybe there is a PSU fault? I did come across a thread where someone was having similar problems to my own, which turned out to be the PSU. I have an older PSU I can swap in to test that theory if necessary.
Honestly I've no idea what's going on with Google Drive, everything but what I mentioned above is disabled, aside from Windows services, so I'm not sure what is trying to access it, I've been unable to access it myself with the services disabled. I can uninstall this for now if you think that might help?
I didn't reset the memory speed after I reset the BIOS to factory, not so much as an oversight I was just focussed on sorting the power cycle/freezing issues first. I will go in and fix that now though.
I've no idea how the power profile ended up on High Performance but I have reset that to Balanced now.
From my end, since my previous post I've gone back into the PC to check connections and things; I noticed the PSU was only secured with one thumb screw so was loose inside the case, clearly a massive oversight on my part, there was also a power cable that may not have been all the way in, though everything was powered so that may mean nothing and a SATA power cable that could potentially have been touching the inside of the case and possibly causing shorting (a bit of a long shot) which I've tidied away.
It's been stable since my last post but I was wondering if maybe there is a PSU fault? I did come across a thread where someone was having similar problems to my own, which turned out to be the PSU. I have an older PSU I can swap in to test that theory if necessary.
- Status