Hi,I have a relatively new computer which has started shutting down spontaneously and then warning on start-up that it has just recovered from a serious error, and giving this error code:BCCode : ea BCP1: 8a6ba9a0 BCP2 : 8b286840 BCP3 : 8ae975a0BCP4 : 00000001 OSVer : 5_1_2600 SP : 3_0 Product : 768_1Is there any way of discovering, or anyone who can tell me, what this error code relates to, so I rectify it? Which driver / application etc needs removing / re-installing / etc..?Thanks in advance,Joe

Hi Joe,· Did you make any software or hardware changes on the machine prior to this issue?· What is the make and model of your machine?· Does the computer shut down while using any particular application?In order to diagnose the issue, let’s follow these methods.Method 1If you have any unnecessary external devices connected to the machine, unplug them & check if the issue persists.Method 2You may boot the computer into ‘safemode’ and check if the issue persists. It will start Windows XP with a limited set of files and drivers. Startup programs do not run in safe mode, and only the basic drivers needed to start Windows are installed, follow the steps to boot the computer in safe mode:a. Restart the computer.b. Start tapping F8 key.c. You will get advanced boot option window.d. Select the option “Safe mode”.For more information, refer this link:A description of the Safe Mode Boot options in Windows XPHope the information helps. Please post back and let us know.RegardsDebleena SMicrosoft Answers Support EngineerVisit our Microsoft Answers Feedback Forum and let us know what you think.

Thanks for the response! I'll give that a try and report back.Thanks again,Joe

Hi Joe,Please take your time & try the steps suggested.Post back the status of the issue, we will be happy to hear back from you.RegardsDebleena SMicrosoft Answers Support EngineerVisit our Microsoft Answers Feedback Forum and let us know what you think.

Hi,We (it's actually my Mother's computer) have started trying to narrow down whether the problem is caused by any of the peripherals, as you suggested. She's unplugged everything except the mouse, keyboard and monitor, and it hasn't happened since. It's tricky, as I'm sure you can imagine, because it didn't happen every day anyway, but she's now going to add peripherals back until she can identify which one it is.FYI: As for the the make and model, the computer is custom made by World Of Computers in Cambridge, UK. The processor is an Intel Core2Duo 8500, and it has 4GB of RAM, running XP Home.The problem doesn't exhibit itself particularly in any application and it has happened consistently since the computer was built.Thanks again for the help. We'll let you know our findings!Thanks,Joe

Hi Joe,You may connect hardware devices one at a time & run the machine for one or two days & check if the issue comes back.Hope the information helps.RegardsDebleena SMicrosoft Answers Support EngineerVisit our Microsoft Answers Feedback Forum and let us know what you think.

Hi there,As an update, the problem hasn't occurred since we unplugged the peripherals. The only items remaining to be plugged back in are a scanner and some speakers.What should we do when we've narrowed down exactly which peripheral is causing the problem. Is this likely to be a driver issue - should I try finding the latest drivers and re-installing?Thanks again for your help with this,Joe

JoeWhat is the make and model of the scanner?Have you looked at the error reports in the System log in Event Viewer? These often give further clues.You can access Event Viewer by selecting Start, Control Panel, Administrative Tools, and Event Viewer. When researching the meaning of the error, information regarding Event ID, Source and Description are important. A tip for posting copies of Error Reports! Run Event Viewer and double click on the error you want to copy. In the next window is a button resembling two pages. Click the button and close Event Viewer. Now start your message and do a paste into the body of the message. Make sure this is the first paste after exiting from Event Viewer.Are there any yellow question marks in Device Manager? Right click on the My Computer icon on your Desktop and select Properties, Hardware, Device Manager. If yes what is the Device Error code?Hope this helps, Gerry Cornell

I would recommend you find out what is causing the BSOD and fix it.I don't go for trail and error, I would rather go right in for the kill! You can waste a lot of time trying things.Here is how to get started:Please provide additional information about your system:What is your system make and model?What is your XP Version and Service Pack?Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.Click Start, Run and in the box enter:msinfo32Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.This will minimize back and forth Q&A and eliminate guesswork. The next time your system crashes, provide more information about what you see.Here is a BSOD example showing information you need to provide:http://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpgSend the information pointed to with the red arrows (3-4 lines total). Send the entire *** STOP message line since there are clues in the 4 parameters.If there is a file name listed under the STOP message, be sure to include that information too.Skip the boring text unless it looks important to you. We know what a BSOD looks like, we need to know what your BSOD looks like.You can get information from any new crashes and even your old crashes and perhaps get some actual clues.Download BlueScreenView from here:http://www.nirsoft.net/utils/blue_screen_view.htmlUnzip and run it (BSV installs nothing) and let it finish scanning all your crash dump files. If you double click on of the dumps, you will get some information about it (including the Caused By Driver field) and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same (start with that driver).Select (highlight) one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files. Try to select just the most recent ones that relate to your issue (maybe five or so dump files to get started).Click File, Save Selected Items and save the information from the dumps to a text file on your desktop called BSOD.txt. Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.Here is an example of the BSV report from a single BSOD that I initiated on purpose that shows the cause of the crash as the i8042prt.sys driver belonging to Microsoft Corporation:==================================================Dump File : Mini062110-01.dmpCrash Time : 6/21/2010 11:51:31 AMBug Check String : MANUALLY_INITIATED_CRASHBug Check Code : 0x000000e2Parameter 1 : 0x00000000Parameter 2 : 0x00000000Parameter 3 : 0x00000000Parameter 4 : 0x00000000Caused By Driver : i8042prt.sysCaused By Address : i8042prt.sys+27fbFile Description : i8042 Port DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2108)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\minidump\Mini062110-01.dmp==================================================Send the information from the last 5 memory dumps. Do, or do not. There is no try.Somebody please tell me how to prepare figgy pudding as these children keep saying they won't go until they get some.I decided to save up points for a new puppy instead of a pony!

Hi,Thanks for the responses. Apologies for the delay - as I say, it's actually my Mother's computer, so I can only investigate further when I'm round hers..!So the crash did happen again before we plugged the other peripherals back in, so if it is related to peripherals then it has to be one of the following: monitor (CTX205A), keyboard (Standard Microsoft Natural Ps/2), mouse (Microsoft Basic optical mouse), speakers (Sony SRS-PC40). I guess we'll keep trying to narrow it down in case it is peripheral-related.Gerry: Thanks for the advice! No yellow question marks in Device Manager. The EventViewer does indeed show up the system crashes. I think the information supplied is just a duplicate of the information I've included below.Jose: Again, thanks for the advice!The XP Version is XP Home Edition 2002 SP3.The make and model is a tricky one - it was constructed by a local retail outlet called World of Computers - so I'm not really sure what else to say on that.Here's the msinfo32 information:OS Name Microsoft Windows XP Home EditionVersion 5.1.2600 Service Pack 3 Build 2600OS Manufacturer Microsoft CorporationSystem Name WORLD-3267DB255System Manufacturer INTEL_System Model ECG3510MSystem Type X86-based PCProcessor x86 Family 6 Model 23 Stepping 10 GenuineIntel ~3148 MhzBIOS Version/Date Intel Corp. ECG3510M.86A.0112.2009.0203.1136, 03/02/2009SMBIOS Version 2.4Windows Directory C:\WINDOWSSystem Directory C:\WINDOWS\system32Boot Device \Device\HarddiskVolume1Locale United KingdomHardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"User Name WORLD-3267DB255\WocUserTime Zone GMT Standard TimeTotal Physical Memory 4,096.00 MBAvailable Physical Memory 2.42 GBTotal Virtual Memory 2.00 GBAvailable Virtual Memory 1.96 GBPage File Space 3.74 GBPage File C:\pagefile.sysWe haven't been seeing a BSOD as such. It just shuts down spontaneously and then restarts and reports that it has recovered from a serious error.I've had a look at the minidumps, as suggested, and they seem to suggest that there is a problem with the Intel graphics driver, so I've updated to the latest relevant driver via the Intel website, and we'll see if that helps.I've also included the last 5 minidump reports below, as suggested (although it's clear from the minidumps that some of the crashes aren't writing out dumps at all):Thanks for all the help. Let me know if you have any other thoughts!Joe==================================================Dump File : Mini122810-01.dmpCrash Time : 28/12/2010 15:14:29Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0x80000004Parameter 2 : 0x806ecae1Parameter 3 : 0xa6d05d34Parameter 4 : 0x00000000Caused By Driver : hal.dllCaused By Address : hal.dll+8ae1File Description : Hardware Abstraction Layer DLLProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2111)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini122810-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 90,112====================================================================================================Dump File : Mini122910-01.dmpCrash Time : 28/12/2010 15:13:40Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVERBug Check Code : 0x000000eaParameter 1 : 0x8a0fd428Parameter 2 : 0x8b29b6a8Parameter 3 : 0x8ae37f08Parameter 4 : 0x00000001Caused By Driver : igxpdv32.DLLCaused By Address : igxpdv32.DLL+211ccFile Description : Component GHAL DriverProduct Name : Intel Graphics Accelerator Drivers for Windows NT(R)Company : Intel CorporationFile Version : 6.14.10.5218Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini122910-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 65,536====================================================================================================Dump File : Mini120810-01.dmpCrash Time : 08/12/2010 20:44:29Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0x80000004Parameter 2 : 0x806ecae1Parameter 3 : 0xa87fcfc8Parameter 4 : 0x00000000Caused By Driver : hal.dllCaused By Address : hal.dll+8ae1File Description : Hardware Abstraction Layer DLLProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2111)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini120810-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 90,112====================================================================================================Dump File : Mini120910-01.dmpCrash Time : 08/12/2010 20:43:51Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVERBug Check Code : 0x000000eaParameter 1 : 0x8a4a2020Parameter 2 : 0x8b291f60Parameter 3 : 0x8b23a0d0Parameter 4 : 0x00000001Caused By Driver : igxpdv32.DLLCaused By Address : igxpdv32.DLL+211ccFile Description : Component GHAL DriverProduct Name : Intel Graphics Accelerator Drivers for Windows NT(R)Company : Intel CorporationFile Version : 6.14.10.5218Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini120910-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 65,536====================================================================================================Dump File : Mini120410-01.dmpCrash Time : 04/12/2010 17:30:57Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0x80000004Parameter 2 : 0x806ecae1Parameter 3 : 0xa788c310Parameter 4 : 0x00000000Caused By Driver : hal.dllCaused By Address : hal.dll+8ae1File Description : Hardware Abstraction Layer DLLProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2111)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini120410-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 90,112====================================================================================================Dump File : Mini120410-02.dmpCrash Time : 04/12/2010 17:30:26Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVERBug Check Code : 0x000000eaParameter 1 : 0x8a4d3c78Parameter 2 : 0x8b2b3bf0Parameter 3 : 0x8af2e960Parameter 4 : 0x00000001Caused By Driver : igxpdv32.DLLCaused By Address : igxpdv32.DLL+211ccFile Description : Component GHAL DriverProduct Name : Intel Graphics Accelerator Drivers for Windows NT(R)Company : Intel CorporationFile Version : 6.14.10.5218Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini120410-02.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 65,536====================================================================================================Dump File : Mini112410-01.dmpCrash Time : 24/11/2010 21:28:10Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0x80000004Parameter 2 : 0x806ecae1Parameter 3 : 0xa7ece540Parameter 4 : 0x00000000Caused By Driver : hal.dllCaused By Address : hal.dll+8ae1File Description : Hardware Abstraction Layer DLLProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2111)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini112410-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 90,112====================================================================================================Dump File : Mini112510-01.dmpCrash Time : 24/11/2010 21:27:32Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVERBug Check Code : 0x000000eaParameter 1 : 0x8a6ba9a0Parameter 2 : 0x8b286840Parameter 3 : 0x8ae975a0Parameter 4 : 0x00000001Caused By Driver : igxpdv32.DLLCaused By Address : igxpdv32.DLL+211ccFile Description : Component GHAL DriverProduct Name : Intel Graphics Accelerator Drivers for Windows NT(R)Company : Intel CorporationFile Version : 6.14.10.5218Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini112510-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 65,536====================================================================================================Dump File : Mini111010-01.dmpCrash Time : 10/11/2010 16:24:21Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLEDBug Check Code : 0x1000008eParameter 1 : 0x80000004Parameter 2 : 0x806ecae1Parameter 3 : 0xa736eb68Parameter 4 : 0x00000000Caused By Driver : hal.dllCaused By Address : hal.dll+8ae1File Description : Hardware Abstraction Layer DLLProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2111)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini111010-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 90,112====================================================================================================Dump File : Mini111110-01.dmpCrash Time : 10/11/2010 16:23:39Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVERBug Check Code : 0x000000eaParameter 1 : 0x8992ad68Parameter 2 : 0x8abb4b08Parameter 3 : 0x8b1c3a28Parameter 4 : 0x00000001Caused By Driver : igxpdv32.DLLCaused By Address : igxpdv32.DLL+211ccFile Description : Component GHAL DriverProduct Name : Intel Graphics Accelerator Drivers for Windows NT(R)Company : Intel CorporationFile Version : 6.14.10.5218Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\Minidump\Mini111110-01.dmpProcessors Count : 2Major Version : 15Minor Version : 2600Dump File Size : 65,536==================================================

That sounds like a good plan.In spite of the fact that BSV sometimes implicates critical XP system files (like hal.dll), I always doubt they are the real cause and I had some notes about that but can't find them right now. You can get a little deeper in the BSV analysis bottom screen or use the Microsoft tools if needed (too much trouble when it clearly says Intel).It sounds like you are on the right track and now know how to use BSV to help you figure out the real cause of your crashes instead of guessing or trying things.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

JoeWhat graphics card? Checking the manufacturers web site for updated drivers might help. Hope this helps, Gerry Cornell