BSOD - BAD_POOL_CALLER

V

VLindemann

Member
Joined
Jun 29, 2020
Posts
13
Hello i just got my first bsod on this system can anyone help me identify the problem.I've been playing Detroit : Become Human and all of a sudden game froze threw me to dekstop and gave me an application error i said meh i'll launch it again but after i clicked close on application error pop up system froze and bsod popped up and pc restarted itself.
Same cirsumtances happened 3 times in total but only this one turned into bsod situation
The other 2 times were I was playing AC:Origins and Spintires both graphical heavy games.
Any help is appreciated.Crashes happened in multiple nvidia driver versions.
I've installed the latest version of the driver just in case.

I also would like a edit in how long i was playing these games before the crashes happened.
I was 9 hours in Detroit Become Human before BSOD happened.
2.5 hours in AC:Origins before crash happened.
4 hours in Spintires before crash happened.

So i don't think reason is overheating.



· OS - Windows 8.1
· x64 (64-bit)
· OS Version : Full Retail Version
· System Age ; 4 Years MOBO 2 Years
· Windows Age ; 3 Years

· CPU : i5 6600
· Video Card : ASUS DUAL GTX 1060 6GB
· MotherBoard - MSI Z270 Gaming M5
· Power Supply - Thermaltake Smart 650w 80+ Bronze

Things I've done.
1 Hour Furmark Test GPU was 82-83 Degrees at max
4 Heaven Benchmarks all run ok.
Installed latest nvidia driver 451.48
 

Attachments

Last edited:
Let's get a thorough overview of what's installed and present:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
Please uninstall Popcorn Time and run the following fix:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 28-06-2020
Ran by Lindemann (29-06-2020 15:58:35) Run:1
Running from C:\Users\Lindemann\Downloads
Loaded Profiles: Lindemann
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
S4 asComSvc; C:\Program Files (x86)\ASUS\AXSP\1.02.00\atkexComSvc.exe [X]
S4 AsSysCtrlService; C:\Program Files (x86)\ASUS\AsSysCtrlService\1.00.22\AsSysCtrlService.exe [X]
S2 Update service; C:\Program Files (x86)\Popcorn Time\Updater.exe [X]
S3 NTIOLib_1_0_C; \??\D:\NTIOLib_X64.sys [X]
S3 xhunter1; \??\C:\Windows\xhunter1.sys [X]
EmptyTemp:
*****************

Restore point was successfully created.
HKLM\System\CurrentControlSet\Services\asComSvc => removed successfully
asComSvc => service removed successfully
HKLM\System\CurrentControlSet\Services\AsSysCtrlService => removed successfully
AsSysCtrlService => service removed successfully
HKLM\System\CurrentControlSet\Services\Update service => removed successfully
Update service => service removed successfully
HKLM\System\CurrentControlSet\Services\NTIOLib_1_0_C => removed successfully
NTIOLib_1_0_C => service removed successfully
HKLM\System\CurrentControlSet\Services\xhunter1 => removed successfully
xhunter1 => service removed successfully

=========== EmptyTemp: ==========

BITS transfer queue => 8388608 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 34374040 B
Java, Flash, Steam htmlcache => 380408007 B
Windows/system/drivers => 8042966 B
Edge => 0 B
Chrome => 1771425113 B
Firefox => 0 B
Opera => 0 B

Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 58353 B
systemprofile32 => 58481 B
LocalService => 58481 B
NetworkService => 57823 B
Lindemann => 2091549893 B

RecycleBin => 577746 B
EmptyTemp: => 4 GB temporary data Removed.

================================


The system needed a reboot.

==== End of Fixlog 16:01:57 ====
 
I'm grateful that you're helping me with my problem.I appreciate fixes and stuff but i would also like to know the reason of the BSOD is it hardware related or was it some freak accident with the nvidia drivers.BlueScreenView does point to nvldmkm.sys after all.
 
You may also want to update your graphics card driver too, looks like there was a newer version released this month - Download The Latest Official GeForce Drivers

Rich (BB code): 
0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff801`a56d1000 fffff801`a6d46000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Sat May 16 00:44:54 2020 (5EBF2976)
    CheckSum:         0160D0DF
    ImageSize:        01675000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:



Rich (BB code): 
0: kd> !pool ffffc001c0d67010
GetUlongPtrFromAddress: unable to read from fffff802b17762a8
GetUlongPtrFromAddress: unable to read from fffff802b1776520
Pool page ffffc001c0d67010 region is Paged pool
GetUlongFromAddress: unable to read from fffff802b16cdaf8
Unable to get pool big page table. Check for valid symbols.
ffffc001c0d67000 is not valid pool. Checking for freed (or corrupt) pool
Bad allocation size @ffffc001c0d67000, zero is invalid

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval ffffc001c0d67000 for more details.


Pool page [ ffffc001c0d67000 ] is INVALID.

Analyzing linked list...
[ ffffc001c0d67000 ]: invalid block size [ 0x0 ] should be [ 0x21 ]


Scanning for single bit errors...

None found

Code: 
0: kd> [COLOR=rgb(65, 168, 95)]dt _POOL_HEADER ffffc001c0d67000[/COLOR]
nt!_POOL_HEADER
   +0x000 PreviousSize     : 0y00000000 (0)
   +0x000 PoolIndex        : 0y00000000 (0)
   +0x002 BlockSize        : 0y00000000 (0)
   +0x002 PoolType         : 0y00000000 (0)
   +0x000 Ulong1           : 0
   +0x004 PoolTag          : [COLOR=rgb(255, 0, 0)]0x6d4d6956[/COLOR]
   +0x008 ProcessBilled    : (null) 
   +0x008 AllocatorBackTraceIndex : 0
   +0x00a PoolTagHash      : 0

Code: 
0: kd> [COLOR=rgb(65, 168, 95)].formats 0x6d4d6956[/COLOR]
Evaluate expression:
  Hex:     00000000`6d4d6956
  Decimal: 1833789782
  Octal:   0000000000015523264526
  Binary:  00000000 00000000 00000000 00000000 01101101 01001101 01101001 01010110
  Chars:   ....[COLOR=rgb(255, 0, 0)]mMiV[/COLOR]
  Time:    Thu Feb 10 10:03:02 2028
  Float:   low 3.97324e+027 high 0
  Double:  9.06013e-315

Rich (BB code): 
0: kd> !pooltag ViMm
Pooltag ViMm
Description: Video memory manager
Driver!Module: dxgkrnl.sys
 
x BlueRobot said:
You may also want to update your graphics card driver too, looks like there was a newer version released this month - Download The Latest Official GeForce Drivers

Rich (BB code): 
0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff801`a56d1000 fffff801`a6d46000   nvlddmkm T (no symbols)         
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Sat May 16 00:44:54 2020 (5EBF2976)
    CheckSum:         0160D0DF
    ImageSize:        01675000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:



Rich (BB code): 
0: kd> !pool ffffc001c0d67010
GetUlongPtrFromAddress: unable to read from fffff802b17762a8
GetUlongPtrFromAddress: unable to read from fffff802b1776520
Pool page ffffc001c0d67010 region is Paged pool
GetUlongFromAddress: unable to read from fffff802b16cdaf8
Unable to get pool big page table. Check for valid symbols.
ffffc001c0d67000 is not valid pool. Checking for freed (or corrupt) pool
Bad allocation size @ffffc001c0d67000, zero is invalid

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval ffffc001c0d67000 for more details.


Pool page [ ffffc001c0d67000 ] is INVALID.

Analyzing linked list...
[ ffffc001c0d67000 ]: invalid block size [ 0x0 ] should be [ 0x21 ]


Scanning for single bit errors...

None found

Code: 
0: kd> dt _POOL_HEADER ffffc001c0d67000
nt!_POOL_HEADER
   +0x000 PreviousSize     : 0y00000000 (0)
   +0x000 PoolIndex        : 0y00000000 (0)
   +0x002 BlockSize        : 0y00000000 (0)
   +0x002 PoolType         : 0y00000000 (0)
   +0x000 Ulong1           : 0
   +0x004 PoolTag          : 0x6d4d6956
   +0x008 ProcessBilled    : (null)
   +0x008 AllocatorBackTraceIndex : 0
   +0x00a PoolTagHash      : 0

Code: 
0: kd> .formats 0x6d4d6956
Evaluate expression:
  Hex:     00000000`6d4d6956
  Decimal: 1833789782
  Octal:   0000000000015523264526
  Binary:  00000000 00000000 00000000 00000000 01101101 01001101 01101001 01010110
  Chars:   ....mMiV
  Time:    Thu Feb 10 10:03:02 2028
  Float:   low 3.97324e+027 high 0
  Double:  9.06013e-315

Rich (BB code): 
0: kd> !pooltag ViMm
Pooltag ViMm
Description: Video memory manager
Driver!Module: dxgkrnl.sys
Click to expand...

Yeap I've already did updated to the latest this morning.
So what does this bugcheck says could it be a hardware related problem ?.
 
x BlueRobot said:
No, this is very likely to be a driver issue.
Click to expand...

That explains the abscence of BSOD's after that one.It has been almost 2 weeks since that BSOD happened.I didnt heavily gamed scared of this being a hardware related issue and i might harm it more.But i've did watched movies and surfed the internet.
 
BSODs won't cause any damage to your system. I would continue to use the system as you normally would with DV enabled if possible.
 
I would hold off from running any hardware tests yet, continue to use the system as normal and inform us of any new crashes.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top