Question

Locked

Blue screen error

By sudu.mlk ·
Hi,

Yesturday when i start my pc, normally i get windows booting screen and after that it automatically starts to reboot, it is continuesly happened. after that i boot from windows xp cd and done chkdsk /p/r.

After that i rebooted the OS and again it starts to reboot. i thought there may hardware driver problem and entered into safe mode, but safe mode does't work properly.

So i decided to reinstall XP. i formatted the hard disk and when starts to copy os file, in b/t that some .dll files could not able to copy and finally it gaves me the blue screen error: IRQL_NOT_LESS_OR_EQUAL.
----

I bought my pc just before two weeks.

The cofiguration is

Intel 945 via chipset Motherboard
Intel core 2 duo 2.2 Mhz Proccessor
1 gb DDR 667 trascent RAM
Mosober 20X DVD Drive.
160 GB Sata Hard disk.

--------

This resolves if i reassemble the pc..

Please help me out....

Thanks in advance

sudu

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Test Memory

by willcomp In reply to Blue screen error

First, test memory using Memtest86+. Allow to run for at least 3 passes.

Memtest86+ and other useful utilities are on the UBCD.
http://www.ultimatebootcd.com/

Replace memory if there are any errors.

If memory tests OK, post back.

Collapse -

IRQ hardware conflict

by PC-guru In reply to Blue screen error

2 or more devices are sharing the same IRQ and are trying to run at the same time.
swap out your removable hardware if possible and find out which device it is.
its also why rebuilding resolves this issue
windows sucks *** and tries to have hardware share IRQ's other route is to manually assign each IRQ which is a *****

Collapse -

Download Avira NTFS4DOS Personal here..

http://www.free-av.com/en/tools/11/avira_ntfs4dos_personal.html

You will need another computer to download this "DOS" program and put it onto "Floppy(s)", when finished, load the floppy into your computer, that is not working properly, and if will come up as "A:/" type in "fdisk" and press enter select yes or "Y" on the next question, when in, you will have a menu list, Select the number in the list that says "delete non dos partitions", if you have dos partitions delete these as well. When finished reboot your computer and then re-install your Windows disk.
Some more info here:
http://www.bootdisk.com/ntfs.htm

Hope this helps you.

Please post back if you have more problems or questions.

Collapse -

Check your BIOS

by Jacky Howe In reply to Blue screen error

If your system has a newer BIOS check that the PnP/PCI Configurations are set to Auto.

On a PC with and older BIOS
PNP OS Installed
Options : Yes, No

If all your operating systems support Plug & Play (PnP), select Yes so that they can take over the management of device resources. If you are using a non-PnP-aware OS or not all of the operating systems you are using support PnP, select No to let the BIOS handle it instead.
For stability reasons, it is better to leave EVERY motherboard regardless of manufacturer set to "PnP OS=no", but still allow the hardware to auto configure PnP devices. Just leave the one setting to always say "PnP OS = no". It won't hurt a thing, you lose nothing, your machine will still autoconfigure PnP devices, and will make your system more stable."

The overall goal of IRQ troubleshooting is to track down shared IRQs at the hardware level, before XP boots, and to avoid having and add-on cards sharing IRQs with onboard resources. The only proper solution to an IRQ conflict in XP is to find a slot for the offending card that is not shared with other resources. And if you don't have a spare, unshared slot, either toss the card or toss your motherboard and get something better and more modern. That is not a joke.

Windows XP will reassign BIOS hardware IRQs and set up its own list of shared IRQ vectors, which it does a very good job of. If your machine is locking or a card is not functioning, and if the problem is caused by an IRQ conflict then the conflict is more than likely occurring before XP can assign new IRQs to the devices. What this means is that it is nigh on pointless to consider modifying XP's automatic IRQ assignments, especially since XP will not let you modify some of its assignments anyway, and also because if you override XP's automatic assignments then you are likely to cause more problems for yourself if you add a new device at some later point.

You need to determine what slots in your machine share what IRQs. Some BIOS have an option that will list the slots in your machine, along with the IRQ that each slot uses, and if you are lucky, the list will indicate if the slot is shared with onboard resources. However, most modern BIOS have no options at all for managing IRQ assignments. For example, many Intel workstation and server boards use ACPI therefore they do not support modification to IRQ assignments.

Manually assigning IRQs in BIOS is generally only applicable to some very old, non-ACPI compliant systems, and if ACPI support is enabled then XP will ignore manual BIOS assignments anyway. If you really must assign IRQ addresses manually in the BIOS on an ACPI-enabled motherboard then you may need to reinstall XP (or do an in-place upgrade) and force it to use the Standard PC HAL. How to force a Hardware Abstraction Layer during upgrade or installation of Windows XP.

http://support.microsoft.com/kb/299340/en-us


SUMMARY
When you start your computer, the basic input/output system (BIOS) checks (among other things) the system-specific settings that are stored in the complementary metal-oxide semiconductor (CMOS) chip. You can modify these settings as the system changes.

To change the CMOS settings, you must enter CMOS Setup by pressing a specific key or a combination of keys during the initial startup sequence. For example, press DEL or CTRL+ALT+ESC during the startup. (The specific key combination that you press is typically indicated during startup as "Press <keyname> to enter Setup".)

After you have entered Setup, windows that display various options and settings appear. Some of these options are standard, while others are specific to the BIOS manufacturer.

One of the CMOS settings is the PNP OS option. This setting tells BIOS how many devices to configure at startup. The table in "More Information" shows the effect of this option on the configuration of the motherboard devices.

The original intent for designing this option was to give Microsoft Windows versions 95 and 98 more freedom to adjust hardware configurations. By default, these operating systems would never move a device configured at startup for fear of breaking a DOS driver. Later versions of Windows also typically leave BIOS-configured hardware alone, even if the BIOS placed the hardware in a less than optimal configuration. This is because moving such hardware frequently exposes latent bugs in the BIOS.
MORE INFORMATION
Setting Description
PNP OS
set to Yes The BIOS configures only critical devices (for example, video, hard-disk, and key- Board). NOTE: In this mode, neither the BIOS nor Windows configures the motherboard devices at startup. Therefore, for these earlier computers, you must set PNP OS to No.
PNP OS
set to No The BIOS configures critical devices and all motherboard devices under the assumption that Windows cannot.

Collapse -

IRQL_NOT_LESS_OR_EQUAL is not an IRQ Conflict

by willcomp In reply to Blue screen error

It basically means unauthorized memory access by a driver and is almost always either driver or memory related (system memory or page file).

I test memory first since that's easy. Next step is minidump analysis provided one is created.

Related Discussions

Related Forums