Pre-release updates cause BSOD on Vista PC???

Discussion in 'ESET Smart Security' started by tnovak, May 22, 2010.

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

    tnovak Registered Member

    Joined:
    Oct 17, 2008
    Posts:
    15
    Pre-release updates (anti-Stealth 101:cool: cause BSOD on Vista PC. (FIXED in 1019)

    Hi,

    please, can someone with Vista OS confirm, that this link:

    (It's official web for tourist maps...)

    http://mapy.byl.cz/kct.htm

    causes BSOD? I get it every time. When I disable pre-release updates, no BSOD...

    Thanks

    Tom

    UPDATE: The pre-release anti-stealth module 1018 was the culprit of BSODs on Vista PCs (both 32/64) - ESET fixed the issue in new anti-stealth module 1019.
     
    Last edited: May 26, 2010
  2. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
  3. tnovak

    tnovak Registered Member

    Joined:
    Oct 17, 2008
    Posts:
    15
    Nope, it did not help, I tried it already, I disabled all ESS functions, anti-virus, anti-spyware, firewall, anti-spam and still got BSODs on this page, and when run some uninstallers.

    Then I found out, that disabling pre-release updates helped (I had not any BSODs since...)

    Here is mini-dump analysis, maybe it helps:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: d3ad0f08, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8233400c, address which referenced memory
    
    MODULE_NAME: nt
    
    FAULTING_MODULE: 82246000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b7d1e08
    
    BUGCHECK_STR:  0xC5_2
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt+ee00c
    8233400c 8b07            mov     eax,dword ptr [edi]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS
    
    LAST_CONTROL_TRANSFER:  from 82475daa to 8233400c
    
    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    9cfc47d4 82475daa 00000001 000000f8 6d4e624f nt+0xee00c
    9cfc47f4 82475cc6 00000030 00000001 9cfc48e0 nt+0x22fdaa
    9cfc4844 82475ba5 000adf00 9cfc4aac 00000001 nt+0x22fcc6
    9cfc4894 82480ac9 00000000 000adf00 000adf00 nt+0x22fba5
    9cfc48e8 8248629c 9cfc4abc 00000000 000adf00 nt+0x23aac9
    9cfc495c 8244c077 9cfc4a98 001000a1 9cfc4abc nt+0x24029c
    9cfc49a4 82290c7a 9cfc4a98 001000a1 9cfc4abc nt+0x206077
    9cfc49c4 8228f13d badb0d00 9cfc4a3c 82007a54 nt+0x4ac7a
    9cfc4a5c d91d8ff7 9cfc4a98 001000a1 9cfc4abc nt+0x4913d
    9cfc4a60 9cfc4a98 001000a1 9cfc4abc 9cfc4ab4 0xd91d8ff7
    9cfc4a64 001000a1 9cfc4abc 9cfc4ab4 00000007 0x9cfc4a98
    9cfc4a98 adefefc8 00000100 00000260 00000018 0x1000a1
    00000000 00000000 00000000 00000000 00000000 0xadefefc8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt+ee00c
    8233400c 8b07            mov     eax,dword ptr [edi]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt+ee00c
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    
    
    Tom
     
  4. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    it could well be a bug if you can replicate it on demand on that page + some software/installers while running pre-release software. Hopefully it gets investigated/fixed
     
  5. tnovak

    tnovak Registered Member

    Joined:
    Oct 17, 2008
    Posts:
    15
    I hope so, because if this pre-release update become final, I will be not able to use ESS anymore, because it has serious stability impact... :-(
     
  6. ESS3

    ESS3 Registered Member

    Joined:
    Dec 11, 2007
    Posts:
    112
  7. tnovak

    tnovak Registered Member

    Joined:
    Oct 17, 2008
    Posts:
    15
    Oh, so the pre-release anti-stealth module 1018 was probably the culprit... In the normal updates is version 1017 yet. So I hope Eset will repair this module for the final version or else we are doomed to BSOD :-(

    ESS3, thank you for confirming.
     
  8. surfer1000

    surfer1000 Registered Member

    Joined:
    Jun 5, 2009
    Posts:
    66
    Location:
    UK
    OMG!!!

    This has given me such a headache over the last 4 days!!!

    My system too has been crashing with the BSOD since the update.

    I get BSOD on demand everytime i try to install or unistall anything on my pc, I've been pulling my hair out (as well as memory sticks, graphics cards) over this!!!

    Also all my system restore points were removed!

    I can't believe an update could cause such a problem.

    I have just unticked pre-release updates and my system is now working again!

    Thank you for the post!, i hope eset get this sorted FAST

    Vista 32bit Ultimate, Eset 4.2.40 and all updates
     
    Last edited: May 24, 2010
  9. surfer1000

    surfer1000 Registered Member

    Joined:
    Jun 5, 2009
    Posts:
    66
    Location:
    UK
    It would be nice to hear back from Eset on this at least letting us know you are aware of the problem and are working on fixing it!
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    First of all, pre-release updates are intended for testing purposes and should not be enabled on production machines as they may contain bugs causing problems under specific circumstances or in certain system configurations (e.g. conflicts with uncommon drivers). The issue is still being investigated.
     
  11. tnovak

    tnovak Registered Member

    Joined:
    Oct 17, 2008
    Posts:
    15
    Thank you, Marcos, for your reply. I'm aware of the nature of the pre-release updates. I just wanted to confirm that it was the real cause of the instability of my PC and make sure that ESET knows about it and will fix it until the final version.
    The other affected users probably can find out this confirmation quite useful too, because personally it took me few hours of my time until I finally find out the source of the BSOD problem...

    I trust ESET will fix the problem, keep up the good work...
     
  12. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,564
    For your info:
    I have pre-release updates enabled (EAV4 on XP-home) and just got a newer version of the anti-stealth module (1019):

    NOD32_2010_05_26_1.gif
     
  13. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    The update should address BSOD reported above so hopefully it will work fine for you all.
     
  14. tnovak

    tnovak Registered Member

    Joined:
    Oct 17, 2008
    Posts:
    15
    Thank you, Marcos, I just installed it and tested the web I posted and ran some uninstallers and everything seems to be OK! Good job!

    I will report back, if something goes wrong...

    Tom
     
  15. Temp Member

    Temp Member Registered Member

    Joined:
    Mar 28, 2009
    Posts:
    263
    Location:
    Glasgow
    ~ Snipped as per TOS ~ now for 1st time in days my PC does not BSOD every time I try to run a new .EXE (like installing programs).

    I had to install all new programs in Safe Mode, even a DX web update would kill PC.

    I started looking at all my drivers as simply disabling ESS did not stop the BSOD's.

    This ia bad news for ESET esp as I am still on the older beta on Vista as current builds mess up my Sidebar every reboot (fine on Win 7 though).

    I am still waiting on my renewal Licence I paid for 6 weeks ago, but am just holding out as curious to know how long it will take them to realise they ain't sent me it and the fact from past experiences the CS is crap. :thumbd:
     
    Last edited by a moderator: May 27, 2010
  16. Temp Member

    Temp Member Registered Member

    Joined:
    Mar 28, 2009
    Posts:
    263
    Location:
    Glasgow
    P.S, I was NOT using any Test Build Apps, it is not checked in UPDATE Menu.
     
Thread Status:
Not open for further replies.