Discussion in 'Windows Vista Performance' started by cab_cool, Jan 1, 2008.

  1. cab_cool

    cab_cool Guest

    is there an update for the error above for 64 bit vista ultimate?
    cab_cool, Jan 1, 2008
    1. Advertisements

  2. Richard G. Harper, Jan 1, 2008
    1. Advertisements

  3. cab_cool

    cab_cool Guest

    thats all well and good but i have already tried this and nothing has changed

    cab_cool, Jan 1, 2008
  4. cab_cool

    cab_cool Guest

    adding on from the last:
    i have a gigabyte 8800gts with drivers released on the 20/12/07 downloaded
    from the NVIDIA webstie.
    a full list of problems and full specs on my newly built computer see message:
    "vista is an old bomb of a car" and that 37 figure is out of 70 problem

    oh and as a side note how do i tell which driver is failing
    cab_cool, Jan 1, 2008
  5. cab_cool

    Mark Guest

    Of course knowing the stop code provided with each error would help.
    For instance:

    Or, if it is occurring after you come out of hibernation:

    But, who ever goes to the knowledge base anymore when you can get all these
    answers here?
    I guess googling the error is just out of the question: (Note: Response 6) knowledge base indicates there may be an actual hotfix to apply if thecase is specific to you, otherwise, it looks like you may have some hardwareissues (e.g. overheating.) But, I can't see your machine and don't reallyhave any details other than that error message."cab_cool" <> wrote in messageis there an update for the error above for 64 bit vista ultimate?
    Mark, Jan 1, 2008
  6. cab_cool

    Rick Rogers Guest

    If the stop error lists a module involved, then that is usually a big clue.
    If not, you often have to scan through the dump file.
    Vista isn't the problem. The problem is the drivers being used, many are
    often non-compliant with or not designed specifically for Vista. Others that
    are still often don't meet specifications.
    Rick Rogers, Jan 1, 2008
  7. cab_cool

    Chris Blunt Guest

    I used to get this BSOD error. It turned out to be a faulty memory
    module. Try running a memory test program for a couple of hours.

    Chris Blunt, Jan 1, 2008
  8. cab_cool

    cab_cool Guest

    thanks i'll check it out

    cab_cool, Jan 2, 2008
  9. cab_cool

    cab_cool Guest

    how does that work cause i asked for drivers that work with 64 bit ultimate?
    are you saying that they might have given xp drivers and said they work for

    thanks for telling me how to identify which drivers fail
    cab_cool, Jan 2, 2008
  10. cab_cool

    cab_cool Guest

    here's the error code:
    STOP: 0x0000000A (0xFFFFF80000000006, 0x000000000000000C,
    0x0000000000000001, 0xFFFFF8000205CC2C)
    these are my specs:
    Q6600, p35c-ds3r, gigabyte 8800gts, 4x kingston 1066MHz 1gig RAM, seagate
    7200rpm 750GB hard drive. also have 3 fans keeping to cool 1 for CPU + 2 for
    case, none are overclocked
    cab_cool, Jan 2, 2008
  11. cab_cool

    Mark Guest

    Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4)
    Address x has base at x - filename

    The parameters refer to the specific issues that are involved:
    • Parameter 1 - An address that was referenced incorrectly.
    • Parameter 2 - An IRQL that was required to access the memory.
    • Parameter 3 - The type of access, where 0 is a read operation and 1 is a
    write operation.
    • Parameter 4 - The address of the instruction that referenced memory in
    parameter 1.

    Parameter 2 indicates IRQ 12 was attempted.
    Looking through Device Manager (List by IRQ), you can find which device
    (This is not necessarily the problem device as another may have been
    preventing this device from working.)
    Your error code left out the last line, but you may not have been given the

    Where to start
    When this error occurs, use the Windows Error Reporting tool. With this
    tool, you can send the error report directly to Microsoft, and then the tool
    will report back if a fix or a workaround is available. To use this tool,
    follow these steps:

    If you receive a Stop 0x0A error after Vista is already installed
    If you receive the Stop 0x0A error after Vista is already installed, use the
    following troubleshooting methods to verify other components.
    Examine third-party software or drivers.
    If you have installed any third-party software or drivers, try removing them
    or disabling them so that they do not load, and then restart the computer to
    see whether that software or driver is causing the error. If that software
    or driver is causing the error, report the problem to the vendor of the
    software or driver.
    Examine the logs in the event viewer to determine whether there is any event
    information that can help you determine what device or driver is causing the

    If you cannot start Vista after you install the software or drivers, attempt
    to restore Windows.
    Roll back drivers.
    Restore points.
    Restore backup.
    Mark, Jan 2, 2008
  12. cab_cool

    Mark Guest

    Sorry, I was paraphrasing some of the links I provided. Here it is arranged
    a little smoother.
    In a nutshell:
    IRQ 12, or 13 (since it's C+)
    Device Manager
    View by Resources by Connection
    Look at IRQs
    If you don't have a 12 or 13 in use, that's the problem... the
    driver sought something not in use.
    If you have 12 or 13 in use:
    Roll back the driver
    or, Disable the device
    or, Update the driver
    Event Viewer:
    Look for critical errors and see if they direct you to a device.
    Make sure the mouse (PS 2) is not using IRQ 12.
    Reserve an IRQ in Device Manager and assign IRQ 12 to it to
    prevent the mouse from grabbing it.
    If you have a USB mouse, use it instead.
    Math Coprocessor:
    This is typical for IRQ 13.
    Let's hope this is not the problem.

    From here it gets difficult:
    1. Disable or disconnect devices one at a time to see if the problem goes
    Most likely culprit if you make it this far is:
    a. Bad memory stick, or
    Run a memory diagnostic.
    Check they are well seated.
    b. CPU overheating
    2. The error is trying to write:
    a. Audio
    b. Video
    c. Memory (Is the memory actually rated for 1066 GHz?)
    You could pull two sticks. It would barely come up, but
    it should.
    Or, you could try swapping them about.
    d. CPU (Q6600, that's a smokin' quad, I think... Lot's of heat?
    3 fans should be enough. Check the sink.)
    As soon as you get the error, reboot to the BIOS and check
    your CPU temp.
    e. Other
    Mark, Jan 3, 2008
  13. cab_cool

    cab_cool Guest

    thanks for your help and info it turns out i have a memory issue that i need
    to see manufacturer about
    cab_cool, Jan 4, 2008
  14. cab_cool

    cab_cool Guest

    i have memory problem that i'll see the manufacturer about
    cab_cool, Jan 4, 2008
  15. cab_cool

    cab_cool Guest

    thanks for your help it turns out i have memory problem that i'll see the
    manufacturer about

    cab_cool, Jan 4, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.