AgTalk Home
AgTalk Home
Search Forums | Classifieds (145) | Skins | Language
You are logged in as a guest. ( logon | register )

BAD_POOL_CALLER
View previous thread :: View next thread
   Forums List -> Computer TalkMessage format
 
WYDave
Posted 10/20/2006 08:41 (#53653 - in reply to #52791)
Subject: RE: BAD_POOL_CALLER


Wyoming

You're on the right track.

The error codes issued in the BSOD, coupled with the following reference, will help you narrow it down further:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/devtest_g/hh/DevTest_g/t06_bugs_B0_7a93f797-6ab2-41ff-bbae-20e9e66897d5.xml.asp

 

Personally, from what I've read on the MSFT site, my money would be on a device driver software error. Pulling the memory simply shifted the layout of your Windows kernel memory around a bit and has hidden the error for now. You could detect bad RAM by running any memory tests available in your POST/BIOS, or by downloading any one of the shareware memory tests (especially the bootable RAM tests).

 

Top of the page Bottom of the page


Jump to forum :
Search this forum
Printer friendly version
E-mail a link to this thread

(Delete cookies)