Windows Vista Driver IRQL Not Less an Eaqual!!

  • Thread starter Thread starter RuffRider
  • Start date Start date
R

RuffRider

Guest
Problem: Regardless of it being XP Pro or Vista Ultimate I am using at the
time then at anytime in the day I get the dreaded blue screen and the Driver
IRQL not less than equal nonsense.
Exact same bunch of numbers and zeros every time.
STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
0x0000000000000008, 0x0000000000000000
Never changes, always the exact same.
Must be something common to XP Pro and Vista to be making it happen.... but
what?
 
Re: Driver IRQL Not Less an Eaqual!!

Hardware problem, or same driver used in XP and Vista.

--
Earle Horton -- earleh@terra.comx

"RuffRider" <RuffRider@horsefield.net> wrote in message
news:%23323Ph8LJHA.4432@TK2MSFTNGP02.phx.gbl...
> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at the
> time then at anytime in the day I get the dreaded blue screen and the
> Driver IRQL not less than equal nonsense.
> Exact same bunch of numbers and zeros every time.
> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
> 0x0000000000000008, 0x0000000000000000
> Never changes, always the exact same.
> Must be something common to XP Pro and Vista to be making it happen....
> but what?
 
Re: Driver IRQL Not Less an Eaqual!!



IRQL Not Less an Equal usually means a incompatible driver or missing driver.

You can use the verifier to check which driver is in question

Start\Run\verifier
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"RuffRider" <RuffRider@horsefield.net> wrote in message news:%23323Ph8LJHA.4432@TK2MSFTNGP02.phx.gbl...
> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at the
> time then at anytime in the day I get the dreaded blue screen and the Driver
> IRQL not less than equal nonsense.
> Exact same bunch of numbers and zeros every time.
> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
> 0x0000000000000008, 0x0000000000000000
> Never changes, always the exact same.
> Must be something common to XP Pro and Vista to be making it happen.... but
> what?
>
 
Re: Driver IRQL Not Less an Eaqual!!

Have you installed any new equipment on your system around the time this
began. This often has something to do with a network driver.

"RuffRider" <RuffRider@horsefield.net> wrote in message
news:%23323Ph8LJHA.4432@TK2MSFTNGP02.phx.gbl...
> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at the
> time then at anytime in the day I get the dreaded blue screen and the
> Driver IRQL not less than equal nonsense.
> Exact same bunch of numbers and zeros every time.
> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
> 0x0000000000000008, 0x0000000000000000
> Never changes, always the exact same.
> Must be something common to XP Pro and Vista to be making it happen....
> but what?
 
Re: Driver IRQL Not Less an Eaqual!!

RuffRider wrote:
> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at
> the time then at anytime in the day I get the dreaded blue screen and
> the Driver IRQL not less than equal nonsense.
> Exact same bunch of numbers and zeros every time.
> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
> 0x0000000000000008, 0x0000000000000000
> Never changes, always the exact same.
> Must be something common to XP Pro and Vista to be making it happen....
> but what?

Test your RAM. On startup hit F9 then TAB to Memory Diagnostic tool.
It will take about 5 mins, worth a shot.
 
Re: Driver IRQL Not Less an Eaqual!!

No new hardware installed.....
Tested ram and no problem
Only things changed was Nvidia drivers for Graphics card and motherboard.

"fatsteve" <internet@sky.com> wrote in message
news:48f817bc$0$10595$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
> RuffRider wrote:
>> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at
>> the time then at anytime in the day I get the dreaded blue screen and the
>> Driver IRQL not less than equal nonsense.
>> Exact same bunch of numbers and zeros every time.
>> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
>> 0x0000000000000008, 0x0000000000000000
>> Never changes, always the exact same.
>> Must be something common to XP Pro and Vista to be making it happen....
>> but what?
>
> Test your RAM. On startup hit F9 then TAB to Memory Diagnostic tool. It
> will take about 5 mins, worth a shot.
>
 
Re: Driver IRQL Not Less an Eaqual!!


RuffRider;862729 Wrote:
> Exact same bunch of numbers and zeros every time.
> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
> 0x0000000000000008, 0x0000000000000000
> Never changes, always the exact same.
>

A 0xd1 bugcheck = DRIVER_IRQL_NOT_LESS_OR_EQUAL and indicates that a
kernel-mode driver attempted to access a pageable memory address (or a
bad address) when it should not have (at a process IRQL that was too
high). A 0xd1 bugcheck is usually caused by drivers using improper
addresses.

A few things in the posted bugcheck I find interesting. I already
mentioned what 0xd1 means. The first parm inside the parenthesis is the
memory address referenced by the object in the 4th parm - so you have an
object with a memory address of 0x0 referencing a 0x0 - these s/b filled
with numbers and letters... not zeroes as far as I have ever seen. The
second parm (0x2) is the IRQL at the time #4 referenced #1, which is
fine (or at least a valid #). The 3rd parm 0x8 tells us that this is an
execution routine (0x0 = read; 0x1 = write).

The real interesting item here is that parm #4 = parm #1 and parm #3 is
0x8, which typically means that the bugcheck was caused by a driver
attempting to execute code that was paged out. Possible causes for this
are:
- the driver trying to acquire a resource/object lock - keeping its
siblings out
- a call was made to a driver that was already unloaded from RAM
- the pointer is bad

If no driver was named by the BSOD, then run the driver verifier in
hopes that it will cause a BSOD (like a 0xc4) and flag the offending
driver. If driver not named on BSOD screen, then maybe something will
show up in the stack text for all to see. No guarantees, of course.

The 0x0 in parms 1 & 4 are still bothersome.

I suggest you run memtest ISO if you have not already done so (not just
the Vista memory check).

If you invoke the driver verifier and BSOD occurs, get that dump, zip
it up and attach - c:\windows\minidump - it may contain the clue needed.

Where does XP Pro fit in here? Is this the same system? Do you have 1
app in common between the two systems that maybe contains old drivers?
The loaded driver list in the dbug output may tell us, unless it was
unloaded at the time of the crash.

You may also want to run driverquery and look over your drivers - Bring
up an *-elevated -*cmd prompt ("DOS") -
START | type cmd.exe into the start search box | right-click on cmd.exe
| select run as administrator - the type or copy/paste the following
into the DOS screen (to paste into DOS screen, right-click at the top,
select Edit, select Paste) hit Enter:


Code:
--------------------

*driverquery /v > %temp%\driverquery.txt & start notepad %temp%\driverquery.txt*

--------------------


A notepad will appear with the driver query report. Watch out for the
ones marked "disabled" under the column "Start Mode".

Regards. . .

jcgriff2

.


--
jcgriff2
 
Re: Driver IRQL Not Less an Eaqual!!

Should have shown as Driver IRQL Not Less Or Equal............
"RuffRider" <RuffRider@horsefield.net> wrote in message
news:%23323Ph8LJHA.4432@TK2MSFTNGP02.phx.gbl...
> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at the
> time then at anytime in the day I get the dreaded blue screen and the
> Driver IRQL not less than equal nonsense.
> Exact same bunch of numbers and zeros every time.
> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
> 0x0000000000000008, 0x0000000000000000
> Never changes, always the exact same.
> Must be something common to XP Pro and Vista to be making it happen....
> but what?
>
 
Re: Driver IRQL Not Less an Eaqual!!

I keep getting the same problem..................
Driver IRQL Not Less Or Equal with the same Stop error.
My pc also has had the drive reformatted and the standard drivers for
motherboard, sound card and graphics card installed just as they were before
the issue started.
No new drivers for anything and it happens after the pc has been in use for
6 or seven hours or so.
Sometimes it happens when I go to certain websites.
---------------------------------------------------------------------------------------
Have not installed any new hardware.
--------------------------------------------------------------------------------------
"John Barnes" <JBarnes@email.com> wrote in message
news:uGMr0u$LJHA.1304@TK2MSFTNGP02.phx.gbl...
> Have you installed any new equipment on your system around the time this
> began. This often has something to do with a network driver.
>
> "RuffRider" <RuffRider@horsefield.net> wrote in message
> news:%23323Ph8LJHA.4432@TK2MSFTNGP02.phx.gbl...
>> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at
>> the time then at anytime in the day I get the dreaded blue screen and the
>> Driver IRQL not less than equal nonsense.
>> Exact same bunch of numbers and zeros every time.
>> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
>> 0x0000000000000008, 0x0000000000000000
>> Never changes, always the exact same.
>> Must be something common to XP Pro and Vista to be making it happen....
>> but what?
>
>
 
Re: Driver IRQL Not Less an Eaqual!!

Ran verifier, did not cause a blue screen but did make my soundcard act
up(screeching sound)
"jcgriff2" <guest@unknown-email.com> wrote in message
news:dab3ba643575d10beaff4bcadebb236d@nntp-gateway.com...
>
> RuffRider;862729 Wrote:
>> Exact same bunch of numbers and zeros every time.
>> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
>> 0x0000000000000008, 0x0000000000000000
>> Never changes, always the exact same.
>>
>
> A 0xd1 bugcheck = DRIVER_IRQL_NOT_LESS_OR_EQUAL and indicates that a
> kernel-mode driver attempted to access a pageable memory address (or a
> bad address) when it should not have (at a process IRQL that was too
> high). A 0xd1 bugcheck is usually caused by drivers using improper
> addresses.
>
> A few things in the posted bugcheck I find interesting. I already
> mentioned what 0xd1 means. The first parm inside the parenthesis is the
> memory address referenced by the object in the 4th parm - so you have an
> object with a memory address of 0x0 referencing a 0x0 - these s/b filled
> with numbers and letters... not zeroes as far as I have ever seen. The
> second parm (0x2) is the IRQL at the time #4 referenced #1, which is
> fine (or at least a valid #). The 3rd parm 0x8 tells us that this is an
> execution routine (0x0 = read; 0x1 = write).
>
> The real interesting item here is that parm #4 = parm #1 and parm #3 is
> 0x8, which typically means that the bugcheck was caused by a driver
> attempting to execute code that was paged out. Possible causes for this
> are:
> - the driver trying to acquire a resource/object lock - keeping its
> siblings out
> - a call was made to a driver that was already unloaded from RAM
> - the pointer is bad
>
> If no driver was named by the BSOD, then run the driver verifier in
> hopes that it will cause a BSOD (like a 0xc4) and flag the offending
> driver. If driver not named on BSOD screen, then maybe something will
> show up in the stack text for all to see. No guarantees, of course.
>
> The 0x0 in parms 1 & 4 are still bothersome.
>
> I suggest you run memtest ISO if you have not already done so (not just
> the Vista memory check).
>
> If you invoke the driver verifier and BSOD occurs, get that dump, zip
> it up and attach - c:\windows\minidump - it may contain the clue needed.
>
> Where does XP Pro fit in here? Is this the same system? Do you have 1
> app in common between the two systems that maybe contains old drivers?
> The loaded driver list in the dbug output may tell us, unless it was
> unloaded at the time of the crash.
>
> You may also want to run driverquery and look over your drivers - Bring
> up an *-elevated -*cmd prompt ("DOS") -
> START | type cmd.exe into the start search box | right-click on cmd.exe
> | select run as administrator - the type or copy/paste the following
> into the DOS screen (to paste into DOS screen, right-click at the top,
> select Edit, select Paste) hit Enter:
>
>
> Code:
> --------------------
>
> *driverquery /v > %temp%\driverquery.txt & start notepad
> %temp%\driverquery.txt*
>
> --------------------
>
>
> A notepad will appear with the driver query report. Watch out for the
> ones marked "disabled" under the column "Start Mode".
>
> Regards. . .
>
> jcgriff2
>
> .
>
>
> --
> jcgriff2
>
 
Re: Driver IRQL Not Less an Eaqual!!

Are you using the network drivers on the MOBO?

"RuffRider" <RuffRider@horsefield.net> wrote in message
news:uhKCoTCMJHA.5692@TK2MSFTNGP04.phx.gbl...
> No new hardware installed.....
> Tested ram and no problem
> Only things changed was Nvidia drivers for Graphics card and motherboard.
>
> "fatsteve" <internet@sky.com> wrote in message
> news:48f817bc$0$10595$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
>> RuffRider wrote:
>>> Problem: Regardless of it being XP Pro or Vista Ultimate I am using at
>>> the time then at anytime in the day I get the dreaded blue screen and
>>> the Driver IRQL not less than equal nonsense.
>>> Exact same bunch of numbers and zeros every time.
>>> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
>>> 0x0000000000000008, 0x0000000000000000
>>> Never changes, always the exact same.
>>> Must be something common to XP Pro and Vista to be making it happen....
>>> but what?
>>
>> Test your RAM. On startup hit F9 then TAB to Memory Diagnostic tool. It
>> will take about 5 mins, worth a shot.
>>
>
 
Re: Driver IRQL Not Less an Eaqual!!


How long did you permit the Driver Verifier to run? It could take >>
days to get to the point of re-creating the events leading up to the
BSOD, if even possible. What settings were applied to the verifier? MS
drivers should not be verified - no need. If BSOD is software related,
it must obviously be a kernel mode driver. The driverquery would be
helpful in a search for out-dated drivers.

As I mentioned, I will run the dump(s) and post the results here. It is
your call. Dump files are in \windows\minidump. I would also like the
driverquery text file along with an msinfo32 NFO file (default file
extension). Zip them up and attach to post. Who knows what may be there.

I asked about Vista vs. XP b/c it matters when running SFC. I would
advise doing just that. If Vista, no DVD required whether SP1 or not.
You are Vista SP1 updated... right? XP sfc needs slipstream XP CD.

As for the Driver Verifier - try it again - but using the following
(Vista instructions): Bring up an *Elevated* command prompt -
*START | type cmd.exe | right-click on cmd.exe uptop under programs |
Run as Administrator | type *verifier* & hit enter - the Verifier screen
will appear | do the following:*

Code:
--------------------

1. SELECT 2ND OPTION - CREATE CUSTOM SETTINGS (FOR CODE DEVELOPERS)[/B]
*2. SELECT 2ND OPTION - SELECT INDIVIDUAL SETTINGS FROM A FULL LIST.*
*3. CHECK THE BOXES -*
*• SPECIAL POOL*
*• POOL TRACKING *
*• FORCE IRQL CHECKING*
*4. SELECT LAST OPTION - SELECT DRIVER NAMES FROM A LIST *
*5. CLICK ON THE PROVIDER HEADING - SORTS LIST BY PROVIDER*
*6. CHECK ALL BOXES WHERE MICROSOFT IS NOT THE PROVIDER*
*7. CLICK ON FINISH *
8. RE-BOOT
--------------------

If the Driver Verifier finds a violation, it will BSOD.

For info, some of the more common bugchecks for verifier violations
are:

Code:
--------------------

• 0xa = irql_not_less_or_equal
*• 0x50 = page_fault_in_nonpaged_area *
*• 0xbe = attempted_write_to_readonly_memory *
*• 0xc1 = special_pool_detected_memory_corruption *
*• 0xc4 = driver_verifier_detected_violation *
*• 0xc6 = driver_caught_modifying_freed_pool *
*• 0xc7 = timer_or_dpc_invalid *
• 0xc9 = driver_verifier_iomanager_violation
--------------------

If you would like to see the status of the Driver Verifier, bring up an
elevated command prompt, type verifier - but this time select the last
option on the first screen - "Display information about the currently
verified drivers..". To turn the Driver Verifier off, bring up an
elevated command prompt and type *verifier /reset* then re-boot.

Anything good in the Event Viewer logs (Vista - eventvwr.msc)? Vista
has at least 54 of them. I only look at 2 in XP - the app and sys logs.
What do the events leading up to the BSOD look like? Or do you find an
event recorded similar to ".. the shutdown at 17:49 was unexpected..."?

How is the Device Manager (devmgmt.msc) doing? Problem Reports and
Solutions (wercon.exe) or the Reliability Monitor (perfmon /rel) have
anything to say?

[image:
http://i250.photobucket.com/albums/gg252/jcgriff2/10-19-08a-1-1-1-1.jpg]


Regards. . .

jcgriff2

.


--
jcgriff2
 
Re: Driver IRQL Not Less an Eaqual!!

It's Kaspersky Internet Security causing the problem...........

"jcgriff2" <guest@unknown-email.com> wrote in message
news:dab3ba643575d10beaff4bcadebb236d@nntp-gateway.com...
>
> RuffRider;862729 Wrote:
>> Exact same bunch of numbers and zeros every time.
>> STOP 0x000000D1 0x0000000000000000, 0x0000000000000002,
>> 0x0000000000000008, 0x0000000000000000
>> Never changes, always the exact same.
>>
>
> A 0xd1 bugcheck = DRIVER_IRQL_NOT_LESS_OR_EQUAL and indicates that a
> kernel-mode driver attempted to access a pageable memory address (or a
> bad address) when it should not have (at a process IRQL that was too
> high). A 0xd1 bugcheck is usually caused by drivers using improper
> addresses.
>
> A few things in the posted bugcheck I find interesting. I already
> mentioned what 0xd1 means. The first parm inside the parenthesis is the
> memory address referenced by the object in the 4th parm - so you have an
> object with a memory address of 0x0 referencing a 0x0 - these s/b filled
> with numbers and letters... not zeroes as far as I have ever seen. The
> second parm (0x2) is the IRQL at the time #4 referenced #1, which is
> fine (or at least a valid #). The 3rd parm 0x8 tells us that this is an
> execution routine (0x0 = read; 0x1 = write).
>
> The real interesting item here is that parm #4 = parm #1 and parm #3 is
> 0x8, which typically means that the bugcheck was caused by a driver
> attempting to execute code that was paged out. Possible causes for this
> are:
> - the driver trying to acquire a resource/object lock - keeping its
> siblings out
> - a call was made to a driver that was already unloaded from RAM
> - the pointer is bad
>
> If no driver was named by the BSOD, then run the driver verifier in
> hopes that it will cause a BSOD (like a 0xc4) and flag the offending
> driver. If driver not named on BSOD screen, then maybe something will
> show up in the stack text for all to see. No guarantees, of course.
>
> The 0x0 in parms 1 & 4 are still bothersome.
>
> I suggest you run memtest ISO if you have not already done so (not just
> the Vista memory check).
>
> If you invoke the driver verifier and BSOD occurs, get that dump, zip
> it up and attach - c:\windows\minidump - it may contain the clue needed.
>
> Where does XP Pro fit in here? Is this the same system? Do you have 1
> app in common between the two systems that maybe contains old drivers?
> The loaded driver list in the dbug output may tell us, unless it was
> unloaded at the time of the crash.
>
> You may also want to run driverquery and look over your drivers - Bring
> up an *-elevated -*cmd prompt ("DOS") -
> START | type cmd.exe into the start search box | right-click on cmd.exe
> | select run as administrator - the type or copy/paste the following
> into the DOS screen (to paste into DOS screen, right-click at the top,
> select Edit, select Paste) hit Enter:
>
>
> Code:
> --------------------
>
> *driverquery /v > %temp%\driverquery.txt & start notepad
> %temp%\driverquery.txt*
>
> --------------------
>
>
> A notepad will appear with the driver query report. Watch out for the
> ones marked "disabled" under the column "Start Mode".
>
> Regards. . .
>
> jcgriff2
>
> .
>
>
> --
> jcgriff2
>
 
Back
Top