locked
Windows 7 64 bit bsod RRS feed

  • Question

  • Hi All,

    I recently did a fresh install to windows 7 home prenium 64 bit. The system gets a bsod after being up fow awhile, I'd say from 15 minutes to several hours. I have ATI CCC installed. I've performed a hotfix (KB979444-x64), disabled the ati hd audio driver that was part of the ATI CCC, and tried different power option settings. Nothing has worked. The event viewer shows it is a kernel-power 43 (61) critical error. The blue screen contains STOP: 0x0000000A and  IRQL_NOT_LESS_OR_EQUA. Last night I ran the extended memory diagnostics and it completed without error.

    I'm real close to loading XP that had been running on this machine for over one year without any crashes but I thought that I'd ask the experts for help first.

    The machine has:

    ecs 780GM-A v1.0 motherboard

    adata ddr2 800 memory (8GB)

    xfx radeon hd5450 video card

    amd 9750 processor

     

    • Edited by bruboy Friday, November 5, 2010 12:07 AM added cpu type
    Friday, November 5, 2010 12:03 AM

Answers

  • IRQL_NOT_LESS_OR_EQUAL

    KMODE_EXCEPTION_NOT_HANDLED

    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc000001d , The exception code that was not handled

    //
    // MessageId: STATUS_ILLEGAL_INSTRUCTION
    //
    // MessageText:
    //
    // {EXCEPTION}
    // Illegal Instruction
    // An attempt was made to execute an illegal instruction.
    //
    #define STATUS_ILLEGAL_INSTRUCTION       ((NTSTATUS)0xC000001D L)

    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download

     


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Friday, November 12, 2010 10:40 AM
    Saturday, November 6, 2010 2:47 PM

All replies

  • A bugcheck (BSOD) is a mechanism to protect your PC from damage.

    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL - This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    http://msdn.microsoft.com/en-us/library/ff560129%28VS.85%29.aspx

    It is also helpful to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your Skydrive [1] and post a link here, so that I can look at the dumps with the debugger and to to see the cause of the crash.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, November 5, 2010 1:27 PM
  • Thanks very much for taking the time to look at this. Here's the link you asked for, it contains 3 dmp files.

     

    http://cid-1b69fe4d71ec9e27.skydrive.live.com/redir.aspx?resid=1B69FE4D71EC9E27!103

    Friday, November 5, 2010 11:04 PM
  • IRQL_NOT_LESS_OR_EQUAL

    KMODE_EXCEPTION_NOT_HANDLED

    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc000001d , The exception code that was not handled

    //
    // MessageId: STATUS_ILLEGAL_INSTRUCTION
    //
    // MessageText:
    //
    // {EXCEPTION}
    // Illegal Instruction
    // An attempt was made to execute an illegal instruction.
    //
    #define STATUS_ILLEGAL_INSTRUCTION       ((NTSTATUS)0xC000001D L)

    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download

     


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Friday, November 12, 2010 10:40 AM
    Saturday, November 6, 2010 2:47 PM
  • Thanks Andre! I'm running memtest now. I did notice that the memory manufacturer rates the dimms at 1.9v-2.1v but sites that reviewed the memory show the spec at 2.0v-2.1v. I was running it at ~1.96v so I kicked it up to ~2.05v.

    Previously i was running 32 bit xp so two of the four banks weren't being hit. I'll let memtest run for ~5 hours as you recommend and let you know the results.

    Thanks again!

    Saturday, November 6, 2010 4:13 PM
  • Hi Andre,

    Memtest has been running for a little over 5 hours and the 3rd pass is almost complete, no errors have been detected.

    Perphaps the voltage boost did the trick. After memtest completes the 3rd pass I'll boot the machine and see how long it stays up.

    Saturday, November 6, 2010 9:43 PM
  • Perphaps the voltage boost did the trick.

    it looks so.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, November 6, 2010 10:57 PM
  • Andre,

    My system hasn't had any more bsod so it looks like it was the voltage setting on the dimms. Once again thanks for taking the time to pinpoint the source of the problem.

    Monday, November 8, 2010 3:09 PM