Blue screen with error signature message showing BCCode 100000d1 BCP1:EEBFDA6A BCP2:00000002 BCP3:00000000 BCP4: EEBFDA6A

My computer shows a blue screen with error signature message showing BCCode 100000d1 BCP1:EEBFDA6A BCP2:00000002 BCP3:00000000 BCP4: EEBFDA6A OSVer:5_1_2600  SP 2_0 Product 256_1
 
Question Info

Last updated August 7, 2018 Views 8,711 Applies to:

Hi,

  • What were the changes made before the issue occur?
  • How long have you been facing this issue?
  • When you receive this error message?

I would suggest you to run memory diagnostic test and check.

Here is the link:

http://oca.microsoft.com/en/windiag.asp

Microsoft-Forum Moderator

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I doubt a memory test will help you at all (that is not what the error is trying to tell you).

But, if you have some time and want to run a memory test, it will not hurt.  It will not solve your issue though.

There are better ways to troubleshoot your Blue Screen of Death (BSOD).

What follows is a lot to read/do, but you will solve your issue faster if you try to follow the directions exactly.

Here is what I suggest:


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.

Was the issue preceded by a power interruption, aborted restart, or improper shutdown?  (this includes plug pulling, power buttons, removing the battery, etc.)

Does the afflicted system have a working CD/DVD drive?

Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?

Does your system seem to boot okay and then crash or does it not boot at all?

If your system was working okay, what do you think might have changed since the last time it worked properly?

Can you make the system crash any time you want?  For example, would you say that there is any particular system activity that coincides with the crashes (like watching videos, playing games, etc.).


The next time your system crashes, provide more information about what you see.

Here is a BSOD example showing information you need to provide:


Send 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.

Now provide more information about your system and information from the most recent crashes.

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.

For video driver information, expand the Components, click Display, 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.


Download BlueScreenView from here:


Unzip 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).

BlueScreenView tries to locate the right driver or module that caused the blue screen by looking inside the crash stack. However, be aware that the driver detection mechanism is not 100% accurate, and you should also look in the lower pane, that display all drivers/modules found in the stack.

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.dmp
Crash Time        : 6/21/2010 11:51:31 AM
Bug Check String  : MANUALLY_INITIATED_CRASH
Bug Check Code    : 0x000000e2
Parameter 1       : 0x00000000
Parameter 2       : 0x00000000
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : i8042prt.sys
Caused By Address : i8042prt.sys+27fb
File Description  : i8042 Port Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 5.1.2600.5512 (xpsp.080413-2108)
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\WINDOWS\minidump\Mini062110-01.dmp
==================================================

Send the information from the last 5 memory dumps (if you don't have 5 memory dumps yet, send the most recent ones you have).



Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

@bikesk T Microsoft Support Engineer:

Why do you think this issue has anything to do with faulty memory and posting a link to a Microsoft memory tester (is a link required in all MSE replies?)

Please let us know your thoughts on the matter.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.