New PC issues are happening again – maybe I caused something worse.
New PC issues are happening again – maybe I caused something worse.
Okay! Updated the setup, reinstalled Windows. Experienced crashes with both RAM and STICK1 in A2, but succeeded with STICK2 in A2. Seems I should probably buy new RAM. Really surprised to see it fail after less than two years, even though I kept it at 6000mhz most of the time. Wonder if I’m still covered under warranty. Also curious about whether it might have failed earlier when running alongside an AM5 chip.
Download and execute memtest prior to confirming your memory is dead.
Memtest86+ is a sophisticated, free, open-source, self-contained memory tester for 32- and 64-bit systems (supports UEFI & BIOS).
www.memtest.org
Will proceed with the plan. Testing both sticks together might be more efficient, but if needed, focusing on A2 followed by B2 could work. Whether to clear CMOS depends on the specific procedure.
Start from a USB drive you plan to create. Perform tests in pairs and individually. I would run the process using default settings without XMP/DOCP profiles, at standard speed.
some third-party driver was communicating with gameflt.sys (Microsoft gaming service), possibly attempting to remove an entry and encountering a bugcheck.
you are using a gaming driver:
CorsairGamingAudio64.sys Tue May 13 06:27:11 2025
the suspected driver is:
IGrWJ5zay5Vt Tue Apr 1 05:04:12 2025
this appears to be a computer-generated string lacking the correct .sys extension, which might indicate malware or a low-quality licensing software trying to verify a license.
notes: there are two instances of this overclock driver running:
NTIOLib_X64.sys Mon Nov 20 00:46:27 2023
NTIOLib_X64.sys Mon Nov 20 00:49:22 2023
AMDRyzenMasterDriver.sys Thu Jul 11 22:53:41 2024
AMDRyzenMasterDriver.sys Sun Apr 28 21:52:50 2024
these files are located in different directories.
in summary, I recommend downloading and running Microsoft Autoruns64.exe to remove the entries for these overclock software, and deleting them.
https://learn.microsoft.com/en-us/sysint...s/autoruns
if you're unsure about the driver, disable it temporarily, reboot, turn off system virtual memory, then restart and create a new pagefile.sys.
then retest to check for failures.
you might also want to consider disabling the Microsoft Gaming Service if it seems to interact with your audio driver.
alternatively, open Windows Device Manager, enable hidden devices, and delete any greyed-out entries.
it’s possible voicemodvad.sys was another source of error.