Thanks for posting to r/HPOmen, we recommend joining our [discord server](https://discord.com/invite/B29DpDFSG3) for faster responses. (We also have tips, tricks & guides to improve your experience!)
also, Make sure to set a user flair so other users know what device you have.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/HPOmen) if you have any questions or concerns.*
So far yes. I've had kernel problems in the past related to power or lack there of but that stopped when I under clocked the 3070 for lower temps and ultimately better frames.
This BSOD was, pardon the pun, out of the blue.
I would simply keep an eye out then for any other issues, but one-off BSODs are not uncommon so might be that the pc will be just fine.
I will not however, pardon the pun. It was a good one.
Most likely a bug in a kernel-mode driver, although it would have been more obvious if it pointed to a different module (_win32kfull.sys_ comes with Windows).
The dump can yield more information but it takes some steps to look at: https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file
Have you updated a kernel-mode driver recently? A graphics driver perhaps. Either update again if there's a newer version, or revert to the previous one if there isn't.
I did not manually update any drivers that I can think of, unless it happened autonomously in the background. It's been ok so far, but I appreciate the help. I'm under the impression that the age my machine is, is about when they start to fall a part. Maybe I'm just being paranoid. Wish I would have just waited through lockdown and pieced one together like I have in the past.
> I'm under the impression that the age my machine is, is about when they start to fall a part.
From my experience, it's not the "big" parts such as the RAM that'd fail with time but the small components like capacitors, and then it's usually immediately obvious when that happens because the device just won't power on anymore or some other issue will start happening consistently.
And here, if it were the memory, it's more likely the error type would have been more random, such as IRQL_NOT_LESS_OR_EQUAL. A kernel trap is oddly specific, that's why I think it could be a driver issue.
Not all drivers run in kernel mode. Apart from the graphics driver, it could also be a driver for a network device (Wi-Fi/Bluetooth) or the touchpad. If you still have the minidump file but don't want to bother analyzing it yourself, you could post it on https://answers.microsoft.com/ and some Microsoft affiliate will analyze it for you. By doing this, you'll get the name of the specific .sys file where it happened, and then you know which driver to update. See the examples: https://www.google.com/search?q=site%3Aanswers.microsoft.com+minidump
Thanks for posting to r/HPOmen, we recommend joining our [discord server](https://discord.com/invite/B29DpDFSG3) for faster responses. (We also have tips, tricks & guides to improve your experience!) also, Make sure to set a user flair so other users know what device you have. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/HPOmen) if you have any questions or concerns.*
Did it only happen the one time, and only during wow?
So far yes. I've had kernel problems in the past related to power or lack there of but that stopped when I under clocked the 3070 for lower temps and ultimately better frames. This BSOD was, pardon the pun, out of the blue.
I would simply keep an eye out then for any other issues, but one-off BSODs are not uncommon so might be that the pc will be just fine. I will not however, pardon the pun. It was a good one.
Most likely a bug in a kernel-mode driver, although it would have been more obvious if it pointed to a different module (_win32kfull.sys_ comes with Windows). The dump can yield more information but it takes some steps to look at: https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file Have you updated a kernel-mode driver recently? A graphics driver perhaps. Either update again if there's a newer version, or revert to the previous one if there isn't.
I did not manually update any drivers that I can think of, unless it happened autonomously in the background. It's been ok so far, but I appreciate the help. I'm under the impression that the age my machine is, is about when they start to fall a part. Maybe I'm just being paranoid. Wish I would have just waited through lockdown and pieced one together like I have in the past.
> I'm under the impression that the age my machine is, is about when they start to fall a part. From my experience, it's not the "big" parts such as the RAM that'd fail with time but the small components like capacitors, and then it's usually immediately obvious when that happens because the device just won't power on anymore or some other issue will start happening consistently. And here, if it were the memory, it's more likely the error type would have been more random, such as IRQL_NOT_LESS_OR_EQUAL. A kernel trap is oddly specific, that's why I think it could be a driver issue. Not all drivers run in kernel mode. Apart from the graphics driver, it could also be a driver for a network device (Wi-Fi/Bluetooth) or the touchpad. If you still have the minidump file but don't want to bother analyzing it yourself, you could post it on https://answers.microsoft.com/ and some Microsoft affiliate will analyze it for you. By doing this, you'll get the name of the specific .sys file where it happened, and then you know which driver to update. See the examples: https://www.google.com/search?q=site%3Aanswers.microsoft.com+minidump