Random BSOD - ntoskrnl.exe. IRQL_NOT_LESS_OR_EQUAL

Page 2 of 2 FirstFirst 12

  1. Posts : 7
    Win 10
    Thread Starter
       #11

    I am no overclock guru. Could this be an overclocking issue? I am new to these techniques, and I may not have stress tested enough. I have dropped my gpu's setting to default in After burner, and am currently letting kombuster run with a minor overclock. I would love for the BSODs be to my over clocking settings.
      My Computer

  2. philc43's Avatar
    Posts : 4,998
    64bit Win 10 Pro ver 20H2 Build 19042.868 and W10 Insider Preview Build 21343
       #12

    Yes, it could be all down to overclocking but I did not see evidence that this was the cause other than a 4.8GHz setting. However, we always ask people to remove overclocking when troubleshooting because it is a common cause of BSOD. Overclocking is not straightforward and needs to be approached carefully, a step at a time.
      My Computers


  3. Posts : 7
    Win 10
    Thread Starter
       #13

    Ok, thanks for that. Truth be told, this was my first foray into any sort of over clocking, and I specifically asked the initial setup by the technician to give me something that overclocks a bit but that would be stable. He said 4.8 and the RAM settings would do that, but not be problematic. My GPU settings, too, were quite low. Anyway, I assumed the BSODs were due to something else because the machine can run perfectly for several days, while under load. I assumed an overclock problem would be seen once the CPU or GPU is stressed. I guess you can close this thread, and if I see another BSOD, I will remove even the meager overclocking I am doing now, and try again.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:33.
Find Us




Windows 10 Forums