Questions

IRQL_NOT_LESS_OR_EQUAL Blue Screen !!

+
0 Votes
Locked

IRQL_NOT_LESS_OR_EQUAL Blue Screen !!

tmlfan_99
Hey guys, after about 30 mins of running COD4 or COD5 I get a blue screen with the following error:

IRQL_NOT_LESS_OR_EQUAL
Stop: 0x0000000A (0x00000000, 0x000000FF, 0x00000000, 0x806E4EA0)

I am running an AMD 6400+, 4 GB RAM, ATI 3870, Windows XP Home.
  • +
    0 Votes
    michaelaknight

    Without reading the previous post, I'm going to say it's a corrupt or incompatible video driver especially given the application running. Could just as easy be a soundcard driver if you're using a beefy card.
    layman wise the error is saying that a piece of memory was trying to be read and couldn't due to any number of reasons but in this case I'd bet on a device driver.

    make sure you have the most up to date drivers for those devices and if thay are the most up to date maybe roll em back to a more stable version.

    +
    0 Votes
    tmlfan_99

    I had updated my ATI drivers to 8.10 and same thing still occurs.

    +
    0 Votes
    patrick

    Heat issue hows your case temps and CPU temp? not running too hot are you?

    -P

    +
    0 Votes
    tmlfan_99

    How can I check? I highly doubt that is the case as I use the Antec 900

    +
    0 Votes
    wanttocancel

    "This error usually occurs after the installation of a buggy device driver, system service, or BIOS." This includes antivirus. I would roll back drivers of device, system or BIOS you updated, if any.

    +
    0 Votes
    tmlfan_99

    No updates were made as this problem just started yesterday. I updated my video card drivers today in hopes that would solve it but it never did

    +
    0 Votes
    wanttocancel

    A program, such as antivirus, could've updated without your knowledge. Probably not but it's worth a look.

    I would do a thorough search through Event Viewer and see if you can pinpoint whatever is causing the BSOD.

    +
    0 Votes
    Jacky Howe

    First thing to do is Update all of your Motherboard Device Drivers and see how it performs. < edit as I missed a bit >
    <br><br>
    My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.
    <br><br>
    Minidump Files can be found here. C:\WINDOWS\Minidump\Mini******-**.dmp
    <br><br>
    How to read the small memory dump files that Windows creates for debugging
    <br>
    http://support.microsoft.com/kb/315263
    <br><br>
    To download and install the Windows debugging tools, visit the following Microsoft Web site:
    <br>
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
    <br><br>
    Instructions on using Windbg.
    <br>
    Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
    <br>
    Close the workpage and save the Workspace information. This should lock in the Symbol path.
    <br>
    Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
    <br>
    There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
    <br>
    When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
    <br>
    Ctrl + a will let you copy the information and paste it into notepad.
    <br>
    Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
    <br>
    FAULTING_THREAD: 864f6a98
    <br>
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
    <br>
    CUSTOMER_CRASH_COUNT: 1
    <br>
    BUGCHECK_STR: 0xEA
    <br>
    PROCESS_NAME: logon.scr
    <br>
    LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea
    <br>
    STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585
    <br>
    STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb
    <br>
    FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)
    <br>
    SYMBOL_STACK_INDEX: 0
    <br>
    SYMBOL_NAME: sgiul50!DrvBitBlt+585
    <br>
    FOLLOWUP_NAME: MachineOwner
    <br>
    MODULE_NAME: sgiul50
    <br>
    IMAGE_NAME: sgiul50.dll
    <br>
    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7
    <br>
    FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
    <br>
    BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

    <br><br>
    <i>Keep us informed as to your progress if you require further assistance.</i>
    <br><br>
    <i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.
    </i>

    +
    0 Votes
    tmlfan_99

    For some reason, it does not make a minidump file.

    +
    0 Votes
    Jacky Howe

    but I think that the others are right about the Video drivers. If your pagefile is a standard setup it should do the minidump but I have seen this before with Video.
    <br><br>
    How to Use Driver Verifier to Troubleshoot Windows Drivers
    <br>
    http://support.microsoft.com/kb/244617
    <br><br>
    Click Start, Run type verifier and press Enter. This will launch the configuration utility for Driver Verifier.
    <br><br>
    Click next to use Create standard settings, select, Automatically select all installed drivers and click next. Click on finish and then OK. Then reboot the PC. It may take a bit longer to boot up.
    <br><br>
    Once you're up and running click Start, Run type verifier /log drvchk.txt and press Enter.
    <br>
    This will open a blank window while it is doing the check. Let it run for 10 minutes, then close the window, you may get an error message, but you can ignore it. Navigate to c:\documents and settings\your user name and double click to open drvchk.txt. Look for any errors.
    <br>
    Remember to reset the verifier options by running verifier again and choosing delete existing settings. Restart the PC.
    <br><br>
    If the computer fails to boot because of the verifier.
    <br>
    Restart in Safe Mode by repeatedly pressing the function key F8 during startup and run verifier /reset. Restart the PC.

    <br><br>
    <i>Keep us informed as to your progress if you require further assistance.</i>
    <br><br>
    <i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.
    </i>

    +
    0 Votes
    tmlfan_99

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 11/12/2008
    Time: 9:13:41 AM
    User: N/A
    Computer: OWNER-7486CD808
    Description:
    Error code 1000000a, parameter1 00000000, parameter2 000000ff, parameter3 00000000, parameter4 806e4ea0.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 30 1000000
    0020: 61 20 20 50 61 72 61 6d a Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 30 30 2c 20 000000,
    0038: 30 30 30 30 30 30 66 66 000000ff
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 38 30 36 65 00, 806e
    0050: 34 65 61 30 4ea0

    +
    0 Votes
    -Q-240248

    Try disabling Triple-Buffering in the ATI control panel. You can disable some other features to troubleshoot, but start with that one.

    +
    0 Votes
    tmlfan_99

    Yea, triple buffering was already disabled.

    +
    0 Votes
    -Q-240248

    Did you install the 8.10 hotfix?

    http://game.amd.com/us-en/drivers_catalyst.aspx?p=xp/radeonx-xp

    It's your driver, like someone else previously stated. If patching doesn't work, uninstall all ATI drivers and freshly install the latest version with hotfix, or go to an older, more stable version.

    +
    0 Votes
    ---TK---

    I had close to the same issue's with the 3850 model. It boiled down to blowing away all of ATI's drivers, and reinstalling ONLY the driver, and not the utility, that helps you "tweak" your card. Also after that I went into services.msi and disabled one of the ATI services. I forget which one off hand, but there should only be two listed.

    The hardware that ATI's coming out with is sweet, however their drivers are sucking hardcore.

    +
    0 Votes
    tmlfan_99

    Yea, I did not have CCC installed at the time the errors began

  • +
    0 Votes
    michaelaknight

    Without reading the previous post, I'm going to say it's a corrupt or incompatible video driver especially given the application running. Could just as easy be a soundcard driver if you're using a beefy card.
    layman wise the error is saying that a piece of memory was trying to be read and couldn't due to any number of reasons but in this case I'd bet on a device driver.

    make sure you have the most up to date drivers for those devices and if thay are the most up to date maybe roll em back to a more stable version.

    +
    0 Votes
    tmlfan_99

    I had updated my ATI drivers to 8.10 and same thing still occurs.

    +
    0 Votes
    patrick

    Heat issue hows your case temps and CPU temp? not running too hot are you?

    -P

    +
    0 Votes
    tmlfan_99

    How can I check? I highly doubt that is the case as I use the Antec 900

    +
    0 Votes
    wanttocancel

    "This error usually occurs after the installation of a buggy device driver, system service, or BIOS." This includes antivirus. I would roll back drivers of device, system or BIOS you updated, if any.

    +
    0 Votes
    tmlfan_99

    No updates were made as this problem just started yesterday. I updated my video card drivers today in hopes that would solve it but it never did

    +
    0 Votes
    wanttocancel

    A program, such as antivirus, could've updated without your knowledge. Probably not but it's worth a look.

    I would do a thorough search through Event Viewer and see if you can pinpoint whatever is causing the BSOD.

    +
    0 Votes
    Jacky Howe

    First thing to do is Update all of your Motherboard Device Drivers and see how it performs. < edit as I missed a bit >
    <br><br>
    My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.
    <br><br>
    Minidump Files can be found here. C:\WINDOWS\Minidump\Mini******-**.dmp
    <br><br>
    How to read the small memory dump files that Windows creates for debugging
    <br>
    http://support.microsoft.com/kb/315263
    <br><br>
    To download and install the Windows debugging tools, visit the following Microsoft Web site:
    <br>
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
    <br><br>
    Instructions on using Windbg.
    <br>
    Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
    <br>
    Close the workpage and save the Workspace information. This should lock in the Symbol path.
    <br>
    Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
    <br>
    There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
    <br>
    When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
    <br>
    Ctrl + a will let you copy the information and paste it into notepad.
    <br>
    Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
    <br>
    FAULTING_THREAD: 864f6a98
    <br>
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
    <br>
    CUSTOMER_CRASH_COUNT: 1
    <br>
    BUGCHECK_STR: 0xEA
    <br>
    PROCESS_NAME: logon.scr
    <br>
    LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea
    <br>
    STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585
    <br>
    STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb
    <br>
    FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)
    <br>
    SYMBOL_STACK_INDEX: 0
    <br>
    SYMBOL_NAME: sgiul50!DrvBitBlt+585
    <br>
    FOLLOWUP_NAME: MachineOwner
    <br>
    MODULE_NAME: sgiul50
    <br>
    IMAGE_NAME: sgiul50.dll
    <br>
    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7
    <br>
    FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
    <br>
    BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

    <br><br>
    <i>Keep us informed as to your progress if you require further assistance.</i>
    <br><br>
    <i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.
    </i>

    +
    0 Votes
    tmlfan_99

    For some reason, it does not make a minidump file.

    +
    0 Votes
    Jacky Howe

    but I think that the others are right about the Video drivers. If your pagefile is a standard setup it should do the minidump but I have seen this before with Video.
    <br><br>
    How to Use Driver Verifier to Troubleshoot Windows Drivers
    <br>
    http://support.microsoft.com/kb/244617
    <br><br>
    Click Start, Run type verifier and press Enter. This will launch the configuration utility for Driver Verifier.
    <br><br>
    Click next to use Create standard settings, select, Automatically select all installed drivers and click next. Click on finish and then OK. Then reboot the PC. It may take a bit longer to boot up.
    <br><br>
    Once you're up and running click Start, Run type verifier /log drvchk.txt and press Enter.
    <br>
    This will open a blank window while it is doing the check. Let it run for 10 minutes, then close the window, you may get an error message, but you can ignore it. Navigate to c:\documents and settings\your user name and double click to open drvchk.txt. Look for any errors.
    <br>
    Remember to reset the verifier options by running verifier again and choosing delete existing settings. Restart the PC.
    <br><br>
    If the computer fails to boot because of the verifier.
    <br>
    Restart in Safe Mode by repeatedly pressing the function key F8 during startup and run verifier /reset. Restart the PC.

    <br><br>
    <i>Keep us informed as to your progress if you require further assistance.</i>
    <br><br>
    <i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.
    </i>

    +
    0 Votes
    tmlfan_99

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 11/12/2008
    Time: 9:13:41 AM
    User: N/A
    Computer: OWNER-7486CD808
    Description:
    Error code 1000000a, parameter1 00000000, parameter2 000000ff, parameter3 00000000, parameter4 806e4ea0.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 30 1000000
    0020: 61 20 20 50 61 72 61 6d a Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 30 30 2c 20 000000,
    0038: 30 30 30 30 30 30 66 66 000000ff
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 38 30 36 65 00, 806e
    0050: 34 65 61 30 4ea0

    +
    0 Votes
    -Q-240248

    Try disabling Triple-Buffering in the ATI control panel. You can disable some other features to troubleshoot, but start with that one.

    +
    0 Votes
    tmlfan_99

    Yea, triple buffering was already disabled.

    +
    0 Votes
    -Q-240248

    Did you install the 8.10 hotfix?

    http://game.amd.com/us-en/drivers_catalyst.aspx?p=xp/radeonx-xp

    It's your driver, like someone else previously stated. If patching doesn't work, uninstall all ATI drivers and freshly install the latest version with hotfix, or go to an older, more stable version.

    +
    0 Votes
    ---TK---

    I had close to the same issue's with the 3850 model. It boiled down to blowing away all of ATI's drivers, and reinstalling ONLY the driver, and not the utility, that helps you "tweak" your card. Also after that I went into services.msi and disabled one of the ATI services. I forget which one off hand, but there should only be two listed.

    The hardware that ATI's coming out with is sweet, however their drivers are sucking hardcore.

    +
    0 Votes
    tmlfan_99

    Yea, I did not have CCC installed at the time the errors began