IRQL_NOT_LESS_OR_EQUAL while booting winxp pro

For some days i am getting BSOD while starting winxp pro

can anyone help .. here is the bugcheck

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini081705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: F:\INSTALL\WINXP\I386
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Built by: 2600.xpclient.010817-1148
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Wed Aug 17 12:09:34.355 2005 (GMT+6)
System Uptime: 0 days 2:18:55.156
Loading Kernel Symbols
............................................................................................................
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {34, 2, 0, f848ab74}

Unable to load image IdeChnDr.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for IdeChnDr.sys
*** ERROR: Module load completed but symbols could not be loaded for IdeChnDr.sys
Probably caused by : IdeChnDr.sys ( IdeChnDr+5b74 )

Followup: MachineOwner
---------

kd> .reload
Loading Kernel Symbols
............................................................................................................
Loading unloaded module list
..........
Loading User Symbols
kd> !analyze -show
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000034, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f848ab74, address which referenced memory

Debugging Details:
------------------

Unable to load image IdeChnDr.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for IdeChnDr.sys
*** ERROR: Module load completed but symbols could not be loaded for IdeChnDr.sys

READ_ADDRESS: 00000034

CURRENT_IRQL: 2

FAULTING_IP:
IdeChnDr+5b74
f848ab74 0fb65834 movzx ebx,byte ptr [eax+0x34]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f848aaa7 to f848ab74

LOCK_ADDRESS: 80543c60 -- (!locks 80543c60)

Resource @ nt!PiEngineLock (0x80543c60) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x80543c60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

TRAP_FRAME: f898e760 -- (.trap fffffffff898e760)
ErrCode = 00000000
eax=00000000 ebx=81f4736c ecx=81f1a480 edx=00000000 esi=81f4736c edi=00eabee9
eip=f848ab74 esp=f898e7d4 ebp=f898e7e0 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
IdeChnDr+0x5b74:
f848ab74 0fb65834 movzx ebx,byte ptr [eax+0x34] ds:0023:00000034=??
Resetting default scope

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f898e7e0 f848aaa7 81f4736c 00000000 81f4736c IdeChnDr+0x5b74
f898e80c f8488e6a 00f4736c 81f470e0 81f18c50 IdeChnDr+0x5aa7
f898e834 804ec04f 81f45030 81f18c50 f84fc0fa IdeChnDr+0x3e6a
f898e844 f84fc121 f84fc0fa f84fc886 81f41ac0 nt!IopfCallDriver+0x31
f898e84c f84fc886 81f41ac0 81f18c50 81f18d08 ACPI!ACPIDispatchForwardIrp+0x27
f898e87c 804ec04f 81f41ac0 f851060c 81e83620 ACPI!ACPIDispatchIrp+0x158
f898e88c f8593cf1 804ed7c2 81fd0c00 00000000 nt!IopfCallDriver+0x31
f898e89c f8595d41 81e83620 81fd0b48 81fd0b48 CLASSPNP!SubmitTransferPacket+0x7e
f898e94c f8584f7d 81fd0b48 81fd0c00 f8587f60 CLASSPNP!ClassReadDriveCapacity+0x96
f898e958 f8587f60 81fd0b48 81fd0de8 81fd0c00 disk!DiskReadDriveCapacity+0x21
f898e978 f859a092 81fd0b48 c00000bb 00000000 disk!DiskEnumerateDevice+0x1a
f898e98c f859ac32 81fd0b48 81a26b20 81fd09d8 CLASSPNP!ClassPnpQueryFdoRelations+0x32
f898e9b8 804ec04f 81fd0b48 81a26b20 81a26c18 CLASSPNP!ClassDispatchPnp+0x52f
f898e9c8 f87cdb3a 81a26bfc 81fd09d8 81a26b20 nt!IopfCallDriver+0x31
f898ea04 f87ce01c 81fd09d8 81a26b20 81a26c20 PartMgr!PmQueryDeviceRelations+0x4d
f898ea40 804ec04f 81fd0920 81a26b20 f898eabc PartMgr!PmPnp+0x18b
f898ea50 8055b50d 00000000 81f41860 81f41860 nt!IopfCallDriver+0x31
f898ea7c 80505cc8 81fd0920 f898ea98 81f41940 nt!IopSynchronousCall+0xb8
f898eabc 805adb93 00000000 81f45030 00000001 nt!IopQueryDeviceRelations+0x39
f898ead0 805adb66 81f41860 00000001 81f41860 nt!PipEnumerateDevice+0x20
f898ed18 805af082 81f41860 00000001 00000000 nt!PipProcessDevNodeTree+0x1b1
f898ed4c 805057fa 00000003 80543d40 80548abc nt!PiProcessReenumeration+0x5e
f898ed74 804ebd08 00000000 00000000 81fccb30 nt!PipDeviceActionWorker+0x133
f898edac 80559026 00000000 00000000 00000000 nt!ExpWorkerThread+0xfe
f898eddc 8050f513 804ebc35 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
IdeChnDr+5b74
f848ab74 0fb65834 movzx ebx,byte ptr [eax+0x34]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: IdeChnDr+5b74

MODULE_NAME: IdeChnDr

IMAGE_NAME: IdeChnDr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d99eac3

STACK_COMMAND: .trap fffffffff898e760 ; kb

FAILURE_BUCKET_ID: 0xD1_IdeChnDr+5b74

BUCKET_ID: 0xD1_IdeChnDr+5b74

Followup: MachineOwner

 

I would boot off of my XP cd and do a "Repair Windows ".

Remember to restall SP2 and any other, new updates.

 

Hello avinashk,

How to do a repair install:
http://www.michaelstevenstech.com/XPrepairinstall.htm

Regards - Charles

 

This webpage suggest to de-install the Intel Driver
http://forums.scotsnewsletter.com/lofiversion/index.php/t2472.html

 

Generally, an IRQL_NOT_LESS_OR_EQUAL error indicates you have a bad driver.
Updating the driver in question will solve it.
Most of the time it turns out to be the video card driver.


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000034, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f848ab74, address which referenced memory


This indicates that whatever device assigned memory address f848ab74 tried to read from memory address 00000034 did not have the correct permissions for that address.
By going to control panel/ system / hardware /device manager and selecting devices one at a time and checking their properties / resources you will find one which has a memory range (note some devices will have more than one assigned) which includes f848ab74, probably something like f8000000 -f8ffffff
. You just update the driver.
Occaisionally this is caused by an incompatible bios entry , and you need to update (flash ) your bios, but this is rare and flashing the bios should be a last resort.
To quote microsoft
"Cause

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses. "

 

I had removed Intel Application Accelerator and also delete virtual memory and recrete it.

After that error is gone.


Thanx Everybody for posting.

 

This is not the first time I have heard of Intel Application Accellerator causing problems. There was a flurry of similar problems when windows update was misidentifying motherboard chipsets and suggesting it for non Intel based motherboards. I thought that had been corrected though.