I have been getting the same thing on my PC. Last week, Wednesday, I started to BSoD about 5 minutes after my computer booted, but not when I used Safe Mode. I tried to get some help to interpret the minidmp files but everyone was busy. I ended up, on Friday, rebuilding the PC from scratch thinking it was a driver that was corrupted.
I finished the rebuild late Friday and the PC was fine the whole weekend. This morning I turned it on and the BSoD was back at the same 5 minute period. I went to a Windows 7 support forum and uploaded my last 4 minidmp files. The one thing they noticed was, every crash had the following in common:
-----------------------------------------------------------------------------
Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: ekrn.exe CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
------------------------------------------------------------------------------
They recommended I uninstall ESET and install Microsoft Security Essentials as a test. I did that and my PC has been running just fine for over an hour now.
I've had your software for over 3 years now, this is the first time you folks have screwed up.
From the looks of all the posts since mine on the first page, ESET is persisting in trying to push this on us and our PCs. Regardless of the fact that the problem started, at least on my PC, after THEIR update and ABSOLUTELY NOTHING had changed on my PC. I'll give it another month and check back again. If they still are, I'll be dumping ESET from all my devices (PC, laptop, Android phone and tablet)