Irql_not_less_or_equal

Status
Not open for further replies.
alas said:
... but only when running in battery. When I boot on AC everything seems fine but when i unplug the cable I get a BSOD. The minidump is attached. I dont think it is a RAM problem cause when i boot in safe mode (battery) everything works fine. I someone can help me please drop a post...:)
Click to expand...
Hi Alas,

One minidump is insufficient to diagnostic your problem. Zip 5 to 6 minidumps and attach them here.
 
Hi Asx,

Your original problem re-occurs again and it seems that Microsoft recommendation does not work. Do you install any new software at your windows?


Debug report
=========
Debug session time: Sat Oct 8 09:26:14.671 2005 (GMT+8)
System Uptime: 4 days 0:25:37.360
BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : NDIS.sys ( NDIS!ndisMIsr+54 )

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000820, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804d9e0e, address which referenced memory

Debugging Details:
------------------
WRITE_ADDRESS: 00000820
CURRENT_IRQL: 1e

FAULTING_IP:
nt!KiIpiSend+10
804d9e0e f0099020080000 lock or [eax+0x820],edx

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 804e6173 to 804d9e0e

STACK_TEXT:
f7c5ac60 804e6173 855180ac 85518088 f7c5ad50 nt!KiIpiSend+0x10
f7c5ac7c f7645ec8 f7ac79c0 00000000 00000000 nt!KeInsertQueueDpc+0xe8
f7c5ac9c 804db90f 861d1610 01518074 01010006 NDIS!ndisMIsr+0x54
f7c5ac9c f7a31062 861d1610 01518074 01010006 nt!KiInterruptDispatch+0x45
f7c5ad50 804dcbef 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
f7c5ad54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10

FOLLOWUP_IP:
NDIS!ndisMIsr+54
f7645ec8 84c0 test al,al

SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: NDIS!ndisMIsr+54
MODULE_NAME: NDIS
IMAGE_NAME: NDIS.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54
BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54
 
Hello and welcome to Techspot.


alas said:
... but only when running in battery. When I boot on AC everything seems fine but when i unplug the cable I get a BSOD. The minidump is attached. I dont think it is a RAM problem cause when i boot in safe mode (battery) everything works fine. I someone can help me please drop a post...:)
Click to expand...


Your mindump crashes at amdk7.sys. This is part of the power throttling of your cpu.

The fact that you only get the problem when running from battery, would suggest that your battery is not providing enough power.

Try getting a new battery. If that doesn`t work, then maybe your charger isn`t charging the battery properly.

Regards Howard :wave: :wave:
 
Hi asx,

One minidump is crashed at ATI display driver and you installed ATI display card at this month. Your version of ATI display card driver is unstable and some forum recommend to omegadrive.

Another minidump is the old problem and you reported the problem to Microsoft. Microsoft's feedback is device driver error and you don't tell me what is the Microsoft's recommendation. Why the problem is still existed?
 
Hi Asx,

Microsoft provides paid service and free service. If you request pay service, they will read your minidumps and find out the culprit. I think you request free service and they reply with a standard answer (ie driver problem).

The lastest dump is crashed at netflt.sys. It is antivirus or firewall software tha you install recently.

BugCheck 100000D1, {28, 2, 1, f75e53e8}
Probably caused by : NETFLT.SYS ( NETFLT+23e8 )

Maybe I am side-trarcked by IRQL x'1E'. Probably the culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
 
I already run memtest like 4 months ago, cpu heat it fine(i have a zalman fan), also change my raid controler and format my pc again this morning. also create a new partition. and now im having new error msg...also test new cpu...when i will have another BSOD, ill post my dump
 
cpc2004, not trying to get in the way of asx's problem so I'm ready to wait till you can possibly help him. I've got the same problem but I can't figure out how to open or save the dump file to post here. I've read a few pages here and have tried dlling programs, changing/adding sybol paths you name it, I've tried I think. Any way I could pm you and then email you my dump file? I have a week old laptop and having this same problem. Really gets to ya when its a brand new expensive machine. Any help or suggestions would be greatlhy appreciated!
 
Hello and welcome to Techspot.

You can find instruction on posting your minidumps etc HERE

Then please start your own thread in the Windows OS forum.

Thanks and regards Howard :wave: :wave:
 
asx said:
here some new dump
Click to expand...
Hi Asx,

Your latest dump does not have new information. It crashed due to hardware problem. It is very hard to find out the culprit. Maybe it is CPU, ram or video card. BTW do you run prime95 to stress test the CPU?

BugCheck 1000007F, {8, f7ac7d70, 0, 0} <-- This is hardware error
 
Microsoft tech told me to put my windows disk, go in recovery mode and run chkdsk /p...even if I certified im that my HDD is ok...As I thought this operation was useless
 
Status
Not open for further replies.

Similar threads

B
Continuing to get BSOD's
Replies
0
Views
2K
Bloano
B
B
BSOD 0x3B
Replies
5
Views
3K
Tmagic650
Tmagic650
Flyingjones
BsoD 0x0000007f
Replies
4
Views
3K
Tmagic650
Tmagic650

Latest posts

Back