Results 1 to 4 of 4
  1. #1
    xJordy's Avatar
    Join Date
    Nov 2007
    Gender
    male
    Posts
    117
    Reputation
    8
    Thanks
    19
    My Mood
    Amused

    BSOD on ijji reactor start

    Hello,

    Maybe someone can help me with my problem:

    When i start the ijji reactor (as administrator) it takes a while for it to load, and than suddenly i get a BSOD (bleu screen of death) wich says: IRQL less_or_equal (blablabla)

    Anyone know how i can fix that? Because of that i can't play AvA.

    Thanks in advance

    p.s. my .NET and directX are up to date in case you girls start about that
    ORLLY!?


  2. #2
    ilovepiez's Avatar
    Join Date
    Jan 2011
    Gender
    male
    Location
    England
    Posts
    346
    Reputation
    48
    Thanks
    50
    My Mood
    Cynical
    do standard memory tests, use memtest software and test your ram, if that doesnt indicate anything then take out RAM modules until there is only 1 left, test each ram module in multiple slots to see if you can find a problem. If not, check your drivers, if that doesnt help, reboot your OS

    hope you dont have to go to the last one because it can be an inconvenience.

  3. #3
    vinvin148's Avatar
    Join Date
    Jan 2010
    Gender
    male
    Posts
    342
    Reputation
    9
    Thanks
    126
    My Mood
    Yeehaw
    IRQL_NOT_LESS_OR_EQUAL (0x0000000A)

    The most common cause of this conflict is improperly installed drivers for a piece of hardware you recently installed. For example, if you’ve installed a webcam two weeks ago, and have been getting BSoDs ever since, start your investigation with the webcam. First, disconnect the hardware, and uninstall the drivers for it completely. If that fixes the blue screen, you can search for updated drivers or contact the manufacturer.

    If you haven't installed any new drivers recently, you'll need to do some more detective work. Start by examining the blue screen to see if it lists a specific driver. Looking at the blue screen, check the text at the very bottom of the screen. You'll probably see a file name. This is the driver that caused the problem. If, for example, the driver in question is named nv4_disp.dll (an nVidia-related file), and you've recently switched from an Nvidia videocard to an ATI part, then it's reasonable to assume that either the old driver was not uninstalled correctly, or the new drivers weren't properly installed.
    Swapping Videocards

    If you've narrowed your search of offending drivers down to those associated with your videocard, turn off the system, disconnect the power, and remove and reseat the videocard. Next, go into the BIOS (press F2 or Delete when your BIOS prompts you to do this, or consult your user manual or motherboard manufacturer's website) and check the bus speed for your videocard. We typically recommend leaving the PCI-E frequency set to Auto in the BIOS, but if you've overclocked your system, it can inadvertently knock the bus speed beyond a stable spec, which can cause blue screens. If that's the case, manually set your PCI-E frequency to 100MHz.

    You're more like to experience this IRQL error when switching form one videocard brand to another, as the drivers will conflict with each other. The safe way to swap videocards is to completely remove all remnants of your old videocard drivers using a utility called Driver Cleaner, or the freebie alternative Driver Sweeper. To begin the process, open up your Control Panel, select Add or Remove Programs in XP or Programs and Features in Vista, highlight the videocard drivers, and click Uninstall. Reboot the computer, holding down the F8 key to enter safe mode. Run the Driver Cleaner utility to scrub away any remnants of the previous drivers that a typical uninstall overlooks. After you reboot, install the appropriate drivers for your new videocard.
    Some Sound Advice

    When the error is related to an audio driver, take note of the program that was running when the BSoD occurred. Make sure the offending application's sound options are configured correctly -- it's especially important that it uses the correct audio device -- and download any patches available that address known issues. You should update your soundcard's drivers as well.

    If you're using an add-in soundcard, verify that the motherboard's onboard audio is disabled in the BIOS, so the two audio drivers don't conflict with each other.
    Change Doctors

    System services known to cause this error include virus scanners and backup utilities. We've had good luck sticking with the major players, such as AVG, Norton, Kaspersky, AntiVir, and Nod32 for our antivirus scanning, and Norton Ghost and Acronis TrueImage for backup duties. Do not run more than one antivirus application on your computer at the same time!
    DATA_BUS_ERROR (0x0000002E)

    This is one of the easier BSoDs to diagnose, as faulty memory sticks are almost always to blame. If you get this error, think for a second: Are those DIMMs you just added compatible with your motherboard? Your motherboard manufacturer's website will have a list of specific brands verified to work with your particular board, although these are often incomplete.

    (Image Credit: Corsair)

    Next, are they installed in the correct slots? Some motherboards are more finicky than others when it comes to proper slot placement, and the situation is compounded when dealing with a dual- or tri-channel board. Most motherboards that run dual-channel require that you install matching sets of RAM in the same-color slots, while others, such as some MSI boards, require that you install them in alternate slots. And if you have a Core i7 setup, you may need to install your RAM starting with the slot farthest from the CPU. When in doubt, RTFM.

    Once you've verified that your RAM is installed correctly and is compatible with your motherboard, check to make sure they're running within spec. It's possible you may have set your memory's latency timings too aggressive, or maybe the sticks can't handle the frequency you're trying to run them at. Your BIOS could also mis-read the SPD settings. Whatever the case, look up the correct parameters for your RAM and try manually setting them in the BIOS.


    (Image Credit: pplware.com)

    If the problem persists, the the problem is likely a bad stick. To find out which stick is bad you can simply remove one stick, then run your system for a while to see if the blue screens stop. Then swap the sticks and run your test again. If the machine blue screens with one stick, but not the other, you've found your culprit. You can also run a diagnostic program such as Memtest86+ to help determine which stick is defective. If you're running Vista, you can also use Microsoft's Windows Memory Diagnostics Tool. Type the name of the program in Vista's search box, and once selected, it will run the next time you reboot. Because most RAM sold today includes a lifetime warranty, be sure to check with your vendor before you toss out a bad stick.

    -copy and pasted from maximumpc.com





  4. #4
    hualuzxcv's Avatar
    Join Date
    Feb 2011
    Gender
    female
    Posts
    4
    Reputation
    10
    Thanks
    0

    i like the artical

    I am in love with the article,it is so excellent~~
    affordable wedding gowns