Announcement

Collapse
No announcement yet.

Win 7 BSOD: irql_less_than_or_not_equal

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Nope, it's still doing it!

    The stupid thing is, when it crashes, it doesn't even tell you what driver caused the error - you need to run the Blue Screen analysis thing to find out.

    This time it was ntoskrnl.exe and USBSTOR.SYS which are highlighted in red. I'll update the chipset drivers and ask Gigabyte what gives and report back.

    Comment


      #32
      Check that you haven't got any dodgy things plugged in via USB. Could be a haywire USB device or one of the ports shorting (although usually windows warns you if it detects that)

      Comment


        #33
        I do have an Apple keyboard. That was problematic on my old motherboard, and on this one before I upgraded the firmware. Hmm. Looks like a process of elimination, which is going to be a pain, because the error isn't always repeatable.
        Last edited by Lyris; 28-01-2011, 23:38.

        Comment


          #34
          Might be worth you checking your USB version against the ones listed here? http://blogs.msdn.com/b/usbcoreblog/...s-version.aspx

          Comment


            #35
            I think I found the culprit: the Cinema Craft Encoder USB copy protection dongle. Had a successful cold boot today with it unplugged.

            Comment


              #36
              Huh... makes sense... I've had a couple of tales from people suffering similar with other copy protection dongles, I guess it never triggered in my head to ask if you were using one.
              Lie with passion and be forever damned...

              Comment


                #37
                False alarm - still happening!

                Gigabyte (UK) support said "It's a Windows problem" (no Scheiße?) and told me to use Google or read this. Wow, I wish I had thought of using Google before, thanks Gigabyte. Maybe I'll ask the US people for support so I can actually get some.

                The trouble is that the problem is hard to debug because it only happens when the PC is turned on after many hours of non-use.
                Last edited by Lyris; 26-02-2011, 15:28.

                Comment


                  #38
                  Sounds a whole lot like a problem with the chipset.

                  See if there are people having the same kind of problem with your make of motherboard

                  Comment


                    #39
                    Do you have any other issues besides the BSOD?

                    I fixed a PC recently that had the same error with a secondary issue of web pages being re-directed. It was a rootkit causing the issue.

                    Comment


                      #40
                      Just the BSOD. Everything else is peachy.

                      Oh look, I'm not the only one. How did I miss this before?

                      Comment


                        #41
                        Maybe it has something to do with SSD and power management, do you have a HDD where you can install win7 onto and try letting it run for a day? Or switch the SSD to always on under power management, and see if it makes any difference.
                        To be honest i would ask for a refund and get another board.

                        Comment

                        Working...
                        X