Irql_not_less_or_equal

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

Hi ASX,

Maybe it is the problem of L2 cache memory of the CPU. Install prime 95 to test your CPU.

http://www.mersenne.org/freesoft.htm

here some new 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:

Howard, sorry bout that. Typical newbie move I guess. I took your advice and posted a new thread in OS.

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

yes i did it for 24h no problem, already test another cpu and video card

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

Asus will RMA my board...so I'll have change evertyhing on this computer..

Hi ASX,

Your problem is very strange and it is caused by hardware error. Probably it is motherboard. As you know there have no reliable tools to test the m/b. Attach the latest dump here.

here we go

Hi ASX,

From the stack trace, it crashes at KiIpiSend which is the interprocessor communication. Probably the CPU has hardware error.

ChildEBP RetAddr Args to Child
f7c5ac60 804e6173 856760ac 85676088 f7c5ad50 nt!KiIpiSend+0x10 (FPO: [0,2,0])
f7c5ac7c f757dec8 f7ac79c0 00000000 00000000 nt!KeInsertQueueDpc+0xe8 (FPO: [Non-Fpo])
f7c5ac9c 804db90f 858aa958 01676074 01010006 NDIS!ndisMIsr+0x54 (FPO: [Non-Fpo])

ok, ill swap it with my friend cpu then, ill keep u posted

swap cpu with my friend, got a diff error msg now

I think the dmp is talking about the driver for my NIC.. So i updated the driver...will see now

Driver was already up to date, i just reinstall them, if u have more info for me, please reply to me, im desperate

Hi asx,

Your problems has two culprits. The first culprit is IRQL x'1E' crashes and the other culprit is stack trace overflow. The stack trace overflow may be caused by ATI display card driver. Extend the stack trace may resolve the problem (use regedit to extend the value of KStackMinFree). BTW two device device are at 1997, you had better upgrade it to latest level.

f7dbd000 f7dbe2a0 DS1410D DS1410D.SYS Thu Jul 24 21:55:39 1997 (33D75EDB) ??
f7f0e000 f7f0eda0 aslm75 aslm75.sys Wed Apr 23 09:15:58 1997 (335D62CE) ??

We have to wait for the new occurence of IRQL x'1E' after you swap the CPU.

Extend the stack trace may resolve the problem (use regedit to extend the value of KStackMinFree). BTW two device device are at 1997, you had better upgrade it to latest level.

f7dbd000 f7dbe2a0 DS1410D DS1410D.SYS Thu Jul 24 21:55:39 1997 (33D75EDB) ??
f7f0e000 f7f0eda0 aslm75 aslm75.sys Wed Apr 23 09:15:58 1997 (335D62CE) ??


In Clear ??