ESS causes reboots

Discussion in 'ESET Smart Security' started by SBMongoos, Nov 17, 2008.

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

    unclejohn Eset Staff

    Joined:
    Nov 20, 2008
    Posts:
    13
    First of all you need to turn off the "Automatic restart" and have the size of the dump-file set to "complete". Then you can uninstall NOD32 and install the faulting ESS. You will find the memory-dump, once it's created upon crashing of operating system, under c:\windows\memory.dmp
    Do you mean deleting your pagefile before shutdown when talking about dumping it?
     
  2. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215

    Right. While back I read where it makes sense to purge the PageFile. Takes longer to shutdown but it clears it. Wanted to find out if this will mess up the memory.dmp file or noto_O

    Been a while since I set this up, see here: http://support.microsoft.com/kb/314834
     
  3. unclejohn

    unclejohn Eset Staff

    Joined:
    Nov 20, 2008
    Posts:
    13
    Good, that you started the question - yes, you should disable this feature.
     
  4. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215
    Not getting a Memory.dmp file after having done this. Interestingly enough I am now getting a BSOD. This may be a coincidence as I'm also trying to work with some RAM memory. However, this RAM has all been used in this PC in the past and always worked fine. Same setup.

    Info about the BSOD:

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    STOP:
    0X00000D1 0X0000002 0X0000000 0X000000A

    I did find the following info at a forum:

    Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
    The Stop 0xD1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.

    Interpreting the Message
    This Stop message has four parameters:

    Memory referenced.
    IRQL at time of reference.
    Type of access (0x00000000 = read operation, 0x00000001 = write operation).
    Address that referenced memory.
    Resolving the Problem
    For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

    Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
    For more information about Stop 0xD1 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000D1, and 0xD1.

    updated and comaptiable drivers are very important when running XP. Check your hardware with the HCL www.microsoft.com/hcl If you hardware is not on the list it does not mean it won't work it just means it hasn't been tested by Microsoft and they won't Guarantee it to be compatible. If it not on the list check the manufacturer's website fo an up to date XP driver, if they don't have one you may be out of luck. This goes for motherboards and the bios too.

    ****

    I don't believe the RAM is having any impact on this situation. I believe it's a driver issue with ESS and something else. I've updated my network driver (onboard NIC) about two weeks ago. But obviously this didn't have any impact.

    Hmmm..

    Where to go from here?
     
    Last edited: Dec 8, 2008
  5. unclejohn

    unclejohn Eset Staff

    Joined:
    Nov 20, 2008
    Posts:
    13
    Hi,
    you now can see the bluescreen, as we set it to appear, and not to restart immediately ("Automatic restart"-option). The bluescreen shows a number indicating the progress of saving (see image below) - if there is no such a number rising up to 100, then there is something wrong with the settings. Either you have the pagefile set as too small, or the dump-type is not correct. Regarding the memory - every time you turn on your computer, you necessarily have to work with your RAM a lot - this is given by technology.
     

    Attached Files:

    • ss1.png
      ss1.png
      File size:
      75.4 KB
      Views:
      176
    • ss2.png
      ss2.png
      File size:
      83.2 KB
      Views:
      179
  6. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215
    No issues with RAM as I stated. I've been working with OCZ to gain back a low CL setting. When I upgraded from 1G to 2G it dropped. So they sent me another 2G kit to try. Otherwise the RAM has been fine. Currently a 1G kit is installed with a fixed pagefile size of just over 1.5G (1.5 x 1).

    Do you recommend that I put a 2G kit back in and try it?

    I've already changed the settings back for the dump file. I have the pagefile set on drive D: (for performance), I assume that is not an issue or does it at least need to be on drive C: to have room to dump the file??
     
    Last edited: Dec 9, 2008
  7. unclejohn

    unclejohn Eset Staff

    Joined:
    Nov 20, 2008
    Posts:
    13
    No, I think you can keep the current memory size (= 1 G), but should set the pagefile to "system managed" (don't forget to press the "Set"-button). I see no problem with having the pagefile stored on drive D: but it should be a drive or partition visible to the operating system in safe-mode or recovery console as well - i.e. not an external usb-drive or other device, that would require third party drivers to run.
     

    Attached Files:

    • sh3.png
      sh3.png
      File size:
      6.1 KB
      Views:
      173
  8. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215
    Okay, so I'll start the process over again. I should be able to get it knocked out this afternoon unless I have an interruption.
     
  9. n1brvfan

    n1brvfan Registered Member

    Joined:
    Dec 9, 2008
    Posts:
    1
    I am having the exact same issue with BSOD, but mine is pointing at epfwtdi.sys as the culprit of my mini-dumps. Just gonna be a fly on the wall while you work with SBMongoos, Unclejohn, unless you know what the problem might be. I just recently switched from Kaspersky where there was no BSOD issue. BSOD will happen with on all OS's I have installed and I have the latest and greatest MS approved drivers for all devices.

    System components are as follows:

    Motherboard
    ASUS Formula RAMPAGE

    Processor
    Intel Core 2 Extreme QX9650

    Memory
    TWIN2X4096-8500C5DF

    Video
    Card # 1 BFG 8800GTX
    Card # 2 BFG 8800GTX

    HD's
    Hard Drive # 1 WD VelociRaptor 150 GB (WD1500BLFS)
    Hard Drive # 2 Maxtor 100 GB (6 L100M0)
    Hard Drive # 3 Maxtor OneTouch 600 GB

    Optical
    Drive # 1 SONY DRU-840A

    Case
    ThermalTake VE2000BWS

    Power Supply
    XION-1000R14HE

    Sound Card
    SurpremeFX II Audio

    Monitor
    SAMSUNG SyncMaster 2693HM

    Operating System
    Windows XP (32 bit)
    Vista Home Premium (32 bit)
    Windows Vista Ultimate (64 bit)

    Thanks in advance,
    n1brvfan
     
  10. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215
    Nice system n1brvfan! I've been building my own as well but have been going for about 3.5 years or so. Been thinking about building another but don't need to build a gaming PC. Starting to consider my options but if I do I want to watch the $$ this time around.
     
  11. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215

    Well, I've done as requested and the results are the same. I put 2G of RAM back in to be sure and it's System Managed. Get the BSOD but no counter saving off a Dump File and no file saved. Do I need to wait for some period of time before I see the status of the file creation complete (% wise that is)?? I checked the settings under Startup and Recovery and they are: Automatically Restart is "unchecked", Write debugging information is "complete memory dump".
     
    Last edited: Dec 12, 2008
  12. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215
    I wasn't confident that ESS v4 Beta would work either but I tried it and had the same results as above.

    Let me know if you have any ideas unclejohn.
     
  13. unclejohn

    unclejohn Eset Staff

    Joined:
    Nov 20, 2008
    Posts:
    13
    Honestly, this is really strange. I've done lots of brainstorming, asked the chief of R&D, but we cannot imagine a situation, when windows would fail to create the dump. It's a very basic feature of a healthy system, once the settings are properly tweaked. Remote advice is a hard job here, but please send me the screenshots of your settings (Startup&Recovery dialogue, Performance->Advanced->VirtualMemory window), maybe I can see something what you've missed. Optionally try to create the "Kernel memory dump" at least, let's see if this makes a difference. Try to search your entire drive, if the MEMORY.DMP-file is not "hiding" somewhere, where you would not expect it, just to make sure.
     
  14. SBMongoos

    SBMongoos Registered Member

    Joined:
    Oct 6, 2008
    Posts:
    215
    unclejohn: well to my disappointment I've run into a bigger problem. After testing different RAM and working out a warranty issue with OCZ I think my mb crapped out. May have been a static charge I'm not sure.

    At this point my PC sits partially pulled apart. Bummed about this as the timing with $$. Not sure I want to bother fixing a 4 year old PC. The machine had been working great. OCZ was finally following up on a very long overdue warranty issue. Not a big thing but just some RAM that was not hitting a certain CL setting.

    At this point I'm trying to determine if I want to get a 478 model mb or just do major upgrades. Either way I see a fresh OS install, etc. At that point I will be loading ESS and see if it will work. Perhaps the conflict won't come up. Not sure when this will be however.

    Thanks for your help...
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.