Vista - System automatically restarts itself

I am using core 2due 6300 1.86Ghz, 2.5GB Ram, 250 GB HD Desktop PC. From two days back, may be after installing some updates, my system crashes instantaneously and restarts itself in the middle of the session and shows the following message after reboot:

Problem Signature:
Problem Even Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFFA8005C00000
BCP2: 00000000000000002
BCP3: 00000000000000000
BCP4: 1_0
Product: 768_1

Files the help describe the problem:
C:\Windows\Minidump\Mini031109-02.dmp
C:\Users\Ravishail\AppData\Temp\WER-1849468-0.sysdata.xml
C:\Users\Ravishail\AppData\Temp\WER96E8.temp.version.txt


help me out!

Hi raviknt....


if this is the result of an update you installed a few days ago, then i'd suggest either manually uninstalling the specific updates from the ''control panel'' or running a ''system restore''

roll it back to just before the updates......


hope this helps.....




SK

Zip up and upload that "C:\Windows\Minidump\Mini031109-02.dmp" file here and someone might be able to tell you more about why the box crashed.

thanx skunksmash but I have'nt created any restore points yet...so I guess this option won't do.



thanx H2SO4 but I have deleted this 'C:\windows\minidump\Mini031109-02.dmp' file two or three times but it again and again comes up...I will upload as soon it comes again. also tell me how can I upload the file here?

The BSOD (Blue Screen of Death) shows the following error:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
stop: 0x000000D1
efe5b32c.sys - Address FFFFFA6002CEC3E1
base at FFFFFA6002CDE000 Datestamp 45ddfe89

check your RAM is good mate, in my experience that BSOD has been related to bad RAM in the past.....


personally i hate ''memtest'' i cant trust it, but for a quick test run ORTHOS, set it to.. priority 8 blend & stress CPU & RAM, these settings will show up errors in minutes..


if the stress test fails then you have a bad RAM stick....if it does not fail within 10 mins then you can rule the RAM out as an issue...






SK

Any time that the BSoD screen actually identifies a non-OS driver, you can be sure it's a good idea to remove that driver, or at least update it.

"efe5b32c.sys" <=== problem

Try to first work out what that driver does, then whether you actually need it. If you do, find the latest version and see whether that helps to end the BSoDs.

---------------------------
There's no obvious mention on the web of a "efe5b32c.sys" driver, which is odd and somewhat suspicious. The name is comprised entirely of hex-valid characters, which sometimes suggests an attempt to morph into something that's difficult to search for. I hope it turns out that the driver is legit and that I'm just paranoid

Thanx SK, but when i ran ORTHOS application it showed following error:

The application failed to initialize properly (0xc0000018). what does that mean?

thanx h2so4, but how could possible know which driver is causing the problem?

You already wrote the name of the driver in one of your earlier posts:

"Technical Information:
stop: 0x000000D1
efe5b32c.sys - Address FFFFFA6002CEC3E1
base at FFFFFA6002CDE000 Datestamp 45ddfe89"

That's a straight cut'n'paste from your post. It's telling you that a driver called "efe5b32c.sys" accessed memory that it shouldn't have been touching.

You now need to work out how that driver got onto your machine, in other words, what's it for, whether you actually need it, and if so whether there's a newer version available.

If you just leave it, the same thing might happen again.