BSOD after fresh install of windows 7 x54 (IRQ_NOT_LESS_OR_EQUAL)


  1. Posts : 7
    Windows 7 64 bit
       #1

    BSOD after fresh install of windows 7 x54 (IRQ_NOT_LESS_OR_EQUAL)


    Hello,

    I have just formatted my desktop pc and installed windows 7 from scratch.

    For 2 weeks now, everything was running fine (no issues or BSODs).

    However, today I got a dump of windows 7 twice.

    I have run the analysis from dm log collector.

    The results are found in the attached file.

    Any help will be appreciated.

    Thank you.

    --- Update ---

    Second/Third dump has just occurred. Uploading the updated files.
      My Computer


  2. Posts : 335
    Windows 7 Pro 64 bit SP1
       #2

    I did analysis and said 'probably caused by ntfs.sys' BAD_POOL_CALLER.

    I would test your hard drive with mini tools partition wizard (do surface test) Or are you using SSD? And always run Ram test after blue screens. Use memtest86
      My Computer


  3. Posts : 7,050
    Windows 10 Pro
       #3

    Please uninstall Avast and use Microsoft Security Essentials as alternative while troubleshooting
    Avast - Uninstall Completely
    Microsoft Security Essentials - Microsoft Windows
    Code:
    *** WARNING: Unable to verify timestamp for aswStm.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
    fffff880`031fbc18  fffff880`02ece0cdUnable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for aswSnx.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
     aswSnx+0x510cd
    Please update the Realtek network driver
    Driver Reference Table - Rt64win7.sys
    Code:
    fffff880`031fbd08  fffff880`04764f12Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0x16f12
    3: kd> lmvm rt64win7
    start             end                 module name
    fffff880`0474e000 fffff880`04780000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Thu Feb 26 10:04:13 2009 (49A65B0D)
        CheckSum:         000361A5
        ImageSize:        00032000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  4. Posts : 7
    Windows 7 64 bit
    Thread Starter
       #4

    OK!

    Thank you guys.

    I have 2 HDDs and one SSD ( recently bought ).

    However, the BSOD issue occurred also before buying the SSD disk.

    I will do the following:

    1) Currently I'm checking my HDDs using CHKDSK /F /R
    2) After (1) has finished, I will download miniTool partition wizard and also
    3) Un-install Avast and update my realtek drivers
    4) Do a surface scan with the miniTool
    5) Do a memtest (leave it for the whole evening)

    I will post here the results and let you know!
      My Computer


  5. Posts : 7
    Windows 7 64 bit
    Thread Starter
       #5

    Hello again,

    I come back with the results.

    1) CHKDSK didn't return any errors for my HDDs
    2) I un-installed AVAST and updated my realtek drivers
    3) miniTool didn't return any errors also
    4) Memtest ran for approx. 12 h and didn't return any errors
    5) I also ran an OCCT test for my GPU and still no errors

    Seems that everything works OK, but do you happen to know how can I "stress" my desktop in order
    to produce this BSOD?

    Thank you.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    The best way to 'stress' your system is by trying to get a bluescreen again.
    Stressing the GPU, CPU or trying to stress the system in any way might not put the stress on the system that you want.
      My Computer


  7. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #7

    Run Driver Verifier for 24 hrs.

    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
      My Computer


  8. Posts : 7
    Windows 7 64 bit
    Thread Starter
       #8

    Hi,

    I just had a couple of BSODs.

    For about 3 days my pc was running fine.

    Today I installed a new DVD-RW drive and my system crashed when performing a surface scan on my new SSD drive (with miniTool).

    I have attached the new dump files here (I got 3 dumps in a row!).

    Any help (again) will be appreciated!

    Thanks!
      My Computer


 

  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 06:09.
Find Us