BSOD - ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows 10 Pro 64bit...

all the motherboard drivers are up to date as of now.

regarding USB, Asus provides a separate driver only for the ASMedia USB 3.1 Controller.
it features 2 USB 3.1 ports located at back panel, as I don't use this controller at all I disabled it in the bios.
thus I did not install the driver for that controller.

the rest of the USB is just controlled by the Intel Z170 Express chipset, a total of 8 USB 3.0 ports.
I'm mostly using 3 of them, except the mouse and keyboard ones, one on the back panel for my portable applications flash drive and 2 on the front panel for temporary data transfer. I already installed the Intel chipset software which was not updated at Asus since last year.

looking at the Device Manager I see that some USB related entries use a Microsoft USB driver, which is quite old.
some others use a more recent one, all installed with the Windows 10 installation I assume.
any idea how to change that?!

Possibly with removing the driver and searching with WU

Try driver verifier again please.

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 follow this tutorial to run driver verifier.

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 when you have a bluescreen, whatever 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 in safe mode driver verifier, 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.

I would ask you to remove the 'marked as solved' sign in the title of the thread.

ok, I had left it as solved because the BSODs were of different kinds but the the real cause maybe still the same.
by the way I'm running driver verifier for almost 48 hours now and no issues at all, exactly like last time.

should I let it run at least some additional 24 hours prior stopping it?


note: as of now Driver Verifier is running for 48 hours + 24hours extra and no issues so ı'm stopping it now.
I'm cluless about the situation, really.

Yep to both questions, sounds like it is gone but always keep an eye open for it :)