Only with the minidump files to identify the cause.
Yes, it will be compatible, however some motherboards are compatible with some RAM and this list can be found on the manufacturer's website.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have been getting occasional BSODs on a newly built PC, with the computer slowing down and losing fps before crashing. Normally, the computer instantly restarts after crashing, but the past two times it has crashed, it remained on the BSOD screen, allowing me to see the stop code. The first was DRIVER IQRL NOT LESS OR EQUAL, and the second was DPC WATCHDOG VIOLATION. I have run memtest86+ on my computer for over 7 hours and it passed 9 times without any errors. There is also nothing in my C:\Windows\Minidump folder, which I checked after the most recent crash.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Only with the minidump files to identify the cause.
Yes, it will be compatible, however some motherboards are compatible with some RAM and this list can be found on the manufacturer's website.
How can I get my computer to generate these minidump files then? They don't seem to generate after a crash.
With the driver verifier, but instead of doing a system restore you should disable it with the command, following the steps in the tutorial I sent before.
Sorry, are you saying I should make sure the driver verifier is off, set a system restore, turn on the driver verifier and try it again? If so, wouldn't that just lead me to the same outcome where the minidump files aren't generated and I'm just prompted to restore my computer?
If it is enabled, minidump files should be generated when the BSOD occurs.
But since you did the restore when trying to activate it, it is probably disabled and you will need to enable it again so that the files are created and then disable it by starting Windows in safe mode as I indicated in the steps above.