drew22to375
New member
- Local time
- 3:06 PM
- Messages
- 4
Hello,
I have recently setup new pc's for our programming staff. The pc's are HP 8300 Elite convertible minitower. 32GB of memory 500GB hard drives RAID 1 configuration, Nvidia 8400 GS. They are all setup with identical software and drivers, etc. out of 11 pc's 3 of them after a month of use get the Bad Pool Caller when rebooting the pc. all of them appear be be the same error. I am unable to use the SF diagnostic tool. So I will post the error what who crashed says.
Along with several of the mini dump files. The Bad Pool Caller is the most common error but I have also received Driver corrupted Expool. Any help troubleshooting these errors would be appreciated. Thanks Drew..
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/3/2013 8:01:07 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xC2 (0x99, 0xFFFFFA801EE48E70, 0x0, 0x0)
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.
I have recently setup new pc's for our programming staff. The pc's are HP 8300 Elite convertible minitower. 32GB of memory 500GB hard drives RAID 1 configuration, Nvidia 8400 GS. They are all setup with identical software and drivers, etc. out of 11 pc's 3 of them after a month of use get the Bad Pool Caller when rebooting the pc. all of them appear be be the same error. I am unable to use the SF diagnostic tool. So I will post the error what who crashed says.
Along with several of the mini dump files. The Bad Pool Caller is the most common error but I have also received Driver corrupted Expool. Any help troubleshooting these errors would be appreciated. Thanks Drew..
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/3/2013 8:01:07 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xC2 (0x99, 0xFFFFFA801EE48E70, 0x0, 0x0)
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.
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- HP Elite 8000
- OS
- Windows 7 Professional 64-bit
- CPU
- Intel Q9505
- Memory
- 8GB
- Graphics Card(s)
- Nvidia Quadro NVS 290
- Hard Drives
- Seagate 500GB in RAID 1 configuration
- Antivirus
- Symantec Endpoint
- Browser
- Firefox
rb: