Driver IRQL Not Less an Eaqual!!

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?

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

--
Earle Horton --

"RuffRider" <> wrote in message
news:%...
> 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?

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" <> wrote in message news:%...
> 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?
>

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" <> wrote in message
news:%...
> 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?

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.

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

"fatsteve" <> wrote in message
news:48f817bc$0$10595$...
> 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.
>

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

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

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

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

If no driver was named by the BSOD, then run the driver verifier i
hopes that it will cause a BSOD (like a 0xc4) and flag the offendin
driver. If driver not named on BSOD screen, then maybe something wil
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 jus
the Vista memory check)

If you invoke the driver verifier and BSOD occurs, get that dump, zi
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
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 wa
unloaded at the time of the crash

You may also want to run driverquery and look over your drivers - Brin
up an *-elevated -*cmd prompt ("DOS") -
START | type cmd.exe into the start search box | right-click on cmd.ex
| select run as administrator - the type or copy/paste the followin
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 th
ones marked "disabled" under the column "Start Mode"

Regards. .

jcgriff



--
jcgriff2

Should have shown as Driver IRQL Not Less Or Equal............
"RuffRider" <> wrote in message
news:%...
> 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?
>

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" <> wrote in message
news:uGMr0u$...
> 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" <> wrote in message
> news:%...
>> 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?
>
>

Ran verifier, did not cause a blue screen but did make my soundcard act
up(screeching sound)
"jcgriff2" <> wrote in message
news:...
>
> 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
>