New 15 R3 Getting Bad Pool Caller.

Hi,

Corrupted drivers, Windows registry errors, a memory (RAM) corruption, or even a virus, are some of the most common causes of the Bad Pool Caller blue screen crash. Did this issue start recently? If it did, you might be able to solve it using the System Restore option.

Yes from new. The laptop is roughly week and a half old. Usually happens during internet stuff. 

I updated all the drivers from Device Manager. I did a Memory Test which took roughly 4 hours. I scanned my computer and there is no virus. 

Hallo.

updating via Device Manager doesn't work most of the Time. it says "already installed" or something like that for Example. you should download and install all new Drivers manually.

also check the Reliability History please. open Start Menu and type Reliability. it should show up in the Result List. are there any Errors?

another good Source for Troubleshooting is Event Viewer. later more about it if Reliability Monitor is clean.

I ran the scan and it shows bunch of problems with Windows shutting down etc from day one. 

Do i start uninstalling and reinstalling and updating drivers per incident?

usually you can install all Drivers on Top of the Old ones. Windows Update does the same. the only Exceptions are Video Card Drivers. i suggest you Download Display Driver Uninstaller and use the Tool to uninstall the old Graphics Card Drivers. then install new ones. Intel first and then Nvidia.

If you:
- Have the latest BIOS
- Have re-seated the ram memory DIMMs (if you know how)

- ePSA passes

I would say probably a bad motherboard and/or ram-memory like these (IIRC, 15-R3 and 17-R4 are similar tech).

Brand new Alienware 17 R4 BSOD  

and

BSOD  

and

 
 
I hate to say it, but if not easily fixable (without replacing parts and boards) I would return it.  
 
After refund, start shopping and buying processes over.

hello, if you still have the problem try to change the killer performance suit with killer network manager, that work for me!

If you are still having the issue with the "Bad pool Caller", you can try this program to view the dump log. 

bluescreenview.

if the last driver is  RfeCo10X64.sys  then you can reinstall the killer drivers.

you can google the driver and see where it is from then reinstall or remove the drivers (if yours is showing a different driver)

i was having the same issue.  could not figure it out till i read another review, hope this helps. 

I have had exactly the same problem with a new Alienware 15 R3 laptop. I downloaded the program BlueScreenView as suggested. It seems the driver causing the crashes is always RN Traffic Control Callout Driver.

I'm not sure what to do now. Is there a new version of it I can install? Why would Dell be shipping new laptops with faulty drivers?

yes exactly what im asking dell. but still in their 'troubleshooting'

phase. i suggest you start a support ticket with them, at least more

people complain they are likely to take action.

currently i have removed the killer control center. the dell version is

differnt from the one on killer website. install on the drivers only,

killer website has the option for driver only. so far that hasn't cause any

issues. but i have only tested that config for a few days. my BSOD tends to

come in waves, so im waiting to see if it works.

i have also talked with killer support, but their osupport was to install

the latest version. they did mention is had some bug fixes in it.

Just to let everyone know: I updated the Killer E2500 Gigabit Ethernet Controller driver from within Device Manager but that has not solved the problem. The crashes are still occurring about once every day on average.

Same issue hear. Has anyone found a definitive resolution to this problem. I don't want to but I may have to return it. 

I uninstalled the Killer software a few days ago and haven't had one of the crashes since then, despite getting an average of one a day before that. Previously, I had updated both of the Killer drivers that show up in Device Manager but that didn't resolve the problem.

Hi guys.

i believe the Killer Driver is not the Problem. it's the Killer Network Suite / Manager that gives you BSOD. Driver Update via Device Manager will not solve anything as long as the Network Software is installed.

for People who can't find a Driver only Version for whatever Reason try following, open Task Manager, go to Startup Tab and disable Killer Network Suite. that Way the Killer Software can't Launch in a first Place. that is my Theory. it might or might not work.

i hope it helps.

Just posting an update 

i've been using these drivers for about 2 weeks.

http://www.killernetworking.com/driver-downloads/category/other-downloads

file : KillerDrivers_1.4.1466_x64

so far no issues.

currently on their web site they have updated a different version. 

to highlight what another user mentioned, i did remove all programs related to killer, before reinstalling their drivers.

as what he said, it may be their app control center.