Freezes, BSOD IRQL Not less or Equal 0x0a

  1. Posts : 3
    Windows 7 64bit

    Freezes, BSOD IRQL Not less or Equal 0x0a


    Approx. a month and a half ago my computer started randomly stalling when idle, at first 1-2 times a week and then daily. After some time, it started only stalling 1-15 minutes after boot, and then would run perfectly fine for hours if it got past that first period, even if idled.

    In the third week, I started getting the following BSODs - Irql not less or equal 0x0a, Page fault in non paged area and eventually also System Service Exception (targeting tcpip.sys). My computer is set up to save small memory dmps but it only has one dump from /08 and it is not saving them when it BSOD's. Sometimes it says that it has saved the data on the screen but there's nothing to be found after or it gets stuck on Collecting data...

    When the computer freezes, basically it comes to a stall and doesn't respond to the keyboard and mouse (keyboard does not register input at all if locks are pressed etc.). This has happened also in safe mode, but only once. Sometimes now, it auto-restarts rather than freezing. Crashes are intermittent, there can be days where it boots and runs OK. If it doesn't crash within 20 minutes of being started up, then it's fine until rebooted the next day.

    So far I have:
    - Cleared some misc errors from event log which haven't had any effect
    - Run memtest to test the RAM (Passed)
    - Ran chkDisk, startup repair & memory diagnostic (Passed)
    - Uninstalled avast! & installed AVG
    - Scanned for virus/malware and cleaned registry
    - Checked nothing has problem icon next to it in Device Manager
    - Updated video drivers a couple times, checked Dell/Intel site but not had any recommended driver updates suggested except one which turned out to be older than my current version; I'm not too sure when it comes to non-video driver updating, I've never had any driver-related problems and needed manual updates for a PC before.

    Install/Update history: It had been about a week at least since I installed any new software on the PC as far as I recalled, and there were recommended/important Windows Updates auto-installed the night before it first started freezing up.

    I am not having much luck tracing the cause of the freeze & bsod (freeze is much more common) because I can't get the dumps to save. I am guessing this is related to the particular problem/s my PC has. I have attached the .rar from SF Diagnostic.

    Any help/advice is most welcome and appreciated

      My Computer

  2. Posts : 3,056
    Windows 10

    Welcome :) .
    Sorry that no one replied until now.

    Let's get to it.

    What you're describing sounds like a Disk is slowly degrading
    I don't think it to be the case at the moment but it's worth a test.
    The Following Method Should NOT Be Performed On An SSD!

    Testing the HDD:

    1. Perform a Disk Check | Disk Check
    2. Then Post the results following | THIS METHOD
    3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

    If SeaTools For DOS does not recognize the drive;
    Boot into the BIOS using the *Fxkey.
    Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
    It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
    Set it to IDE then save and exit usually by pressing the F10 key.
    Now boot into SeaTools and it should detect the drives.
    Start the Long Test and let it run.
    Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
    and change the SATA setting back to what it was in the first place.

    The last bugcheck recorded was as you said from August 29th.

    BugCheck 1E, {ffffffffc000001d, fffff800032ad005, 2, fffffa8009ae9000}
    Probably caused by : memory_corruption ( nt!MiCopyDataPageToImagePage+99 )
    Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    PROCESS_NAME:  netsession_win
    I see a fair bit of memory activity in the dump, nVidia's driver was somehow involved as well.
    This is most probably a driver at work but it can also be an infection.

    Perform a clean start up by following this tutorial.

    Please scan for possible infection and file corruption.

    (*Kaspersky Rescue CD from a USB thumbdrive)

    Please follow this detailed quote and install a more stable release.

    Arc said:
    Install the 314.22 WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

    You said you tested the RAM, how?

    Arc said:
    Your crash dumps are not showing any finite probable cause.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Arc said:
    First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

    But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
    If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.


    Let us know the results, with the subsequent crash dumps, if any.
    Keep us posted.
      My Computer

  3. Posts : 3
    Windows 7 64bit
    Thread Starter


    Thanks for the welcome and the reply.

    I got several more Page Fault errors so I decided to test the RAM with memtest86 again this morning and took a look at number of passes recommended etc. and saw the mention of trying it both warm&cold. I previously ran it when the computer was working OK in the evening and not crashing. This time I ran it off a cold boot with the intention to leave it going whilst I was at work and it got 1234 errors at test 4 @ only 4 minutes on the clock before I left. Memtest also completely froze up so I couldn't continue on with it.

    Since it froze up, I'm not sure if it's another hardware component that was faulting but I am going to start singling out the RAM to see if I have a bad stick or if all the RAM is similarly struggling. The problem seems to be temperature-related/cold boot because once the PC "warms up" all the problems go away and can't be detected. Fortunately and unforunately, it's running fine for 10 minutes so far since I turned it on this evening which means I can't progress til it starts error'ing again :)

      My Computer

  4. Posts : 3,056
    Windows 10

    Thanks for the update and cooperation :) .
    1234 errors? nice number .

    Yes it's the right thing to target the RAM / motherboard slots at the moment.
    You can always let the PC cool down (shut it down for 15 minutes or so) and try to pin point what the issue
    is by following the table above :) .

    Also you can test the PC for thermals.

    • Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
      • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).

      My Computer

  5. Posts : 3
    Windows 7 64bit
    Thread Starter

    I took the first RAM stick out and it's been perfectly fine since. Seems I got the luck of the draw.

    Thanks for the help
      My Computer

  6. Posts : 3,056
    Windows 10

    Thanks for updating back with a cause :) .
    Happy computing.
      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 08:07.
Find Us