Win2K getting stranger and stranger...

[gillus]

I finally solved the "Maxtor in PIO mode" problem
on my 2K/Via box. It appears that Via 4in1 patch do
not automaticaly install the IDE Bus patch. I installed
it separatly (v3.11b) and my Maxtor is now in UDMA5.

But....

There's another strange issue, and I can't say if it's
related with the previous one. When I remove my secondary
master drive (I use a removing bay), Win2K crashes (BSOD)
with error message :

STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL

If I plug a drive in the bay, everything works fine
and W2K boots normaly. I visited the MS Knowledge base,
but found only one article regarding this issue and it's
not really helping me.

Any suggestion ?

Gillus

 

[lucidguy]

You can try using an OS that never crashes.

I don't know which one that would be. But it's certainly not a Microsoft OS.

 

[gillus]

He he, sure Seems to be a "Lucid" advice

Anyway, Win2K is by far the most stable MS operating
system ever ; or the least unstable, if you prefer.

Anyone for another suggestion ?

Gillus

 

[Psychoholic]

<< You can try using an OS that never crashes.

I don't know which one that would be. But it's certainly not a Microsoft OS. >>


Thank you for calling. Have a nice day.....try not to die!!!

 

[ValkyrieKT7]

that would mean some odd driver conflict. What are your system specs?

 

[Shadow07]

Thanks LUCID-TROLL. We really need to change your name from LUCIDGUY to LUCIDTROLL.

BACK TO THE TOPIC...

What is the entire error message? Also, what SP do you have installed? The cause of the problem is driver related. In most cases it is because the driver tried to access invalid memory which casues the IopLoadUnloadDriver funtion within NTOSKRNL.EXE.

Let me know if you need any further help or questions answered.

 

[HansXP]

<< You can try using an OS that never crashes.

I don't know which one that would be. But it's certainly not a Microsoft OS. >>



Hey Lucid, when was the last time one of us Windows 2000 users came into a Linux thread and said something along the lines of &quot;Linux blows, Windows 2000 would fix your problem&quot;? Hmm...I think the answer is never.

I wonder why?

Maybe it's because we're mature enough to realize that there are different OSes for different people.
Maybe it's because we don't like to start flame wars.
Maybe it's because we have other things to do than sit on our ass all day.

Whatever the reason, I wish you'd grow up or get lost.

 

[rbV5]

<< You can try using an OS that never crashes >>



If my Win2k box crashed in a year as many times as you crap threads in a weekend, I would........forget it, not possible.

 

[Psychoholic]

Okay guys, while we're beating off the troll we need to help the author of the thread since it wasn't started by our resident troll.

gillus
What article did you come across at Microsoft??? Does this page help any???

The message you describe is caused by a hardware conflict or bad driver. The link I gave you may provide some insight. You also may want to check your jumper settings.