- Nov 17, 2018
- 6
- 0
- 10
I recently built a new computer and after setting everything up, I overclocked my CPU, GPU, and set my RAM to 3200mHz (via XMP). I was getting repeated BSoD and after much frustration, I got rid of both OCs, yet was STILL getting the issue. I then reinstalled windows completely, and after an hour of gaming, got it yet again.
I was thinking the OC was the issue but now I feel like it has to be hardware, no? Also, I kept the RAM at 3200 via XMP, that shouldn't be a problem since that is what I bought, right? Do I have to return my GPU, RAM, CPU (got them all very recently)? Idk who is the culprit!
Specs:
MOBO: ASUS ROG Strix Z370-E Gaming
CPU: i7-8700k
RAM: CORSAIR Vengeance RGB Pro 32GB DDR4 3200 (PC4 25600)
GPU: MSI GeForce RTX 2080 GAMING X TRIO
PSU: RM1000x
SSD: Samsung 970 EVO 500GB - NVMe PCIe M.2 2280 SSD
Here are my most recent error codes via WhoCrashed:
On Sat 11/17/2018 7:19:56 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111718-9031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0xC2 (0x7, 0x4D52564E, 0x4050001, 0xFFFFC9093C9780C0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 11/17/2018 7:19:56 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xDD8C6)
Bugcheck code: 0xC2 (0x7, 0x4D52564E, 0x4050001, 0xFFFFC9093C9780C0)
Error: BAD_POOL_CALLER
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6992f55a2cc4b209\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 416.94
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 416.94
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 416.94 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
I was thinking the OC was the issue but now I feel like it has to be hardware, no? Also, I kept the RAM at 3200 via XMP, that shouldn't be a problem since that is what I bought, right? Do I have to return my GPU, RAM, CPU (got them all very recently)? Idk who is the culprit!
Specs:
MOBO: ASUS ROG Strix Z370-E Gaming
CPU: i7-8700k
RAM: CORSAIR Vengeance RGB Pro 32GB DDR4 3200 (PC4 25600)
GPU: MSI GeForce RTX 2080 GAMING X TRIO
PSU: RM1000x
SSD: Samsung 970 EVO 500GB - NVMe PCIe M.2 2280 SSD
Here are my most recent error codes via WhoCrashed:
On Sat 11/17/2018 7:19:56 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111718-9031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0xC2 (0x7, 0x4D52564E, 0x4050001, 0xFFFFC9093C9780C0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 11/17/2018 7:19:56 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xDD8C6)
Bugcheck code: 0xC2 (0x7, 0x4D52564E, 0x4050001, 0xFFFFC9093C9780C0)
Error: BAD_POOL_CALLER
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6992f55a2cc4b209\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 416.94
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 416.94
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 416.94 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
Facebook
Twitter
Instagram