yet another driver_irql_not_less_or_equal...

Status
Not open for further replies.
I get this crash after playing almost any game for a while.
Since my Windows language is not English, I created a translated the text of the dumps:

Dump 1. Error code 100000d1 (7471735f, 00000002, 00000000, 7471735f‏ )

Dump 2. Error code 00000019 (00000020, 8194f0b8, 8194f1e0, 0a250003)

Dump 3. Error code 100000d1 (f18c840d, 00000005, 00000001, 00000001)

Attached are the dump files...

:) Thank you very much :wave:
 
Hi ykkky,

IRQL 5 is device interrupt which is unlike to crash unless it is hardware error. What USB device do you use when the crash occurs? It maybe hardware error of the USB device or your PSU has inadequate power.

Mini102905-02.dmp BugCheck 19, {20, 8194f0b8, 8194f1e0, a250003}Mini102905-02.dmp
Mini102905-02.dmp Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_CompleteTransfer+43f )

Mini102905-01.dmp BugCheck 100000D1, {7471735f, 2, 0, 7471735f}
Mini102905-01.dmp Probably caused by : usbuhci.sys ( usbuhci!UhciInterruptDpc+5a )

Mini102905-03.dmp BugCheck 100000D1, {f18c840d, 5, 1, 1}
Mini102905-03.dmp Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_InterruptService+3d )
 
Thanks for your support.

However, I don't use any specific USB device. Some games crash after some time, and some don't.
I tried to disable all my USB ports in the device manager and it still crashes...
 
Hi,

The running processes of two of your minidumps are ntvdm which windows 16 bit Virtual Machine. Can you recall what you did you do when windows crash? I want the latest minidumps after you disable USB service.
 
Here:

Minidump 1:
error code 1000000a (000092fe, 00000002, 00000000, 804dbe7b )

Minidump 2:
error code 000000f4 (00000003, 819632d0, 81963444, 805f9f88 )

Thank you! :)
 
Hi ykkky,

The stack trace of your latest dump is very clear that windows crashes at timer routine. It crashes only if hardware errors occurs. Probably it is faulty ram. Another crash is at termination routine which is also caused by faulty ram.

STACK_TEXT:
f9e4de04 804dbeff fff79b90 ffffffff a769f4fa nt!KiInsertTimerTable+0x2f
f9e4de20 804dc3cb fff79b90 ffffffff f35c41d0 nt!KiInsertTreeTimer+0x7d
f9e4de40 804dc402 005c41a0 fff79b90 ffffffff nt!KeSetTimerEx+0x4b
f9e4de5c f35ba405 f35c41a0 fff79b90 ffffffff nt!KeSetTimer+0x18
f9e4de88 804dc4fd f35c41e0 00000000 a622e40e rdbss!RxTimerDispatch+0xbe
f9e4dfa4 804dc378 a769f4fa 0000017a ffdff000 nt!KiTimerListExpire+0x122
f9e4dfd0 804dbbd4 80559280 00000000 009ed1a8 nt!KiTimerExpiration+0xaf
f9e4dff4 804db89e f19f2d44 00000000 00000000 nt!KiRetireDpcList+0x46
f9e4dff8 f19f2d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a

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 did all the steps, and even bought a new memory stick, but it still crashes (now with a different error code...).

error code 10000050 ( ffffffbb, 00000000, 8174f1f0, 00000000 )
 
Hi,

Do you mean you replace the memory stick or just add a new memory stick? Do you diagnostic which memory stick is bad? If yes, you must take it out. Attach the latest minidumps for further analysis.
 
Status
Not open for further replies.
Back