Just another "Driver_IRQL_Not_Less_Or_Equal" problem

  • Thread starter Thread starter Stefan Fisches
  • Start date Start date
S

Stefan Fisches

Hi out there,

I just saw that another guy is posting about this problem right now.
Also found out that Google has some stuff to say about it.
Still I am posting another thread... why?

Well, my problem has to do with my SATA Drive. The bluescreen states
there is something wrong with my viaraid.sys.
Driver problem? Guessed so. What really puzzles me is this: my buddys
harddisk works just fine. It's just that as soon as my own 160 Gig
harddisk is hanging on the SATA Bus that the bluescreen appears during
boot up.
My harddisk works fine on my friends WinXP machine. So, I don't see that
an indiviual part seems to be faulty (neither my harddisk as such, nor
my RAID).

Does anybody know how that comes? I mean, it's just a harddisk, isn't
it? It doesn't have a special driver, or does it?

I didn't install any new drivers recently. What I did to the harddisk is
setting up a new partition. But could that be really responsible for all
that mess?

I updated my RAID drivers and my BIOS, but no succes so far. Luckily
enough my WinXP is resting on a IDE drive :-)

Would be gratefull for any informations.
Best regards,

Stefan
 
It seems that some hard disks take too long to respond to commands from the
Sata controller.
That was the official response I got from Adaptec technical support.
Adaptec sata controllers with Hitachi or Western Digital disks seem to have
the most problems, even with 80Gb drives.
Now after a lot of testing I found that the culprit is the Power supply!!!
Upgrading the power supply, "fixed" this problem. I do not know the
technical details, but this worked for me.
200 to 250watt supplies seem to suffer most, also moving the Sata controller
card away from PCI slots 1 and 2 seems to help.
The raid builds fine and even the xp pro sp0 install works, ( I did have a
problem when trying to install several new xp pro sp2 cds though), it seem
to mess up when booting the pc with the processor runs at 100%.

Not enough power might be the problem??
 
pete said:
It seems that some hard disks take too long to respond to commands from the
Sata controller.
That was the official response I got from Adaptec technical support.
Adaptec sata controllers with Hitachi or Western Digital disks seem to have
the most problems, even with 80Gb drives.
Now after a lot of testing I found that the culprit is the Power supply!!!
Upgrading the power supply, "fixed" this problem. I do not know the
technical details, but this worked for me.
200 to 250watt supplies seem to suffer most, also moving the Sata controller
card away from PCI slots 1 and 2 seems to help.
The raid builds fine and even the xp pro sp0 install works, ( I did have a
problem when trying to install several new xp pro sp2 cds though), it seem
to mess up when booting the pc with the processor runs at 100%.

Not enough power might be the problem??
Click to expand...

Yep, 250W is on the small side for a PSU
these days...best to buy the biggest brand name
PSU you can find.
 
pete said:
It seems that some hard disks take too long to respond to commands from the
Sata controller.
[..]
Not enough power might be the problem??
Click to expand...


Hello Pete,
thanks for your responce. It thought that a very interesting idea. I did
unplug my other devices to make sure that the SATA disk gets enough
power. Unfortunatly it didn't solve the problem. Windows still crashes
with the quoted error massage.
What puzzles me is that everything worked just fine. I did shut down
WindowsXP over night and the next day it won't boot up anymore while my
disk is connected.

Does anybody have another guess what might be wrong, or even better how
to fix the problem?

Thanks for you efforts,

Stefan
 
Hello everybody out there,

I was able to get my drive back in operational mode. One of my NTFS
partitions turned out to be the culprit.
Once I deletet it windows is starting up again.

I didn't think a faulty filesyste could cause such a trouble, after all
windows was booting up from an entirely different harddisk.

Cheers,

Stefan

Stefan said:
pete said:
It seems that some hard disks take too long to respond to commands
from the Sata controller.
[..] Not enough power might be the problem??
Click to expand...


Hello Pete,
thanks for your responce. It thought that a very interesting idea. I did
unplug my other devices to make sure that the SATA disk gets enough
power. Unfortunatly it didn't solve the problem. Windows still crashes
with the quoted error massage.
What puzzles me is that everything worked just fine. I did shut down
WindowsXP over night and the next day it won't boot up anymore while my
disk is connected.

Does anybody have another guess what might be wrong, or even better how
to fix the problem?

Thanks for you efforts,

Stefan
Click to expand...
 
Back
Top