J
JABRO
Hello
About two weeks ago I started getting the BAD_POOL_CALLER blue screen when I
tried to open Adobe Photoshop Album ( but I have not tried all my other
programmes to determine whether this issue is restricted to this programme)
The message is as follows:
“A problem has been detected and Windows has been shut down to prevent
damage to your computer.
BAD_POOL_CALLER
If this is the first time you’ve seen this STOP error screen, restart your
computer. If this screen appears again, follow these steps:…….â€
and then the standard advice which has been repeated in many previous posts
on this topic and so I won’t repeat it here, followed by:
“Technical information:
*** STOP: 0X000000C2 (0X0000009A, 0X00000002, 0X00000040, 0X20434650)
Beginning dump of physical memory
Physical dump of memory complete
Contact your system administrator or technical support group for further
assistance.â€
I have read whatever I can find on the MS site KB’s, newsgroups and
elsewhere about this error and so add the following information:
1 I am running Windows XP Home Edition with SP2 and all upgrades up to date.
2 The only software that was added just before the issue was an office
update, windows update and a Dell support programme. I removed all three
but the issue still exists and have since re-loaded the windows updates.
One driver update from Nvidia a couple of weeks before - I rolled back but
still the issue exists.
3 I ran the MS memory test programme overnight on advanced tests and there
were no errors.
4 I opened the case and re-seated the memory and checked all the cable and
power connections.
5 I ran Verifier.exe and as far as I can tell no issues arose.
6 I have checked EVENTVIEWER and although it records the STOP it contains
only the information in the BSOD and the references in the help screen are
all to KB’s that don’t appear to be relevant to the circumstances I encounter.
7 The only hardware I have fitted recently was an additional Hitachi hard
drive (about two months ago, - so long before this issue arose) but I have
uninstalled and reinstalled the driver. The Hitachi website does not have
specific drivers referring only to standard MS drivers. After this there
has been no change in the status of the issue.
8 In SAFE mode the issue does NOT seem to arise ( about 20 - 25 programme
openings, closes without problem).
9 I used MSCONFIG to progressively bring up services and startup items and I
thought that I had found the problem until I found that on ocassions the
issue will arise after several successful openings of the programme.
Different boots with the same configuration can produce different results,
(ie the blue screen can come on the first attempt at starting the programme,
the second or the sixth, when previous programme openings have been
successful so I realised that the process of selective startup does not help
as I cannot be sure when the issue will arise, although on a normal startup
in normal (not SAFE) mode the issue is almost always at the first attempt to
open the programme.
10 Device Manager shows no driver with any warning etc – all appear to be
working normally, at least as far as device manager goes.
11 I have looked at a number of sites but most simply reference to KB265879
which is principally related to Windows 2000 and contains no references to
any differences in XP. Also to a NON IT professional I find this particular
KB hard to follow in terms of a practical approach in XP to determining which
driver (if it is a driver) is the cause of the issue. It is, to me, unclear
on where and how to use the debugger, if there is one in XP, for example.
So, I have sort of run out of ideas on how to solve this myself. I would
be grateful for any help on this issue and in particular any help or
direction to a site which deals with how to debug using KB 265879 (at a
practical non IT professional level) or alternatively if there are other KB’s
which will help me to understand how to use this one – that would be good too!
Thanks in advance for any help.
About two weeks ago I started getting the BAD_POOL_CALLER blue screen when I
tried to open Adobe Photoshop Album ( but I have not tried all my other
programmes to determine whether this issue is restricted to this programme)
The message is as follows:
“A problem has been detected and Windows has been shut down to prevent
damage to your computer.
BAD_POOL_CALLER
If this is the first time you’ve seen this STOP error screen, restart your
computer. If this screen appears again, follow these steps:…….â€
and then the standard advice which has been repeated in many previous posts
on this topic and so I won’t repeat it here, followed by:
“Technical information:
*** STOP: 0X000000C2 (0X0000009A, 0X00000002, 0X00000040, 0X20434650)
Beginning dump of physical memory
Physical dump of memory complete
Contact your system administrator or technical support group for further
assistance.â€
I have read whatever I can find on the MS site KB’s, newsgroups and
elsewhere about this error and so add the following information:
1 I am running Windows XP Home Edition with SP2 and all upgrades up to date.
2 The only software that was added just before the issue was an office
update, windows update and a Dell support programme. I removed all three
but the issue still exists and have since re-loaded the windows updates.
One driver update from Nvidia a couple of weeks before - I rolled back but
still the issue exists.
3 I ran the MS memory test programme overnight on advanced tests and there
were no errors.
4 I opened the case and re-seated the memory and checked all the cable and
power connections.
5 I ran Verifier.exe and as far as I can tell no issues arose.
6 I have checked EVENTVIEWER and although it records the STOP it contains
only the information in the BSOD and the references in the help screen are
all to KB’s that don’t appear to be relevant to the circumstances I encounter.
7 The only hardware I have fitted recently was an additional Hitachi hard
drive (about two months ago, - so long before this issue arose) but I have
uninstalled and reinstalled the driver. The Hitachi website does not have
specific drivers referring only to standard MS drivers. After this there
has been no change in the status of the issue.
8 In SAFE mode the issue does NOT seem to arise ( about 20 - 25 programme
openings, closes without problem).
9 I used MSCONFIG to progressively bring up services and startup items and I
thought that I had found the problem until I found that on ocassions the
issue will arise after several successful openings of the programme.
Different boots with the same configuration can produce different results,
(ie the blue screen can come on the first attempt at starting the programme,
the second or the sixth, when previous programme openings have been
successful so I realised that the process of selective startup does not help
as I cannot be sure when the issue will arise, although on a normal startup
in normal (not SAFE) mode the issue is almost always at the first attempt to
open the programme.
10 Device Manager shows no driver with any warning etc – all appear to be
working normally, at least as far as device manager goes.
11 I have looked at a number of sites but most simply reference to KB265879
which is principally related to Windows 2000 and contains no references to
any differences in XP. Also to a NON IT professional I find this particular
KB hard to follow in terms of a practical approach in XP to determining which
driver (if it is a driver) is the cause of the issue. It is, to me, unclear
on where and how to use the debugger, if there is one in XP, for example.
So, I have sort of run out of ideas on how to solve this myself. I would
be grateful for any help on this issue and in particular any help or
direction to a site which deals with how to debug using KB 265879 (at a
practical non IT professional level) or alternatively if there are other KB’s
which will help me to understand how to use this one – that would be good too!
Thanks in advance for any help.