Tekforums

Chat => Entertainment & Technology => Topic started by: Bacon on April 11, 2007, 21:11:05 PM

Title: Bad Pool Caller = BSOD
Post by: Bacon on April 11, 2007, 21:11:05 PM
Bought a new computer with a dual core processor, kept having random reboot problems, so reinstalled, played with a shed load of drivers and it seemed to work fine for several days.

Decided to reinstall today, with the drivers i had tested and were working stable and now i keep getting this error, and really cant find any information that strings together in an understandable way from microsoft site, so please help me.
Title: Re:Bad Pool Caller = BSOD
Post by: Beaker on April 11, 2007, 21:13:47 PM
Any further error messages?  I had something similar with some crappy USB drivers a while back.  
Title: Re:Bad Pool Caller = BSOD
Post by: madmax on April 11, 2007, 21:15:26 PM
download memtest and check your ram out
http://www.memtest.org/

if it all comes back green then fair enough, but ive known the cheap ram pc builders sometimes like to use to be flaky.
Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 11, 2007, 21:15:45 PM
Ill attempt to get it to bsod again and post the parameters here.

edit madmax its corsair ram so not so crappy :D
Title: Re:Bad Pool Caller = BSOD
Post by: madmax on April 11, 2007, 21:17:01 PM
lol no worries  :mrgreen:
Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 11, 2007, 21:19:37 PM
Oh i have had this system stable and running for a whole week, running games / videofiles etc with no problems, so i dont believe this is a hardware issue.

Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 11, 2007, 21:21:54 PM
ive got a minidump file and sysdata if someone can help me work out how to read them ? :D
Title: Re:Bad Pool Caller = BSOD
Post by: Eggtastico on April 11, 2007, 21:35:56 PM
get hold of Hirens boot CD & run some tests.
I never f**kabout with new hardware as It can get arsey to get replaced after a short while.
Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 11, 2007, 23:26:58 PM
I remember last week i downloaded an update which caused errors related to my realtek hd sound driver, thus i removed it again and it solved an issue i had before, this week a new update was realeased to fix the issue that update caused.

Ive now removed both of them as i have a feeling its that causing the issue.

Im sat typing this and no crash yet, ill leave the pc on tonight and we will see how it goes.
Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 12, 2007, 09:05:54 AM
Crashed at 7.24am this morning, is totally random..

Source: System Error
Category: 102
Event ID: 1003

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 020a0002, parameter4 88f0e708.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 12, 2007, 17:34:40 PM
did a system restore, installed drivers again, now i get this error

http://support.microsoft.com/kb/925922/en-us

tbh all this started happening after i did windows updates,

windows update this week fixed one last that had issue with realtek hd driver

i think its those 2 updates causing further issues
Title: Re:Bad Pool Caller = BSOD
Post by: Bacon on April 12, 2007, 17:38:48 PM
shucks might have worked out its actually a conflict between windoes and modem driver, lets see how it goes, used windbg and read the minidmp files.