BSOD after Fall Creators Update [IRQL_NOT_LESS_OR_EQUAL]

First time this happened, I was playing Wolfenstein 2 and I assumed it was the game. However, this happened just 5 minutes ago again and I was on my desktop.

I'm suspicious it's my GPU undervolt on the new AMD drivers. The BSOD happened in the game on 17.10.2, and I'm currently on 17.10.3. The undervolt has never caused a BSOD before, I've only gotten driver crashes whilst in-game. I don't believe I've had a driver crash on after the Fall update.

Attachment 161333

The rules are very clear on our not being able to help you when any software is installed and illegally used. Please uninstall Techsmith.

See rule 4: No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.

I don't have Camtasia installed, that's most likely leftover files.

I did wonder. Unfortunately you get leftover files and traces of programs even when you think they are removed. Your hosts file still has the entries from the illegal use of the software. Troubleshooting is difficult as it is not known what other changes may have been made.

philc43 said:

Your hosts file still has the entries from the illegal use of the software.

I didn't think you could edit hosts on Windows 10? Regardless, I haven't had Camtasia installed in a long time (it's really quite bad, especially in todays standards). I would doubt that that's what's causing the issues, as nothing has happened until the Fall update and/or AMD's new drivers.

As there is only one crash dump file and it is not very helpful I am at a loss to find a cause for this one. I would suggest you run Driver Verifier to see if any of your drivers are misbehaving.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.