BSOD crashing on custom pc after 2-3 weeks of stability

[jacket321]

UPDATE - Dead GPU - EVGA RTX 2070 XC - In the RMA process. If you have similar issues might be worth just opening an RMA ticket ASAP, they will help you troubleshoot first anyways.

Hardware: ASUSTeK COMPUTER INC., TUF Z390M-PRO GAMING (WI-FI)
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
GSKILL Trident Z RAM: 34199744512 bytes total, EVGA RTX 2070 Black

I built a PC in November, and slowly overclocked RAM, CPU, and GPU. I got to a point where everything was stable and put in about 60 hours on Witcher 3 over a week or two with no issues

Saturday morning I started getting a variety of BSOD errors within minutes of gaming. IRQL, Bad Pool Caller, System Exception. I then replaced the CPU and MOBO thanks to Micro Center - and also tried RAM from another PC - still getting BSOD.

Since replacing CPU and MOBO I'm mostly getting Bad pool caller BSODs now, though after updating bios - I got a DPC watchdog error (Game crashed first, then a few minutes later BSOD instead of right away.)

I'd appreciate any help - hopefully I've already replaced enough parts to start removing hardware as an issue.

Things I've done so far with no luck:

• 
  Updated GPU Drivers (DDU, clean install)
  Updated BIOS
  Replaced CPU
  Replaced Mobo
  Tested RAM from other PC
  Run Driver Verifier and deleted a few leftover drivers, until it PC boots with driver verifier running

Sample Mini-dump from whocrashed - all the Bad Pool Caller Dumps are the same - they point to ntoslrnl.exe which i understand to be a generic error. Haven't been able to generate a minidump where an actual driver was identified.

On Sun 12/16/2018 2:24:37 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121618-11765-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xC2 (0x7, 0x484C764E, 0x50005, 0xFFFF8E0975C90550)
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.

Thanks

UPDATE: After removing a few drivers from driver verifier until it booted into windows - I got to a bad pool caller error that showed an Nvidia driver as the cause: This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xDDBA6)

 

[rgd1101]

MERGED QUESTION
Question from jacket321 : "BSOD crashing on custom pc after 2-3 weeks of stability"

Hardware: ASUSTeK COMPUTER INC., TUF Z390M-PRO GAMING (WI-FI)
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
GSKILL Trident Z RAM: 34199744512 bytes total, EVGA RTX 2070 Black

I built a PC in November, and slowly overclocked RAM, CPU, and GPU. I got to a point where everything was stable and put in about 60 hours on Witcher 3 over a week or two with no issues

Saturday morning I started getting a variety of BSOD errors within minutes of gaming. IRQL, Bad Pool Caller, System Exception. I then replaced the CPU and MOBO thanks to Micro Center - and also tried RAM from another PC - still getting BSOD.

Since replacing CPU and MOBO I'm mostly getting Bad pool caller BSODs now, though after updating bios - I got a DPC watchdog error (Game crashed first, then a few minutes later BSOD instead of right away.)

I'd appreciate any help - hopefully I've already replaced enough parts to start removing hardware as an issue.

Things I've done so far with no luck:

• 
  Updated GPU Drivers
  Updated BIOS
  Replaced CPU
  Replaced Mobo
  Tested RAM from other PC

Sample Mini-dump from whocrashed - all the Bad Pool Caller Dumps are the same - they point to ntoslrnl.exe which i understand to be a generic error. Haven't been able to generate a minidump where an actual driver was identified.

On Sun 12/16/2018 2:24:37 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121618-11765-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xC2 (0x7, 0x484C764E, 0x50005, 0xFFFF8E0975C90550)
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.

Thanks

 

[rgd1101]

it is still oc?
did you try running without the nvidia gpu?

 

[jacket321]

it is still oc?
did you try running without the nvidia gpu?

No I removed all OC including XMP before I began the troubleshooting steps.

The PC runs with the GPU, just crashes while gaming when it used to be fine. I'm sure it would run fine without the GPU, but I wouldn't be able to test a game like the Witcher with an onboard GPU.

 

[rgd1101]

contact gpu support.
try older driver

 

[johnbl]

bugcheck 0xc2 BAD_POOL_CALLER with parmeter 1=7
means a driver freed up the same memory handle twice.

most of the time it would just be a bug in the driver. (update or downgrade the driver)
if it is a gpu driver I would make sure the motherboard sound driver has been updated.
there were some versions that corrupted the gpu sound support driver and can cause various errors)

make sure you run the gpu firmware update utility if required.
you might also disable any gpu utilities that you are not actually using.
(it will make your hardware have less things to do and will run faster and close timing windows for bugs in the driver)

you might also disable sound devices that do not actually have speakers attached to them.

 

[originalletmepicyou]

What power supply are you using?

 

[jacket321]

bugcheck 0xc2 BAD_POOL_CALLER with parmeter 1=7
means a driver freed up the same memory handle twice.

most of the time it would just be a bug in the driver. (update or downgrade the driver)
if it is a gpu driver I would make sure the motherboard sound driver has been updated.
there were some versions that corrupted the gpu sound support driver and can cause various errors)

make sure you run the gpu firmware update utility if required.
you might also disable any gpu utilities that you are not actually using.
(it will make your hardware have less things to do and will run faster and close timing windows for bugs in the driver)

you might also disable sound devices that do not actually have speakers attached to them.

I tried updating motherboard audio driver as there is an update - but I get an issue where there is no sound. Rolling back the driver got me sound back. The crashes where still there with no audio driver, and the audio driver with no sound.

There hasn't been a firmware update for the evga 2070, and all other sound devices are disabled.

I've been noticing that I'm also getting more and more artifacts for the few minutes that games do run before crashing.

 

[jacket321]

What power supply are you using?

EVGA g1+ 650 watt

 

[jacket321]

contact gpu support.
try older driver

I rolled back to the earliest driver I could but still got crashes.

 

[jacket321]

UPDATE - Dead GPU - EVGA RTX 2070 XC - In the RMA process. If you have similar issues might be worth just opening an RMA ticket ASAP, they will help you troubleshoot first anyways.