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

I really hope it too.

Keep me posted *Smile

 

I will keep you posted axe0, sure.
by the way you are doing such a great job here, can't thank you enough for your support.
just keep the great work going. *Wink

 

I've been running the new ram with zero issues until now.
it really seems some kind of incompability had been causing the issue with the old one.
I think it is time to mark the thread as solved, thanks to you axe0. *Wink

 

hi axe0,

could you have a short look at the log files attached?

I had a single crash with the description IRQ_NOT_LESS_OR_EQUAL right after starting a portable application from USB.

I have the feeling it could be somehow related as I use portable application quite a lot and at the same time.

 

Check for USB driver updates or try to reinstall the USB drivers (not sure if this has already been done?)
MAXIMUS VIII GENE | Moederbord | ASUS Nederland

 

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?! *sarc

 

Possibly with removing the driver and searching with WU

 

I tried but it did not find any newer driver.

I got a second BSOD of the same type a couple of minutes a go. it was actually rather a freeze with a following reboot.

maybe the previous one had nothing to do with the USB and was just coincidence. the last one right now happened while just browsing the internet. strange though that this time I also got a crash log for Java. could it be Java causing the crashes all the time as the Internet browser were involved in almost all of the crashes?!

I attached the logs and hope they give some clue.

 

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 started the verifier now and will let it run for at least 48 hours as suggested.
while configuring I realized that I have very few non Microsoft drivers installed at all.
basically Intel, nVidia and Realtek - that's how I like it, slim and clean - no mess.
what I don't like is that no matter that I still got this BSOD.

by the way last week there was a new bios release for my motherboard which I downloaded and installed.
no issues so far with the ram, same configuration as with the previous bios.

 

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. *sarc

 

hi axe0,
I stopped the Verifier and did not have any BSOD since.
should I mark the thread as "solved" for now and just keep my eyes open just in case?

 

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

 

axe0, this issue is really driving me crazy.
just some hours after marking the thread as solved I got a complete system freeze with a following reboot.
the BSOD seems to be of the same type IRQ_NOT_LESS_OR_EQUAL, I attached the log files.
I was just listening to music over portable AIMP and playing a small flashgame in Chrome.
what's going on here? I really don't understand that - how can an issue be so random and cluless. *sarc