BSOD Cache_memory, IRQL_NOT_LESS_OR_EQUAL_TO, and others.


  1. Posts : 3
    Windows 7 Home premium 64 bit
       #1

    BSOD Cache_memory, IRQL_NOT_LESS_OR_EQUAL_TO, and others.


    Hey all, I'm relatively new at all this. I just installed a new processor and mobo, and I have been plagued with BSOD ever since. Here are my system specs
    CPU-AMD Phenom II 1100t
    MOBO-ASUS 990FX
    RAM-Corsair Vengeance 16GB
    HDD-WD Velocirapter 600GB

    I'm sorry if I did not give all necessary info. I attached the folders that the site told me. Thank you in advance for the help everyone.
    -JP
    Last edited by JPTro; 01 Dec 2011 at 02:06. Reason: Forgot to attach files
      My Computer


  2. Posts : 3
    Windows 7 Home premium 64 bit
    Thread Starter
       #2

    Ok apparently they did not upload? It says invalid file type, even though i zipped them?
      My Computer


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

    JPTro said:
    Ok apparently they did not upload? It says invalid file type, even though i zipped them?
    What was the name of the zip file? it should end in zip.

    Another thing to consider is new members take a day or two to get permissions for that.
      My Computer


  4. Posts : 3
    Windows 7 Home premium 64 bit
    Thread Starter
       #4

    Hey yeah I used 7zip, which apparently is not an accepted zip program. I downloaded winrar, and it worked.
      My Computer


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

    These crashes were caused by memory corruption. 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.


    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

    I'd suggest that you first backup your data 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" 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).

    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.
    Driver Verifier - Enable and Disable


    Also run an sfc

    Run a system file check to verify and repair your system files.
    To do this type cmd in search, then right click to run as administrator, then
    SFC /SCANNOW

    It may need to be run up to three times before sucessful

    Read here for more information SFC /SCANNOW Command - System File Checker

    Let us know the results from the report at the end.


      My Computer


 

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 17:15.
Find Us