Jump to content

2 different BLUE SCREEN ERRORS


fireman5214
 Share

Recommended Posts

Hello all, I just had a blue screen error about 10 minutes ago. it was called BAD POOL CALLER and the details on the restart are as follows:

BCP3: 0000000000210010

BCP4: FFFFFA8006A67E00

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\010213-17300-01.dmp

C:\Users\Jason\AppData\Local\Temp\WER-139979-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: c2

BCP1: 0000000000000007

BCP2: 000000000000109B

Link to post
Share on other sites

Possible causes are bad memory, but more frequently a faulty driver, or problematic (often security) software.

The minidump file will usually tell you what process crashed and/or what driver was involved. Even if no particular third party driver is named as the culprit, the processes and drivers involved in the crash will often give a good indication of where the problem lies.

Did you recently install or update a driver or security software?

Removing, reverting to a prior version of, or updating the driver or software in question will often fix the problem; then again, it may simply be a one-off incident, and you could choose to ignore it for a while, and wait for it to reoccur, if it does at all...

Link to post
Share on other sites

well I am not sure what it was, the ONLY thing I downloaded was EASYWEATHER for my weather station that reports to Wunderground.com for the National Weather Service, Community Collaborative Rain Hail Snow Network as well. This was the first time I had this problem in a while. I did have a comp overheating prob and we cleaned that out with the compressed air and it worked fine, this happened from being on a video call, and on facebook at the same time. Also when i had the blue screen error, i was clicking to reply to a comment on a picture on facebook. Here is a thread I had with a blue screen error earlier. Do you know if its the same thing? It begins on post 19 (page 1) of this thread: http://forums.malwarebytes.org/index.php?showtopic=112374&st=0

Link to post
Share on other sites

oh ok thanks tony. I have been busy so I have not had time ot get on here, taking down 40,000+ christmas lights is time consuming.

Link to post
Share on other sites

ok I actually just (literlaly jsut restarted from it) got another blue screen error PFN_LIST_CORRUPT and here are the details for it:

oblem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: 4e

BCP1: 0000000000000007

BCP2: 000000000013366F

BCP3: 0000000000000001

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\011113-17846-01.dmp

C:\Users\Jason\AppData\Local\Temp\WER-146796-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Link to post
Share on other sites

Error #1 Jan 2nd 2013 Hello all, I just had a blue screen error ... it was called BAD POOL CALLER and the details on the restart are as follows:

BCP3: 0000000000210010

BCP4: FFFFFA8006A67E00

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\010213-17300-01.dmp

C:\Users\Jason\AppData\Local\Temp\WER-139979-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: c2

BCP1: 0000000000000007

BCP2: 000000000000109B

****and then i had this reply: Possible causes are bad memory, but more frequently a faulty driver, or problematic (often security) software.

The minidump file will usually tell you what process crashed and/or what driver was involved. Even if no particular third party driver is named as the culprit, the processes and drivers involved in the crash will often give a good indication of where the problem lies.

Did you recently install or update a driver or security software?

Removing, reverting to a prior version of, or updating the driver or software in question will often fix the problem; then again, it may simply be a one-off incident, and you could choose to ignore it for a while, and wait for it to reoccur, if it does at all...

*****then I had a 2nd error on 1-11-13 another blue screen error PFN_LIST_CORRUPT and here are the details for it:

oblem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: 4e

BCP1: 0000000000000007

BCP2: 000000000013366F

BCP3: 0000000000000001

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\011113-17846-01.dmp

C:\Users\Jason\AppData\Local\Temp\WER-146796-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

(any help is appreciated)

Link to post
Share on other sites

Is this the same Dell system that had the overheating issue ?

ref http://forums.malwar...howtopic=119884

yes it is but that has since been fixed taking it apart and cleaning it like mrcharlie instructed me to do via PM. I had the blue screen errors since about June 2012 though.
Link to post
Share on other sites

<kibbitz & information only>

To me, you did so -much- editing in your posts, one cannot "see" the actual STOP code.

See this next image as a "sample" of the important information that needs your posting here or for your follow-up.

See the 1st 2 lines. That information is just what you need to post -----clearly & without editing or formatting.

The STOP + 0x----------- and any of the other items following in the first 2 lines.

To me, it appeared you posted all other stuff, plus put in editing, but you left out the real STOP code

Cc750081.bsoda_big%28l=en-us%29.gif

But beyond this, from your posts of last year, I was convinced your hardware issue had to be fixed, and then, thereafter, a likely wipe / deletion of your old Windows partition / and then a clean install of Windows and then all your application programs.

So do be aware, I will not be monitoring this thread. I am no longer watching this.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.