driver_irql_not_less_or_equal (please help again)

[sykopath79]

This question has probably been asked already, but I ask it anyway: Are you overclocking?

I ask because on my Nforce2 board, I will get this exact same BSOD if I push it too hard on an overclock. It doesn't seem to like going more than a few MHz above 11x200 with my 2500+ Barton without giving me a BSOD.

 

[imported_tightflks]

no i wasnt overclocking, it doesnt allow me to overclock it

i have an nforce

 

[sykopath79]

Originally posted by: tightflks
no i wasnt overclocking, it doesnt allow me to overclock it

i have an nforce

You have an ASUS Nforce board that doesn't allow overclocking? I find that odd.

 

[imported_tightflks]

yah i no, i can overclock it, if i mess with the jumpers on the motherboard, but from BIOS i cant do it wierd eh?

got a7n266-vm, or something like that, cant remember off the top of my head

edit:
i got the damn blue screen again..........

 

[Ryoga]

Originally posted by: Sianath
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.

Hey, look. Somebody who knows what they're talking about!

Make sure you're using the most recent nForce drivers. Those are the ones that appear to be throwing the exception, not the sound card.

To test your memory , get MemTest86. Run the thorough/complete test on continuous for a few hours.

To test your CPU, get something like Prime95 and run it overnight. Any kind of CPU "burn-in" program will do.

Your third option, since you have onboard sound, is to simply remove the Santa Cruz and go back to your onboard audio to see if that fixes your problem. Can you really tell the difference in quality? What is the Santa Cruz giving you that the nForce audio isn't?

 

[imported_tightflks]

5.1 channels, and I'll try all those things you have suggested

and its not the santa cruz anyways, i just noticed that they name a file on the blue screen

nv4_mini.sys which is from the nfroce drivers, so im pretty sure thats it

i just thought it was the santacruz, because when installing xp once i got errors but when i removed the santa cruz it was fine

 

[Sianath]

Definately update the nForce stuff... that's what I saw in the first dump analysis and they are fairly old (2002 drivers).

 

[imported_tightflks]

Ok, well I think I have figured it out. Before the blue screens came from that NVENET.sys which is an nforce network card driver file. So when I updated everything, the new blue screen with the nv4_mini.sys came from the display drivers. So I uninstalled only the display driver this time and installed an older one which people say work.


So, hopefully this new configuration will work, and if not, well theres nohing ele you all here can do.

Id like to thank everyone for their advice and help, you've helped a lot.