blue screen * STOP 0x0000000A in Windows XP

blue screen error message: * STOP 0x0000000A (0xFF1701F0. 0 x 00000002, 0 x 00000000, 0x80536A1C) win xp home edition

Around my house (less than 100 feet I can't use / the view high tower or net - only 'safe mode' whenever I start it (under each variable with or without battery) I get the error message blue screen (see above) - outside of the area of 100 feet, lap top works fine... perfect, starts every time;) HP lap top xp home ed works very well... (I can't use it at home or within 100 feet of my house via especially blue screen message)

blue screen * STOP 0x0000000A (0xFF1701F0. 0 x 00000002, 0 x 00000000, 0x80536A1C) xp home ed

You get the following BSOD:

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

Please download the files dmp from the Windows\Minidump on your Skydrive folder (copy the dmp first on your desktop, otherwise you can not download them) and post a link here, so that we can look at landfills. Perhaps we see the cause.

"A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

Tags: Windows

Similar Questions

  • Blue screen STOP: 0x0000000A (0 x 0000000000000000, 0 x 0000000000000002, 0 x 0000000000000001, 0xFFFFF8000328097C)

    Hello! I have a problem with my computer when it starts up, a blue screen appears, there is a message and an error code:

    STOP: 0X0000000A (0 X 0000000000000000, 0 X 0000000000000002, 0 X 0000000000000001, 0XFFFFF8000328097C)

    I tried to boot into safe mode and run the system restore, but the problem restart again and again...

    Please, can you help me for this problem.

    You've done everything just great, thank you!

    The last DMP file attached is IRQL_NOT_LESS_OR_EQUAL (a) bug check.

    This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

    This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high. The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

    If we take a look at the call stack:

    2: kd > kv
    Child-SP RetAddr: Args to child: call Site
    fffff880'067ab1d8 fffff800'03283169: 00000000' 0000000 a 00000000'00000000 00000000'00000002 00000000'00000001: nt! KeBugCheckEx
    fffff880 '067ab1e0 fffff800' 03281de0: 00000000'00000000 00000000' 00000bfc 00000002'00000000 00000000'00000000: nt! KiBugCheckDispatch + 0 x 69
    "fffff880 '067ab320 fffff800' 0328a97c: 00000000 ' 00000000 fffffa80 ' 072a 3200 00000000' 00000bfc 00000000' 00000bfc: nt! KiPageFault + 0 x 260 (TrapFrame @ fffff880'067ab320)
    fffff880 '067ab4b0 fffff800' 0325591e: 00640074' 006e0000 fffff800'00000022 00200000'006 c 0000 0061006d ' 00610000: nt! KeWaitForSingleObject + 0x17c
    "fffff880 '067ab550 fffff800' 032952f5: 00000000 ' 00000001 fffffa80 ' 072a 3238 00000000'00000040 20000000'00000039: nt! KiAcquireFastMutex + 0x4e
    fffff880 '067ab590 fffff880' 06cc733e: fffff8a0'0bbd3820 00000000 00000000' fffffa80 '0727abf0 fffffa80' 0727abf0: nt! ExAcquireFastMutex + 0 x 45
    fffff880 '067ab5c0 fffff8a0' 0bbd3820: 00000000 00000000 fffffa80 '0727abf0 fffffa80' 0727abf0 00000000' 001 a 9000: aswSP + 0x4133e
    fffff880'067ab5c8 00000000' 00000000: fffffa80'0727abf0 fffffa80 '0727abf0 00000000' 001 a 9000 fffff880' 06cc50ee: 0xfffff8a0'0bbd3820

    -FAILURE_BUCKET_ID: X64_0xA_aswSP + 4133

    ^^ aswSP.sys = avast! Auto pilot Protection.

    -----------------

    1. remove and replace avast! with Microsoft Security Essentials for purposes of troubleshooting temporary:

    avast! removal - http://www.avast.com/uninstall-utility

    -MSE http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

    2 in your list of drivers loaded, dtsoftbus01.sys figure who is the driver for Daemon Tools. Daemon Tools is a very popular cause of BSOD in 7/8 base systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    Kind regards

    Patrick

  • Error blue screen - Stop: 0x0000000A (0 x 00000001, 0x81AIEFE9, 0 x 00000054, 0x0000001B)

    I recently had a lot of blue screen errors and I took a lot of steps in my attempt to deal with them.  I have updated and uninstalled the drivers who had the yellow exclammation mark next to them in the Device Manager.  I ran Microsoft Memory Diagnostic tool.  I went through all the steps to repair the windows that are arranged in the executable file for Tweaking.com.  However, I'll always have this annoying problem.  What I really want to get to is the root of the problem.  I want to know if it's a hardware problem, so that I can replace the parts that I need to replace, or be it a software problem.  Here is some info about my computer: I'm currently connected to the internet via a cable modem and that modem is connected to my computer via a USB cable because my NETWORK card is down.  I have already disabled the CARD driver and have properly installed the drivers for the modem.  The blue screen issue occurs very randomly.  I've already gotten two technicians from Microsoft support and they were not able to provide any real indication of the problem.  Please, I beg you!  I'm desperate to get to the bottom of this!

    Information on my computer:
    Windows Vista Edition Home Premium
    Service Pack 2 (I got all the updates of Windows)
    Processor: Intel Premium Dual CPU E2140 @1. 60 GHz
    (Vivid RAM) memory: 4.00 GB
    32-bit operating system
    Compaq Presario SR5250NX
    Blue screen error information:
    Stop unexpectedly on 27/04/2012 @ 14:40
    Signature of the problem
    Problem event name: BlueScreen
    The system version: 6.0.6002.2.2.0.768.3
    Locale ID: 1033
    Files helping to describe the problem (some files may be is no longer available)
    Mini042712 - 01.dmp
    SysData. XML
    Version.txt
    See a temporary copy of these files
    WARNING: If a virus or other security threat caused the problem, open a copy of file can harm your computer.
    Additional information about the problem
    BCCode: a
    BCP1: 00000054
    BCP2: 0000001 B
    BCP3: 00000001
    BCP4: 81A1EFE9
    OS version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1
    Information about the server: cbe24a1e-1cde-4419-8436-2034621b48bc

    Hello

    Pick up the pieces after a computer breakdown - see what to do if Windows won't start correctly
    http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

    Since you re-installed Windows that indicates the hardware problem (near 100%) with
    possibilities of tiny that BIOS, low-level chipset or other low load drivers drivers are in
    play (such as video).

    Make sure that the integrated NETWORK interface is disabled in the BIOS (if possible) and/or Device Manager.

    Check with Compaq Support, their drivers and documentation online and ask for their
    Forums about known problems.

    Compaq - support, drivers and documentation online
    http://www.Compaq.com/country/cpq_support.html

    Compaq (HP) - Forums
    http://h30434.www3.HP.com/PSG/|

    Remove ALL power and then reconnect the cables (at both ends where possible), memory and cards
    -in fact, remove and replace - do not just tight. Clean the dust bunnies, clear the vents,
    and make sure the fans are working. Try adding a small fan blowing into the socket to reduce the
    heat of luck is a part of the question (heat associated with does not always mean too much heat as one
    component may be too sensitive to even normal levels of heat).

    You checked the memory, but the tests detect memory errors such as small speed
    differences between identical memory modules. We therefore often swap memory
    modules and out in different combinations and patterns.

    To test the RAM here control - run 4 + hours or so.<-- best="">
    www.memtest.org

    Remove any devices that you can to make the system as simple as possible to see if this
    an impact on the issues.

    Check with a real computer store (one that makes its own service internal on Compaq and)
    No leeks and peaks at a Best Buy or other stores) or Support of Compaq.

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

  • Blue screen STOP: 0x000000F4 in Windows XP, SP3

    Lots of code: STOP: 0x000000F4(0x00000003,0x8913EB50,0x8913ECC4,0x805D2954). The only consistency is that it is usually pretty shortly after the start, but not all the time. The incidents are increasing frequency and very disturbing.  Requires power off and restart to recover, but until now always restarts. What is the problem and how to fix it?

    Hello Pierre_60,

    You do not give a lot of information to go with the error 0x0000000F4.

    See the following article to see if this is your case.

    Article number: 330100 - connect a hard drive in slave only leads to stop the system for the recovery of the standby mode
    http://support.Microsoft.com/kb/330100
     
    I hope this helps.

    Marilyn

  • Windows xp blue screen stop: 00000024

    Title: original windows xp blue screen

    had a blue screen with stop:

    Hi steveshepherd,

    (1) since when are you facing this problem?

    (2) remember to make changes?

    (3) what happens when you insert the Windows XP CD?

    You can follow the steps provided by Karena R in the link below, which relate to this issue

    http://answers.Microsoft.com/en-us/Windows/Forum/windows_xp-system/blue-screen-stop-error-0x00000024-while-booting/196033b0-fbe9-45dd-abbf-889291d0d133

    Kind regards

    Ajay K

  • Windows 7 - Crash blue screen - STOP: 0X000000F4

    Hi all

    Windows 7 - Crash blue screen - STOP: 0X000000F4

    Screen shows e blue screen will display the following error code:

    STOP: 0X000000F4 (0XFFFFFA800C4C4B10, 0XFFFFFA800C4C4DF0, 0 X 0000000000000003, 0XFFFFF8000418FE20).
    I tried to restore the mode, the safe & all the option available to start properly.  Given that I have no DVD of windows 7 to re - install windows again.
    My question is as follows:
    -Is - error code says something.
    -A way to re - install windows without CD or DVD or save the image.
    -Also, I can read and access data from the C: & D: drive in cmd in restore mode guest mode.
    Waiting for your suggestions.
    concerning
    Jagdish kone

    Blue_Screen_image_.PDF

    Hi Philippe,.

    Thanks for your reply. I want to reinstall windows on the same SSD. Given that the SSD drive works great as external drive.

    So please could you confirm, how do I reinstall windows again. As I see there are recovery drive comes when I use the SSD as external drive.

    Waiting for your suggestions.

    Concerning

    Jagdish

  • Blue screen (STOP) errors that cause Windows Vista to shut down (blue screen of death)

    I get this on a blue screen stop code and I can't find what this code means someone can help me please v

    00000101 0 x (0 x 0000000000000061, 0 x 0000000000000000, 0xffff98000c6e180, 0 x 0000000000000001

    Best advice I've seen on this error (here: http://www.sevenforums.com/crashes-debugging/35427-win-7-clock-interrupt-bsod-101-error.html#post356791 )
    What you are looking for will be in one of the following categories:

    (a) the BIOS bug
    (b) a pilot whose activity is at the origin of the processor target lock
    (c) a defect in hardware (temperature, voltage, dust, RFI, pure and simple borkedness...)? I also wonder about default CPU)
    Therefore, check the drivers
    Then check the inside of the species (temperature, voltage, dust, etc.).
    Then run tests of stress of material

    Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/
    Try this free stress test: OSS - GIMPS

    CPU Stress Tests:
    Just do 1 or 2 tests in most circumstances. I have not used one of these tests myself, so I listed everything I could find.
    - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
    - http://7byte.com/index.php?page=hotcpu
    - http://www.7byte.com/index.php?page=burnin64
    - http://www.overclock.net/general-processor-discussions/657486-cpu-stress-test.html
    - http://www.fossiltoys.com/cpuload.html
    - http://www.pcworld.com/downloads/file/fid, 7146-order, 1 page, 1-c, alldownloads/description.html
    - http://www.overclock.net/general-processor-discussions/657486-cpu-stress-test.html
    - http://majorgeeks.com/CPU_Stability_Test_d215.html
    - http://www.xtremesystems.org/forums/showthread.php?t=201670
    -l' or the tests suggested at this link are bootable: http://www.techsupportforum.com/forums/f15/headless-cpu-stress-testing-393435.html#post2232929

    Then try to replace parts.
    Then look for the version of your BIOS to see what changes have been made.

    Text courtesy of http://www.carrona.org/ Usasma

  • A blue screen (Stop error) has been reported. The message contains the error details.

    Hello Hello.
    can someone help me why this error is coming.
    I use a laptop lenovo.
    Error details:
    product-windows stytem, operating
    ID-1003,
    source-system error,
    version - 5.2.
    sysmbolicname-ER_KRNLCRASH_LOG,
    error code %1, %2 parameter %3, parameter3 %4 parameter 4 %5 2 parameter1

    A blue screen (Stop error) has been reported. The message contains the error details. An event with event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.

    Concerning

    Chandra Murali

    .net developer,

    HYD.

    Hi Murali,

    ·         What is the random question?

    Try the following.

    Method 1: Check for memory questions

    Microsoft Online Crash Analysis - windiag

    Method 2: Updated with the latest chipset and other computer device driver updates. Log in the Web site of the manufacturer to do the same thing.

  • Blue screen stop: c00002 / a (fatal system error)

    Blue screen stop: c00002 / a (fatal system error)

    the windows login process ended unexpectedly with status 0xc0000005 (0x00000000 0x00000000) the system has been shut down.

    I have dell windows XP home service Pack 3 computer.

    I had a problem with security thinkpoint and called microsoft and after they had me take measures running a couple different scanshttp://live.sunbeltsoftware.com/download VIPRERescue andwww.eset.com virus more microsoft had click me start, run and type in the press temp ok delete all files, run and type prefetch and delete all the files, run %Temp% remove all the files then empty the trash restart and everything should be ok.

    the computer starts fine until I stopped and tried it begins again, same blue screen problem, I went to safe mode and don't start running and temp, prefetch and %Temp% remove empty the Recycle Bin and restart and computer ran fine, after the 2nd screen blue again.

    I'm now working on the computer and if I press start, run make temp, prefetch and % temp % and delete and empty the trash before turn me computer turned off it will start very well, if I don't do the temp, prefetch and %Temp% steps that I will get the blue screen at the start.

    How can I solve this problem and get rid of the blue screen for good message?

    Hi C_O_A_C_H_11,

    Perform the last known good and then restart your computer and check if you receive the error message. You can check the link below:

    How to start your computer by using last good known Windows XP Configuration:http://support.microsoft.com/kb/307852

    With regard to:

    Samhrutha G S - Microsoft technical support.

    Visit ourMicrosoft answers feedback Forum and let us know what you think.

  • Error blue screen STOP: 0x0000007e. I powercycled the sys, unable to choose for sure (keys do not work when you try to select a mode) sys is trying just to go back to the blue screen. Help, please

    STOP: 0x0000007e (0xc000001d, ox8537008 0xba4c3508 0xba4c3204) and the system would not come to the top.

    Error blue screen STOP: 0x0000007e. I powercycled the sys, unable to choose for sure (keys do not work when you try to select a mode) sys is trying just to go back to the blue screen. Help, please

    Symptoms: Booted computer, loaded the raid drivers and showed at the start screen XP for half a second then to BSOD with a Stop error Code 0x0000007E - see also a lot of users (0xC0000001D, 0 x-, etc.) as well.

    Solution:

    1 boot from your Windows XP CD and start the recovery console. You may need to press F6 while RC loads in order to load the SATA drivers. you will have a prompt c:\WINDOWS to the console.

    2. type: CD $NtUninstallKB977165$ \spuninst (it's the update, I had to uninstall to get out of the boot loop, other updates can be uninstalled by changing the name of the directory to $NtUninstallKBCODE$, where KBCODE is the code KB)

    3. type: BATCH spuninst.txt

    4. type: exit

    Don't forget to configure your system to boot from the HD before resuming. I hope this helps. Saved me a lot of hassle today.

    -Tom Steele
    http://www.hawkandtom.com Tom Steele

  • Blue screen STOP: 0 x 00000124 (0x00000000, 0x89BED028, 0xB2000040, 0 x 00000800)

    Hello

    This is my first post, please have mercy,
    I have a BSD at startup and this is the code that continues to show upward.  System Restore (from system repair and also safe mode) has not solved the teething problems.
    Blue screen STOP: 0 x 00000124 (0x00000000, 0x89BED028, 0xB2000040, 0 x 00000800)
    I think the code means some sort of failure hardware, is anyway to deduce which device has failed in assessing these codes?
    Please let me know if I'm on the wrong track with a hardware failure, I appreciate all the advice.
    Thank you

    Stop 0 x 124 is a hardware error

    If you are overclocking try to reset your settings to standard processor and see if that helps.

    If you keep getting the BSOD here are things more than you may want.

    This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.

    Stop 0 x 124 - what it means and what to try
    Synopsis:

    A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.

    Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.

    Generic troubleshooting ' Stop 0 x 124 ":

    (1) ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.

    (2) make sure that the machine is sufficiently cooled.
    If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).

    3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
    It is best to run the latest drivers anyway.

    (4) update of the BIOS of the motherboard according to the manufacturer's instructions.
    Their website should provide detailed instructions on the brand and model-specific procedure.

    (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.

    (6) attempt (stress) test these hardware components that can be put to the test artificially.
    The most obvious examples are the RAM and HDD (s).
    For the RAM, use diagnostics from built-in memory (run MDSCHED) or the utility memtest86 3rd - party to run plenty of evidence of hours of testing.
    For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
    Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.

    (7) as the last troubleshooting no invasive steps, perform a reinstallation of Windows 'vanilla': just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
    Who stops working mitigate the problem of the 0 x 124, jump to the next step.
    If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
    Smash back, obviously the latest addition of software may be somehow connected to the root cause.
    If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
    Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:

    (8) clean and carefully remove the dust inside the machine.
    Reinstall all memory modules and connectors.
    Use a can of compressed air to clean the RAM DIMM supports as much as possible.

    (9) if all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
    Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

    If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

  • service pack 2 Installation error blue screen stop 0 x 0000003

    Hello

    I was unable to download the Update Service Pack 2 on my Windows Vista forever.  Get the message every time I start my computer something like "error on blue screen Stop 0 x 0000003.  When I tried to download the 2 means of redress, both gave me the screens that says 'this update not supported'.  How can I fix it?

    Search for updates of hardware of your computer - including the system BIOS manufacturer.  Do not use all facilities built to perform the check - in fact visit the web page of your computer make & model and update the drivers for your system.

    You can also try this:
    How to reset the Windows Update components?

    (Try first the value default - restart and try your download again.  If this does not work - try the aggressive - restart and try your download again.)

  • Blue screen STOP: 0x0000005C (0x0000010B, 0x00000001, 0x00000000, 0x00000000)

    WHEN I TRY TO INSTALL WIN 7 I GOT THIS HELP PLEASE
    Blue screen STOP: 0x0000005C (0x0000010B, 0x00000001, 0x00000000, 0x00000000)

    DN

    If you cannot start in safe mode and can not boot from the dvd, your options are extremely limited.  The fact that you can boot from Ubuntu suggests that something is wrong with e OS not material.

  • I get a blue screen in the main window to develop the module

    I just downloaded LR6 from CC Adobe on my new computer laptop > it worked fine on the old laptop, but now I have a problem. I imported the photos that look very well, but when I try to open on (one) in the develop module I get a blue screen in the main window.  The image appears in the navigator Panel. I use Windows 10, which I never used before LR.

    Lightroom preferences-> Performance tab, disable the GPU option. It may be necessary to restart Lightroom.

  • Windows 7 blue screen STOP: 0 x 00000119 (0 x 0000000000000001, Ox0000000000023B4E, 4 x 0000000000023898, 0 x 0000000000023699)

    Get this error message on blue screen.  Said minidump but cannot read

    This Stop error has to do with the video card. The pilots are wrong or the card is a failure. If you can get into Windows, uninstall the video drivers and install the good. See below for where to get them. If you can't in normal Windows Mode, see if you can get Safe Mode and uninstall the drivers from there. More details about your computer, your hardware, the recent history of the machine, and if you can get into Windows help you more focused troubleshooting. If uninstall/reinstall drivers does not help then the video card may have failed and must be replaced.

    Never get the drivers from Windows Update. Bring:

    1. site of the device mftr. ; OR
    2. site of the card mother mftr. If the material is on board; OR
    3. website of the OEM manufacturer for your specific machine if you have a PC OEM (HP, Dell, Sony, etc.).

    Read the installation instructions on the Web site where you get the drivers.

    To find out what hardware is in your computer:

    1. read all documentation that you got when you purchased the computer.
    2. If the computer is OEM, access the site Web of the OEM for your specific model machine and look at the specs (you'll be there to get the drivers anyway)
    3. download, install and run a program of inventory of the free system like Belarc Advisor or System Information for Windows.

    http://www.belarc.com/free_download.html - Belarc Advisor
    http://www.gtopala.com/ - System Information for Windows

    MS - MVP - Elephant Boy computers - don't panic!

Maybe you are looking for