Vista - BlueScreen Error

Hi there,

I have HP dv2000. My OS is Window vista home premium 32bit. Every now and then I get Bluescreen error followed by restart of my laptop.
Here's the error detail

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

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 82267018
BCP3: 8C24A7F4
BCP4: 00000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini052709-01.dmp
C:\Users\Shalini M\AppData\Local\Temp\WER-57689-0.sysdata.xml
C:\Users\Shalini M\AppData\Local\Temp\WER5550.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

Please HELP!!!!

Thanks,

If you zip up and upload that file with a DMP extension I highlighted above, it may be possible for someone here to help you work out why the machine is crashing. It's a "minidump" which contains code-level information about what was happening at the time of the crash.

To zip it up, you'll have to first copy it elsewhere (and then zip up the copy) as the \windows\minidump folder is security-protected.

Hi,

I have followed your direction and attached the file. Please let me know if you need any other info. Thankyou so much for your prompt response.

Thanks,

Your machine crashed while attempting to open a registry key and check its auditing settings (whether the act of accessing the key needed to be audited according to current policy).

It's not immediately clear what wrote the bad memory that caused the crash, but it will very probably fall into one of two categories:

1) Malfunctioning hardware. This includes the effects of overclocking or inadequate cooling. If the crashes are frequent and "all over the place" in terms of their details (the bugcheck types and parameters), that generally makes a hardware problem more likely.

2) One or more old and buggy drivers. What stands out for me is the considerable age of some of the drivers you've got on that machine, including the absolutely ancient (2007) builds of your anti-virus. Those should be updated as a matter of priority because they've got the potential to cause this crash and other problems too. I'd suggest you start with the eldest ones - update what you can and remove whatever you don't need:

start end module name
805a2000 805e0000 HSXHWAZL Thu Jun 21 04:28:32 2007 (467971D0)
81164000 8116c000 xaudio Wed Jul 11 07:27:55 2007 (4693F9DB)
8116c000 81172f60 mfebopk Fri Aug 17 01:55:06 2007 (46C4735A)
81173000 81184b80 mfeavfk Fri Aug 17 01:54:26 2007 (46C47332)
81187000 8118f3e0 mfesmfk Tue Jul 17 03:47:52 2007 (469BAF48)
8273c000 82744de0 PxHelp20 Thu Jun 21 08:26:00 2007 (4679A978)
8a1b0000 8a1e3000 CHDRT32 Wed Mar 05 05:31:57 2008 (47CD959D)
8dcf0000 8dcf1c00 HpqRemHid Thu Jul 12 01:30:21 2007 (4694F78D)
8dd12000 8dd58000 yk60x86 Tue Jul 31 20:11:26 2007 (46AF0ACE)
8de0c000 8e4e9000 igdkmd32 Sat Apr 19 11:16:23 2008 (480947E7)
8e801000 8ea29000 NETw4v32 Thu Jun 21 21:51:25 2007 (467A663D)
8ea61000 8ea72000 rimmptsk Wed Aug 08 21:42:07 2007 (46B9AC0F)
8ea72000 8ea86000 rimsptsk Mon Jul 30 11:42:56 2007 (46AD4220)
8ea86000 8ead8000 rixdptsk Mon Jul 30 12:54:01 2007 (46AD52C9)
8eaef000 8eaf3180 HpqKbFiltr Tue Jun 19 08:12:03 2007 (46770333)
8eaff000 8eb28000 Apfiltr Wed Apr 18 13:03:25 2007 (46258A7D)
8ec03000 8ed06000 HSX_DPV Thu Jun 21 04:29:51 2007 (4679721F)
8ed06000 8edbb000 HSX_CNXT Thu Jun 21 04:28:20 2007 (467971C4)
8ef62000 8ef89000 Mpfp Sat Jul 14 00:21:09 2007 (46978A55)
8f100000 8f12f820 mfehidk Fri Aug 17 01:51:29 2007 (46C47281)

Thankyou so much for your response. I dont know much about computers. Is this something I can resolve on my own or I need to get some professional help to update the drives?

Thanks,

No problem at all.

Don't let the numbers put you off. They're just a side-effect of the way that data is extracted from the minidump which you've uploaded. The key bit of info are the names of the various drivers: HSXHWAZL.sys, xaudio.sys, mfebopk.sys, and so on.

It is quite likely that one of the drivers in that list caused the crash described in the minidump. The ones whose names begin with MFE correspond to your McAfee anti-virus utility. What's strange is that all of those drivers are very old versions on your machine - from 2007. By now, there would be many updates for that software so you should use whatever "update" mechanism is built into the McAfee utility, and hence hopefully obtain the latest versions.

NETw4v32 is a driver for your (wireless) network interface card (NIC), and it's old too so it should be updated.

Some of the names of other drivers in that list don't mean much to me (HSX...), so you may wish to do some web searches on those names to first work out how they got onto your machine - what do they do - and hence whether you need them or whether they can be removed.

If you take the machine to a shop with these symptoms, they will most likely just reinstall the operating system from scratch. It may fix the issue, but unless you're a technophobe you may wish to do a bit of updating yourself first. My gut feeling is that a newer (2009) version of the McAfee drivers will solve that particular crash.

Hi,

Thanks. After reading your explaination, everything makes sense . I have McAfee through comcast. I tried running updates on McAfee but there is no update available. May be i should call comcast. I found out hsxhwazl.sys is a Conexent file (dont know what it means) for 56k modem. So may be its my comcast modem !!! So what I am understanding is my McAfee, modem and wireless , all drives are old and need to be updated. May be its a silly question but can I go online and update modem and wireless drive????

Thanks for all ur help.....

The precise spot where this crash occurred - while accessing a registry key - makes it more likely that the anti-virus is somehow involved, and it lessens the likelihood that the other drivers (network card, audio...) are somehow part of the problem. Hence, while it's a good idea to always run the latest drivers for all hardware devices, I'd suggest you prioritise the McAfee update.

While I don't currently run any machines with McAfee on them, I'd be amazed if their latest drivers were indeed from 2007. I don't know why it's telling you there are no updates, but perhaps that's a specialised version of the McAfee package that was somehow co-branded with comcast, or perhaps your subscription has expired and they're not letting you download any newer updates. Whatever the reason, you'd want to contact McAfee and clarify your status. Even if it wasn't for this crashing issue, having a 2007 version of the AV scan engine may leave you open to internet nasties.