Intermittent BSOD's with different stops codes

[bakury162]

Have been having blue screens every few weeks over the last few months they are few and far between but they are still annoying and i haven't been able to solve them. Recently when trying to update the game fortnite i have been consistently crashing during the patch install with stop codes matching the intermittent problems i had before.
These were the most common stop codes i received from the intermittent stops and the install stops.
- IRQL not less than or equal
- PFN list corrupt
There were 1 or 2 others but i do not recall them as these were about 80% of them.

This is the most recent minidump from the failed patch install
google drive

From just looking around on google i have done dskchk as well as a memory diagnostic. To the best of my knowledge my drivers are up to date. I also tried running driver verifier for all drivers but a few minutes after signing into windows i would crash to
- Driver page fault in freed special pool
- what failed rzudd.sys
This was also rather scary as if i did not very quickly turn of the verifier it would loop and i read it could brick your motherboard.
Any help with this would be greatly appreciated.

 

[johnbl]

the system bugchecked because virtual memory that was being freed was corrupted. I think a driver has overwritten another drivers data which caused the crash.

I would start cmd.exe or powershell as an admin then run
verifier.exe /all /standard
you should also change the memory dmp type from minidump to a kernel memory dump.
then reboot the system
be sure you know how to get into safe mode so you can turn off verifier if you get a bugcheck during the next boot.
when you get the bugcheck hopefully verifier will have caught the driver that corrupted the data.
assuming the data was corrupted because the memory address looked like a header size rather than a kernel memory address.

I would also remove this driver:
AMD Overdrive; also in EasyTune6 (overclocking driver)
AODDriver2.sys Tue Oct 29 17:58:36 2013
(not a likely cause of this bugcheck)

be sure to update the drivers from your motherboard vendors website.
SATA and cpu chipset drivers could cause this problem.

 

[bakury162]

All right after turning on the verifier and setting the dump to kernel memory dump i attempted the install which crashed to pfn list corrupt but it would not get past 0% for the dump files and i left it on the blue screen for ~10 min. After i tried again with the same code and no progress. The third time just after i opened chrome and not intentionally trying to crash i got the
- Driver Page Fault in Freed Special Pool
- What Failed Rzudd.sys
This did go to 100% on the dump but after going into my files there was no dump file.

As for removing the driver you mentioned i am not sure how to go about that. From looking around every place says to remove via device manager or from the add or remove programs but it does not reside in either of these places.

 

[johnbl]

make sure you look in the correct place for the file. when you change the dump type to kernel the file location and name gets changed to
c:\windows\memory.dmp

try and update the Razer Rzudd Engine Driver
http://drivers.razersupport.com/index.php?_m=downloads&_a=view&_m=downloads&_a=view

some of the older versions had a design flaw. the app assumed the driver memory never would moved.
(bad assumption but it works most of the time if you reboot often, now that most machines sleeps, the memory eventually gets moved or compressed and app ends up modifying some other drivers data and causes a bugchceck)

All right after turning on the verifier and setting the dump to kernel memory dump i attempted the install which crashed to pfn list corrupt but it would not get past 0% for the dump files and i left it on the blue screen for ~10 min. After i tried again with the same code and no progress. The third time just after i opened chrome and not intentionally trying to crash i got the
- Driver Page Fault in Freed Special Pool
- What Failed Rzudd.sys
This did go to 100% on the dump but after going into my files there was no dump file.

As for removing the driver you mentioned i am not sure how to go about that. From looking around every place says to remove via device manager or from the add or remove programs but it does not reside in either of these places.