BSOD every time (5-10 min), BAD_POOL_CALLER

[Ballose]

Hello everyone,

I'm having big troubles with my computer, I can't manage to use it more than 10 minutes since it keeps having BSODs..

I'm using Windows 8.1, and, during the time I wrote those few lines, it already restarted 3 times !!

Here are specy snapshot, dump files and minitoolbox results, I hope it's not an hardware problem (I was thinking about the mobo, which slot 1 seems broken) or the ram sticks.

dmp files (.zip password : Ballose) :
http://s000.tinyupload.com/index.php?file_id=04873287284812275433

http://speccy.piriform.com/results/BW5PbAiJUcLNUtaeTnnumiD

minitoolbox :
http://s000.tinyupload.com/index.php?file_id=87376231705933151694



Thanks !!!

 

[tejimthrowniy]

go to safe mode and see if it still happens. if it doesn't happen in safe mode, then it may be caused by any software you installed or a virus. if it doesn't happen in safe mode, it maybe a hardware problem or disk error. i can help. just go to safe mode and tell the results.
tejimthrowniy.

 

[Ballose]

Can someone please look at the dump files ? So I can get an accurante answer, please

 

[tejimthrowniy]

please go to safe mode and tell the results

 

[johnbl]

note: looks like your ksapersky software is from oct 2013 you might want to check for updates

Note: all three bugchecks look about the same, corrupted stack, containing Kaspersky networking code
you might also want to check your audio driver
amdkmafd.sys Sat Sep 22 18:04:42 2012 and make sure you don't have some conflict with
AtihdWB6.sys Tue Mar 11 16:50:02 2014

(two different audio driver's dated 2 years apart)
note:
one memory dumps had InfoWatch Encrypt Sector Library driver installed.
CSCrySec.sys Tue Sep 17 23:40:54 2013


this is a older machine, the last update to the bios was in 2010 and the last driver update from gigabyte was in 2010. You will have to dig around to find a updated NEC usb 3.0 driver to fix the problem. (or remove the driver and disable the USB 3.0 support in BIOS)
---------
- my first guess would be that your 2010 version of NEC Electronics USB 3.0 Host Controller Driver
is corrupting kernel memory and resulted in corruption of kaspersky software which resulted in a bugcheck in networking code when a bad address (corrupted) memory address was passed to a kernel function that was being verified by verifier.exe


first bugcheck was in networking code called by klwfp.sys Kaspersky Network Filtering Component
looks like something overwrote the stack. (malware ?)


jraid.sys Mon Sep 06 19:37:00 2010 (JMicron RAID Driver)
this driver is out of date
: NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
nusb3hub.sys Thu Nov 18 17:34:24 2010
nusb3xhc.sys Thu Nov 18 17:34:25 2010
machine info:
BIOS Release Date 09/16/2010
Manufacturer Gigabyte Technology Co., Ltd.
Product Name P55A-UD4

Processor Version Intel(R) Core(TM) i7 CPU
Processor Voltage 8ah - 1.0V
External Clock 133MHz
Max Speed 4000MHz
Current Speed 2933MHz

 

[Lutfij]

tejimthrowniy,
Please stop with your safe mode solutions. That is not what is needed to solve the issue at hand.

Ballose,
Without any reverting you could install Whocrashed onto your system and analyse your dump files with a screen shot of your results/page of results.

if these are your system specs;

Operating System
Windows 8.1 64-bit
CPU
Intel Core i7 860 @ 2.80GHz: 48 °C
Lynnfield 45nm Technology
RAM
10,0GB Single-Channel DDR3 @ 532MHz (7-7-7-19)
Motherboard
Gigabyte Technology Co., Ltd. P55A-UD4 (Socket 1156): 37 °C
Graphics
2367 (1920x1080@60Hz)
2048MB ATI AMD Radeon HD 5800 Series (Sapphire/PCPartner): 45 °C
Storage
59GB Crucial C300-CTFDDAC064MAG ATA Device (SSD)
931GB LaCie Rugged FW USB3 USB Device (USB (SATA)): 33 °C
Optical Drives
HL-DT-ST DVDRAM GH24LS50 ATA Device
Audio
Realtek High Definition Audio

How on earth did you force Windows 8.1 onto your system? The highest support in terms of driver(s) with a corresponding OS is Windows 7. Why are you running your ram at 1066 and its showing 10GB it should either show 4GBx4(dual channel) 16GB of ram or the least 2GBx1 or do you have all 4 dimms populated with 4GB and 1GB sticks? also remove the USB drive connected to your system.

Revert to Windows 7 and see if the issue persists but the broken ram slot, can you identify which slot/dimm is broken?

 

[Ballose]

First of all, thanks everyone for your quick answers!!!

note: looks like your ksapersky software is from oct 2013 you might want to check for updates

you might also want to check your audio driver

one memory dumps had InfoWatch Encrypt Sector Library driver installed.


this is a older machine, the last update to the bios was in 2010 and the last driver update from gigabyte was in 2010. You will have to dig around to find a updated NEC usb 3.0 driver to fix the problem. (or remove the driver and disable the USB 3.0 support in BIOS)

First, I checked kaspersky website and I've seen the latest product is kaspersky total security 2015, and I just installed it !

The computer is not that old, 4 years old. But gigabyte only makes new BIOS versions for 1 year, then nothing :/

About the audio driver, I'm using the latest version of Realtek, not provided by gigabyte but on their own website, the whole suite (v2.75), should I not ?

"one memory dumps had InfoWatch Encrypt Sector Library driver installed."
What should I do about this ?

Finally, the nec usb driver is the latest version available on gigabyte.com, but I'm looking for another source !

tejimthrowniy,
How on earth did you force Windows 8.1 onto your system? The highest support in terms of driver(s) with a corresponding OS is Windows 7. Why are you running your ram at 1066 and its showing 10GB it should either show 4GBx4(dual channel) 16GB of ram or the least 2GBx1 or do you have all 4 dimms populated with 4GB and 1GB sticks? also remove the USB drive connected to your system.

Revert to Windows 7 and see if the issue persists but the broken ram slot, can you identify which slot/dimm is broken?

I'm not sure what you mean about Win 8.1

It seems that memory slot #1 is broken!! I first tought it was the memory stick but it's not, but changing mobo means no computer during the time I receive a new one from gigabyte, so I never contacted them....

I'm using 2x4GB dual channel + 2x2GB dual channel, but only 1 memory stick of the 2GBs are recognized, so 8+2 = 10

 

[Lutfij]

You installed windows 8.1 onto a machine that has no driver support for the motherboard by the motherboard maker and the only driver with no-conflicts with windows 8.1 would be the audio driver.

Next, you should always, always run your kits in a matched pair - this means either having all of the dimms or only 2(since its a P55 platform) populated with the same capacity , timings and frequency. Now since you have a broken slot, I'd request you remove the 2GB dimms to have 8GB's on your system for testing and not have any stick populating the broken dimm.

Honestly mate, you've got too many variables to narrow down the issue... any progress with your dump files?

 

[Ballose]

Hey, thanks for the reply!!!

You installed windows 8.1 onto a machine that has no driver support for the motherboard by the motherboard maker and the only driver with no-conflicts with windows 8.1 would be the audio driver.

Well, it seems what 7 can handle, 8.1 can handle too
No way I go back to seven

Next, you should always, always run your kits in a matched pair - this means either having all of the dimms or only 2(since its a P55 platform) populated with the same capacity , timings and frequency. Now since you have a broken slot, I'd request you remove the 2GB dimms to have 8GB's on your system for testing and not have any stick populating the broken dimm.

I would have loved the 12GB works, since 8GB is easily full with games or heavy tasks, unfortunatly it looks like I have no other choice...

Honestly mate, you've got too many variables to narrow down the issue... any progress with your dump files?

I use bluescreenview which works like a charm, is there a difference ?
If this is really needed then I'll do it.
But I assume you have it ?

Thanks again!

 

[Lutfij]

You're welcome but I was talking about chipset drivers, IME drivers as well as the broken DIMM slot - it could be a short. There is a reason there are drivers supplied for a motherboard otherwise system integrator's wouldn't need to be concerned about compatibility with OS and hardware.

I went about talking about you introducing many variables and thus many reasons for a failure was noted above and primarily after reading this in brief;
http://jaiminworld.wordpress.com/2008/09/21/causes-of-bad-pool-caller-problem/

Yes it would be better if you could go through the dump file with and...I just noticed you put up the results. Your error report is littered with 0xC2 errors.

 

[Ballose]

I mostly see the manufacturer wants us to pay more and more often to have the "certified" hardware, but windows is backward compatible enough not to give me troubles so that's fine.

Who are those 0xC2 bad boys ?

 

[tejimthrowniy]

this should help though i havent tried it
just dont download registry ace just follow the steps.
http://www.personalcomputerfixes.com/general-errors/steps-to-fix-the-bad-pool-caller-blue-screen-error/