Vista Home Premium BSOD driver_irql_not_less_or_equal

By shaiman
Jun 2, 2009
  1. Hi all,

    I know this type of error has been posted several times before, but nonetheless
    I would appreciate your help.

    As mentioned above I get a BSOD on my Windows Vista Home Premium system
    at irregular intervals. The affected .sys-file is almost always a different one. The
    BSOD mostly occurs two hours after system boot at latest. The system is not
    under heavy load because I'm running only Word/Excel and two or three Internet
    Explorer windows.

    Here are the hardware specs:
    Fujitsu Siemens Amilo PA 2510
    - AMD Turion64 X2
    - ATI Radeon Xpress 1200 graphics board with 128 Megs
    of shared RAM configured
    - Realtek RTL8101 Fast Ethernet NIC
    - Atheros AR5007EG WiFi Adapter
    - Western Digital WD2500BEVS-22UST0 Hard Disk

    I've double checked the system RAM with memtest86, but there occurred
    no errors. I've also run the WDC drive fitness test, but again with no errrors.

    I'll attach some of the most recent minidump files that were created after
    the crashes.

    Again, I'd be really glad if someone could help me pinpoint the problem :)


  2. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    Your issues lies with your Symantec/Norton driver SYMTDI.SYS. We have seen more people than we can count have issues with this software and particularly this driver.

    1. Completely uninstall Symantec from your system. To do this properly, after you uninstall then you need to go to their website and find their removal tool for your particular version and use it. This software is notorious for leaving remnants of itself behind so much so that Symantec had to create a special tool to make sure a system is free of any of their left over drivers.

    2. You could simply update it to see if that corrects it.

    3. Completely uninstall and use a better option.
  3. shaiman

    shaiman TS Rookie Topic Starter


    wow, that was a quick reply :)

    just for the sake of completeness (and my curiosity) ;) :
    how could you conclude from the minidumps that the Symantec
    software causes the problem?

    Kind regards,

  4. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    To answer your question, in every one of your minidumps the driver SYMTDI.SYS was either cited as your probable cause or its symbols could not load. Again, many, many, many people have had issues with this driver and software.
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...