Different BSOD during gaming
Different BSOD during gaming
In anticipation of assistance, these recent months my computer began behaving oddly while playing games, as if it would abruptly switch to the desktop via "alt tab." Several programs would crash while the game continued running. I reformatted the system, but after a week I started encountering random BSODs during gaming, beginning at the first 30 minutes and then restarting the PC, which would remain unresponsive for hours. Now it mostly fails within an hour, even when leaving a game idle and triggering various error codes.
I attempted to update drivers, ran chkdsk, applied the default BIOS settings (never overclocked), used memtest, performed OCCT with stress tests lasting up to 60 minutes—everything was fine except for the power test, where CPU temperatures started at 40°C and gradually dropped to 25°C, then decreased rapidly, reaching around 30,000 errors before causing a crash or triggering a BSOD.
The error codes observed were:
IRQL_NOT_LESS_OR_EQUAL
ATTEMPTED_WRITE_TO_READONLY_MEMORY
FAULTY_HARDWARE_CORRUPTED_PAGE
MODE_EXCEPTION_NOT_HANDLED
PAGE_FAULT_IN_NONPAGED_AREA
System details:
Motherboard: ROG STRIX X370-F
CPU: AMD Ryzen 7 1700
GPU: GeForce Nvidia GTX 1070
RAM: 2x8GB at 3000MHz (operating at 2133hz)
SSD: SanDisk 255GB
HDD: WD 1TB - Toshiba 1TB
PSU: XFX XT 600W
I also uploaded my dump files for reference:
https://www.mediafire.com/file/k3lgh00ek...p.rar/file
Hi, I processed the dump files using the debugger and received these details:
https://jsfiddle.net/eh8fsw3k/show
This link is intended for anyone assisting. You don’t need to open it; running the fiddle is safe as per the page instructions.
Spoiler:
Dump File Results
File information:
090921-7859-01.dmp (Sep 9 2021 - 09:28:40)
Bugcheck:
IRQL_NOT_LESS_OR_EQUAL (A)
Likely due to memory corruption (Process: CpuOcct64.exe)
Uptime:
0 Day(s), 0 Hour(s), 16 Min(s), 39 Sec(s)
File information:
090821-8687-01.dmp (Sep 8 2021 - 13:24:03)
Bugcheck:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
download this and execute it on the Sandisk SSD -
https://www.techspot.com/downloads/5363-...olkit.html
this seems to point to a page file on the SSD
i can ask a friend to convert dumps, but if it's hardware it might point to wrong causes
some of these could be drivers, not usually hardware issues
wait to observe what dumps indicate. He could respond within the next few hours.
If I can't identify a clear reason, I'll examine which drivers need replacement.
Hi, I processed the dump files using the debugger and received these details:
https://jsfiddle.net/eh8fsw3k/show
This resource is intended for anyone wishing to assist. You don’t need to open it; simply running the fiddle is safe as per the instructions.
Spoiler:
Dump File Results
File information:
090921-7859-01.dmp (Sep 9 2021 - 09:28:40)
Bugcheck:
IRQL_NOT_LESS_OR_EQUAL (A)
Likely due to:
memory_corruption (Process: CpuOcct64.exe)
Duration:
0 Day(s), 0 Hour(s), 16 Min(s), 39 Sec(s)
File information:
090821-8687-01.dmp (Sep 8 2021 - 13:24:03)
Bugcheck:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver alerts:
*** WARNING: Timestamp verification failed for nvlddmkm.sys
Possible cause:
memory_corruption (Process: System)
Duration:
0 Day(s), 15 Hour(s), 18 Min(s), 47 Sec(s)
File information:
090721-8218-01.dmp (Sep 7 2021 - 19:25:10)
Bugcheck:
KERNEL_SECURITY_CHECK_FAILURE (139)
Possible cause:
memory_corruption (Process: WerFault.exe)
Duration:
0 Day(s), 0 Hour(s), 00 Min(s), 16 Sec(s)
File information:
090721-7750-01.dmp (Sep 7 2021 - 19:34:33)
Bugcheck:
ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Possible cause:
memory_corruption (Process: NVIDIA Share.exe)
Duration:
0 Day(s), 0 Hour(s), 08 Min(s), 55 Sec(s)
The listed dump files had no data, indicating they are invalid:
090721-12359-01.dmp
Note: The GPU tweaking driver "iomap64.sys" was detected on your system. (AI Suite or GPU Tweak 2)
The nvlddmkm.sys file relates to a NVIDIA graphics card driver. Several actions can help resolve this issue. Consider performing a complete uninstall via DDU in Safe Mode, then reinstall the driver (more details available). Alternatively, update to the newest driver version. You may also try one of the three most recent drivers released by NVIDIA. Drivers can be found at:
http://www.nvidia.com/
or enable Windows Update to automatically download the appropriate driver, which might be an older or improved version.
Possible motherboard information:
https://rog.asus.com/us/motherboards/rog...ing-model/
There is a BIOS update available for your system. You are currently using version 0401, while newer versions exist (e.g., 5606).
Please wait for further guidance before proceeding.
Important: Ensure you are linking to the correct motherboard. Updating BIOS can be risky—avoid doing so during power outages or severe weather.
This information may help others assist you. More details will likely come from someone else.
Please stay tuned for additional responses.
Good luck.
2nd Error points to Nvidia drivers; run DDU as recommended.
4th error victim is Nvidia, but the dumps suggest it might have caused itself, making Nvidia the actual culprit.
Is this a MSI GPU? Because this can overclock cards:
Jan 19 2020
MsIo64.sys
MSI Gaming App driver
I don't think it's part of afterburner—it could clash with Nvidia drivers.
Since it's an Asus motherboard, I assume it's also included in the Armory crate now.
Consider updating chipset drivers:
https://www.amd.com/en/support/chipsets/...t-am4/x370
I don't believe it's an MSI GPU. After running DDU and rolling back to the nvidia 471.41 driver, everything seems fine. Games stopped showing BOSD but would crash less for those under stress. The event viewer indicates that nvwgf2umx.dll is likely the cause. Some users reported NVIDIA GeForce Experience being involved, though I'm not sure. I'll try updating chipset drivers just in case.
The name reveals the origin of the software. Nvidia D3D10 driver. Direct3D documentation available at the provided link. It uses the GPU and communicates with DirectX. If issues persist, try removing the MSI driver using this method. Clearing the tick next to its name will halt it at startup. You can also install drivers without using GeForce Experience if possible.
Sure thing, anyway. Thanks for getting rid of those blue screens, a lot of thanks to you all.