Win 10 bad pool caller on boinc suspend/exit

Message boards : Questions and problems : Win 10 bad pool caller on boinc suspend/exit
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77671 - Posted: 29 Apr 2017, 9:40:23 UTC
Last modified: 29 Apr 2017, 9:40:59 UTC

Hi,

I suffer from several BAD POOL CALLER BSOD on win 10 since few months
at the moment I close or suspend boinc.

I use the following project on CPU and GPU (NVIDIA):

einstein.phys.uwm.edu
milkyway.cs.rpi.edu_milkyway
setiathome.berkeley.edu
www.gpugrid.net
www.worldcommunitygrid.org

Running on 3 GPU (GTX 1070/GTX1070/GTX 1060).
My machine is rock stable and only have issue with boinc.

Using latest drivers and so on.

Any clue to solve this ?

I use BOINC 7.6.33
ID: 77671 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 77673 - Posted: 29 Apr 2017, 10:08:22 UTC - in response to Message 77671.  

The BAD POOL CALLER error indicates a memory problem, the 'pool' in the name is called the memory pool.
Having said that, don't immediately think you have bad memory (RAM), because it can be caused by a driver for any part of your hardware that gets stressed out.

The guy on this site explains what the error is and what may cause it, and how to fix it - a long and winding road through unplugging everything possible and starting from scratch, adding one thing at a time and testing. Yes, the easiest way is to just stop BOINC, but that's a work around, not a fix. Your system has a problem getting stressed, else it won't throw an error.

If you find one of the dump files Windows made of this error and put it someplace any of us can check it - with Windbg (Windows debug), we may point out what hardware/driver combo is causing it in detail. These dumps are usually saved in C:\LocalDumps\
ID: 77673 · Report as offensive
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77682 - Posted: 29 Apr 2017, 13:22:36 UTC - in response to Message 77673.  

Looks like to be an Nvidia driver issue:

On Sat 4/29/2017 11:33:48 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x83546)
Bugcheck code: 0xC2 (0x7, 0x4D52564E, 0x5000B, 0xFFFF8B89873EC160)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_274d0ab8ee30c459\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 381.89
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 381.89
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 381.89 , NVIDIA Corporation).
Google query: NVIDIA Corporation BAD_POOL_CALLER
ID: 77682 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 77684 - Posted: 29 Apr 2017, 13:55:25 UTC - in response to Message 77682.  

I'm not an Nvidia user, so I don't know if 381.89 is a stable driver for Windows 10 or not, I'll leave that to the next guru to pass by. Perhaps ask about that on any of the Number Crunching forums of the project forums you're participating in, there you usually have a faster answer than here.

And since you have three Nvidia cards, it may also be that one of them is having a problem.
ID: 77684 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5078
United Kingdom
Message 77685 - Posted: 29 Apr 2017, 16:03:22 UTC - in response to Message 77684.  

I've already called 'possible faulty driver' on 381.89 at GPUGrid (message 47141), but no confirmation or even corroboration yet. But in a previous message (47121) I identified that the user had updated drivers between 'last good task' (an ambiguous driver in the 376 range), and 'first task failure' (apparently under 381.89)
ID: 77685 · Report as offensive
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77727 - Posted: 2 May 2017, 20:31:48 UTC

Got another issue (boinc seems guilty in this case)


On Tue 5/2/2017 10:25:58 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050217-20718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF801C3C75348)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



ID: 77727 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 77729 - Posted: 2 May 2017, 22:58:00 UTC - in response to Message 77727.  

I don't see why that needs to be BOINC that causes the Windows kernel to crash. It may be a process running under BOINC that does it, but without that dump file I think our hands are tied.

You haven't said anything about trying different drivers for your Nvidia GPU.
Microsoft's answers on their forum point to outdated or incompatible videocard drivers for the error application has been blocked from accessing graphics hardware, with people getting rid of the error by downgrading to earlier drivers that do work correctly.
ID: 77729 · Report as offensive
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77762 - Posted: 6 May 2017, 8:24:49 UTC - in response to Message 77729.  

Since I changed from boinc version 7.6.33 to version 7.7.2
and nvidia drivers 381.89 to 382.05 i had no bsod anymore so far.
ID: 77762 · Report as offensive
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77847 - Posted: 10 May 2017, 17:39:26 UTC - in response to Message 77762.  

Still got a bsod actually on suspend.
ID: 77847 · Report as offensive
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77871 - Posted: 12 May 2017, 16:45:31 UTC - in response to Message 77847.  

ID: 77871 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 77872 - Posted: 12 May 2017, 17:45:28 UTC - in response to Message 77871.  

No one can read that error. So if it's the same as before, no need to repost. If it's a new one, please repost.

But let's try something different: 3DMark, download, install, run the Firestrike Test/Demo.
See if it survives that. Any artifcating you see, tell us about it.

You can also install Whocrashed and have it run over your dump files to tell you what crashed your computer.
ID: 77872 · Report as offensive
Profile xixou

Send message
Joined: 28 Dec 15
Posts: 33
Belgium
Message 77877 - Posted: 13 May 2017, 5:44:53 UTC - in response to Message 77872.  
Last modified: 13 May 2017, 5:45:52 UTC

No one can read that error. So if it's the same as before, no need to repost. If it's a new one, please repost.

But let's try something different: 3DMark, download, install, run the Firestrike Test/Demo.
See if it survives that. Any artifcating you see, tell us about it.

You can also install Whocrashed and have it run over your dump files to tell you what crashed your computer.


the report text is already in the picture.
Graphics cards are underclocked (-100 MHz core/gddr) and stable in any benchmark/games.


ID: 77877 · Report as offensive

Message boards : Questions and problems : Win 10 bad pool caller on boinc suspend/exit

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.