Are the BSoDs causing instability?
Are the BSoDs causing instability?
Generally, when testing my RAM OC, it often fails at pass three or four. After four attempts or a complete run, consider trying other stress tests. Record any errors that occur.
To improve stability, set the BIOS to default and enable XMP for your RAM. Run memtest86 to check if the RAM performs well with standard CPU speeds. If your CPU is unstable, you may encounter RAM errors.
Once stable, proceed with overclocking the CPU. Some motherboards might interfere with memtest results.
UPDATE:
I did run a memtest and everything passed fine.
HOWEVER, and this might sound a bit weird to you guys, cause it sure did to me.
A lot of people told me the issue could be software related, so i started digging a bit. I looked in my eventlog and found critical warnings about a HID-compliant Headset causing issues. And the timings on those critical warnings was exactly the same timings I had BSoDs.
When I opened Device Manager and checked HID-Compliant Headset, it had a yellow exclamationmark. I tryid updating it, but was fully updated. However, deactivating it and activating it, removed the yellow exclamationmark.
I now don't see any critical warnings in eventlog and haven't experienced any BSoD's the last 32 hours so far.
I do however still get "warnings" about
"The driver \Driver\WudfRd failed to load for the device HID\VID_0951&PID_16A4&MI_03&Col02\7&1c94fa2&0&0001."
HID/VID_0951 is "HID-Compliant Headset".
I also researched abit about HID-Compliant Headset issues, and found a lot of people having same issues as me, due to this. And from my understanding, it is caused by my HyperX Cloud 2 headset for some reason.
By now, HyperX havent found a working solution, and as they said "are waiting for windows to come with an update that will sort the HID issue".
I would take the device out of the system and check if the problems disappear, though I question it. I’m not sure.
So what you're proposing is to try a different headset and check if the warnings continue or not? I mean, from what I found online, no one else seems to have experienced this problem except those using a Hyperx headset. But it's possible it might still happen with another headset as well.