BSOD in Windows 7 Problem

mangew on 14/02/2015 - 21:58
Last edited 14/02/2015 - 22:23

Help! I am having a BSOD error on Windows7. IRQ_L_NOT_LESS_OR EQUAL
It seems to be getting worse to the point I cannot boot into windows nor in safe mode without it going to BSOD.

This issue occured post removing my SODIMM memory from laptop. I've tried reinstalling both chips in various configs to no avail. Reverting back to how it originally was but no help. I even disabled memory protection in bios.

I performed system restores to last good boots but now it fails.
I am perplexed with whst is the issue. I have run windows diagnostic test on my memory and doesnt show issues.

Screenshot of bsod

Computing

Related Stores

Microsoft
Microsoft

Comments

  • scrimshaw on 14/02/2015 - 22:16

    IRQL Not less or equal is a generic BSOD message pointing to a driver issue.

    It could also in some circumstances point to faulty hardware, if this is the case your only recourse is to get the laptop serviced.

    Usually in this circumstance, you would check the Event Viewer to see what caused the crash, and analyze the .dmp (dump) files created during the BSOD event to see what actually caused it. But if you can't start into Safe Mode then that complicates things abit, but you can still retrieve the dump files via other methods (pulling out the drive from the laptop and sticking into a HDD dock, or booting Linux Live CD instead of Windows)

    If Safe Mode fails, I would start off with attempting to repair or reinstall Windows to see if that helps (it's a good idea to backup your stuff first).

    • mangew on 14/02/2015 - 23:20

      Well i made it into safe mode and looked at event viewer and BSV.
      Not sure what to make of it but hightlights ntoskrnl.exe
      It is getting out of my league now and not sure what to do next, so far it hssnt had a BSOD while in safe mode for a hour now. Shame i cannot go online in safe mode. Seems like a fresh OS install?

      • scrimshaw on 15/02/2015 - 11:16

        You haven't tried testing the machine with brand new RAM yet have you?

        • mangew on 15/02/2015 - 21:43

          Not yet. Why? I am about to buy new ram to see if that fixes it.

        • cypher67 on 15/02/2015 - 22:59

          @mangew: Run a Memtest first, doesn't take long and could save you time and money

        • mangew on 16/02/2015 - 06:45

          @cypher67:

          I ran the windows diagnostic memory test and had no errors.

        • cypher67 on 16/02/2015 - 08:17

          @mangew:
          Windows one is terrible, download the memtest one and boot it from DOS.

  • cypher67 on 14/02/2015 - 23:39

    I find that BSOD are 1 of 3 things, Your Hard drive has rooted partitions and I suggest running HDD test using SeaTools (DOS boot), Your memory has a bad section so run Memtest (again DOS boot), or your Windows in Corrupt which means you can try do a windows repair to see if it fixes the issue otherwise its a fresh install. Id check your HDD and Memory before doing the windows part.

  • Ramrunner on 15/02/2015 - 10:39
    +1

    I'm a technician and my GUESS/OPINION (no flames please this is my honest opinion) is that when you played around with the memory you did not take anti-static precautions, had a small discharge into one or both of your SoDIMMS, which is/are now irreparably damaged.

    Memory chips and motherboards are EXTREMELY sensitive to static, and unfortunately our bodies build up static on a constant basis. A slight touch on the copper contacts at the wrong time and it's over red rover.

    90% of the YouTube clips I watch do not use precautions either which is unfortunate as this is where most people now seem to get their knowledge.

    The other 10% of YouTube clips they use special anti-static gloves when handling sensitive parts, OR you can get away generally with using some sort of anti-static mat (purchased or using one of those bags your motherboard came in), using an anti-static wrist strap or at the very least touching a grounded metal frame of some sort to discharge yourself before touching sensitive computer parts.

    This is based on what you've told me, and having laptops brought in with same issues, and remarkably a similar story to what you just told. I do not think it is coincidence this happened after touching your memory. In the tech world coincidences rarely happen

  • Kawaii69 on 15/02/2015 - 17:38

    I'd have to agree with Ramrunner, I built my own computer and a few months later I plugged in an iphone 4 that was faulty and caused my computer to short circuit, 2 days later i got bsod, had to reinstall windows and it's been working fine, the short circuit that was caused effected my hdds. So I'd suggest reinstalling windows

  • Bystander on 15/02/2015 - 19:30

    Clean the contacts on the RAM. I use folded photocopy paper pinched between my fingers. Usually I will see oil/dirt left on the paper. Worked many times for me in various situations. Might help you. P.S. Never touch the contacts. Skin oil interferes with the connections.

  • mangew on 16/02/2015 - 12:46

    Something weird just happened. I left it off (laptop) for a day and tried it out today and suddenly works again (so far)
    I have been on for a few hours now. Running antivirus and CPUID so have no idea what the issue is/was???!

    • MasterScythe on 19/02/2015 - 09:32

      I do; Ram not seated properly, or dirty contacts.
      What did Memtest have to say?

      • mangew on 19/02/2015 - 10:54

        memtest x86 v5.01 had no errors. So you are right, must of been a fleck of dust or something on the contacts.

        The annoying thing that happened was I went out and bought new ram (Patriot) and it ended up having errors according to memtest. So refunded.

Login or Join to leave a comment
Login Join