BSOD's on cold boot since 3119

Discussion in 'ESET NOD32 Antivirus' started by MichaelD245, May 25, 2008.

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

    MichaelD245 Registered Member

    Joined:
    May 25, 2008
    Posts:
    6
    Ever since the 3119 incident, my system has gotten random BSOD's upon cold booting. Rebooting has no issues whatsoever. it's usually a memory or hard disk error such as:

    Page fault In non paged area
    or
    An attempt was made to write to read-only memory.

    I've tried deleting the nod32 folders followed by a reinstall of Nod32

    I've performed all sorts of diagnostics to verify that my hardware is not at fault. Including Prime95, Memtest+ 2.01, Windows DSKCHK

    I've tried reinstalling system drivers and games that were afflicted by the bug.

    I've disabled advanced heuristics.

    I've tried a system restore and registry restore.
     
  2. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,798
    Location:
    Texas
    Hello MichaelD245,

    If you will, list your operating system, other security programs you may use, and any other pertinent information that may allow others to help you.
     
  3. MichaelD245

    MichaelD245 Registered Member

    Joined:
    May 25, 2008
    Posts:
    6
    Windows Vista 64-bit Home Premium

    Nod32 is the only security program I use. I suppose windows defender too.

    System information cut and pasted from dxdiag:

    Time of this report: 5/25/2008, 23:00:01
    Machine name: KIKOKU
    Operating System: Windows Vista™ Home Premium (6.0, Build 6001) Service Pack 1 (6001.longhorn_rtm.080118-1840)
    Language: English (Regional Setting: English)
    System Manufacturer: NVIDIA
    System Model: 132-CK-NF79
    BIOS: Phoenix - AwardBIOS v6.00PG
    Processor: Intel(R) Xeon(R) CPU X3350 @ 2.66GHz (4 CPUs), ~3.6GHz
    Memory: 4094MB RAM
    Page File: 1549MB used, 6825MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 10
    DX Setup Parameters: Not found
    DxDiag Version: 6.00.6001.18000 32bit Unicode

    Everything is stable except for the cold boot issue.
     
  4. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,798
    Location:
    Texas
    Download Sysinspector , double click the file you downloaded, and save the log which is in the upper right corner of the gui after it finishes a scan.

    Don't post the log here.

    An ESET moderator should be able to help you with the log.
     
  5. MichaelD245

    MichaelD245 Registered Member

    Joined:
    May 25, 2008
    Posts:
    6
    Help? I've since reinstalled vista and the problem is persisting. It's a different blue screen every time.

    Most recently it was a 0x000001E error

    Theres a 80% possibility it was nod32 that caused this problem. I've not gotten a response yet from them.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    The problem was fixed the same day it occured on. If it's actually related to the problematic update 3119, it must disappear after updating the Antivirus and antispyware scanner module to version 1116 (20080523) and restarting the computer. If you have done this, then it must be caused by something else. Does the problem disappear after you uninstall EAV? If so, would it be possible for you to create a complete memory dump and convey it to us for analysis?
     
  7. MichaelD245

    MichaelD245 Registered Member

    Joined:
    May 25, 2008
    Posts:
    6
    It takes me a few hours for each trouble shooting attempt because in order to cause a cold boot bsod, I have to leave the computer off for a few hours and then switch it back on. I generally leave my computer off nights.

    I'll uninstall ESET nod32 next.

    It's the wierdest thing, I would have figured a reinstall of vista would have fixed this. I get a different BSOD every time and have yet to get the same bsod twice. The most recent one was a 0x000001E.

    Is it possible my hard disks were damaged by the bug? Again everything was running stable until I came back to my computer after the 3119 update and saw that nod32 was detecting everything as possible viruses. I deleted quite a few files before I caught on.
     
  8. MichaelD245

    MichaelD245 Registered Member

    Joined:
    May 25, 2008
    Posts:
    6
    update: uninstalling nod32 did not solve the bsod problem.

    I will continue to search for a solution on my own. thanks.
     
  9. Bakker

    Bakker Registered Member

    Joined:
    May 28, 2008
    Posts:
    90
  10. MichaelD245

    MichaelD245 Registered Member

    Joined:
    May 25, 2008
    Posts:
    6
    After a series of 0x000001E's I believe I have narrowed it down to the motherboard BIOS.

    I have since re-flashed it and I didn't get a cold boot BSOD for the first time in a week.
     
Thread Status:
Not open for further replies.