[eamonm.sys BSOD - Stop code: SYSTEM_THREAD_EXCEPTION NOT HANDLED]

Updated last night to KB5004237.

So far the system appears stable.  At least the MTBF is > 12 hours.

So, whatever the changes are they appear to have largely resolved the rapid bug check issues.

If the problems re-occurs I'll re-post, but for now, thankfully, I'll retire into the background.

[eamonm.sys BSOD - Stop code: SYSTEM_THREAD_EXCEPTION NOT HANDLED]

Just a piece of additional information:  I'm running version 14.1.20.0 of "Eset Internet Security"

 

I'll add to the reports.  After updating windows with KB5004945 my system will run from 30 seconds to 3-4 minutes.  Trying to get anything done will result in a bug check "System Thread exception not handled"  .  This includes trying "System Restore" from within windows.  It's necessary to do it from the bluescreen troubleshooting window.

The address is listed as eamonm.sys +6200 as previously reported

Deleting the update via system restore removes the problem.  Re-installing the update caused the BSOD to repeat with the same eamonm.sys+6200 address.  Removing the update again restores normal behavior. 

I would submit to others that rebuilding the PC is not required unless there are no system restore points available.

I've paused updates until this issue is resolved.

[eamonm.sys BSOD - Stop code: SYSTEM_THREAD_EXCEPTION NOT HANDLED]

Attached is a minidump file from the last crash.  The full dump is about 1GB and I can't upload that one.

I renamed it to "<>.txt" as <>.dmp is not allowed (pretty silly since that's what you need).  You'll need to rename it to <>.dmp.

 

070821-10234-01.txt

[eamonm.sys BSOD - Stop code: SYSTEM_THREAD_EXCEPTION NOT HANDLED]

I'll add to the reports.  After updating windows with KB5004945 my system will run from 30 seconds to 3-4 minutes.  Trying to get anything done will result in a bug check "System Thread exception not handled"  .  This includes trying "System Restore" from within windows.  It's necessary to do it from the bluescreen troubleshooting window.

The address is listed as eamonm.sys +6200 as previously reported

Deleting the update via system restore removes the problem.  Re-installing the update caused the BSOD to repeat with the same eamonm.sys+6200 address.  Removing the update again restores normal behavior. 

I would submit to others that rebuilding the PC is not required unless there are no system restore points available.

I've paused updates until this issue is resolved.