Virtualbox 4.1 issue???

Discussion in 'ESET Smart Security' started by vigen, Jul 22, 2011.

Thread Status:
Not open for further replies.
  1. vigen

    vigen Registered Member

    Joined:
    Mar 28, 2011
    Posts:
    60
    Hello,

    After installing Virtualbox 4.1, I have a BSOD.

    OS: Win 7 64 bits Service Pack 1 Up to date.

    Eset Smart Security 4.2.71.2


    On Thu 21/07/2011 09:05:37 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\072111-24882-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
    Bugcheck code: 0xC5 (0x6359, 0x2, 0x0, 0xFFFFF800033C0DD3)
    Error: DRIVER_CORRUPTED_EXPOOL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Thu 21/07/2011 09:05:37 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: vboxnetflt.sys (VBoxNetFlt+0x3ABA)
    Bugcheck code: 0xC5 (0x6359, 0x2, 0x0, 0xFFFFF800033C0DD3)
    Error: DRIVER_CORRUPTED_EXPOOL
    file path: C:\Windows\system32\drivers\vboxnetflt.sys
    product: Oracle VM VirtualBox
    company: Oracle Corporation
    description: VirtualBox Bridged Networking Driver
    Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vboxnetflt.sys (VirtualBox Bridged Networking Driver, Oracle Corporation).
    Google query: vboxnetflt.sys Oracle Corporation DRIVER_CORRUPTED_EXPOOL


    Regards,

    Vigen.
     
  2. MattJN

    MattJN Former ESET Support Rep

    Joined:
    Feb 19, 2010
    Posts:
    149
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    I'd suggest trying the following, one at a time, to find out what helps:
    - make sure that Verifier is disabled for ESET's drivers epfw.sys and epfwwfpr.sys
    - rename C:\Windows\System32\drivers\epfw.sys in safe mode
    - rename C:\Windows\System32\drivers\epfwwfpr.sys in safe mode
     
  4. vigen

    vigen Registered Member

    Joined:
    Mar 28, 2011
    Posts:
    60
    Hello ,

    Its ok, the problem is ending with this "rename".

    Thanks,

    Vigen.
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Rename of which file?
     
  6. flyelfrickchu

    flyelfrickchu Registered Member

    Joined:
    Aug 1, 2011
    Posts:
    2
    Hi,

    I have the same BSOD issue in my NB. Have any suggestion to avoid BSOD if install VirtualBox 4.10 with ESET?
    I also found the other people discuss this in "http://www.sevenforums.com/crashes-debugging/95118-bsod-epfw-sys.html".

    PS: I have to disable all of protect in ESET to avoid BSOD; to rename files is not workable for me.

    My NB environment:
    OS: Win7 64-bit w/ SP1 up to date
    Eset Smart Security 4.2.71.2
    VirtualBox 4.1 (crashed with BSOD), back to Virtual Box 4.0.10

    Rick
     
    Last edited: Aug 2, 2011
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Where can I download your memory dump from to confirm or deny that an ESET driver was the culprit?
     
  8. flyelfrickchu

    flyelfrickchu Registered Member

    Joined:
    Aug 1, 2011
    Posts:
    2
    Hi Macros,

    After enable Win7 crash dump(i disable it on before) and re-install VirtualBox 4.10 on my NB.
    Strangely, this time the BSOD issue is not happened. o_O

    I have no idea why it becomes normally on my NB, but I am happy using my develop environment now.

    Anyway, thanks for your help and quickly reply.

    BR,
    Rick
     
  9. vigen

    vigen Registered Member

    Joined:
    Mar 28, 2011
    Posts:
    60
    Hello,

    Just for information, this issue happened only with Eset products.

    Just one example:

    http://www.virtualbox.org/ticket/9404

    I tested the 4.1 version with other products, no problem.

    Regards;

    Vigen.
     
  10. Meardon

    Meardon Registered Member

    Joined:
    Apr 9, 2009
    Posts:
    4
    Hi,

    As a workaround, it's possible to install ESET products first, and then Virtual Box.
    The only reason why the reverse order of installation (installing ESET first, then Virtual Box) works is the fact, that during startup ESET drivers are started first and thus the aforementioned Virtual Box issue did not manifest.

    Meardon
     
Thread Status:
Not open for further replies.