ESET Insiders SlashRose 25 Posted February 11, 2016 ESET Insiders Share Posted February 11, 2016 The v9 is the worst version, there has been Eset! (German: Die v9 ist die schlechteste Version die es bisher von Eset gegeben hat!) ==================================================Dump-Datei : 021116-11218-01.dmpAbsturzzeit : 11.02.2016 20:17:18Fehlerprüfstring : SYSTEM_SERVICE_EXCEPTIONFehlerprüfcode : 0x0000003bParameter 1 : 00000000`c0000005Parameter 2 : ffffe001`eb4623dfParameter 3 : ffffd000`23ed9ab0Parameter 4 : 00000000`00000000Verursachender Treiber: em006_64.datVerursachende Adresse: em006_64.dat+123dfDateibeschreibung :Produktname :Hersteller :Dateiversion :Prozessor : 64-BitAbsturzadresse : ntoskrnl.exe+142480Stapeladresse 1 :Stapeladresse 2 :Stapeladresse 3 :Computername :Pfad : C:\WINDOWS\Minidump\021116-11218-01.dmpCPUs : 8Hauptversion : 15Nebenversion : 10586Dump-Dateigröße : 311.540Dump-Dateizeit : 11.02.2016 20:18:29================================================== Link to comment Share on other sites More sharing options...
Administrators Marcos 5,294 Posted February 11, 2016 Administrators Share Posted February 11, 2016 If you are able to reproduce the crash (nobody else has reported it so far AFAIK), configure Windows to generate complete or at lease kernel memory dumps, reproduce the crash and then provide us with the dump in a compressed form so that we can analyze if it was actually caused by ESET or by something else running on your computer. Link to comment Share on other sites More sharing options...
Ádám Fekete 0 Posted March 16, 2016 Share Posted March 16, 2016 I had near the same problem: hxxp://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/unexpected-kernel-mode-trap-bsod/f68f42c0-ca47-430b-952c-9dd91fc95a1d Link to comment Share on other sites More sharing options...
itman 1,758 Posted March 17, 2016 Share Posted March 17, 2016 I had near the same problem: hxxp://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/unexpected-kernel-mode-trap-bsod/f68f42c0-ca47-430b-952c-9dd91fc95a1d Appears you traced the problem back to MalwareBytes Anti-Malware: Thanks for help! You are the best support! You answered fast and you were really helpful! I uninstalled Malwarebytes Anti-Malware and now everything is fine! Was MBAM running in realtime mode? Even if used as a second on-demand solution, the later versions of MBAM can cause problems with any other AV solution running in realtime. Link to comment Share on other sites More sharing options...
ESET Insiders SlashRose 25 Posted March 18, 2016 Author ESET Insiders Share Posted March 18, 2016 Marcos you write with any problem that no one else has this error, although the Board are previously full of my errors reported. what is the nonsense of them? (German: Marcos du schreibst bei jedem Problem das kein anderer diese Fehler hat, obwohl die Foren bisher voll von meinen gemeldeten Fehler sind. was soll der Quatsch von ihnen?) Link to comment Share on other sites More sharing options...
Administrators Marcos 5,294 Posted March 19, 2016 Administrators Share Posted March 19, 2016 Searching for "em006_64.dat" didn't yield any other results than this topic. Please provide links to topic where you think the issue was discussed. Link to comment Share on other sites More sharing options...
itman 1,758 Posted March 20, 2016 Share Posted March 20, 2016 Em006_64.dat along with other Eset .dat files are currently being loaded into the kernel globalroot driver area. My question is why is Eset loading .dat files into a kernel area reserved exclusively for drivers? Link to comment Share on other sites More sharing options...
Recommended Posts