# Any other values for parameter 1 must be individually examined.Īrg1: 0000000000041792, A corrupt PTE has been detected.
To cut a long story short, I ran a bugcheck analysis using the Windows Debug tools which threw me the following: 12: kd> !analyze -v Originally I believed perhaps that drivers were the issue, however, now I'm not so sure. I also changed my power plan on the rig from Balanced to Performance, though I don't expect this to be the cause. Besides that, it doesn't appear any different specification wise, so I'm unclear on whether this is the cause. I know that this week I plugged in a new keyboard that is different to that of my old one, and in doing so I needed to download some more drivers for it, however I went from a Roccat Aimo 120 to a Roccat Aimo 100, to which the only real difference is the fact that the 100 doesn't have a hand wrest with the keyboard. As far as I can tell, these issues began this week. So far as far as causation goes, this is the only thing throwing flags, as I've successfully performed Windows Memory Diagnostics with no issues being found, system file checks with no corruption being found, and lastly checking in on the device manager and checking all tabs to ensure nothing in there is throwing errors. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
"The system has rebooted without cleanly shutting down first.
Rom reviewing the Event Logs I can see one in there stating the following: For the past week or so I've been experiencing BSODs whenever I power on the computer first during the day after we REACH the Windows splash screen, I have no further issues, even when restarting.
0 kommentar(er)
