Check for IRQ conflicts

Thanks Bill,
Plug and play is enabled and although i havent checked
each driver indidually-they are all new components and
the latest and greatest and have all been updated to most
recent versions from suppliers so am 'assuming' that they
are all ok and also that they are p'n'p compatible
because they are new! My windows updates are current also
which makes the problem even more baffling...

>-----Original Message-----
>If you have Plug'n'Play, enabled in your BIOS, then IRQ

Steering should

>handled all that for you. Of course all your devices

have to support p'n'p.

>Also, it will be common, and ok, to see more than one

device sharing the

>same IRQ, when this is in effect.
>
>Have you run MS Windows Update, and installed them? Are

you using XP

>compatible drivers for all your hardware? Are they the

latest, from the

>OEM, rather than what came with them on a CD?
>
>Bill Crocker
>
>
>"Paul" <anonymous@discussions.microsoft.com> wrote in

message

>news:04b001c3a9de$ab806c60$a001280a@phx.gbl...

>> Hi, does anyone know how of any software or application
>> that i can run on my PC to check for IRQ conflicts
>> because my machine is constantly just shutting itself
>> down with spurious errors and given that i built it
>> myself i am suspicious of conflicts.
>> Thanks..

>
>
>.
>

>-----Original Message-----
>Thanks Bill,
>Plug and play is enabled and although i havent checked
>each driver indidually-they are all new components and
>the latest and greatest and have all been updated to most
>recent versions from suppliers so am 'assuming' that they
>are all ok and also that they are p'n'p compatible
>because they are new! My windows updates are current also
>which makes the problem even more baffling...

If you're reasonably certain that it is not a software or
hardware conflict (which you seem to have done your best
to determine) you may want to check your memory modules,
and verify that the BIOS settings for your memory are
correct.

I've seen what you describe happen when a memory module is
faulty, or under/over powered. (Wrong voltage settings in
BIOS.)

The other thing you should consider is heat and if your
motherboard polls the CPU, CPU Fan and/or System fans. One
of these may be malfunctioning, and the BIOS may be
attempting to shut down the PC to try and prevent damage.
This can generate odd errors as the BIOS interrupts
Windows processes to protect the system.

Thanks again-i had suspicions about the temperature the
CPU was getting up to so have, as of yesterday set up a
monitor on the temperature and at least for future
crashes i can check the temp at the time to confirm/rule
this out so we seem to be thinking along the same lines.
Im unable however to check the voltage settings for the
memory although i may have a further snoop around the
BIOS because i could well have overlooked it. Do you by
any chance know the optimum operating temp for a CPU as
mine is working at approx 48 DegC...
Paul

>-----Original Message-----
>

>>-----Original Message-----
>>Thanks Bill,
>>Plug and play is enabled and although i havent checked
>>each driver indidually-they are all new components and
>>the latest and greatest and have all been updated to

most

>>recent versions from suppliers so am 'assuming' that

they

>>are all ok and also that they are p'n'p compatible
>>because they are new! My windows updates are current

also

>>which makes the problem even more baffling...

>
>
>If you're reasonably certain that it is not a software

or

>hardware conflict (which you seem to have done your best
>to determine) you may want to check your memory modules,
>and verify that the BIOS settings for your memory are
>correct.
>
>I've seen what you describe happen when a memory module

is

>faulty, or under/over powered. (Wrong voltage settings

in

>BIOS.)
>
>The other thing you should consider is heat and if your
>motherboard polls the CPU, CPU Fan and/or System fans.

One

>of these may be malfunctioning, and the BIOS may be
>attempting to shut down the PC to try and prevent

damage.

>This can generate odd errors as the BIOS interrupts
>Windows processes to protect the system.
>.
>

48 C is no problem at all.

--
Steve C. Ray
Replace "mail" with "36db"
<anonymous@discussions.microsoft.com> wrote in message
news:0edd01c3a9f5$c4bbf5c0$a301280a@phx.gbl...

> Thanks again-i had suspicions about the temperature the
> CPU was getting up to so have, as of yesterday set up a
> monitor on the temperature and at least for future
> crashes i can check the temp at the time to confirm/rule
> this out so we seem to be thinking along the same lines.
> Im unable however to check the voltage settings for the
> memory although i may have a further snoop around the
> BIOS because i could well have overlooked it. Do you by
> any chance know the optimum operating temp for a CPU as
> mine is working at approx 48 DegC...
> Paul

> >-----Original Message-----
> >

> >>-----Original Message-----
> >>Thanks Bill,
> >>Plug and play is enabled and although i havent checked
> >>each driver indidually-they are all new components and
> >>the latest and greatest and have all been updated to

> most

> >>recent versions from suppliers so am 'assuming' that

> they

> >>are all ok and also that they are p'n'p compatible
> >>because they are new! My windows updates are current

> also

> >>which makes the problem even more baffling...

> >
> >
> >If you're reasonably certain that it is not a software

> or

> >hardware conflict (which you seem to have done your best
> >to determine) you may want to check your memory modules,
> >and verify that the BIOS settings for your memory are
> >correct.
> >
> >I've seen what you describe happen when a memory module

> is

> >faulty, or under/over powered. (Wrong voltage settings

> in

> >BIOS.)
> >
> >The other thing you should consider is heat and if your
> >motherboard polls the CPU, CPU Fan and/or System fans.

> One

> >of these may be malfunctioning, and the BIOS may be
> >attempting to shut down the PC to try and prevent

> damage.

> >This can generate odd errors as the BIOS interrupts
> >Windows processes to protect the system.
> >.
> >