Vista - deciphering bluescreen message - BCCode: d1

I'm suffering blue screens around once a day, and have been now for a
number of weeks. I believe that it is a driver problem, but beyond that
I don't know. If anyone could shed a little more light on the cause of
this, or even the culprit then it would be most appreciated.

Vista Home Premium, with all of the latest patches installed.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: 00000000
BCP2: 00000002
BCP3: 00000001
BCP4: 87E4A8EA
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1


If any further information would help, then please tell me what would
be helpfull.

Many thanks in advance...Freekie


--
freekie
------------------------------------------------------------------------
freekie's Profile: http://forums.techarena.in/members/84082.htm
View this thread: http://forums.techarena.in/vista-help/1145337.htm

http://forums.techarena.in

If I were you I would be more concerned about a failing hard drive than
anything else.
If that is the case, while you still can, backup all your important
documents, images, etc.
Hard drive manufacturers have software on their websites to test the hard
drive.
A failing power supply can cause this although often you see the problem at
boot up.
The Microsoft memory diagnostic is very good for evaluating RAM.

Yes, back up HD.

Then look at drivers.
I had the exact same problem and it turned out to be a driver.
MS did not have an update so I went to the manufacturer's website and found
their latest and downloaded and installed.
Problem went away.

Difficulty is determining what went wrong.
But look in the event log immediately after the bluescreen reboot to look
for critical errors.
I will probably show up there.

Control Panel / Administrative Tools / Event Viewer / Critical or Error
under +Critical or +Error Double-Click on an entry under this to see what is
was.
then double click on the critical or error line to get more details.

You will be amazed at all the problems going on behind the scenes.



"freekie" <freekie.3pejjb@xxxxxx> wrote in message
news:freekie.3pejjb@xxxxxx

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was
too high. The most typical cause is a bad device driver (one that uses improper
addresses). It can also be caused by caused by faulty or mismatched RAM, or a
damaged pagefile.
Also when it happens next time take a note of the mini dump and maybe then we can
find a fix or suggestion for a fix. As it is reight now it could be anything
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"freekie" <freekie.3pejjb@xxxxxx> wrote in message
news:freekie.3pejjb@xxxxxx

Thanks for your replies

pupick / Lorin, I've been caught by hd failure in the past, I keep a
recent ghost image of the OS drive now . All of the data etc is
mirrored for safety. There are no read errors in the event viewer, and
no strange clicking sounds, but I will run a drive test anyway just to
be on the safe side.

The power supply was replaced 2 months ago, as the previous one was too
loud, but I had this problem with the old one too (yes, it has been
happening for that long).

Rick Rogers, there is no stop message, just the usual ‘previous
system shutdown was unexpected’. Thanks for the offer, and a copy
of the minidump file has been sent to you.

Peter Foldes, thanks for the advice, I will try a RAM test.


--
freekie
------------------------------------------------------------------------
freekie's Profile: http://forums.techarena.in/members/84082.htm
View this thread: http://forums.techarena.in/vista-help/1145337.htm

http://forums.techarena.in

freekie

There is a Stop (d1) message. You posted it in your post Bccode D1. And I posted the
problem associated with it

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"freekie" <freekie.3pexfe@xxxxxx> wrote in message
news:freekie.3pexfe@xxxxxx