Page 1 of 1 |
|
Posted: Wed, 3rd Jan 2007 20:19 Post subject: B.S.O.D - Bad Pool Call |
|
 |
Ive been getting the dreaded BSOD lately, and it usually gives me a message like:
Bad Pool Call and various numbers..
Ive trudged round various forums looking for the cause, but get conflicting information..
So does anyone here know 'Exactly' what causes a 'bad pool call'
thanks for any info
|
|
Back to top |
|
 |
|
Posted: Wed, 3rd Jan 2007 20:24 Post subject: |
|
 |
i have had bsod often when i setup my new pc
i got a bad pool caller and a few other ones.
for me it was related to my system memory.
what i did was set my memory voltage and agp voltage
in the bios to "high" instead of "auto" and the bsod curse left me.
i guess my stuff wasn't gettin enough voltage to be stable.
|
|
Back to top |
|
 |
|
Posted: Wed, 3rd Jan 2007 20:28 Post subject: |
|
 |
with google i find that its mostly a faulty driver.
when do you get the error?
while playing a game? burning a cd?
|
|
Back to top |
|
 |
|
Posted: Wed, 3rd Jan 2007 20:32 Post subject: |
|
 |
that's another cause, bad driver.
make sure you got the most up to date drivers
motherboard drivers, - chipset, lan, audio [if you use onboard audio]
videocard drivers and soundcard drivers.
i used to get the bsod most often after gaming for a while.
|
|
Back to top |
|
 |
|
Posted: Wed, 3rd Jan 2007 21:09 Post subject: |
|
 |
Thanks forthe info so far.. most sites i looked on said it was caused by bad or conflicting drivers.. I just really wanted to know if its hardware related (i hope not cos im skint!)
So is there any good diagnostic progs anyone can recommend? maybe a reg cleaner is needed? although ive tried that
oh and BTW it happens anytime regardless of what im doing on the pc.. its not really that much of a prob because i can go 3-4 days without it happening.. then it pops up.
But would still like to know if its 'fixable' without a re-install or other drastic measures
|
|
Back to top |
|
 |
Rinze
Site Admin
Posts: 2343
|
Posted: Fri, 5th Jan 2007 15:53 Post subject: |
|
 |
Find the driver causing the problem by using microsoft debugging tools (or post the minidump somewhere, probably someone will take a look at it)
|
|
Back to top |
|
 |
|
Posted: Fri, 5th Jan 2007 16:59 Post subject: |
|
 |
You can check if it's a memory (or hardware that cause memery conflit) problem by using memtest86 (http://www.memtest86.com/).
|
|
Back to top |
|
 |
Page 1 of 1 |
All times are GMT + 1 Hour |