BSOD with memory management error stop code

[posterboi]

hello,

I have tried most of what I have read on here and on google... I have also took my pc to tech and they couldn't figure out the problem.

They just moved my ssd and organized some cables and moved my fans, and said that it should be good.

it hasn't fixed my issue im getting 4 bsod stop codes:

• 
  Memory Management
  IRQL Not Less or Equal
  Badpool header
  kernel security check

got a new stop code just now I was downloading overwatch and got * attempted write to read only memory


everytime I install a game on steam my pc crashes half way through the installation, it says its collecting info and restart but it never does its always stuck on 100% and bsod screen.
please help.






Specs
-
Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s)
-
GTX 1080 Ti
-
32 GB RAM Corsair
-
Motherboard
ASUSTeK COMPUTER INC. ROG MAXIMUS X HERO

MINI DMP FILE

https://1drv.ms/u/s!Ajw5WWqvIi8HgXrwDjDaqBfGw2h0

 

[scout_03]

memtest all ram stick one at the time .

 

[johnbl]

you should provide the actual files from c:\windows\minidump directory. IE put them on a cloud server like Microsoft onedrive, share the files for public access and post a link.

the bugcheck with Badpool header
will be the most interesting. generally a driver corrupts its own memory or the data in memory next to it.

you might have to run verifier in order to get the system to bugcheck at the time of the memory corruption so the bad driver can be found.

generally, if it is a memory problem the first parameter will be error code 0xc0000005
it does not hurt to update the bios and motherboard drivers then run memtest86 on its own boot image if you suspect a memory problem

 

[posterboi]

you should provide the actual files from c:\windows\minidump directory. IE put them on a cloud server like Microsoft onedrive, share the files for public access and post a link.

the bugcheck with Badpool header
will be the most interesting. generally a driver corrupts its own memory or the data in memory next to it.

you might have to run verifier in order to get the system to bugcheck at the time of the memory corruption so the bad driver can be found.

generally, if it is a memory problem the first parameter will be error code 0xc0000005
it does not hurt to update the bios and motherboard drivers then run memtest86 on its own boot image if you suspect a memory problem

This is the mini dmp file but It doesn't show the error img

https://1drv.ms/u/s!Ajw5WWqvIi8HgXrwDjDaqBfGw2h0

 

[johnbl]

memory management bugcheck with a undocumented code
0x41201
most likely going to be a problem in the code that maintains the working set.
this is the code that tracks what is in physical ram and where it is paged to in virtual memory (c:\pagefile.sys)

generally, I would:
start cmd.exe or powershell as an admin and run
dism.exe /online /clean-image /restorehealth
then run a Malwarebytes scan
then turn off the system virtual memory, reboot and turn it back on. just so you get a new pagefile.sys file created.
I would also look in the task manager and look for tasks that are installing system hacks.

I would apply the current windows update and see why the windows antivirus updata did not complete.

the debugger could not read your bios interface, generally you would want to update the bios and motherboard drivers. Or at least reset the bios to bios to defaults, reconfigure and reboot.

it looks like windows processor specific microcode patches are not being loaded for some reason.
make sure windows updates are not being blocked. These patches have to be loaded by bios updates from the motherboard vendor or from a windows update and fix known bugs in various CPUs

you can also get working set corruptions if the cpu is over heated or has bad overclocking or power fluctuations to certain cpu pins (or incorrect voltages set to the pins by the bios, another reason to get a bios update)


the dism.exe command above will wipe out any license hack installed. you can also use the autoruns to check to see if there is a task to reinstall a hack.



other issues:

get rid of these two drivers:
SiLib.sys Thu Jul 15 15:08:26 2010
SiUSBXp.sys Thu Jul 15 15:27:13 2010

you can use autoruns64.exe to prevent them from loading.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
find the menu item to hide Microsoft entries
then find the old usb drivers and disable them or delete the entry.
and reboot.