![]() Anyone else who can report similar observations?Īddendum: My German readers told me in comments, that they was able to start Windows 7 in safe mode – then they was able to uninstall Apex (others disabled TM services). Since then many readers confirmed that issue, also on embedded clients, and it affects 32 and 64 bit systems. What all computers have in common so far is that they are still running Windows 7 and TrendMicro (various editions) is installed as the virus scanner.Īre there any findings from other readers? Ticket at TrendMicro is opened. just contacted me by mail and writes:Ĭurrently we have the problem with at least 15 customers that shortly after login the message "Critical error, the system will restart in 1 minute" appears on the computer and then the computer actually restarts. I myself can't find any problems with my Windows 7 SP1 with ESU at the moment, the system runs since hours without any problems. Affected are 32- and 64-bit Windows 7 clients (including embedded), and in all cases Trend Micro seems to be involved as the security solution. The module name "tmevtmgr" is also mentioned, indicating that it may be related to the issue.After I published the initial blog post in German, I receivedseveral reports from various users that there are problems with Windows 7 restarts because a critical error has occurred. ![]() The stack text shows that the process "javaw.exe" was running when the bugcheck occurred. ![]() The debugging details indicate that there was a warning that the timestamp for the "tmevtmgr.sys" file could not be verified. It's possible that there's a compatibility issue between the driver and the version of Windows running, or there could be an issue with the OfficeScan software itself. Tmevtmgr.sys is a driver associated with the TrendMicro OfficeScan antivirus software. The error code indicates a system service exception with a memory access violation (0xC0000005). Here it looks like the tmevtmgr.sys driver caused the crash, specifically an unknown function within that driver. cxr 0xffff91803baba0f0 kbįAILURE_BUCKET_ID: 0x3B_c0000005_tmevtmgr!unknown_functionįAILURE_ID_HASH: *** WARNING: Unable to verify timestamp for tmevtmgr.sysĬONTEXT: ffff91803baba0f0 - (.cxr 0xffff91803baba0f0) Kernel base = 0xfffff806 3c814000 PsLoadedModuleList = 0xfffff8063cc2d470ĭebug session time: Wed Mar 15 17:01:45.080 2023 (UTC - 4:00)įor analysis of this file, run !analyze -vĪn exception happened while executing a system service routine.Īrg1: 00000000c0000005, Exception code that caused the bugcheckĪrg2: fffff80638e16c09, Address of the instruction which caused the bugcheckĪrg3: ffff91803baba0f0, Address of the context record for the exception that caused the bugcheckĪrg4: 0000000000000000, zero. Product: Server, suite: TerminalServer SingleUserTSīuilt by: 17763.1.amd64fre.rs5_release.180914-1434 Windows 10 Kernel Version 17763 MP (8 procs) Free 圆4 Mini Kernel Dump File: Only registers and stack trace are available Microsoft (R) Windows Debugger Version 1.1 AMD64Ĭopyright (c) Microsoft Corporation. So I finally checked minidump and it showed the following Analysis. ![]() I have ran SFC scan and Chkdsk to check for any problems. I have windows 2019 server which got unexpected reboot due to a bugcheck. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |