Windows 7 BSOD Help "bad pool caller"

[markymark]

I've included all the files requested on BSOD getting help page in a zipped folder. Hopefully somebody might know what direction I need to go to fix this issue. Any help would be appreciated on this "bad pool caller" BSOD. Thanks!

 

[usasma]

Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

One of the dumps seems to point at a Hawking Technologies device, but I'm unable to definitely identify the drivers that are involved.
What make and model Hawking device are you using?

Another seems to point at TotalRecorder, please un-install it.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

wn311b64.sys Thu Mar 27 18:31:07 2008 (47EC202B)
RangeMax NEXT Wireless Adapter WN311B
Link Removed

RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 (492ADDCD)
Virtual Serial Port driver for Blackberry
Link Removed

nusb3hub.sys Fri Nov 20 05:15:57 2009 (4B066C5D)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with earlier versions)
Link Removed

nusb3xhc.sys Fri Nov 20 05:16:01 2009 (4B066C61)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with earlier versions)
Link Removed

AppleCharger.sys Thu Apr 22 03:05:49 2010 (4BCFF54D)
GIGABYTE On/Off Charge driver. See here for details - Link Removed [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Fri Apr 12 01:10:58.907 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041113-30232-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:29.828[/B]
*** WARNING: Unable to verify timestamp for TotRec8.sys
*** ERROR: Module load completed but symbols could not be loaded for TotRec8.sys
Probably caused by :[B]TotRec8.sys ( TotRec8+1d2ca )[/B]
BugCheck [B]D1, {fffff880051872ca, 2, 8, fffff880051872ca}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff880051872ca, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880051872ca, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_TotRec8+1d2ca[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: [B]2833[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Apr 11 23:42:56.567 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041113-38095-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:31:32.488[/B]
Probably caused by :[B]memory_corruption ( nt!MiUnsecureVirtualMemory+ef )[/B]
BugCheck [B]19, {20, fffffa80081b4e00, fffffa80081b4e00, 4000001}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80081b4e00, The pool entry we were looking for within the page.
Arg3: fffffa80081b4e00, The next pool entry.
Arg4: 0000000004000001, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  brpjp04a.exe
FAILURE_BUCKET_ID: [B]X64_0x19_20_nt!MiUnsecureVirtualMemory+ef[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: [B]2833[/B]
  BIOS Version                  FA
  BIOS Release Date             04/20/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  X58A-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Apr 11 21:10:06.118 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041113-39639-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 5:36:44.039[/B]
*** WARNING: Unable to verify timestamp for HawkingUDSMBus.sys
*** ERROR: Module load completed but symbols could not be loaded for HawkingUDSMBus.sys
Probably caused by :[B]HawkingUDSMBus.sys ( HawkingUDSMBus+a395 )[/B]
BugCheck [B]C2, {7, 109b, 4030009, fffffa800aa79d20}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000004030009, Memory contents of the pool block
Arg4: fffffa800aa79d20, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7_SUBM
PROCESS_NAME:  Control Center
FAILURE_BUCKET_ID: [B]X64_0xc2_7_SUBM_HawkingUDSMBus+a395[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: [B]2833[/B]
  BIOS Version                  FA
  BIOS Release Date             04/20/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  X58A-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Fri Apr 12 01:10:58.907 2013 (UTC - 4:00)**************************
jraid.sys                   Wed Jan 27 03:58:17 2010 (4B600029)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
TotRec7.sys                 Mon Apr 12 08:16:15 2010 (4BC30F0F)
TotRec8.sys                 Mon Apr 12 08:17:43 2010 (4BC30F67)
[COLOR=RED][B]AppleCharger.sys            Thu Apr 22 03:05:49 2010 (4BCFF54D)[/B][/COLOR]
SYMDS64.SYS                 Mon May 16 18:15:03 2011 (4DD1A1E7)
SymIMv.sys                  Sat Nov 12 16:08:22 2011 (4EBEE046)
SYMNETS.SYS                 Sat Nov 12 16:11:53 2011 (4EBEE119)
Ironx64.SYS                 Mon Nov 14 21:00:53 2011 (4EC1C7D5)
SYMEVENT64x86.SYS           Mon Jan 23 13:57:54 2012 (4F1DADB2)
SYMEFA64.SYS                Fri May 18 21:29:56 2012 (4FB6F794)
ccSetx64.sys                Wed Jun  6 23:00:55 2012 (4FD01967)
SRTSP64.SYS                 Mon Jul  2 14:20:28 2012 (4FF1E66C)
SRTSPX64.SYS                Mon Jul  2 14:20:37 2012 (4FF1E675)
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
EX64.SYS                    Thu Dec 20 04:22:39 2012 (50D2D8DF)
ENG64.SYS                   Thu Dec 20 04:24:21 2012 (50D2D945)
BHDrvx64.sys                Sat Mar 16 01:18:38 2013 (514400AE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Apr 11 23:42:56.567 2013 (UTC - 4:00)**************************
[COLOR=RED][B]wn311b64.sys                Thu Mar 27 18:31:07 2008 (47EC202B)[/B][/COLOR]
[COLOR=RED][B]RimSerial_AMD64.sys         Mon Nov 24 12:01:01 2008 (492ADDCD)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]nusb3hub.sys                Fri Nov 20 05:15:57 2009 (4B066C5D)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Fri Nov 20 05:16:01 2009 (4B066C61)[/B][/COLOR]
Rt64win7.sys                Thu Mar  4 08:42:52 2010 (4B8FB8DC)
RTKVHD64.sys                Fri Mar 26 06:30:50 2010 (4BAC8CDA)
vmwvusb.sys                 Fri Jul 23 22:30:08 2010 (4C4A5030)
LEqdUsb.Sys                 Tue Aug 24 13:21:23 2010 (4C73FF93)
LHidEqd.Sys                 Tue Aug 24 13:21:26 2010 (4C73FF96)
LHidFilt.Sys                Tue Aug 24 13:21:36 2010 (4C73FFA0)
LMouFilt.Sys                Tue Aug 24 13:21:43 2010 (4C73FFA7)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
HawkingUDSTcpBus.sys        Mon Jun  4 04:30:46 2012 (4FCC7236)
HawkingUDSMBus.sys          Mon Jun  4 04:34:12 2012 (4FCC7304)
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
AtihdW76.sys                Tue Nov  6 16:41:51 2012 (5099841F)
atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[markymark]

BTW,
Thank you for your analysis. I will address the recommended areas that you suggested. You asked which Hawking product that I was using. Are there any known issues with this device? I've done a web search and can't seem to find anything on it:
Hawking Model #: HMPS2U is the device model which is a wireless print server.
I will trying removing one thing at a time and see if stability returns to my system.
Thanks,
Mark

 

[usasma]

BSOD analysis (at our level) is an art - not a science. We get clues as to what's wrong and make suggestions based on those clues.

In this case there are several questionable things that point at the USB sub-system. They are:
- outdated wireless USB network device drivers
- outdated USB 3.0 controller drivers
- Hawking USB device drivers blamed in one memory dump (there are more recent drivers available from Hawking here: hawkingtech.com/products/downloadfile/983.html (direct download link))
- and the AppleCharger USB drivers that have had problems in the past (I suggest un-installing it).
- I'm unsure if the Blackberry device connects via USB, but that is usually how they work - so it's older drivers can be involved in this also. In cases like this I suggest removing it temporarily. If it helps, then you can re-install the latest, Win7 compatible version after the system has been stable for a bit.

I would fix all of them (rather than one at a time) as the goal here is to get your system functioning. Also, often BSOD's are caused by a combination of drivers - and repairing one can leave you with a different type of error (such as freezing or a black screen).