also @ TechSpot: AMD Radeon HD 7770 & Radeon HD 7750 Review
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.

Go Back   TechSpot OpenBoards > Tech Support > Device Drivers

Download Now:

DRIVER_IRQL_NOT_LESS_OR_EQUAL - Can you help?

Thread Tools Search this Thread
  #1  
Old 09-29-2005
Newcomer, in training
 
Location: WA
Member since: Sep 2005, 2 posts
DRIVER_IRQL_NOT_LESS_OR_EQUAL - Can you help?

I have been having the same problem. I have unistalled my printer and changed my virtual memory to be system managed. While I had my printer uninstalled, I didn't have any errors. After an hour and a half I reinstalled the printer and printed twice, then I got an error. So, I think it is a printer driver problem, but I'm just not sure. My printer is an HP laserjet 1200se. My computer is a DELL Dimension DIM3000 Intel Celeron, 2.4Ghz, 256 MB of RAM 40G hard drive. I have also gotten error messages regarding my Linksys Wireless-G PCI adapter. There are six minidumps for you to look at.
Thanks for your time!!
Attached Files
File Type: zip Mini092705-08.zip (95.0 KB, 3 views)
  #2  
Old 09-29-2005
TechSpot Evangelist
 
Location: HK
Member since: Jan 2005, 2,044 posts
Hi,

I need more minidumps to find out the culprits. Attach 6 to 8 minidumps here.
  #3  
Old 06-16-2008
Newcomer, in training
 
Member since: Feb 2008, 17 posts
memory dumps

just curious how i get a "mini dump" when i have an error?

thanks!
  #4  
Old 06-16-2008
Route44's Avatar
TechSpot Ambassador
 
Location: The Socialist Republic of New Jersey
Member since: Sep 2006, 11,800 posts
Quote:
Originally Posted by m.erin33
just curious how i get a "mini dump" when i have an error?

thanks!
Minidumps are created by Windows anytime you have a Blue Screen of Death (BSOD). These files are stored in your Minidump Folder which is found in your Windows Folder in your C Drive. These files contain information pointing to the proabable cause of your crash.
  #5  
Old 06-17-2008
Newcomer, in training
 
Member since: Feb 2008, 17 posts
thank you route44!
  #6  
Old 06-20-2008
Newcomer, in training
 
Member since: Jun 2008, 3 posts
I've also got this message also, in my case I'll used the newest nForce driver, but now I've got other BSOD.

I've debugged one of your .dmp:

==============================================

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


Loading Dump File [c:\windows\minidump\a\Mini092705-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is: c:\windows\i386
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Sep 27 21:02:47.640 2005 (GMT+3)
System Uptime: 0 days 0:02:41.140
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
........................................................................... .............................................................
Loading User Symbols
Unable to load image RT2500.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RT2500.sys
*** ERROR: Module load completed but symbols could not be loaded for RT2500.sys
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {257e, 2, 0, f8fcdac2}

Probably caused by : RT2500.sys ( RT2500+bac2 )

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

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: 0000257e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f8fcdac2, address which referenced memory

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


READ_ADDRESS: 0000257e

CURRENT_IRQL: 2

FAULTING_IP:
RT2500+bac2
f8fcdac2 0fb608 movzx ecx,byte ptr [eax]

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from f8fe2c94 to f8fcdac2

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8054ff48 f8fe2c94 80550070 0000257e 00000006 RT2500+0xbac2
805500a8 f2500000 00000102 0002f250 80550000 RT2500+0x20c94
805500ac 00000000 0002f250 80550000 f8fd5f4b 0xf2500000


STACK_COMMAND: kb

FOLLOWUP_IP:
RT2500+bac2
f8fcdac2 0fb608 movzx ecx,byte ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: RT2500+bac2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RT2500

IMAGE_NAME: RT2500.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42675c99

FAILURE_BUCKET_ID: 0xD1_RT2500+bac2

BUCKET_ID: 0xD1_RT2500+bac2

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

=======================================

This caused your BSOD: Sample Driver for Ralink 802.11g Wireless PCI Adapters - Ralink 802.11g Wireless PCI Adapters - Ralink Technology Inc.

Last edited by eusceptic; 06-20-2008 at 10:29 AM..
Closed Thread

Similar Topics
Topic Replies Forum
Driver_irql_not_less_or_equal 3 Device Drivers
Driver_irql_not_less_or_equal 2 Software Apps
Driver_irql_not_less_or_equal 6 Windows OS
Driver_irql_not_less_or_equal 11 Processors and Motherboards
Driver_IRQL_NOT_LESS_OR_EQUAL 0 Device Drivers

Thread Tools Search this Thread
Search this Thread:

Advanced Search
All times are GMT -4. The time now is 10:23 AM.