Question Random Bluescreens again

valeman2012

Distinguished
Apr 10, 2012
1,272
11
19,315
Following this thread that resolved : https://forums.tomshardware.com/thr...ames-on-different-days.3785525/#post-22857882
I getting blue screen again

My both RAM is also okay. My SSD had no bad sectors, chipset drivers up-to-date, audio (motherboard driver which was customized) and network adapter updated

I focusing on RAM because its a "2x8GB Intel DDR4-3200 RAM" (CMK16GX4M2B3200C16 ) on AMD Ryzen 3000 CPU/X570 Computer, Will this cause instability?

https://www.dropbox.com/s/plucejxfdoex8fh/MAGH.zip?dl=0
 
I focusing on RAM because its a "2x8GB Intel DDR4-3200 RAM" (CMK16GX4M2B3200C16 ) on AMD Ryzen 3000 CPU/X570 Computer, Will this cause instability?
that is mostly just marketing, was ram tested by Corsair to work with board?

yes, it was. its 1st on the list of ram tested with mb & CPU. So it should be fine
https://www.corsair.com/us/en/Categories/Products/Memory/VENGEANCE-LPX/p/CMK16GX4M2B3200C16 = top one here (notices he has wrong CPU but its on list, not taking another screenshot)
5wykoHv.jpg

thats good enough for me. May not make Asus happy but I didn't look on there.

Conversion of Dumps

report - click run as fiddle to read


File: 122722-6031-01.dmp (Dec 28 2022 - 17:20:40)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: masterduel.exe)
Uptime: 0 Day(s), 8 Hour(s), 13 Min(s), and 17 Sec(s)

File: 122522-5921-01.dmp (Dec 26 2022 - 18:45:17)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: ntkrnlmp.exe (Process: chrome.exe)
Uptime: 0 Day(s), 11 Hour(s), 16 Min(s), and 10 Sec(s)

File: 122122-5765-01.dmp (Dec 22 2022 - 10:24:28)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: Npfs.SYS (Process: chrome.exe)
Uptime: 0 Day(s), 3 Hour(s), 03 Min(s), and 49 Sec(s)

File: 121422-5906-01.dmp (Dec 15 2022 - 18:09:30)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: Unknown_Image (Process: TslGame.exe)
Uptime: 0 Day(s), 10 Hour(s), 10 Min(s), and 07 Sec(s)

updated ESET recently?

I already suggested replacing intel lan drivers and they must be the newest if you tried.
I also suggested GPU drivers.

And its not ram since its still happening.

perhaps @johnbl might see something.
 
  • Like
Reactions: valeman2012
that is mostly just marketing, was ram tested by Corsair to work with board?

yes, it was. its 1st on the list of ram tested with mb & CPU. So it should be fine
https://www.corsair.com/us/en/Categories/Products/Memory/VENGEANCE-LPX/p/CMK16GX4M2B3200C16 = top one here (notices he has wrong CPU but its on list, not taking another screenshot)
5wykoHv.jpg

thats good enough for me. May not make Asus happy but I didn't look on there.

Conversion of Dumps

report - click run as fiddle to read


File: 122722-6031-01.dmp (Dec 28 2022 - 17:20:40)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: masterduel.exe)
Uptime: 0 Day(s), 8 Hour(s), 13 Min(s), and 17 Sec(s)

File: 122522-5921-01.dmp (Dec 26 2022 - 18:45:17)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: ntkrnlmp.exe (Process: chrome.exe)
Uptime: 0 Day(s), 11 Hour(s), 16 Min(s), and 10 Sec(s)

File: 122122-5765-01.dmp (Dec 22 2022 - 10:24:28)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: Npfs.SYS (Process: chrome.exe)
Uptime: 0 Day(s), 3 Hour(s), 03 Min(s), and 49 Sec(s)

File: 121422-5906-01.dmp (Dec 15 2022 - 18:09:30)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: Unknown_Image (Process: TslGame.exe)
Uptime: 0 Day(s), 10 Hour(s), 10 Min(s), and 07 Sec(s)

updated ESET recently?

I already suggested replacing intel lan drivers and they must be the newest if you tried.
I also suggested GPU drivers.

And its not ram since its still happening.

perhaps @johnbl might see something.
ESET will auto update signature and software (which i would know)
There no more GeFroce Driver as its the latest one this year.

Audio Driver is at latest for my AsRock X570 Phantom Gaming 4 Motherboard for Windows 10
Also i use
Chrome Incognito 90% of the time and sometime while playing those game.

I applied Latest Windows 10 Intel Driver for the specific Network Adapter (August 2022 Driver) and Latest AMD Chipset Drivers after the previous BSOD
I stopped getting "KERNEL_SECURITY_CHECK_FAILURE (139) Blue Screen" ever since.
 
Last edited:
I would uninstall eset, then use autoruns64 to confirm all parts are uninstalled.
and see if you still have various bugchecks.

bugchecks were in functions that I would guess that eset is calling.
file filter manager, double removes of resources, cancel a timer that was already expired,
your eset dlls have files from 2020 and files from 2022.

after you uninstall, confirm the removed files, then see if you bugcheck. then do a clean reinstall of eset and see if you still get bugchecks.


em000k_64.dll Wed Jul 1 02:54:43 2020 (5EFC5D63) <<<<< wonder about this file based on the date>>>
em006_64.dll Mon Sep 19 01:13:32 2022 (632824AC)
em008k_64.dll Wed Jun 22 04:02:39 2022 (62B2F6CF)
em018k_64.dll Mon Nov 21 12:13:01 2022 (637BDBCD)
em042_64.dll Fri Jul 15 03:44:29 2022 (62D1450D)
epfw.sys Wed Oct 5 01:53:30 2022 (633D460A)
epfwwfp.sys Wed Oct 5 01:53:31 2022 (633D460B)

one of the bugchecks indicated:
0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

I would check the voltages in bios, run memtest86 and confirm the RAM and the cpu are working without error. maybe reset bios to defaults or update if you have not done so.

disable chrome extensions

if all else fails and you can not find the cause of the problem, I would install the chipset drivers and the ryzenmaster drivers directly from AMD website.
 
Last edited:
  • Like
Reactions: valeman2012
I would uninstall eset, then use autoruns64 to confirm all parts are uninstalled.
and see if you still have various bugchecks.

bugchecks were in functions that I would guess that eset is calling.
file filter manager, double removes of resources, cancel a timer that was already expired,
your eset dlls have files from 2020 and files from 2022.

after you uninstall, confirm the removed files, then see if you bugcheck. then do a clean reinstall of eset and see if you still get bugchecks.


em000k_64.dll Wed Jul 1 02:54:43 2020 (5EFC5D63) <<<<< wonder about this file based on the date>>>
em006_64.dll Mon Sep 19 01:13:32 2022 (632824AC)
em008k_64.dll Wed Jun 22 04:02:39 2022 (62B2F6CF)
em018k_64.dll Mon Nov 21 12:13:01 2022 (637BDBCD)
em042_64.dll Fri Jul 15 03:44:29 2022 (62D1450D)
epfw.sys Wed Oct 5 01:53:30 2022 (633D460A)
epfwwfp.sys Wed Oct 5 01:53:31 2022 (633D460B)

one of the bugchecks indicated:
0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

I would check the voltages in bios, run memtest86 and confirm the RAM and the cpu are working without error. maybe reset bios to defaults or update if you have not done so.

disable chrome extensions

if all else fails and you can not find the cause of the problem, I would install the chipset drivers and the ryzenmaster drivers directly from AMD website.
I do a instant clean re-install Eset Internet Security latest version in response of the 4th blue screen . I checked the certificate information and same date July 1, 2020 after clean Eset Reinstall

The other 3 Bluescreen more likely were cause by bugs from AMD Chipset drivers which led to Memory Management and Check failure bluescreen. I updated the Chipset drivers after the 3rd blue screen.
 
Last edited:
try installing the amd ryzenmaster drivers. they will override some of the voltagesset by the bios to the cpu pins

I think the bugcheck related to PAGE_TABLE_RESERVED_BITS_SET_IMAGE is going to be related to an internal cpu function messing up.

you should confirm memtest86 runs without any errors. Or run prime95 to look for cpu errors
 
Last edited:
  • Like
Reactions: Colif