Memory Management BSOD after Windows update

[DenyingEverything]

I've been getting BSOD since last month's update like "memory management" & "Bad pool header".
i tried and checked everything (sfc,chdsk,memtest etc etc) and also updated all drivers and bios to the latest but it didn't helped.I realised the BSOD occurs mostly while watching youtube or an usb device is connected (xbox controller/ thumbdrive), or it could be totally unrelated and that i spend too much time on youtube.

My specs:
i5-6600
4x4GB G.skill ram
Gigabyte h170 d3h MB
Aorus 1080TI extreme
WD Blue 1TB
Intel 600p M.2 SSD
Asus AC68 PCI wifi card
Windows 10 Home 1703 Os Build 15063.674

Dump files:
https://www.dropbox.com/s/avy6aszd1mmlls6/101517-4187-01.dmp?dl=0
https://www.dropbox.com/s/vv77wpr9eayvc1e/101617-4593-01.dmp?dl=0
https://www.dropbox.com/s/o362a8hyk0q3mqw/101817-4609-01.dmp?dl=0

 

[johnbl]

you have a driver that has written beyond its owned memory buffer.

I would suspect this driver just because I have never seen it before.

\SystemRoot\system32\DRIVERS\jswpslwfx.sys Thu May 15 03:28:50 2008
http://www.carrona.org/drivers/driver.php?id=jswpslwfx.sys
it is listed as a usb wireless driver. if it is really dated in 2008 then it would be a suspect driver (windows vista) (debugger has been showing bogus dates)

it would be good to remove the overclocking driver until you figure out the cause of this problem.
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Fri Sep 30 05:03:17 2016

if you have a activation hack, you should also do a malware scan/rootkit scan.

problems like this can also be caused by not installing the motherboard drivers, particularly the motherboard sound driver. check the motherboard vendor for bios and driver updates.

if you still get the problem, the most direct way of inding the driver will be to:
change the memory dump type to kernel, then run cmd.exe or powershell as an admin then run
verifier.exe /standard /all
and reboot your system.

Note: be sure you know how to get into safe mode so you can turn off verifier if the system bugchecks during the next boot.
use
verifier.exe /reset

to turn off verifier, also note you have to turn it off after testing or your machine will run slowly until you do.

with verifier running and a kernel memory dump, verifier should catch the bad driver and name it in the c:\windows\memory.dmp file (kernel memory dump)

 

[DenyingEverything]

you have a driver that has written beyond its owned memory buffer.

I would suspect this driver just because I have never seen it before.

\SystemRoot\system32\DRIVERS\jswpslwfx.sys Thu May 15 03:28:50 2008
http://www.carrona.org/drivers/driver.php?id=jswpslwfx.sys
it is listed as a usb wireless driver. if it is really dated in 2008 then it would be a suspect driver (windows vista) (debugger has been showing bogus dates)

it would be good to remove the overclocking driver until you figure out the cause of this problem.
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Fri Sep 30 05:03:17 2016

if you have a activation hack, you should also do a malware scan/rootkit scan.

problems like this can also be caused by not installing the motherboard drivers, particularly the motherboard sound driver. check the motherboard vendor for bios and driver updates.

if you still get the problem, the most direct way of inding the driver will be to:
change the memory dump type to kernel, then run cmd.exe or powershell as an admin then run
verifier.exe /standard /all
and reboot your system.

Note: be sure you know how to get into safe mode so you can turn off verifier if the system bugchecks during the next boot.
use
verifier.exe /reset

to turn off verifier, also note you have to turn it off after testing or your machine will run slowly until you do.

with verifier running and a kernel memory dump, verifier should catch the bad driver and name it in the c:\windows\memory.dmp file (kernel memory dump)

I checked under the DRIVER folder and it shows 2015 instead of 2008 and i couldn't find any programme for the wireless adapter for me to uninstall too. I'm trying out the verifier now

i updated every possible drivers and scanned in every possible way but it doesn't yield any results

EDIT: Not sure if it helps or if im doing right but the verifier gave me "System Thread exception not Handled" BSOD and also this huge DUMP file
https://www.dropbox.com/s/035fhazak04v4on/MEMORY.DMP?dl=0

 

[johnbl]

guess it could be a bug in your SATA driver, bios or actual drive firmware also.
something is not storing the crashdump correctly. I could only see one unknown module at a strange memory address. (not a expected kernel address)
check the intel firmware update tool for your drive:
https://downloadcenter.intel.com/download/26491/Intel-SSD-Firmware-Update-Tool

----------------
basically, the debugger really does not like the memory dump. the debugging commands just will not work on it. the module list is corrupt.

the error code was not from verifier.

I would confirm you do not have memory problems, ie run memtest86
and I would most likely wipe the drive or put in a new drive and install a known good copy of windows, then install just the motherboard drivers and see if it works correctly.

basically, I would guess you have a hardware problem or rootkit installed.

 

[DenyingEverything]

guess it could be a bug in your SATA driver, bios or actual drive firmware also.
something is not storing the crashdump correctly. I could only see one unknown module at a strange memory address. (not a expected kernel address)

----------------
basically, the debugger really does not like the memory dump. the debugging commands just will not work on it. the module list is corrupt.

the error code was not from verifier.

I would confirm you do not have memory problems, ie run memtest86
and I would most likely wipe the drive or put in a new drive and install a known good copy of windows, then install just the motherboard drivers and see if it works correctly.

basically, I would guess you have a hardware problem or rootkit installed.

Damn, guess i have to try out which hardware is causing the problem
Thanks anyway

 

[johnbl]

I added a note about the intel ssd firmware update tool, a bug in the firmware could cause problems like this also. last firmware update by intel was sept 8 2017

guess it could be a bug in your SATA driver, bios or actual drive firmware also.
something is not storing the crashdump correctly. I could only see one unknown module at a strange memory address. (not a expected kernel address)

----------------
basically, the debugger really does not like the memory dump. the debugging commands just will not work on it. the module list is corrupt.

the error code was not from verifier.

I would confirm you do not have memory problems, ie run memtest86
and I would most likely wipe the drive or put in a new drive and install a known good copy of windows, then install just the motherboard drivers and see if it works correctly.

basically, I would guess you have a hardware problem or rootkit installed.

Damn, guess i have to try out which hardware is causing the problem
Thanks anyway