Second opinions for troubleshooting hard lockups
Could do with some second opinions about what might be behind several hard lock-ups/freezes I've been experiencing lately.
Unfortunately, I have no other symptoms to go on than that. The computer simply freezes in the middle of whatever it was doing and I have to hard-reboot. No BSODs, no error messages. Nothing.
So far I've tried running the full memory test suite (Windows10 built in, not Memtest86), which passed several times with no errors, so I'm pretty certain it's not memory related.
I've run sfc /scannow a bunch of times, and DISM.exe too, all with no corruptions or anything to be detected.
Currently, my only other hypothesis is that it maybe an overheating issue, though there is some evidence for and against this...
For:
Computer does run quite hot in general (GPU temps anyway, CPU seems pretty happy).
I've seen GPU temps in-game >80 degrees (I'm running Xfire'd XFX RX480s and they really pump out some heat).
I think I've seen hard-locks as a symptom of overheating in the past (though my memory may be wrong).
I recently had to move the PC to a more confined space and it seems to be occurring more frequently.
Against:
I would expect the GPUs to throttle before simply grinding to a halt, and this supposedly doesn't kick in until about 93 degrees.
It happens when sat idle at the desktop occaisionally (though much more frequently in game), where the load is minimal and the idle temps are about 53 on the master GPU and 38 on the second card.
I updated the Radeon drivers and it doesn't seem to have made a great deal of difference.
I think my next step will be to remove one of the GPUs in case its Xfire itself that's breaking something, or the combined heat from the 2 cards is the culprit, but if anyone has any better suggestions for things to try/ways to get some more diagnostic info, I'm all ears!
Full specs below in case it's useful:
AMD FX-9590 Octacore 4.7-5.0Ghz (stock OC) cooled w/ H100i
16GB DDR3 1600MHz CAS 8-8-8-24 Crucial Ballistix
Gigabyte 990FXA-UD5 rev 02 MOBO
2x XFX RX480 Double Dissipation Black Edition GPUs (16x/8x Crossfire)
Kingston HyperX 256 GB OS Boot drive
bios freeze power-management
|
show 3 more comments
Could do with some second opinions about what might be behind several hard lock-ups/freezes I've been experiencing lately.
Unfortunately, I have no other symptoms to go on than that. The computer simply freezes in the middle of whatever it was doing and I have to hard-reboot. No BSODs, no error messages. Nothing.
So far I've tried running the full memory test suite (Windows10 built in, not Memtest86), which passed several times with no errors, so I'm pretty certain it's not memory related.
I've run sfc /scannow a bunch of times, and DISM.exe too, all with no corruptions or anything to be detected.
Currently, my only other hypothesis is that it maybe an overheating issue, though there is some evidence for and against this...
For:
Computer does run quite hot in general (GPU temps anyway, CPU seems pretty happy).
I've seen GPU temps in-game >80 degrees (I'm running Xfire'd XFX RX480s and they really pump out some heat).
I think I've seen hard-locks as a symptom of overheating in the past (though my memory may be wrong).
I recently had to move the PC to a more confined space and it seems to be occurring more frequently.
Against:
I would expect the GPUs to throttle before simply grinding to a halt, and this supposedly doesn't kick in until about 93 degrees.
It happens when sat idle at the desktop occaisionally (though much more frequently in game), where the load is minimal and the idle temps are about 53 on the master GPU and 38 on the second card.
I updated the Radeon drivers and it doesn't seem to have made a great deal of difference.
I think my next step will be to remove one of the GPUs in case its Xfire itself that's breaking something, or the combined heat from the 2 cards is the culprit, but if anyone has any better suggestions for things to try/ways to get some more diagnostic info, I'm all ears!
Full specs below in case it's useful:
AMD FX-9590 Octacore 4.7-5.0Ghz (stock OC) cooled w/ H100i
16GB DDR3 1600MHz CAS 8-8-8-24 Crucial Ballistix
Gigabyte 990FXA-UD5 rev 02 MOBO
2x XFX RX480 Double Dissipation Black Edition GPUs (16x/8x Crossfire)
Kingston HyperX 256 GB OS Boot drive
bios freeze power-management
1
Look at this answer for strategy on isolating the cause of the problem
– Twisty Impersonator
Feb 14 '18 at 22:39
I’m not really looking for a general strategy, I’m more than happy isolating the issues by trial and error. I’m more on the lookout for any more specific suggestions anyone might have with these particular symptoms.
– Joe Healey
Feb 14 '18 at 22:43
1
You don't know what's causing the issue. You need to systematically eliminate possibilities. That's exactly what the answer I linked helps you do.
– Twisty Impersonator
Feb 14 '18 at 22:57
Yes, I realise that. I dont need help eliminating possibilities. I'm looking for specific input about whether the symptoms fit a GPU issue or whether I should look elsewhere.
– Joe Healey
Feb 14 '18 at 22:59
From the info you have gathered, it could be a GPU, but it could just as easily not be. You could try stress testing the GPU to see if that turns anything up. If not, grant me the observation that you only have a guess as to what's wrong. If it comes to a place where you feel that's indeed the case, I suggest the divide & conquer strategy previously suggested. Good luck.
– Twisty Impersonator
Feb 14 '18 at 23:06
|
show 3 more comments
Could do with some second opinions about what might be behind several hard lock-ups/freezes I've been experiencing lately.
Unfortunately, I have no other symptoms to go on than that. The computer simply freezes in the middle of whatever it was doing and I have to hard-reboot. No BSODs, no error messages. Nothing.
So far I've tried running the full memory test suite (Windows10 built in, not Memtest86), which passed several times with no errors, so I'm pretty certain it's not memory related.
I've run sfc /scannow a bunch of times, and DISM.exe too, all with no corruptions or anything to be detected.
Currently, my only other hypothesis is that it maybe an overheating issue, though there is some evidence for and against this...
For:
Computer does run quite hot in general (GPU temps anyway, CPU seems pretty happy).
I've seen GPU temps in-game >80 degrees (I'm running Xfire'd XFX RX480s and they really pump out some heat).
I think I've seen hard-locks as a symptom of overheating in the past (though my memory may be wrong).
I recently had to move the PC to a more confined space and it seems to be occurring more frequently.
Against:
I would expect the GPUs to throttle before simply grinding to a halt, and this supposedly doesn't kick in until about 93 degrees.
It happens when sat idle at the desktop occaisionally (though much more frequently in game), where the load is minimal and the idle temps are about 53 on the master GPU and 38 on the second card.
I updated the Radeon drivers and it doesn't seem to have made a great deal of difference.
I think my next step will be to remove one of the GPUs in case its Xfire itself that's breaking something, or the combined heat from the 2 cards is the culprit, but if anyone has any better suggestions for things to try/ways to get some more diagnostic info, I'm all ears!
Full specs below in case it's useful:
AMD FX-9590 Octacore 4.7-5.0Ghz (stock OC) cooled w/ H100i
16GB DDR3 1600MHz CAS 8-8-8-24 Crucial Ballistix
Gigabyte 990FXA-UD5 rev 02 MOBO
2x XFX RX480 Double Dissipation Black Edition GPUs (16x/8x Crossfire)
Kingston HyperX 256 GB OS Boot drive
bios freeze power-management
Could do with some second opinions about what might be behind several hard lock-ups/freezes I've been experiencing lately.
Unfortunately, I have no other symptoms to go on than that. The computer simply freezes in the middle of whatever it was doing and I have to hard-reboot. No BSODs, no error messages. Nothing.
So far I've tried running the full memory test suite (Windows10 built in, not Memtest86), which passed several times with no errors, so I'm pretty certain it's not memory related.
I've run sfc /scannow a bunch of times, and DISM.exe too, all with no corruptions or anything to be detected.
Currently, my only other hypothesis is that it maybe an overheating issue, though there is some evidence for and against this...
For:
Computer does run quite hot in general (GPU temps anyway, CPU seems pretty happy).
I've seen GPU temps in-game >80 degrees (I'm running Xfire'd XFX RX480s and they really pump out some heat).
I think I've seen hard-locks as a symptom of overheating in the past (though my memory may be wrong).
I recently had to move the PC to a more confined space and it seems to be occurring more frequently.
Against:
I would expect the GPUs to throttle before simply grinding to a halt, and this supposedly doesn't kick in until about 93 degrees.
It happens when sat idle at the desktop occaisionally (though much more frequently in game), where the load is minimal and the idle temps are about 53 on the master GPU and 38 on the second card.
I updated the Radeon drivers and it doesn't seem to have made a great deal of difference.
I think my next step will be to remove one of the GPUs in case its Xfire itself that's breaking something, or the combined heat from the 2 cards is the culprit, but if anyone has any better suggestions for things to try/ways to get some more diagnostic info, I'm all ears!
Full specs below in case it's useful:
AMD FX-9590 Octacore 4.7-5.0Ghz (stock OC) cooled w/ H100i
16GB DDR3 1600MHz CAS 8-8-8-24 Crucial Ballistix
Gigabyte 990FXA-UD5 rev 02 MOBO
2x XFX RX480 Double Dissipation Black Edition GPUs (16x/8x Crossfire)
Kingston HyperX 256 GB OS Boot drive
bios freeze power-management
bios freeze power-management
edited Jan 9 at 20:55
Joe Healey
asked Feb 14 '18 at 21:51
Joe HealeyJoe Healey
1116
1116
1
Look at this answer for strategy on isolating the cause of the problem
– Twisty Impersonator
Feb 14 '18 at 22:39
I’m not really looking for a general strategy, I’m more than happy isolating the issues by trial and error. I’m more on the lookout for any more specific suggestions anyone might have with these particular symptoms.
– Joe Healey
Feb 14 '18 at 22:43
1
You don't know what's causing the issue. You need to systematically eliminate possibilities. That's exactly what the answer I linked helps you do.
– Twisty Impersonator
Feb 14 '18 at 22:57
Yes, I realise that. I dont need help eliminating possibilities. I'm looking for specific input about whether the symptoms fit a GPU issue or whether I should look elsewhere.
– Joe Healey
Feb 14 '18 at 22:59
From the info you have gathered, it could be a GPU, but it could just as easily not be. You could try stress testing the GPU to see if that turns anything up. If not, grant me the observation that you only have a guess as to what's wrong. If it comes to a place where you feel that's indeed the case, I suggest the divide & conquer strategy previously suggested. Good luck.
– Twisty Impersonator
Feb 14 '18 at 23:06
|
show 3 more comments
1
Look at this answer for strategy on isolating the cause of the problem
– Twisty Impersonator
Feb 14 '18 at 22:39
I’m not really looking for a general strategy, I’m more than happy isolating the issues by trial and error. I’m more on the lookout for any more specific suggestions anyone might have with these particular symptoms.
– Joe Healey
Feb 14 '18 at 22:43
1
You don't know what's causing the issue. You need to systematically eliminate possibilities. That's exactly what the answer I linked helps you do.
– Twisty Impersonator
Feb 14 '18 at 22:57
Yes, I realise that. I dont need help eliminating possibilities. I'm looking for specific input about whether the symptoms fit a GPU issue or whether I should look elsewhere.
– Joe Healey
Feb 14 '18 at 22:59
From the info you have gathered, it could be a GPU, but it could just as easily not be. You could try stress testing the GPU to see if that turns anything up. If not, grant me the observation that you only have a guess as to what's wrong. If it comes to a place where you feel that's indeed the case, I suggest the divide & conquer strategy previously suggested. Good luck.
– Twisty Impersonator
Feb 14 '18 at 23:06
1
1
Look at this answer for strategy on isolating the cause of the problem
– Twisty Impersonator
Feb 14 '18 at 22:39
Look at this answer for strategy on isolating the cause of the problem
– Twisty Impersonator
Feb 14 '18 at 22:39
I’m not really looking for a general strategy, I’m more than happy isolating the issues by trial and error. I’m more on the lookout for any more specific suggestions anyone might have with these particular symptoms.
– Joe Healey
Feb 14 '18 at 22:43
I’m not really looking for a general strategy, I’m more than happy isolating the issues by trial and error. I’m more on the lookout for any more specific suggestions anyone might have with these particular symptoms.
– Joe Healey
Feb 14 '18 at 22:43
1
1
You don't know what's causing the issue. You need to systematically eliminate possibilities. That's exactly what the answer I linked helps you do.
– Twisty Impersonator
Feb 14 '18 at 22:57
You don't know what's causing the issue. You need to systematically eliminate possibilities. That's exactly what the answer I linked helps you do.
– Twisty Impersonator
Feb 14 '18 at 22:57
Yes, I realise that. I dont need help eliminating possibilities. I'm looking for specific input about whether the symptoms fit a GPU issue or whether I should look elsewhere.
– Joe Healey
Feb 14 '18 at 22:59
Yes, I realise that. I dont need help eliminating possibilities. I'm looking for specific input about whether the symptoms fit a GPU issue or whether I should look elsewhere.
– Joe Healey
Feb 14 '18 at 22:59
From the info you have gathered, it could be a GPU, but it could just as easily not be. You could try stress testing the GPU to see if that turns anything up. If not, grant me the observation that you only have a guess as to what's wrong. If it comes to a place where you feel that's indeed the case, I suggest the divide & conquer strategy previously suggested. Good luck.
– Twisty Impersonator
Feb 14 '18 at 23:06
From the info you have gathered, it could be a GPU, but it could just as easily not be. You could try stress testing the GPU to see if that turns anything up. If not, grant me the observation that you only have a guess as to what's wrong. If it comes to a place where you feel that's indeed the case, I suggest the divide & conquer strategy previously suggested. Good luck.
– Twisty Impersonator
Feb 14 '18 at 23:06
|
show 3 more comments
2 Answers
2
active
oldest
votes
So after some swapping in and out of components, monitoring hardware statuses and various checks, I pretty much ruled out any hardware issues.
Searching around further on the web and speaking to some friends of mine, it seems many people have been experiencing hard lockups lately, and with increased frequency. There is some suggestion that it is due to the Windows Fall Creators update. (I'm on build 16299.248)
It seemed that this was therefore a software issue.
I made 2 changes in particular that seem to have (touch wood) helped - though much more prolonged testing is needed on my part:
Temp
I emptied the temp folder following the instructions of a thread I found elsewhere. I did this in concert with the step below, so I'm not sure if this explicitly had anything to do with any improvement - it may just be coincidental.
Simply type temp in an open Run box, and empty the contents. Try to quit as many applications as possible so that as few files in the folder are in active use as they can be.
Paging
I suspect this is where the key lies, and given the symptoms, is probably not unlikely.
On inspecting the paging file size/usage, the file was approximately 2.5GB for my machine, and was entirely set to be determined automatically. This seemed on the low side, especially given that my PC has 16GB RAM.
I overruled the automatic settings, and set a custom minimum size of 1000MB (it complains if its lower than 800MB anyway), and set the maximum to 1.5x my RAM size for now (24000MB) for my C: drive. This is probably excessive, but I'll tweak it later.*
*NB: don't do this if your boot drive doesn't have sufficient space to allow it.
My paging filesize has now increased to a little over 4GB, so I suspect this could well have been the culprit all along.
add a comment |
A follow up to my previous posts, as I think I finally resolved the issue.
I'm posting this as a second answer as my first one did seem to help somewhat, so I don't think its 'wrong' per se.
There are reports online of Vishera series CPUs in particular, suffering from issues with their intelligent power management (though unfortunately, I can't find the specific link that tipped me off now).
I won't post specific instructions as it no doubt varies by board/BIOS, but since changing the following BIOS settings, I have experienced exactly 0 crashes in several months:
- Disable
C6 Power state
- Disable
Cool & Quiet
- Disable
HPC Mode
I think C6 Power State is the particular culprit, but I changed a few things and it's been stable ever since so I didn't really have the inclination to go back and do it one by one, but I'd start with C6 perhaps.
Hope this helps someone else!
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1295043%2fsecond-opinions-for-troubleshooting-hard-lockups%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
So after some swapping in and out of components, monitoring hardware statuses and various checks, I pretty much ruled out any hardware issues.
Searching around further on the web and speaking to some friends of mine, it seems many people have been experiencing hard lockups lately, and with increased frequency. There is some suggestion that it is due to the Windows Fall Creators update. (I'm on build 16299.248)
It seemed that this was therefore a software issue.
I made 2 changes in particular that seem to have (touch wood) helped - though much more prolonged testing is needed on my part:
Temp
I emptied the temp folder following the instructions of a thread I found elsewhere. I did this in concert with the step below, so I'm not sure if this explicitly had anything to do with any improvement - it may just be coincidental.
Simply type temp in an open Run box, and empty the contents. Try to quit as many applications as possible so that as few files in the folder are in active use as they can be.
Paging
I suspect this is where the key lies, and given the symptoms, is probably not unlikely.
On inspecting the paging file size/usage, the file was approximately 2.5GB for my machine, and was entirely set to be determined automatically. This seemed on the low side, especially given that my PC has 16GB RAM.
I overruled the automatic settings, and set a custom minimum size of 1000MB (it complains if its lower than 800MB anyway), and set the maximum to 1.5x my RAM size for now (24000MB) for my C: drive. This is probably excessive, but I'll tweak it later.*
*NB: don't do this if your boot drive doesn't have sufficient space to allow it.
My paging filesize has now increased to a little over 4GB, so I suspect this could well have been the culprit all along.
add a comment |
So after some swapping in and out of components, monitoring hardware statuses and various checks, I pretty much ruled out any hardware issues.
Searching around further on the web and speaking to some friends of mine, it seems many people have been experiencing hard lockups lately, and with increased frequency. There is some suggestion that it is due to the Windows Fall Creators update. (I'm on build 16299.248)
It seemed that this was therefore a software issue.
I made 2 changes in particular that seem to have (touch wood) helped - though much more prolonged testing is needed on my part:
Temp
I emptied the temp folder following the instructions of a thread I found elsewhere. I did this in concert with the step below, so I'm not sure if this explicitly had anything to do with any improvement - it may just be coincidental.
Simply type temp in an open Run box, and empty the contents. Try to quit as many applications as possible so that as few files in the folder are in active use as they can be.
Paging
I suspect this is where the key lies, and given the symptoms, is probably not unlikely.
On inspecting the paging file size/usage, the file was approximately 2.5GB for my machine, and was entirely set to be determined automatically. This seemed on the low side, especially given that my PC has 16GB RAM.
I overruled the automatic settings, and set a custom minimum size of 1000MB (it complains if its lower than 800MB anyway), and set the maximum to 1.5x my RAM size for now (24000MB) for my C: drive. This is probably excessive, but I'll tweak it later.*
*NB: don't do this if your boot drive doesn't have sufficient space to allow it.
My paging filesize has now increased to a little over 4GB, so I suspect this could well have been the culprit all along.
add a comment |
So after some swapping in and out of components, monitoring hardware statuses and various checks, I pretty much ruled out any hardware issues.
Searching around further on the web and speaking to some friends of mine, it seems many people have been experiencing hard lockups lately, and with increased frequency. There is some suggestion that it is due to the Windows Fall Creators update. (I'm on build 16299.248)
It seemed that this was therefore a software issue.
I made 2 changes in particular that seem to have (touch wood) helped - though much more prolonged testing is needed on my part:
Temp
I emptied the temp folder following the instructions of a thread I found elsewhere. I did this in concert with the step below, so I'm not sure if this explicitly had anything to do with any improvement - it may just be coincidental.
Simply type temp in an open Run box, and empty the contents. Try to quit as many applications as possible so that as few files in the folder are in active use as they can be.
Paging
I suspect this is where the key lies, and given the symptoms, is probably not unlikely.
On inspecting the paging file size/usage, the file was approximately 2.5GB for my machine, and was entirely set to be determined automatically. This seemed on the low side, especially given that my PC has 16GB RAM.
I overruled the automatic settings, and set a custom minimum size of 1000MB (it complains if its lower than 800MB anyway), and set the maximum to 1.5x my RAM size for now (24000MB) for my C: drive. This is probably excessive, but I'll tweak it later.*
*NB: don't do this if your boot drive doesn't have sufficient space to allow it.
My paging filesize has now increased to a little over 4GB, so I suspect this could well have been the culprit all along.
So after some swapping in and out of components, monitoring hardware statuses and various checks, I pretty much ruled out any hardware issues.
Searching around further on the web and speaking to some friends of mine, it seems many people have been experiencing hard lockups lately, and with increased frequency. There is some suggestion that it is due to the Windows Fall Creators update. (I'm on build 16299.248)
It seemed that this was therefore a software issue.
I made 2 changes in particular that seem to have (touch wood) helped - though much more prolonged testing is needed on my part:
Temp
I emptied the temp folder following the instructions of a thread I found elsewhere. I did this in concert with the step below, so I'm not sure if this explicitly had anything to do with any improvement - it may just be coincidental.
Simply type temp in an open Run box, and empty the contents. Try to quit as many applications as possible so that as few files in the folder are in active use as they can be.
Paging
I suspect this is where the key lies, and given the symptoms, is probably not unlikely.
On inspecting the paging file size/usage, the file was approximately 2.5GB for my machine, and was entirely set to be determined automatically. This seemed on the low side, especially given that my PC has 16GB RAM.
I overruled the automatic settings, and set a custom minimum size of 1000MB (it complains if its lower than 800MB anyway), and set the maximum to 1.5x my RAM size for now (24000MB) for my C: drive. This is probably excessive, but I'll tweak it later.*
*NB: don't do this if your boot drive doesn't have sufficient space to allow it.
My paging filesize has now increased to a little over 4GB, so I suspect this could well have been the culprit all along.
answered Feb 19 '18 at 23:39
Joe HealeyJoe Healey
1116
1116
add a comment |
add a comment |
A follow up to my previous posts, as I think I finally resolved the issue.
I'm posting this as a second answer as my first one did seem to help somewhat, so I don't think its 'wrong' per se.
There are reports online of Vishera series CPUs in particular, suffering from issues with their intelligent power management (though unfortunately, I can't find the specific link that tipped me off now).
I won't post specific instructions as it no doubt varies by board/BIOS, but since changing the following BIOS settings, I have experienced exactly 0 crashes in several months:
- Disable
C6 Power state
- Disable
Cool & Quiet
- Disable
HPC Mode
I think C6 Power State is the particular culprit, but I changed a few things and it's been stable ever since so I didn't really have the inclination to go back and do it one by one, but I'd start with C6 perhaps.
Hope this helps someone else!
add a comment |
A follow up to my previous posts, as I think I finally resolved the issue.
I'm posting this as a second answer as my first one did seem to help somewhat, so I don't think its 'wrong' per se.
There are reports online of Vishera series CPUs in particular, suffering from issues with their intelligent power management (though unfortunately, I can't find the specific link that tipped me off now).
I won't post specific instructions as it no doubt varies by board/BIOS, but since changing the following BIOS settings, I have experienced exactly 0 crashes in several months:
- Disable
C6 Power state
- Disable
Cool & Quiet
- Disable
HPC Mode
I think C6 Power State is the particular culprit, but I changed a few things and it's been stable ever since so I didn't really have the inclination to go back and do it one by one, but I'd start with C6 perhaps.
Hope this helps someone else!
add a comment |
A follow up to my previous posts, as I think I finally resolved the issue.
I'm posting this as a second answer as my first one did seem to help somewhat, so I don't think its 'wrong' per se.
There are reports online of Vishera series CPUs in particular, suffering from issues with their intelligent power management (though unfortunately, I can't find the specific link that tipped me off now).
I won't post specific instructions as it no doubt varies by board/BIOS, but since changing the following BIOS settings, I have experienced exactly 0 crashes in several months:
- Disable
C6 Power state
- Disable
Cool & Quiet
- Disable
HPC Mode
I think C6 Power State is the particular culprit, but I changed a few things and it's been stable ever since so I didn't really have the inclination to go back and do it one by one, but I'd start with C6 perhaps.
Hope this helps someone else!
A follow up to my previous posts, as I think I finally resolved the issue.
I'm posting this as a second answer as my first one did seem to help somewhat, so I don't think its 'wrong' per se.
There are reports online of Vishera series CPUs in particular, suffering from issues with their intelligent power management (though unfortunately, I can't find the specific link that tipped me off now).
I won't post specific instructions as it no doubt varies by board/BIOS, but since changing the following BIOS settings, I have experienced exactly 0 crashes in several months:
- Disable
C6 Power state
- Disable
Cool & Quiet
- Disable
HPC Mode
I think C6 Power State is the particular culprit, but I changed a few things and it's been stable ever since so I didn't really have the inclination to go back and do it one by one, but I'd start with C6 perhaps.
Hope this helps someone else!
answered Jan 9 at 20:54
Joe HealeyJoe Healey
1116
1116
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1295043%2fsecond-opinions-for-troubleshooting-hard-lockups%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Look at this answer for strategy on isolating the cause of the problem
– Twisty Impersonator
Feb 14 '18 at 22:39
I’m not really looking for a general strategy, I’m more than happy isolating the issues by trial and error. I’m more on the lookout for any more specific suggestions anyone might have with these particular symptoms.
– Joe Healey
Feb 14 '18 at 22:43
1
You don't know what's causing the issue. You need to systematically eliminate possibilities. That's exactly what the answer I linked helps you do.
– Twisty Impersonator
Feb 14 '18 at 22:57
Yes, I realise that. I dont need help eliminating possibilities. I'm looking for specific input about whether the symptoms fit a GPU issue or whether I should look elsewhere.
– Joe Healey
Feb 14 '18 at 22:59
From the info you have gathered, it could be a GPU, but it could just as easily not be. You could try stress testing the GPU to see if that turns anything up. If not, grant me the observation that you only have a guess as to what's wrong. If it comes to a place where you feel that's indeed the case, I suggest the divide & conquer strategy previously suggested. Good luck.
– Twisty Impersonator
Feb 14 '18 at 23:06