kenpachizero

Member
  • Content Count

    21
  • Joined

  • Last visited

Posts posted by kenpachizero


  1. 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


  2. 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   
    ---------------------------
     

    post-14015-0-98050100-1455870030_thumb.jpg
    Download Image


  3. Hello, every 4 days or so i get this Invalid pointer operation error, it pops up behind everything so i don't notice the issue till i minimized everything, after i press ok i don't see anything else happen(no crashes or other errors) so its more just trying to fix a error.

    emsisoft internet security 10.0.0.5735

    windows 10 pro x64

    only emsisoft is installed no other security applications


  4. Bridged networking is where the virtualization software (in the case Virtual Box) sets up virtual network devices that act like they are connected directly to your network, so that they have IP addresses assigned by your router. The primary alternative to this is NAT (Network Address Translation) mode, where the virtualization software uses the network connection in a more traditional manner. In Virtual Box there can be some issues with UDP packets in NAT mode, but you only really see those issues when trying to run a game server in the virtual machine.

    awesome thank you


  5. The blue screen is caused by the VirtualBox NDIS driver. Their driver is unfortunately known for causing a whole bunch of issues with firewall and AV filter drivers. The only way to fix it is to install VirtualBox without Bridged Networking support at the moment, as Oracle refuses to fix that particular issue in their driver.

    cause i am just learning linux, what would i lose if i removed the bridged networking?