DRIVER_IRQL_NOT_LESS_OR_EQUAL in NDIS.SYS

mtroxmtrox Minnesota
edited March 2007 in Science & Tech
Client is in New York right now....he can't boot up without getting a BSOD with DRIVER_IRQL_NOT_LESS_OR_EQUAL and mentioning NDIS.SYS.

I know this can be a bad memory error, but the NDIS.SYS thing is always NIC related, and all the advice I can find tells me what to do while I'm in Windows. This guy's a good user. He says he gets the BSOD whether he boots normally or tries to go into safe mode. On a real computer I'd pull the NIC and see if it boots. But this is a lappy. Anyone seen this before you even get into Windows? He'll be back in town tomorrow.

Comments

  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited February 2007
    I'm sure you've already Googled the problem, so I'll skip the rehash of what I've found there. (I'll be happy to link you up, if requested to. :) )

    My first thought is that since your client is on the road he has encountered one of the following:

    1) Had to set up some weird proxy to get into a Network where is is staying, which borked his Network settings.

    2) Was surfing some {ahem} questionable sites to alleviate the boredom of traveling and picked up an SVT-type problem.

    Is he competent enough to be able to disable the onboard NIC in the BIOS, should that option even be available? That might give you a shot at booting up far enough to work on the problem.
  • mtroxmtrox Minnesota
    edited February 2007
    profdlp wrote:
    Is he competent enough to be able to disable the onboard NIC in the BIOS, should that option even be available? That might give you a shot at booting up far enough to work on the problem.

    Good idea. Hadn't thought of that one Prof. He'll be back tomorrow AM and I'm supposed to be there first thing (he's panicked to say the least). Thanks, I'll see if I can kill the NIC in the BIOS. As for the SVT.......there's usually not a lot of bread crumbs leading back to "those kinds of sites" on his computer. But if I can get in...that is a question to ask. I might be doing one of those deals where you get in with Barts and pull and old registry out of Sys Restore.
  • mtroxmtrox Minnesota
    edited February 2007
    Thanks for the effort Prof but as usual, when you see the computer its a bit different than the client describes it. You could log in, but got an error soon after that. He mentioned that his hard drive was almost full so I looked. On a 30 hard drive, he had 234 KB free. Thing was just crawling. He's getting a new laptop in a couple weeks so I parked 3 Gigs of music onto the server. No errors now.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited February 2007
    Yep, that's pretty much on the full side. ;D
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    My machine is getting just IRQL_NOT_LESS_OR_EQUAL. I tried pulling the PCI NIC but nothing. I even swapped PSU and HDDs. I tried reinstalling WinXP onto a new HD and the thing BSOD during the install. I'm stumped. is my next check the RAM? I haven't swapped out the videocard and my MoBo doesn't support onboard so I can't even check that. If that could be a problem I might be able to snag a friend's but I just haven't even tried yet.
  • mtroxmtrox Minnesota
    edited March 2007
    Private, you have to pay attention to the file that's mentioned near the bottom too, and the Stop error code. If the file is NDIS.sys like mine was, that's all about the Ethernet card.

    A memory test is never a bad idea with a BSOD error. Faulty RAM or pagefile problems can produce that error. Here's the page on DRIVER_IRQL_NOT_LESS_OR_EQUAL from aumha.
  • mtroxmtrox Minnesota
    edited March 2007
    Just re-read your post. If you're getting a BSOD during an install, I would move hardware concerns way up the list. Test your memory with a Mem86 boot disk. When you're installing to a new HD that doesn't leave a lot of hardware to test. Install with no peripherals at all...no PCI cards, nothing. If it installs, start adding things...slowly. Reboot after each install to make sure you don't blue screen.
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    mtrox wrote:
    Just re-read your post. If you're getting a BSOD during an install, I would move hardware concerns way up the list. Test your memory with a Mem86 boot disk. When you're installing to a new HD that doesn't leave a lot of hardware to test. Install with no peripherals at all...no PCI cards, nothing. If it installs, start adding things...slowly. Reboot after each install to make sure you don't blue screen.

    I can do that, I'll get back when I try that out. Hope I can figure this thing out soon.

    Thanks for the help so far.
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    mtrox wrote:
    Just re-read your post. If you're getting a BSOD during an install, I would move hardware concerns way up the list. Test your memory with a Mem86 boot disk. When you're installing to a new HD that doesn't leave a lot of hardware to test. Install with no peripherals at all...no PCI cards, nothing. If it installs, start adding things...slowly. Reboot after each install to make sure you don't blue screen.

    I was able to get my system booted up this time, no BSOD on the install. It works fine for a few hours then cuts off now, except I think it is different because the blue screen is only flashing up then restarting, its not doing the memory dump like it did.

    Its flashing too fast though, so I can't read it, is there a file where it would be that I can see what the error is posting?

    Thanks
  • mtroxmtrox Minnesota
    edited March 2007
    Is the blue screen flashing by too fast because its rebooting right away? If so, go to Control Panel> System. Then in that window hit the Advanced tab, then click the Settings button under Startup and Recovery. Halfway down in the next window, uncheck the box beside, "Automatically restart".

    Now you should be able to read the blue screen.

    How did you get in? Did you take off some hardware?
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    mtrox wrote:
    Is the blue screen flashing by too fast because its rebooting right away? If so, go to Control Panel> System. Then in that window hit the Advanced tab, then click the Settings button under Startup and Recovery. Halfway down in the next window, uncheck the box beside, "Automatically restart".

    Now you should be able to read the blue screen.

    How did you get in? Did you take off some hardware?

    Thats the reason, now I just need to wait for it to blue screen for me to read it.

    I took the NIC card I had out and used the onboard ethernet connection. It seemed to fix one problem, now it would appear I'm having another somewhere else :(.
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    The only thing the blue screen is telling me is that normal hardware thing, no file or anything is linked to it. All I have is a stop message under Technical Information, should I write that stop message down and tell you about it?
  • mtroxmtrox Minnesota
    edited March 2007
    Yea do.....take a picture if its easier than writing it all down. Seriously, its all those lame camera phones are good for.
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    Quick update on my BSOD issue.

    My rig has BSODed two times recently and neither were IRQL_NOT_LESS_OR_EQUAL.

    The first one was PAGE_FOUND_IN_NONPAGE_AREA

    the second was DEREF_UNKNOWN_LOGON_SESSION. The tech data for the second Blue Screen was STOP: 0x0000046 (0x00000000 0x00000000 0x00000000 0x00000000)
  • mtroxmtrox Minnesota
    edited March 2007
    Private have you tested the memory on that? That 0x50 PAGE_FOUND_IN_NONPAGE_AREA error is often memory, but can be other hardware issues. The 0x46 error is pretty rare.

    I think you need to get to know BSOD's. This is a great site to start out. And when you find your errorr click on the Win XP Resource Kit link behind it.

    I strongly suspect some hardware. I'd download Memtest (make a boot disk so more memory is free to test). You might also defrag your pagefile. Download PageDefrag.zip here and run that.
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    mtrox wrote:
    Private have you tested the memory on that? That 0x50 PAGE_FOUND_IN_NONPAGE_AREA error is often memory, but can be other hardware issues. The 0x46 error is pretty rare.

    I think you need to get to know BSOD's. This is a great site to start out. And when you find your errorr click on the Win XP Resource Kit link behind it.

    I strongly suspect some hardware. I'd download Memtest (make a boot disk so more memory is free to test). You might also defrag your pagefile. Download PageDefrag.zip here and run that.

    I have a memtest boot disk handy, I used it once before and it took 3 hours and was 15% done, is that normal? The first 15% was error free though :P.

    I'm reading that site now, lots of info thanks for the link.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited March 2007
    Three hours for 15% is kind of on the slow side. Were you watching the "Pass" column carefully? As soon as you see a "1" there it means you've completed one full pass. The program will run forever, if you let it. :)
  • Private_SnoballPrivate_Snoball Dover AFB, DE, USA
    edited March 2007
    profdlp wrote:
    Three hours for 15% is kind of on the slow side. Were you watching the "Pass" column carefully? As soon as you see a "1" there it means you've completed one full pass. The program will run forever, if you let it. :)

    Perhaps it did run fine than, I'm not fully sure because I was looking at a bit of things I didn't fully comprehend the meaning to. I shall run it tomorrow and see how it goes, over the three hours however there were no errors found.
  • GorbyGorby
    edited March 2007
    Hi, I was doing a search for this error message and saw this thread so I thought I'd post my problem here after reading.

    I just recently got this BSOD also. I was just browsing some news on the web and puter froze, then got the BSOD.

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    Stop: 0x000000D1 (0x00000008, 0x00000002, 0x00000000, 0xBA5D2BEF)

    NDIS.SYS - Address BA5D2BEF base at BA5BC000, Datestamp 41107ec3

    Not sure what this is, but I've gotten this 3x in the last couple days.

    Any other information I need to post, please let me know.
  • mtroxmtrox Minnesota
    edited March 2007
    Gorby,

    This thread's getting a little out of control so I started a new one for you over here. DRIVER_IRQL_NOT_LESS_OR_EQUAL in NDIS.SYS Part Deux
Sign In or Register to comment.