How to access the Registry

Do you leave the battery in its bay when you're running on AC power?

How old is the battery?

Tip: Always remember the First Rule of Computers: If it ain't broke, don't fix it!

Note: Please do not edit a post of yours after someone's replied to it *or to a later post of yours*in the thread. (When can subscribe to receive email alerts when there's a new post but not an edited post.) THX

I just closed the lid. It was running on mains power.

It's configured to sleep.

I haven't had a BSOD since, but I've only closed the lid once, and as a test.

I think the answer to the last question is no. I'll try it out a few times as a test, and if I get a BSOD again, I'll edit this post.

I don't think I'm out of the woods. I had another BSD this morning when I opened the lid of my computer. (I saw the words "BAD POOL CALLER".)...

Did you turn off (Start > Shut Down) the computer yesterday or did you just close the lid? Was the computer running on AC power at the time or on battery?

Assuming you just closed the lid, what is closing the lid configured to do? => Turn off the computer; Sleep; Hibernate; or Nothing [PICK ONE]

Have you encountered a BSOD (same or different error) since this morning?

Running on AC power => If you turn off the computer, disconnect it from the power source, wait a few minutes, reconnect to the power and then turn on the computer, does the BSOD persist?

I don't think I'm out of the woods. I had another BSD this morning when I opened the lid of my computer. (I saw the words "BAD POOL CALLER".) After the reboot this was what followed the notice that Windows had recovered from an unexpected shutdown:

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional information about the problem:

BCCode: c2

BCP1: 0000000000000007

BCP2: 000000000000109B

BCP3: 0000000005130210

BCP4: FFFFF8A0156DAE50

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\011916-32479-01.dmp

C:\Users\Dale\AppData\Local\Temp\WER-100215-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

To read the dmp files I appear to need a reader called dmpchk. So I'll try and find this, to find out what's what. In the meantime, however, perhaps you can help with the following. I googled BAD POOL CALLER and I found this:

<<

Hello !

I've got problems with a computer!\[\](http://images.intellitxt.com/ast/adTypes/icon1.png) using Windows 7. The problem is that it prompts error "BAD POOL CALLER". I've dont some research on this and I found out that ".dmp" files are needed in order to resolve the problem. Here are the ".dmp" files:

1. http://speedy.sh/g2EWV/101814-21871-01.dmp
2. http://speedy.sh/UJdhK/101814-21091-01.dmp

>>

That was on a website called Tomshardware, written by someone called Kirev on 18 October 2014.

Assuming this advice is sound, where should these files be placed? In Appdata/Local/Temp? Or in Windows/Minidump?

[No. That was a stupid question. Apologies. I'm leaving it as it is in case you saw it before I edited this post.]

Thanks in advance for any advice, however.

PS In case you're wondering why I didn't let Windows look for a solution. I did. It seemed to be working for a while but then nothing happened. At least, I don't think anything did.

Very good.