Steve--
I meant to include an explanation of the IRQL BSOD, but you will see it
won't help you fix anything, and it can represent a broad range of HDW or
Software, or even both problems:
That stop error, like many of them, is rather general and can be caused by a
number of situations. It can be from a software or hdw incompatiblity
problem.
You'll love this--It's generated when a kernel mode process or driver
attempts to access a memory location at an interrupt request level (IRQL)
that is to high or tries to access a memory location for which it doesn't
have permission.
Here's the thing though that can be practical for you. ***You can use the
stop error (blue screen message) often to determine which driver is
offending if it is a driver problem.
Remember, because people often forget or don't realize, software has drivers
as well as hdw, and sometimes several drivers are installed for a software
program. Put "driververifier" (lose quotes) in your run box and you'll get
that idea.
Good luck,
CH
"SteveC" <sconklan.nospam.yahoo.com> wrote in message
news:F3C843A0-0349-44B1-9480-...
When I get the BSOD and the IRQ does not equal or does something less than
garbage, it is when the computer is churning in the background. I have
turned off Disk defrag and antivirus and spyware checks, etc. Could someone
direct me to what else to turn off so this churning that starts every day
around noon can be stopped. I don't have any spyware or virus on my PC.
|