driver_irql_not_less_or_equal (please help again)

imported_tightflks · May 11, 2004

i am gettin this blue screen error on xp

driver_irql_not_less_or_equal

and i thought maybe it was time for a format, so i did, but when installing XP i got blue screen errors while installing and i dont remembr which ones for sure. i thought it might be the sound card so i took that out and i installed XP fine. So im sorta assumin its cause of my sound card, anyone got any ideas?

I have a turtle beach santa cruz

some say if i switch the slot it will help, but im not sure, anyone got any ideas, and if switchin the slot does help, could you tell me why, cause i dont see how it would

johnjkr1 · May 11, 2004

Welcome to the forum!

Different slot, different IRQ's. You should definitely not have it in the first slow near the AGP card. When you formatted and installed xp, did you do the proper chipset drivers for your pc? When I had a santa cruz I never had a problem. You might also flash to the latest bios for your motherboard.

imported_tightflks · May 11, 2004

thanks for the welcome

i installed the proper chipset, i have an nforce motherboard by asus and used thier drivers and updated them

as for the sound card it was in the one next to the agp slot, and i did move it just now, one over. But i got the error again. thanks

johnjkr1 · May 11, 2004

Try a reinstall with it in a slot furthur down. See what happens. Also, make sure you have the latest santa cruz drivers, I had all kinds of problems with the ones on the CD.

imported_tightflks · May 11, 2004

so move it down one more time? should i uninstall driver before i move it?

imported_tightflks · May 11, 2004

exactly what is irql, cause i got the error again

if i remove stuff of the computer like this digitical optic sound output hting i never use, and an extra serial port i dont use, would it help?

cause my game port on the santa cruz always has this yellow warning sign next to it in the device manager, it always did, saids i need to free up resources

johnjkr1 · May 11, 2004

It could be related, try turning off unnecessary items in the bios....what is a "digitical optic" thing?

johnjkr1 · May 11, 2004

also, what version of the santa cruz driver are you using?

imported_tightflks · May 11, 2004

digital optic thing is where u stick in someonthing for high end speakers

u mean driver? the latest driver

Need4Speed · May 11, 2004

thats generally a sign of a bad driver

imported_tightflks · May 11, 2004

oki disabled the game port, the only thing in the deviec manager with a question mark, i got a blue screen again, but this time it didnt say driver_irql_not_less_or_equal, it just said check drivers and maybe change driver adapters, so any ideas?

alos says turn of bios caching and shadowing, whats that?

imported_BikeDude · May 12, 2004

I think it's fairly important to point out that the bugcheck code in question (DRIVER_IRQL_etc..) has absolutely nothing to do with interrupts/IRQs. Basically an exception has been thrown in the kernel because a driver has accessed a resource (memory) which it currently has no access to. (search http://support.microsoft.com/ for an explanation of various bugcheck codes including this one, or read Mark Russinovich' excellent "Inside Windows xxxx" book(s))

That said, there's probably a reason this happens with your setup. If this was a common error, the device driver developers would've seen it and hopefully delayed the release (ahem)... The other day we tested Nokia's Symbian SDK which comes with a driver, and it turns out that it produces the DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD on computers with hyperthreading enabled. Many drivers (Creative probably have problems still :-( ) aren't tested on SMP rigs and will thus fail on many P4s with hyperthreading enabled too.

You're probably a sensible person who doesn't buy overpriced Intel stuff, so this probably does not apply to you.

(OTOH you could be running dual Opterons for all I know, which is a sensible thing to do, but would tickle the Nokia driver I mention)

huesmann · May 13, 2004

Does your mobo have on-board sound, and is it disabled?

imported_tightflks · Jun 7, 2004

my mobo does have onboard, i recently disbaled, and i stilll get this error

i have the latest santa cruz drivers, which arent digitally recognized by micrsoft, so i want back to an od one which is, and i still get the errors

ive disabled serials ports and usb ports, and i am still getting this error

can anyone help?

imported_tightflks · Jun 7, 2004

can someone please help me again

jhbball · Jun 7, 2004

as stated above, this isn't an actual irq problem, rather, it's a memory problem. How many sticks of ram are you running? First, try using one stick at a time. If that works, try the other one, and see if it's a faulty stick. Second, you could also try uppping your memory voltage.

I've had this problem before, and it was definetly memory related. good luck.

imported_tightflks · Jun 7, 2004

how do i up the memory voltage in bios? and if so, how much should i up it

would updating the bios help any?

oldman420 · Jun 7, 2004

i agree with jh it sounds like a memory problem did you try to uninstall and reinstall the card in the device manager without using the driver setup program? that might help too short of that reinstall windows usualy fixes these things as long as you have good hardware

jhbball · Jun 7, 2004

updating the bios couldn't hurt, but I'm guessing it won't solve the problem. In the bios, if you have the option, try upping the voltage to 2.7 or so. Also, if it hasn't been done already, try setting the ram speed to "SPD", this should set the ram timings to what the stick is rated for.

Finally, trying moving the stick(s) two a different slot. It's possible that the ram slot may be faulty etc. Keep us posted.

imported_tightflks · Jun 9, 2004

would reinstalling windows, fix this problem in any way?

i have on stick of RAM so i cant really take it out and seeing if it works or not

I did run windows memeory test thing on it, and it passed fine so..................

and i disbaled the onboard soundcard in bios, sorta runnin out of ideas here =/

jhbball · Jun 9, 2004

just try swapping slots at the very least.

spacelord · Jun 10, 2004

make sure you run the extended memory tests. My computer could pass the standard ones with flying colors, but test 10 or 11 in the extended tests would fail every time when I run my 2700 memory at 2700 speeds.

Sianath · Jun 10, 2004

Almost all instances of that bugcheck (in current drivers) are not caused by actually trying to reference paged pool at a high IRQL... most driver writers have that one down by now. What normally happens when you examine the dump is that you are referencing a bogus address due to data corruption (either another driver or bad memory/cpu) and the bad address happens to be in pageable memory space (hence the error we throw).

Definately check the memory on the machine as was suggested... proc is one that's not easy to check unfortunately.

If you are bugchecking on boot (or shortly after) please post the stop code and parameters. Do this two or three times so we can verify if we are crashing in the same spot each time, or if it's the same stop code with different parameters. If it's different parameters each time you are almost guaranteed to have a hardware issue.

Sianath · Jun 17, 2004

=========================
Problem:
=========================

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

=========================
Recommendations:
=========================

NVENET.SYS is trying to dereference a bogus memory address. The memory address may have been valid at one point, but then either freed prior to referencing, or corrupted by another driver running on the system. I can't tell how it got that way with a minidump (not enough info) but it is a constant factor in all of the mini dumps you have. If it was a different driver referenced in each dump, I would suspect a driver is corrupting memory, but this is the same driver each time, so it's likely this is our culprit.

This is a driver provided by nForce The version you have installed is from 2002. I would suggest updating this driver.

=========================
Analysis:
=========================

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

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

Debugger Dbgportaldb Connection::Open failed 80004005

Database Dbgportaldb not connected
ADO ERROR 80004005,11: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

READ_ADDRESS: 5e044688

CURRENT_IRQL: 2

FAULTING_IP:
NVENET+6367
f6e74367 8b08 mov ecx,[eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f6e6fcdc to f6e74367

TRAP_FRAME: f78a6f0c -- (.trap fffffffff78a6f0c)
ErrCode = 00000000
eax=5e044688 ebx=83f17234 ecx=f72cb65e edx=5e044688 esi=83f17000 edi=83e8e000
eip=f6e74367 esp=f78a6f80 ebp=f78a6fa4 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
NVENET+0x6367:
f6e74367 8b08 mov ecx,[eax] ds:0023:5e044688=????????
Resetting default scope

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78a6fa4 f6e6fcdc 83e8e000 84cb76e8 83f171e0 NVENET+0x6367
83e8e010 00000000 00000000 00000000 00000000 NVENET+0x1cdc

FOLLOWUP_IP:
NVENET+6367
f6e74367 8b08 mov ecx,[eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: nforce

SYMBOL_NAME: NVENET+6367

MODULE_NAME: NVENET

IMAGE_NAME: NVENET.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3de59761

STACK_COMMAND: .trap fffffffff78a6f0c ; kb

BUCKET_ID: 0xD1_NVENET+6367

Followup: nforce

kd> .trap fffffffff78a6f0c
ErrCode = 00000000
eax=5e044688 ebx=83f17234 ecx=f72cb65e edx=5e044688 esi=83f17000 edi=83e8e000
eip=f6e74367 esp=f78a6f80 ebp=f78a6fa4 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
NVENET+0x6367:
f6e74367 8b08 mov ecx,[eax] ds:0023:5e044688=????????

kd> kv
*** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
f78a6fa4 f6e6fcdc 83e8e000 84cb76e8 83f171e0 NVENET+0x6367
83e8e010 00000000 00000000 00000000 00000000 NVENET+0x1cdc

kd> dd eax
5e044688 ???????? ???????? ???????? ????????
5e044698 ???????? ???????? ???????? ????????
5e0446a8 ???????? ???????? ???????? ????????
5e0446b8 ???????? ???????? ???????? ????????
5e0446c8 ???????? ???????? ???????? ????????
5e0446d8 ???????? ???????? ???????? ????????
5e0446e8 ???????? ???????? ???????? ????????
5e0446f8 ???????? ???????? ???????? ????????

kd> !pool eax
Pool page 5e044688 region is Unknown
GetUlongFromAddress: unable to read from 805479d0
5e044000 is not a valid small pool allocation, checking large pool...
unable to get pool big page table - either wrong symbols or pool tagging is disabled
5e044000 is freed (or corrupt) pool
Bad allocation size @5e044000, too large

***
*** An error (or corruption) in the pool was detected;
*** Pool Region unknown (0x5E044000)
***
*** Use !poolval 5e044000 for more details.
***

kd> !poolval 5e044000
Pool page 5e044000 region is Unknown

Validating Pool headers for pool page: 5e044000

Pool page [ 5e044000 ] is INVALID.

kd> lmvm NVENET
start end module name
f6e6e000 f6e81c00 NVENET T (no symbols)
Loaded symbol image file: NVENET.sys
Image path: NVENET.sys
Image name: NVENET.sys
Timestamp: Wed Nov 27 20:11:13 2002 (3DE59761)
CheckSum: 00014996
ImageSize: 00013C00
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

imported_tightflks · Jun 20, 2004

I had the most updated drivers, so i think rolling back would help

are you sure I have 2002, the package date (file name) has 2003 in it

well apparenlty at the nvidia site are more updated drivers, i been goin to asus site

sianath, i would like to thank you a lot for your help

driver_irql_not_less_or_equal (please help again)

Member

Platinum Member

Member

Platinum Member

Member

Member

Platinum Member

Platinum Member

Member

Diamond Member

Member

Senior member

Diamond Member

Member

Member

Platinum Member

Member

Platinum Member

Platinum Member

Member

Platinum Member

Platinum Member

Senior member

Senior member

Member