kenpachizero 0 Report post Posted February 19, 2016 hello, just a small error, after i download the emergency kit extracting it and update it successfully, i then try and run cmd for the 64bit version it comes up with the attached error, the 32bit has no issue, below is the clipboard thing it said to do. Also this emergency kit i just recently downloaded from your site --------------------------- EurekaLog 7.2.6.17 RC 1 crash report --------------------------- Access violation at address 00007FFEF26471DB in module 'ntdll.dll'. Read of address 0000000000000040 ExceptionLog7.Init (Location: (000000000{ntdll.dll }00371DB) [00007FFEF26471DB] ntdll.RtlVirtualUnwind + $1DB) (report generated by EDebugInfo.DebugInfoInitDoneErrorHandler) Press Ctrl + C to copy report to clipboard --------------------------- OK --------------------------- Download Image Share this post Link to post Share on other sites
minegroasprilla 1 Report post Posted February 19, 2016 Man, I have the same problem using EAM on Windows 10 and I haven't had a solution: http://support.emsisoft.com/topic/19749-problem-ntdlldll/ Share this post Link to post Share on other sites
GT500 495 Report post Posted February 19, 2016 Lets get a log from FRST, and see if it shows the cause of the issue. Please download Farbar Recovery Scan Tool (FRST) from one of the following links, and save it to your Desktop (please note that some web browsers will automatically save all downloads in your Downloads folder, so in those cases please move the download to your desktop): For 32-bit (x86) editions of Windows: http://download.bleepingcomputer.com/farbar/FRST.exeFor 64-bit (x64) editions of Windows:http://download.bleepingcomputer.com/farbar/FRST64.exeNote: You need to run the version compatible with your computer. If you are not sure which version applies to your computer, then download both of them and try to run them. Only one of them will run on your computer, and that will be the right version.Run the FRST download that works on your computer (for Windows Vista, Windows 7, and Windows 8 please right-click on the file and select Run as administrator). When the tool opens click Yes for the disclaimer in order to continue using FRST. Press the Scan button. When the scan is done, it will save a log as a Text Document named FRST in the same place the tool was run from (if you had saved FRST on your desktop, then the FRST log will be saved there). Please attach the FRST log file to a reply using the More Reply Options button to the lower-right of where you type in your reply to access the attachment controls. The first time the FRST tool is run it saves another log (a Text Document named Addition - also located in the same place as the FRST tool was run from). Please also attach that log file along with the FRST log file to your reply. Share this post Link to post Share on other sites
kenpachizero 0 Report post Posted February 19, 2016 Hello, attached are the files requested from the frst, let me know if you need me to do anything else Addition.txt FRST.txt Share this post Link to post Share on other sites
GT500 495 Report post Posted February 24, 2016 Please try the following: Hold down the Windows key on your keyboard (the one with the Windows logo on it, usually between the Ctrl and Alt keys) and tap R to open the Run dialog. Type in (or copy and paste) %APPDATA%\EurekaLab s.a.s\EurekaLog\Bug Reports and then click OK. Look for a folder named a2emergencykit.exe, and if you find it right-click on it, go to Send to, and select Compressed (zipped) folder. Using the More Reply Options button to access the attachment controls, please attach the new file that was created to a reply. Share this post Link to post Share on other sites
kenpachizero 0 Report post Posted February 24, 2016 hello, EurekaLab s.a.s is not there unfortunately . Share this post Link to post Share on other sites
minegroasprilla 1 Report post Posted February 25, 2016 Hey kenpachizero, Do you use any software of Comodo?. Share this post Link to post Share on other sites
kenpachizero 0 Report post Posted February 25, 2016 no, i don't trust comodo Share this post Link to post Share on other sites
minegroasprilla 1 Report post Posted February 25, 2016 no, i don't trust comodo ok. I have the same problem with ntdll.dll, but here anyone solves anything. Share this post Link to post Share on other sites
GT500 495 Report post Posted February 26, 2016 Lets get some debug logs from EEK: Open 32-bit Emsisoft Emergency Kit. In the 4 little gray boxes at the bottom, click on the one that says Need assistance?. At the bottom, turn on the option that says Enable advanced debug logging. Close the Emsisoft Emergency Kit window. Reproduce the issue you are having with the error message when opening 64-bit Emsisoft Emergency Kit. Once you have reproduced the issue, open 32-bit Emsisoft Emergency Kit again, and click on the gray box for Need assistance? again. Click on the button that says Send an email. Select the logs in the left that show today's dates. Fill in the e-mail contact form, and be sure to mention who was helping you, and if possible please leave a link to the topic on the forums that the logs are related to in your message. If you have any screenshots or another file that you need to send with the logs, then you can click the Attach file button at the bottom (only one file can be attached at a time). Click on Send now at the bottom once you are ready to send the logs. Important: Please be sure to turn debug logging back off after sending us the logs. There are some negative effects to having debug logging turned on, such as reduced performance and wasting hard drive space, and it is not recommended to leave debug logging turned on for a long period of time unless it is necessary to collect debug logs. Share this post Link to post Share on other sites
kenpachizero 0 Report post Posted February 27, 2016 Lets get some debug logs from EEK: Open 32-bit Emsisoft Emergency Kit. In the 4 little gray boxes at the bottom, click on the one that says Need assistance?. At the bottom, turn on the option that says Enable advanced debug logging. Close the Emsisoft Emergency Kit window. Reproduce the issue you are having with the error message when opening 64-bit Emsisoft Emergency Kit. Once you have reproduced the issue, open 32-bit Emsisoft Emergency Kit again, and click on the gray box for Need assistance? again. Click on the button that says Send an email. Select the logs in the left that show today's dates. Fill in the e-mail contact form, and be sure to mention who was helping you, and if possible please leave a link to the topic on the forums that the logs are related to in your message. If you have any screenshots or another file that you need to send with the logs, then you can click the Attach file button at the bottom (only one file can be attached at a time). Click on Send now at the bottom once you are ready to send the logs. Important: Please be sure to turn debug logging back off after sending us the logs. There are some negative effects to having debug logging turned on, such as reduced performance and wasting hard drive space, and it is not recommended to leave debug logging turned on for a long period of time unless it is necessary to collect debug logs. that has been sent, i am impressed with the support options built into the EEK, you guys thought ahead Share this post Link to post Share on other sites
GT500 495 Report post Posted March 2, 2016 OK, I have passed your debug logs on to our QA team. They'll make sure that a bug report gets opened so that our developers can look into this. 1 Share this post Link to post Share on other sites
kenpachizero 0 Report post Posted March 2, 2016 awesome thank you Share this post Link to post Share on other sites
GT500 495 Report post Posted March 3, 2016 You're welcome. Share this post Link to post Share on other sites
