- This topic has 8 replies, 4 voices, and was last updated 16 years, 9 months ago by
.
-
Posts
-
Hello,
my NC10 goes to blue death on relatively clean install (original setup with XP Home Edition) with this error – BAD POOL CALLER.
After restart, this message appears.
I have 2 gig ram (checked – they are ok) and the newest BIOS 04CA.
On my NC10 I primarly use Eclipse PDT environment for developing web pages via FTP.This problem occurs once in ten hours in average.
What can be a reason of this BAD POOL CALLER blue death?
Thank you!
Does the “To view technical information about the error report, click here”, show any more details?
The error appears to relate to memory management, so the RAM is the first suspect.
How did you check the RAM? Did you run tests, and if so did you let it run several passes (over at-least a few hours)?
Does the error occur with the original 1GB module which came with it?When the crashes occur is exactly the same error produced each time?
hmmm based on the fact that you’re doing web dev this seems the most likely culprit
Hello Alfihar,
there were no other additional informations when clicked this link.
I checked RAMs with Memtest86+ 2.11 from DOS and let it run to the end (it took about 1,5 hour) with no errors result.
Maybe I can try to take 1GB out and see if problem persists.PC crashed when Eclipse, Wifi, Chrome browser, Miranda IM and maybe XnView were running with minimal CPU load.
Sometimes the system was completely idle only with these applications opened (crashed when I wasn’t working on pc).@PanMan: Thats a rather interesting support article. I wonder what exactly it means by a “Web-based program”.
I guess the question is does the computer crash only when you run a “Web-based program” or does it crash at other times? From the last post it sounds like this is not the case.
@niverin: I can’t see any of those applications being a problem, I’ve run all of them except Chrome without any issues (though I just use Eclipse + Pydev, not PDT).It’s interesting that there was no additional error information, I was hoping for at-least some parameters. Are there any events logged in the Event Viewer that relate to the crashes?
The Event Viewer should be under Administrative Tools in the Control Panel.[quote1231023863=Alfihar]
It’s interesting that there was no additional error information, I was hoping for at-least some parameters. Are there any events logged in the Event Viewer that relate to the crashes?
The Event Viewer should be under Administrative Tools in the Control Panel.
[/quote1231023863]
Hello, I uploaded events logs here
I have found a crash log at date 2009/01/02 15:38:29 (event 1003) but still don’t know what could cause it.Thank you for your help.
Since that Microsoft article said something about limiting the computer to a single processor, that reminded me of something I noticed the other day. In the device manager of my sammy, it shows two entries for the Intel Atom N270. Shouldn’t there only be one? Is it safe if I disable/remove one of those entries?
Just going to take a look at those logs.
[quote1231065231=Nucleon]
Since that Microsoft article said something about limiting the computer to a single processor, that reminded me of something I noticed the other day. In the device manager of my sammy, it shows two entries for the Intel Atom N270. Shouldn’t there only be one? Is it safe if I disable/remove one of those entries?
[/quote1231065231]
The Atom N270 has hyper-threading and so will show as two entries, I would not recommend trying to disable one. If you must, you can go into the BIOS and turn off hyper-threading there. This may result in a bit of a performance drop depending on what you are doing.
- You must be logged in to reply to this topic.