IRQl_NOT_LESS_OR_EQUAL Random BSOD in 3 weeks old ACER 5755G Laptop

Page 3 of 3 FirstFirst 123

  1. Posts : 28,845
    Win 8 Release candidate 8400
       #21

    aaron6530 said:
    is there any way to confirm whether it has been removed or not???? Thanx in advance!!
    McAffee is installed on your crash dated 1/28, but not visible on the 1/31 crash
      My Computer


  2. Posts : 15
    Windows 7 Home Basic x64
    Thread Starter
       #22

    what to do now? Please help! Thanx in advance!
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #23

    aaron6530 said:
    what to do now? Please help! Thanx in advance!

    We are in a holding pattern. Waiting to see if you crash again. If you do you of course know to upload the dmp for examination.
      My Computer


  4. Posts : 15
    Windows 7 Home Basic x64
    Thread Starter
       #24

    this time it was also IRQL NOT LESS OR EQUAL. This time it crashed while playing ASSASSINS CREED REVELATIONS. but i observed that the crashes generally take place at night. All day most probably the machine works fine. But i will upload the dump files for the next crash.
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #25

    aaron6530 said:
    this time it was also IRQL NOT LESS OR EQUAL. This time it crashed while playing ASSASSINS CREED REVELATIONS. but i observed that the crashes generally take place at night. All day most probably the machine works fine. But i will upload the dump files for the next crash.


    We will wait for the dmps
      My Computer


  6. Posts : 15
    Windows 7 Home Basic x64
    Thread Starter
       #26

    Well these were the dumps for the last crash. Hope it sheds some light. Ive run memory diagnostics with 8 passes 3 to 4 times. Theres no problem with the memory. Thanx in advance.
      My Computer


  7. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #27

    Your analysis was inconclusive.
    Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  8. Posts : 15
    Windows 7 Home Basic x64
    Thread Starter
       #28

    another BSOD:-(
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #29

    aaron6530 said:
    another BSOD:-(

    With only one new DMP and none with driver verifier enabled it is still it or miss. There does seem to be some evidence pointing towards your Driver for Intel Graphics Adapter.

    I would re-install the newest version available using these instructions. We still need you to run verifier to be certain.

    When upgrading your graphic driver you MUST remove all traces of the current driver.

    In order to do that we recommend using
    Phyxion.net - Driver Sweeper

    When it is removed then download and install the fresh copy.



      My Computer


 
Page 3 of 3 FirstFirst 123

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:59.
Find Us