Just another "Driver_IRQL_Not_Less_Or_Equal" problem
WinXPTalk.com Forum Index WinXPTalk.com
Forums for Windows XP users.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winxptalk.com
Just another "Driver_IRQL_Not_Less_Or_Equal" problem

 
Post new topic   Reply to topic    WinXPTalk.com Forum Index -> Hardware
Author Message
Stefan Fisches
Guest





Posted: Sat Oct 22, 2005 10:44 pm    Post subject: Just another "Driver_IRQL_Not_Less_Or_Equal" problem Reply with quote

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
Back to top
V Green
Guest





Posted: Sun Oct 23, 2005 12:27 am    Post subject: Re: Just another "Driver_IRQL_Not_Less_Or_Equal" problem Reply with quote

"pete" <petefa@f2s.com> wrote in message
news:djeenp$7ga$1@news.freedom2surf.net...
Quote:
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??

Yep, 250W is on the small side for a PSU
these days...best to buy the biggest brand name
PSU you can find.


Quote:




"Stefan Fisches" <sfisches@yahoo.com> wrote in message
news:djdtoh$2s5$1@infosun2.rus.uni-stuttgart.de...
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

Back to top
pete
Guest





Posted: Sun Oct 23, 2005 12:27 am    Post subject: Re: Just another "Driver_IRQL_Not_Less_Or_Equal" problem Reply with quote

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??




"Stefan Fisches" <sfisches@yahoo.com> wrote in message
news:djdtoh$2s5$1@infosun2.rus.uni-stuttgart.de...
Quote:
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
Back to top
Stefan Fisches
Guest





Posted: Mon Oct 24, 2005 12:27 am    Post subject: Re: Just another "Driver_IRQL_Not_Less_Or_Equal" problem Reply with quote

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



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
Back to top
Stefan Fisches
Guest





Posted: Sat Nov 05, 2005 1:27 am    Post subject: Re: Just another "Driver_IRQL_Not_Less_Or_Equal" problem Reply with quote

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 Fisches wrote:
Quote:
pete wrote:

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



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
Back to top
 
Post new topic   Reply to topic    WinXPTalk.com Forum Index -> Hardware All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Office Forums Access Forums Windows Server Exchange Server Help
New Topics Powered by phpBB