BSOD at, or right after, startup

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • YarrOfDoom
    Recognized Expert Top Contributor
    • Aug 2007
    • 1243

    BSOD at, or right after, startup

    Yesterday I assembled my brothers pc and it all worked fine. Something about an hour ago, I finally plugged it in into our router. And a couple of minutes later I got a BSOD, now everytime the pc is started it gives this other BSOD. I've tried repairing and reinstalling Vista from the cd, but it doesn't help.
    Does somebody knows what's going on and how to fix it, or where I could find out?
    These are the specs:

    • Asus P5K
    • Asus EN8600GT Magic
    • Intel Core 2 Duo E6750
    • Xilence Power 550W
    • Maxtor 500GB HDD (SATA)
    • WriteMaster (SATA)
    • 2GB RAM
    edit: there seems to be nothing wrong with the ram-modules
  • YarrOfDoom
    Recognized Expert Top Contributor
    • Aug 2007
    • 1243

    #2
    problem omitted by removing one of the Ram-modules, now it just falls "almost dead"(only leds and fans working) unattended. I'm going to bring him in in one of the following days.

    Comment

    • Studlyami
      Recognized Expert Contributor
      • Sep 2007
      • 464

      #3
      I would search Google for the error your receiving (IRQL_NOT_LESS_ OR_EQUAL).
      The first page that showed up had a few suggestions, or check out this discussion. There were several other pages discussing this error. Try what it says and when you find out the problem let us know.

      Best of luck, it's always annoying when you build a new pc and you encounter errors, or have faulty hardware.

      Comment

      • YarrOfDoom
        Recognized Expert Top Contributor
        • Aug 2007
        • 1243

        #4
        The problem is solved now, the motherboard had something wrong. So it just had to be replaced (under guarantee of course), and now everything is just working fine. (except for Vista complaining that the authentication key is already used on another computer, but that's going to be fixed soon).

        Comment

        Working...