Results 1 to 8 of 8

Thread: Irq_not_less_or_equal

  1. #1
    asphinctersayswhat dannyboy83's Avatar
    Join Date
    Sep 2005
    Location
    Hamilton, Scotland
    Posts
    677
    Thanks
    3
    Thanked
    0 times in 0 posts

    Irq_not_less_or_equal

    Has there ever been a difinitive answer to these BSOD crashes?

    I had them a lot before. Then I bought a new mobo, hard disk, graphics card (practically rebuilt system) and have started getting them again.

    Windows was completely reinstalled on a new Hard Disk.

    It's driving me nuts. Could it be the RAM? surely its not a CPU problem, or even a PSU problem.

    My System: Coolermaster Centurion 5 (black) case, Intel E6750 Core2Duo, Tagan Easy-Con 530W, Asus P5B Deluxe WIFI, OCZ 2GB Kit (2x1GB) DDR2 800MHz/PC2-6400 CL 4-4-4-15 PLATINUM XTC, Samsung SpinPoint 200Gb SATA2 / 2 x Maxtor DiamondMax 10 200Gb SATA, 256Mb Sapphire ATI PCI-E X1950PRO, Creative X-Fi Xtreme 7.1, 19" Daewoo W9ZQ Black Widescreen TFT, 4Mb Virgin Cable Broadband (formerly Blueyonder) with Linksys WRT54GL Wireless-G and DD-WRT firmware.

  2. #2
    Splash
    Guest
    I've seen it be a lot of things, but it usually comes down to RAM - run a RAM checker on the machine and see what happens.

  3. #3
    Registered+
    Join Date
    Jan 2006
    Location
    south uk
    Posts
    32
    Thanks
    0
    Thanked
    0 times in 0 posts
    thought it ment that the system had run out of mem and has had to close used to see it alot when i had 512mb of ram with x64
    AMD4400+ X2@2742mhz 2GB 0CZ pc4000 EB
    AN8 x32,150gb Raptor's in raid0 ,7900gtx's sli'ed
    Tagan u-15 580w Samsung 244t thermaltke tai chi watercooled case

  4. #4
    Gaarrrrr! Dav0s's Avatar
    Join Date
    Aug 2005
    Location
    Bristol
    Posts
    1,442
    Thanks
    1
    Thanked
    3 times in 3 posts
    if it did do that it would use the page file, not just die lol

    its usually a ram error, run memtest or put your system to stock

  5. #5
    Senior Member
    Join Date
    Aug 2005
    Location
    Surrey
    Posts
    299
    Thanks
    3
    Thanked
    4 times in 4 posts
    I have had these with bad drivers or graphics cards and faulty graphics cards as well.
    Intel i5 2500K
    Gbyte Z68mx-ud3
    2x 4GB Corsair Vengance
    NEC ND3540A BLACK DVDR
    1TB HDD
    Sony SDM-HS75P 17" TFT
    Logitech Cordless Mouse and Keyboard LX700

  6. #6
    Large Member
    Join Date
    Apr 2004
    Posts
    3,720
    Thanks
    47
    Thanked
    99 times in 64 posts
    Errors like this are caused by anything that windows dosn't agree with, and therefore could quite literally be caused by anything. That said, it will usually be either a driver or hardware setting that is to blame. Some are les obvious than others (i.e. a driver installed by an iteration of ZoneAlarm caused BSOD's for a lot of people), some are just fantastically gob smacking (Windows sometimes quite literally makes a balls up of pre-install and subsequently installs the wrong HAL configuration for your system, which is a certain candidate for BSOD's).

    To be quite honest, you can't be helped. You will have to go through a process of elimination.
    To err is human. To really foul things up ... you need a computer.

  7. #7
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    Along with the brief 1-liner on the bugcheck should be a STOP code and maybe a filename which give a bit more information to work on.

    Also, if you check in the Event Viewer and look in the System event log you should find a record along the lines of "Windows has recovered from a bugcheck" and have the details recorded in there.

    My only personal experience with IRQL_NOT_LESS_THAN_OR_EQUAL bugchecks has been display drivers (typically nVidia), and upgrading (or sometimes regressing) them has fixed the problem.
    I would be more inclined to think it a driver problem than a hardware issue.
    Last edited by Paul Adams; 20-01-2006 at 09:45 PM.

  8. #8
    www.5lab.co.uk
    Join Date
    Sep 2003
    Posts
    6,406
    Thanks
    1
    Thanked
    0 times in 0 posts
    i'd reset all the irqs on your bios - do a full flash/restore to defaults - see if that sorts it
    hughlunnon@yahoo.com | I have sigs turned off..

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •