[Solved] Pool Corruption

[Knofbath]

I seem to be getting Pool_Corruption BSOD crashes on windows 7 that started on the 25th. Scanning my recent changes, the only thing I noticed was the update to 2.04.

I'm not sure if its related or not, but I rolled back utorrent to 2.03 just now to test. Might be unrelated, but I had 19 days of uptime prior.

So, no crashes since I rolled back utorrent. I lost 4 of the crash minidumps when I did a system restore the first time, but Pool_Corruption was listed as main causes in those dumps as well.

I ran 7 passes of memtest386 last night trying to narrow the cause down. So I don't think my RAM is the issue here. Chkdsk showed no errors when run.

Operating system is Windows 7 Ultimate x64. uTorrent is running in 32 bit mode.

Here's some windbg output, the bugcheck varied in previous dumps, but all had Pool_Corruption ( nt!ExDeferredFreePool+100 ) listed as probable cause. If you have somewhere to upload a minidump, I will be happy to post that as well.

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002faaf8c, fffff880033c47e8, fffff880033c4050}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption

---------

Debugging Details:

------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:

nt!ExDeferredFreePool+100

fffff800`02faaf8c 4c8b02 mov r8,qword ptr [rdx]

[Knofbath]

Updated to 2.04(Build 21586)

It's been stable for 4 hours now, so the issue may have been resolved. I'll repost if anything changes.

[moogly]

You can open and read dumps with this freeware and post the contents here.

http://www.nirsoft.net/utils/blue_screen_view.html

[Knofbath]

Windows Error Log Events:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002fb6f8c, 0xfffff88002534db0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082510-24616-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082610-21512-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000300af8c, 0xfffff88003d6cca0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082610-19905-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082710-25740-01.

I did a system restore on the 27th and rolled back to the 25th, so I lost the minidumps for the first 4, but I had run them through windbg and the results were all Pool_Corruption ( nt!ExDeferredFreePool+100 )

Crash on the 28th occurred after I allowed utorrent to update again.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002faaf8c, 0xfffff880033c47e8, 0xfffff880033c4050). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-18985-01.

Bluescreenview output for the minidump from last crash, after this one I rolled back the utorrent exe and haven't had any more issues.

082810-18985-01.dmp 8/28/2010 7:47:12 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02faaf8c fffff880`033c47e8 fffff880`033c4050 Wdf01000.sys Wdf01000.sys+31a71 x64 C:\Windows\Minidump\082810-18985-01.dmp 4 15 7600

As I said, I updated to Build 21586 and haven't had any more issues. Faulting versions were 2.0.4 (build 21515) and (build 21431). I'm on 14 hrs stable now.

[Firon]

Wdf01000.sys

Some driver on your system was crashing. Security software? Wireless LAN?

[Knofbath]

I'm guessing that Wireless LAN is a good possibility. I know the wdf01000.sys is a driver file of some sort. "WDF Dynamic"???

Linksys WMP300N is the wireless card I'm using. AFAIK they haven't pushed out a decent driver for it, so I'm using the windows default driver. "Broadcom 802.11n Network Adapter"

I don't use a security software suite, just ClamAV, and Malwarebytes occasionally, but neither of those were running. And Windows Firewall since I'm behind a router.

[moogly]

Did you test with this driver?

http://homesupport.cisco.com/en-us/wireless/lbc/WMP300N

[Knofbath]

Hadn't known about it, last time I went looking was for a linux version.

I just installed it, so we'll see how well it works.

Only took them 9 months or so. Previous drivers didn't support Windows 7, and the last new driver I saw before was a generic broadcom in windows update that didn't work at all.

[edit]

That driver seems to have a nasty habit where it stops scanning for networks. It drops over half my available APs after a bit, including the one I am currently connecting to.

[frost_ua]

I have the same problem with 2.04(Build 21586) on my laptop (MSI Wind PC) Wireless adapter Realtek 802.11b/g Mini and Wireless router D-link DIR-300.

On 2.0.2 & 2.0.3 everything good.

[Knofbath]

Updating to 2.04(Build 21586) seems to have fixed my issue. I'm just playing around with drivers now.

Give the nice forum people some more details, and maybe see if either of the earlier 2.04 builds crash on you as well.

One of the devs probably needs to sit down with a debugger and find a memory leak. That's the best reason I could think up for why this happens.

[Firon]

Nope, the problem was your network adapter's drivers crashing (because our client was generating way more connections than it should've).

[Knofbath]

Ah, that explains it. Thanks for the help.