BSOD BSOD Driver irql-not-less-or-equal/freezes with immediate restart

Page 1 of 5 123 ... LastLast

  1. Posts : 30
    Windows 7 Professional x64
       #1

    BSOD BSOD Driver irql-not-less-or-equal/freezes with immediate restart


    Hi. I've been having this problem for about one year now and I decided it's time I sought online help. My PC is about 2 and a half years old and the current windows installation is roughly 2 years old (windows 7 professional x64 from microsoft academic alliance...).
    Crashes/freezes happen at random times (I had gone about a month with none) and not when a particular program is running. I've attached minidump files and system health report.
      My Computer


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

    Related to netr7364.sys 802.11 USB Wireless Adapter Driver from Ralink Technology, Corp. I would re-install newest

    ALSO

    Asacpi.sys

    The pre 2009 version of this driver is a known BSOD cause.
    Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

    ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

    Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

    Download and install it.

    Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).
      My Computer


  3. Posts : 30
    Windows 7 Professional x64
    Thread Starter
       #3

    zigzag3143 said:
    Related to netr7364.sys 802.11 USB Wireless Adapter Driver from Ralink Technology, Corp. I would re-install newest
    Done.

    zigzag3143 said:
    ALSO

    Asacpi.sys

    The pre 2009 version of this driver is a known BSOD cause.
    Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

    ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

    Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

    Download and install it.

    Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).
    Done and checked. Time stamp reads: Last Modified:14/5/2009, Date Created:27/5/2012. Will let you know how it goes...
      My Computer


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

    Good luck
      My Computer


  5. Posts : 30
    Windows 7 Professional x64
    Thread Starter
       #5

    Just had a crash restart with no blue screen or freeze. Could be due to power spikes though...
      My Computer


  6. Posts : 30
    Windows 7 Professional x64
    Thread Starter
       #6

    Just had a BSOD with driver-irql-not-less-or-equal. I have attached the minidump...
      My Computer


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


    These crashes were caused by memory corruption/exception (Cx05) probably a driver.
    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!!!

    * If you have a Raid update its Driver.




    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-7 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+






    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.

    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).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    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 "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like.
    From my limited experimentation it makes the BSOD's come faster.
    - 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.

    If you are using win 8 add these

    - Concurrency Stress Test
    - DDI compliance checking

    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.


    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.

    Thanks to JCGriff2 & Usasma.

    Sysnative Forums

    Driver Reference Table (DRT)


    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Driver Verifier

    Using Driver Verifier (Windows Drivers)
      My Computer


  8. Posts : 30
    Windows 7 Professional x64
    Thread Starter
       #8

    Run memtest and my sticks passed the test twice with no errors. I will run the test on each stick individually though sometime in the weekend. I have started the driver verifier thing and so far i have one bsod from 000.fcl. I attached minidumps for this and a couple of other bsods i had while playing League of Legends.
    (I tried to upload the memory.dmp file too but it was too big...)
      My Computer


  9. Posts : 30
    Windows 7 Professional x64
    Thread Starter
       #9

    I'm posting this reply as a reference so here goes:
    Non-microsoft drivers/Tested(yes or no)/Result
    000.fcl/yes/crashed
    asacpi.sys/yes/pending further tests
    asio.sys/yes/pending further tests
    atihdw78.sys/no
    atikmpag.sys/no
    atmfd.dll/no
    dump_dumpfve.sys/no
    dump_iastorv.sys/no
    iastorv.sys/no
    netr7364.sys/no
    pcouffin.sys/no
    pkwcap64.sys/no
    rt64win7.sys/no
    secdrv.sys/no
    serial.sys/no
    speedfan.sys/no
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #10

    000.fcl is part of Cyberlink software. What is the age of your Cyberlink software?


    asio.sys: Asus PCProbe Utility (can probably be uninstalled without causing issues)


    Your asacpi.sys should not be a problem; more than likely it is due to another driver conflicting with it and perhaps asio.sys?
      My Computer


 
Page 1 of 5 123 ... LastLast

  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 07:59.
Find Us