After removing the overclock, bluescreen issues appear.
After removing the overclock, bluescreen issues appear.
I've been working on resolving this problem for roughly a month without success. Around 8 months prior, I increased my Phenom II X6 1090t's clock speed from 3.2GHz to 3.6GHz while keeping the voltage at the standard setting, turned off turbo mode, and let it run for ten hours—initially everything seemed fine. Two months later, I tried pushing it even higher to 4.0GHz and accidentally activated ASUS' EZ mode, which caused a reboot into the BIOS with an aggressive overclock across all components. Since I'm not particularly skilled in overclocking, I reset everything and set the multiplier to 20, aiming for a 4.0GHz speed with a CPU voltage of 1.46. After running Prime for 13 hours, it functioned properly.
However, the issue started appearing during games, only in Fallout 4 at first, which I attributed to that title. It then spread to GTA 5 and Space Engine. I adjusted the CPU voltage to 1.48 and 1.5 but didn't see improvement. I returned the CPU to its original setting and tested the same games again, still encountering bluescreens. I performed an F5 and reset the BIOS, but nothing resolved the problem.
I increased the CPU voltage to 1.48 and 1.5, then reverted it back to stock and tried running the games once more, but they still displayed bluescreens. I reset the BIOS again without success. The message "MEMORY_MANAGEMENT" appeared in Fallout 4 and Space Engine, so I ran MemTest twice on both RAM sticks—no errors detected. GTA 5 also showed the "irql_not_less_or_equal" error. After removing the CMOS battery for 15 minutes, I still faced bluescreens with that warning. I ran MemTest again, but it didn't help.
I decided the issue wasn't memory-related and removed the CMOS battery once more. Now, both Fallout 4 and Space Engine would shut down my PC instead of just bluescreening. GTA 5 continues to show the same problem. It's perplexing how I can handle CPU-intensive tasks in Maya and UE4 without issues, yet once FO4 runs for five minutes it crashes my system. I'm really hoping that the accidental EZ mode click didn't harm my motherboard or RAM.
I've searched extensively but haven't found a solution. A few notes: I changed both my PSU and graphics card in November last year, which didn't seem to be the cause—the games ran smoothly at 3.6GHz stock. In January, I upgraded to Windows 10 and overclocked my GPU from its stock 1040MHz core and 1500MHz memory clock to 1125MHz on the core and 1625MHz on VRAM, with a power limit of 20%. My CPU remains at stock speed. Any advice would be greatly appreciated.
The opencl.dll appears to be functioning properly in Windows 10. This issue seems to occur occasionally, likely due to Geforce drivers detecting file corruption and overwriting them. Following a driver update, Nvidia drivers may repeat this behavior. Are you noticing any shutdowns? If so, I’d like to check temperatures or the power supply unit, even though you mentioned the PC is new. Do you have any log files in Event Viewers or service issues reported?
You might have altered OS files. Consider rolling back some Windows updates and possibly restoring the GPU to its original state until the issue is resolved. Running an SFC /scannow could also help verify the system's integrity.
I installed my GPU on stock and ran a scan which only detected opencl.dll as being damaged. GTA 5 now operates for about 15 minutes instead of the usual 5 minutes before my PC would shut down. FO4 is currently uninstalled at this time. Tomorrow I plan to test my PC with an extra RAM stick I have on hand, just in case that's the problem.
The opencl.dll appears to be functioning properly in Windows 10. This issue seems to occur occasionally, likely due to Geforce drivers detecting file corruption and overwriting them. Following a driver update, Nvidia drivers may repeat this behavior. Are you noticing any shutdowns? If so, I’d like to check temperatures or the power supply unit, even though you mentioned the PC is new. Do you have any log files in Event Viewers or service issues?