BSOD bad_pool_caller Win 7 x64

I have been getting BSODs for the past 4 - 5 days all occurring on startup. They are all bad_pool_callers. I haven't installed any new hardware on my Vaio laptop check my sig. Using windows 7 ultimate although windows updated my IE to version 10 recently and installed security updates. The only other thing I did was uninstall the software and drivers for 4 different CDMA mobile broadband dongles or usb keys used to go online which I had not been using. I've had laptop for year and a half and this is the first time I'm seeing this. They all tend to deal with ntoskrnl.exe and ndis.sys.

110113-37268-01.dmp 11/1/2013 12:36:39 AM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`0420000f fffffa80`07465910 ndis.sys ndis.sys+106c x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-37268-01.dmp 4 15 7601 271,028 11/1/2013 12:38:01 AM


103113-35427-01.dmp 10/31/2013 11:20:50 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200000 fffffa80`0731f010 ndis.sys ndis.sys+106c x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-35427-01.dmp 4 15 7601 271,028 10/31/2013 11:23:09 PM


103113-47283-01.dmp 10/31/2013 10:38:35 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200013 fffffa80`06940b10 ndis.sys ndis.sys+106c x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-47283-01.dmp 4 15 7601 271,028 10/31/2013 10:39:45 PM


103113-36192-01.dmp 10/31/2013 8:43:18 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200000 fffffa80`07185010 watchdog.sys watchdog.sys+7195d0 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-36192-01.dmp 4 15 7601 270,972 10/31/2013 8:44:24 PM


103113-49545-01.dmp 10/31/2013 8:06:06 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200002 fffffa80`074e1ab0 i8042prt.sys i8042prt.sys+b78ab0 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-49545-01.dmp 4 15 7601 271,028 10/31/2013 8:08:06 PM


103113-67408-01.dmp 10/31/2013 6:55:00 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`0020000d fffffa80`0684e7c0 mouclass.sys mouclass.sys+15425d0 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-67408-01.dmp 4 15 7601 271,028 10/31/2013 6:57:14 PM


103113-91276-01.dmp 10/31/2013 2:58:55 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200000 fffffa80`0734f010 ndis.sys ndis.sys+106c x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-91276-01.dmp 4 15 7601 271,028 10/31/2013 3:01:16 PM


103113-37533-01.dmp 10/31/2013 2:44:40 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`0420007d fffffa80`0728fe10 rdpbus.sys rdpbus.sys+ea4e10 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-37533-01.dmp 4 15 7601 271,028 10/31/2013 2:45:35 PM


103113-106642-01.dmp 10/31/2013 9:29:27 AM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200023 fffffa80`0489c7c0 ndis.sys ndis.sys+106c x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\103113-106642-01.dmp 4 15 7601 271,028 10/31/2013 9:36:43 AM


102913-43602-01.dmp 10/29/2013 11:23:34 AM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`04200001 fffffa80`039e3e10 ndis.sys ndis.sys+106c x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\102913-43602-01.dmp 4 15 7601 271,084 10/29/2013 11:24:33 AM

 

My first suggestion is being as you have done some changes is to go to system restore from before you were getting the errors. If all is fine then start making the changes one at a time with a few reboots between. Hopefully this way you can find the change that is the culprit..............

 

No results, it's getting worse in frequency now almost every bootup, and in bluescreenview I'm getting the following as the drivers causing it: raspppoe.sys WAN miniport driver, i8042.sys vaio keyboard, watchdog.sys I think AVG, mouclass.sys Sony vgp-wms30 usb wireless mouse, rdpbus.sys remote desktop redirector, igdpmd64m.sys intel acc. Graphics have dual graphics AMD and intel, NDproxy.sys PNP_TDI.

The above list have, according to blue screenview caused the problem once or twice, but the majority of the time it's ndis.sys along with ntoskrnl.exe causing the issues I've had over 20 instances of bad_pool_caller in 3 days. I ran memtest like 2 times for a total of 7 passes and it is ok along with chkdsk which found no errors. The very first BSOD I had dealt with ew_jubusenum.sys which is linked to the cdma dongle drivers and softwares I removed, could it cause BSOD after it's uninstalled and not even plugged in to laptop? I also have Atheros nic and lan card which have caused this issue in others but even with both disabled in device manager this is occuring.

 

I uninstalled the drivers for the Atheros LAN and Wifi along with the Broadcom bluetooth, problem still exists. Came up now as TDI.sys, along with ndis.sys and ntoskrnl.exe,which I think has to do with AVG Internet Security 2013, I'll try removing that too.

 

Well, Well, Well, I think we have the villain AVG INTERNET SECURITY 2013. 10 consecutive reboots and no sign of the BSOD, pc is also booting somewhat faster too.

Now I'll reinstall the drivers for the Atheros Gigabit LAN and AR9285 wifi and Broadcomm bluetooth one by one and fingers crossed all should be ok.

Now, I need a new Antivirus. Avast is great but it doesn't catch and identify all the viruses that AVG does, also it scans slow. I'm a college student and many of my classmates copy data to and from my pc, so I need to be protected well. Any better alternatives you guys can recommend?

 

WhoCrashed - Free download and software reviews - CNET Download.com

Use for future issues

 

I have it but it isn't telling me much.


Welcome to WhoCrashed (HOME EDITION) v 5.00
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.


--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: 1234-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: VPCCB15FA, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4201857024 total
VM: 2147352576, free: 1931980800




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 11/3/2013 12:34:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110313-22323-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x420002A, 0xFFFFFA80074D2AD0)
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/2/2013 11:54:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110313-52993-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x106C)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4200014, 0xFFFFFA80048C2CF0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 11/2/2013 9:12:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110313-71292-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x420000B, 0xFFFFFA80048CD270)
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/2/2013 8:55:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-60512-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x106C)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x420007D, 0xFFFFFA80048B3E10)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 11/2/2013 8:45:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-76378-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x106C)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x420004F, 0xFFFFFA8007CEFE10)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 11/2/2013 7:31:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-46067-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4200004, 0xFFFFFA80048397F0)
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/2/2013 7:08:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-97063-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x420004F, 0xFFFFFA8006BC0E10)
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/2/2013 5:13:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-26395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4200000, 0xFFFFFA8005D3D010)
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/2/2013 9:41:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-26410-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x106C)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4200007, 0xFFFFFA80048DFC80)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 11/2/2013 8:25:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110213-37627-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x106C)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4200003, 0xFFFFFA8007162850)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

28 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

Here is the link to my dumps FileSwap.com : Minidump.rar download free FileSwap.com : Minidump.rar download free Any ideas? I'm going nuts here.

 

http://forum.notebookreview.com/not...your-system-running-like-new.html#post9396290

Follow this link and do step three (3)

if the above fix does not work try this:

To run Startup Repair using preinstalled recovery options

Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer using the computer's power button.

Do one of the following:

If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.

If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to repair, and then press and hold F8.

On the Advanced Boot Options screen, use the arrow keys to highlight Repair your computer, and then press Enter. (If Repair your computer isn't listed as an option, then your computer doesn't include preinstalled recovery options, or your network administrator has turned them off.)

Select a keyboard layout, and then click Next.

On the System Recovery Options menu, click Startup Repair, and then follow the instructions.

 

As far as an anti virus I just use MSE..................

 

you're hosed. reinstall windows.