driver verifier just flagged the driver
as doing something that is not recommended anymore.
Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
NonPagedPool (memory allocated for kernel drivers where code will run)
NonPagedPoolNx= means memory allocated but for data only ( no code execution)
Pool is just space allocated in RAM for kernel drivers. they allocated a space that could be used for code or data. This could be used for malware to attack the system. ie data is loaded into the memory and then later the cpu can be told to execute the data as code.
looks like this was done while the system plug and play was setting up the driver.
Normally you would now need to exclude this driver from the verifier.exe testing and continue testing.
use /driver.exclude DriverList
to your verifier command line
something like this:
verifier.exe /standard /all /driver.exclude amdgpio3.sys
and amdgpio3.sys will not be tested.
since the bugcheck happens in 5 seconds you will have to boot into safe mode and run the command
or run verifier.exe /reset
to turn verifier off (while in safe mode) so you can boot.
This error is not likely the error that you are looking to find. it would be considered a warning to the programmer.
note: it did look like the stack was corrupted coming out of a call
(raw stack looks reasonable so I would ignore and just look at the raw stack)
and when I look at the driver:
Wdf01000.sys (looks ok)
(microsoft antimalwar driver, maybe just need a windows update?)
was not able to read the bios info from the memory dump. Sometimes this means the the bios is really outdated. You should look at updating the bios or resetting it to defaults. BIOS makes a database of hardware that is sent to windows, this database is the starting point for the windows plug and play for configuration of the hardware.
even with a new motherboard you should update to the most current bios. Lots of bugs get fixed in bios after the product ships.
ROG STRIX X670E-I GAMING WIFI - Support (asus.com)
4 updates shown
I would not install Armoury Crate
and make sure it is turned off in BIOS.
it installs files directly from bios onto your drive during boot up. Just like a rootkit
I tried it before an just got bugcheck after bugcheck and had to turn it off in bios and manually delete the files from the drive, and remove the installer from the system task scheduler. problem keeps coming back until you get all of the install vectors cut off. (guess it might be related to the problem you are looking for)
note: asus did not put the file dates for drivers on their website, just the driver version number. This makes it hard for me to quickly see which 3rd party drivers you have installed that are out of date.
the debugger shows:
\SystemRoot\System32\drivers\mtkwl6ex.sys Fri Nov 18 00:41:05 2022
but the website shows Version 188.8.131.523 14.14 MB
without a date. they might be the same version you will not know until you download and look at the driver. (looks like the download has a driver that is two days newer than the date of the driver you have installed, looks like some newer wifi firmware patches also)
asus is not putting the dates on the websited that the patch was last updated is really bad news.
People should complain to ASUS so they change it back to make it easier to see that a update is needed.
Most oem drivers still have driver dates, Microsoft stopped using the dates and now use
build hash: this is what a microsoft timestamp looks like in the debugger:
Timestamp: 11447CC9 (This is a reproducible build file hash, not a timestamp)
this is what the oem timestamp looks like in the debugger:
Timestamp: Tue Jul 12 05:22:17 2022 (62CD6779)
modified microsoft driver often show invalid in the debugger
some modified (hacked) drivers show a zero out date and time stamp