Vista BSoD (because of Nod32)

pilotaz

New Member
hey guys, im new here and i have a problem with Vista ( BSoD- blue screen of death >.<)

i searched google... everywhere says about it but nothing about how to fix . and noone got this because of nod32.

im 99% sure that it is because of nod32. but dont know why.. Vista on which i tryed to install is 32bit, and nod32 install were 32bit too. and sudenly bsod appeared. :(

safe mode - dont work, stops on cycmod.sys , shows bsod
safe mode with networking - dont work, same stops on crcdisk.sys , shows bsod
same mode with command prompt - dont work, same stops on crcdisk.sys , shows bsod:
Image Hosting

launch startup repair(recommended) - windows failed to start. a recent hardware or software change might be the cause. and nothing happenes. again goes 30 sec to choose "launch startup repair" or "normaly booting"...

normaly booting - boots till logon and after 5-10secs shows Different bsod:
Image Hosting

any ideas?

thanks for reading this ^^
sorry for my english
and thanks for help <3
 

My Computer

I doubt it is NOD32. I run Vista x64 and nod32 3.0, and my wife runs Vista x86 (32-bit) with NOD32, and neither of us have had the issues you are having. NOD32 works flawlessly. If you use a registry cleaner I would suspect that as the culprit as they like to delete windows files and .dll entries corrupting the operating system files.

Do an advanced recovery with either recovery partition or Vista disk, and restore to time before you had issues, then check your performance monitor for system stability problems(software, appications, hardware, windows, misc)
Start> in search type "perfmon" (without quotations)>click perfmon> click continue>double click Reliability Monitor
 
Last edited:

My Computer

System One

  • CPU
    T7600G Core2Duo 2.66 Ghz
    Motherboard
    Intel 945PM + ICH7 Chipset
    Memory
    4GB DDR2 PC2-5300 667MHz
    Graphics card(s)
    Mobility Radeon x1900 256MB
    Sound Card
    Realtek HD
    Monitor(s) Displays
    WUXGA 17"
    Screen Resolution
    1920X1200
    Hard Drives
    640GB 7200RPM SATA/RAID 0 (2x320GB) and 320GB 7200RPM External
    Mouse
    Wireless Microsoft 3000
    Internet Speed
    10 mbps/2 mbps
    Other Info
    Optical Drive: Panasonic UJ-220 DL BD-RE (Blu-Ray)
too late...

i recovered files i needed by ubuntu live cd.

and now i already did format with ubuntu and soon will install vista. :)

Hi Pilotaz,

Heres the infomation about the BlueScreen screenshots..Guess you wont be needing them now :(

The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad memory request...The Process thread attempted to free memory, which was already freed.

Resolution: run memory diagnostics

The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.


the second parameter 0x00000008 appears on the screenshot you posted aka Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
  • A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use the !thread debugger extension to determine the stack limits, and then use the kb (Display Stack Backtrace) debugger command with a large parameter (for example, kb 100) to display the full stack.
  • A hardware problem.
Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows i.e. Virus Scanner or Mismatched memory!

Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

The memory scanner is especially important. Faulty or mismatched memory can cause this bug check. For more informaiton about these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

If the error appears on a newly installed system, check the availability of updates for the BIOS, the SCSI controller, or network cards. These kind of updates are typically available on the Web site or BBS of the hardware manufacturer.

If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console in order to access the file.
Also restart your computer, and then press F8 at the character-based menu that displays the operating system choices. At the Advanced Options menu, select the Last Known Good Configuration option. This option is most effective when you add only one driver or service at a time.

Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. You can also disable memory caching of the BIOS to try to resolve the problem.

If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version of Windows.

If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed Windows Service Pack 1

Finally, if all the above steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.
 

My Computer

Why do I get the feeling you'll be back?
 

My Computer

System One

  • Manufacturer/Model
    Fumz' Flux-Capacitor
    CPU
    E8400
    Motherboard
    DFI LP DK P35-T2RS
    Memory
    4GB G.Skill PC-1066
    Graphics card(s)
    eVGA 8800 GTS
    Sound Card
    X-Fi XtremeGamer
    Monitor(s) Displays
    Samsung 226BW
    Screen Resolution
    1680x1050
    Hard Drives
    500GB W.D. RE2 Primary 1TB W.D. Caviar GP WD10EACS
    PSU
    PC Power & Cooling Silencer 610
    Case
    Lian Li Lancool K62
    Cooling
    Thermalright Ultima-90/S-Flex 120mm
    Mouse
    Logitech G5
    Keyboard
    MS Natural Elite 4000 Ergonomic
    Internet Speed
    2.5MB/430
    Other Info
    D-Link DGL 4500
i used recovery cd so now im back to vista ^^
maybe but... ;D but not today for sure, this time i installed kaspersky v7 ;)
everything works just fine :P
 

My Computer

Back
Top