Vista - BSOD-IRQL--Stop Error

Can some one please help me with the below Stop Error. I get a variation of
it at least once a day..... This is todays version....

PLEASE HELP!!!!


Product
Windows

Problem
Shut down unexpectedly

Date
1/5/2008 7:05 PM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini010508-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: a
BCP1: 00000008
BCP2: 0000001B
BCP3: 00000000
BCP4: 81CB0FEF
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: c22e9f34-8cb7-4b8b-a569-3e2bc5e63842

--
Thanks for your time,
Webangel

Hi,

Incompatible hardware, incorrect BIOS settings, faulty memory, bad drivers
are all possible causes of this type of error. This article was written for
XP, but it's basically the same with Vista:
http://support.microsoft.com/kb/314063

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Webangel" <Webangel@xxxxxx> wrote in message
news:6E9073BA-4FD4-478D-A2DE-156FFDCEF4C4@xxxxxx

Forgive me - why not tell me something on your computer is not right....
Well doh. I meant specifically what does the below error mean. And how to
fix it....

This is a new computer. All the Hardware is not reporting any problems. I
have not changed the BIOS. The Computer is brand new nothing has changed
with the memory. However I do belive it to be a driver issue somewhere???

Since I have seen at least 108 BSOD post here I would suspect the problem is
more with Windows Vista in General then a driver issue. Sounds to me Like
Microsoft release Vista before it was ready for prime time......

Please can someone please tell me specifically what the error detailed below
is other then have you tried this or done this kind of thing. I can do that
just fine on my own. I need to know what the actual error is?????????????

Again thanks to all who respond.
--
Thanks for your time,
Webangel


"Rick Rogers" wrote:

Rick Rogers is a very knowledgeable and helpful person here.
What he has said is correct; it can be a variety of reasons.

Your attitude is now to blame vista, and demand an exact answer.
People here do not get paid to help you!
It is free advice newsgroup.

It is under Warranty; take it back to whoever you bought it off, and annoy
them!

"Webangel" wrote:

The error you quote does not have a single solution.
It could be any one of many things, or a combination of things.
Your computers manufacturer (or their website FAQ) is a good place to start
on a brand new machine.
They know your specific machine and the factory installed hardware/software
better than anyone here.
Since it is brand new, call the manufacturer, it should be under warranty.
Anyone who answers questions here is a volunteer. No one gets paid for the
time they spend researching and answering questions in this group.
There are many experts here, but having an attitude will not help get a
solution.

"Webangel" <Webangel@xxxxxx> wrote in message
news:9CAD93A0-26B9-4867-8162-B2027D9DFB29@xxxxxx

Hi,

I can't give you a specific reason as there are several possible reasons it
is happening, most of which are covered in that link. If the system is new,
use your warranty as there is a chance the hardware is faulty, this is not
uncommon in new machines. Don't waste your time trying to fix something that
may be out of your depth. Troubleshooting that error could easily take hours
to isolate. Think of it this way: If you tell the mechanic that your new
car's check engine light comes on and ask him to tell you over the phone why
and how to fix it, do you think he's going to be able to answer you with
anything useful? It could be something as simple as a loose gas cap, it
could also be an internal engine component failing, but it's impossible to
guess which based on a light coming on.

For what it's worth, the fault isn't the operating system (Vista). It is
only reporting that there is a problem with the hardware or the driver files
supporting the hardware. The dump file (Mini010508-01.dmp) being created may
contain a clue, feel free to send it to me at rick@xxxxxx, using a subject
line of 'per req'. I'll see if it contains anything pertinant.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Webangel" <Webangel@xxxxxx> wrote in message
news:9CAD93A0-26B9-4867-8162-B2027D9DFB29@xxxxxx

In article <9CAD93A0-26B9-4867-8162-B2027D9DFB29@xxxxxx>,
Webangel <Webangel@xxxxxx> wrote:Ok, if it worked before and doesn't work now something changed.
If it's a pretty clean box (not lots of software etc installed) just reinstall
Windows and start from a known good point. If you can't do that then
you'll need to use trial and error. A common place to find the source of
this kind of nonsense (and it's nonsense because there's no reason windows
can't output a useful error - fault in vga subsystem for instance - or even
a stack trace instead sorry gotta go...) anyway a common place to find the
source of this is video drivers. So start there, by updating those. Then
try resinatlling an older version...

Good luck.

In article <ez1DzlFUIHA.4656@xxxxxx>,
Rick Rogers <rick@xxxxxx> wrote:Yes it is. Why can't it output "Fatal error in driver foo"?
Or even "Stack Trace Follows" Or how about ABEND DFH70000I ???

> Why can't it output "Fatal error in driver foo"? Or even "Stack TraceWhat do you think is in the dump file?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"the wharf rat" <wrat@xxxxxx> wrote in message
news:flr9rm$6al$1@xxxxxx

In article <#dXdsSKUIHA.6060@xxxxxx>,
Rick Rogers <rick@xxxxxx> wrote:Well, I think NOTHING is in it unless you've configured memory
dumps appropriately for your system. And then it's some kind of un-
documented binary format so you need to get dumpchk to read it. It might
as well be Ancient Egyptian as far as an ordinary home user is concerned.
Anyway, all dumpchk gives you that's at all useful is the exception
code and the address. To make any real progress you need to install
the whole nine yards, symbol kit and everything.

You could look ABENDs up in the Big Green Book. Heck, even a
Java stack dump has the names of the offending objects. But Microsoft?

My favorite example of a standard Microsoft error message is

Your backup fails. The console displays

"Backup has failed. Consult the system event log for more
information" (Not an exact quote...)

And what's in the event log? "Backup has failed. Examine the
backup console for more information."

I once found the night operator unconcious on the floor of the
machine room. When we revived him all he could say was "Please see
the event log click. Please see the backup console click. Please..."