Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

A Serious Error Suspected Mainly Caused By Windowsxp Rndis Driver


  • Please log in to reply
3 replies to this topic

#1 dbboy

dbboy

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:21 AM

Posted 28 July 2006 - 04:22 PM

Hi guys,
I encouter a seriouls driver error and I suspected it is caused by Microsoft RNDIS driver(Specificly, the C:\WINDOWS\system32\drivers\usb8023.sys, 11kb, 2001-8-23 2:00) :thumbsup: . Here is the result from Windbg when I check the dump file when bluescreen and crash happen.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 021e0002, Memory contents of the pool block
Arg4: 86ae71f8, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS: 86ae71f8

FREED_POOL_TAG: aPmI

BUGCHECK_STR: 0xc2_7_aPmI

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80550fc5 to 805371aa

STACK_TEXT:
f7a61ba0 80550fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f7a61bf0 f741c60f 86ae71f8 00000000 f7a61c34 nt!ExFreePoolWithTag+0x2c1
f7a61c00 f7b44bc6 86ae71f8 00000084 00000000 NDIS!NdisFreeMemory+0x3b
WARNING: Stack unwind information not available. Following frames may be wrong.
f7a61c34 f7422fe4 00000000 f7a61c5c 867603d4 eacfilt+0xbc6
f7a61cd0 f742563d 806ff830 86638858 804e5d81 NDIS!ndisInitializeBinding+0x189
f7a61d58 f74256d6 867c05b8 805694c0 86fc3a20 NDIS!ndisCheckAdapterBindings+0x13a
f7a61d6c f7421bfe 867c05b0 00638858 f7a61dac NDIS!ndisQueuedCheckAdapterBindings+0x83
f7a61d7c 804e23b5 867c05b0 00000000 86fc3a20 NDIS!ndisWorkItemHandler+0xe
f7a61dac 80574128 867c05b0 00000000 00000000 nt!ExpWorkerThread+0xef
f7a61ddc 804efc81 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
eacfilt+bc6
f7b44bc6 ?? ???

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: eacfilt

IMAGE_NAME: eacfilt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3da72b4e

SYMBOL_NAME: eacfilt+bc6

FAILURE_BUCKET_ID: 0xc2_7_aPmI_eacfilt+bc6

BUCKET_ID: 0xc2_7_aPmI_eacfilt+bc6

Followup: MachineOwner


It can be found that the crash happen in NdisFreeMemory(). So I am sure that it is the rndis driver that make the crash happen. When the crash happen, sometimes I am doing nothing and just keep the RNDIS connected to my PC, then system crahs left a dump file. For manytimes, the bugcheck error from the dump are toally the same.

Is my analysis correct? I hope so actually :flowers: . Does anybody know how I can get the latest Windows XP RNDIS driver? As I know from WidowsXP, it is shipped with the OS together.

Thanks a hunders of time for your reply.

BC AdBot (Login to Remove)

 


m

#2 Animal

Animal

    Bleepin' Animinion


  • Site Admin
  • 34,286 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Where You Least Expect Me To Be
  • Local time:03:21 AM

Posted 28 July 2006 - 05:13 PM

Is this what you are looking for? Remote NDIS USB Driver Kit

Be (Driver) Safe

Da Bleepin AniMod, Animal

The Internet is so big, so powerful and pointless that for some people it is a complete substitute for life.
Andrew Brown (1938-1994)


A learning experience is one of those things that say, "You know that thing you just did? Don't do that." Douglas Adams (1952-2001)


"Imagination is more important than knowledge. Knowledge is limited. Imagination circles the world." Albert Einstein (1879-1955)


Follow BleepingComputer on: Facebook | Twitter | Google+

#3 Enthusiast

Enthusiast

  • Members
  • 5,898 posts
  • OFFLINE
  •  
  • Location:Florida, USA
  • Local time:06:21 AM

Posted 28 July 2006 - 05:15 PM

Have you checked all devices in the device manager especially the USB section to see if you have a yellow or red warning icon?

If so, update the driver.

Do you have SP2 and subsequent MS Critical Updates installed?

#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,076 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:21 AM

Posted 29 July 2006 - 10:48 AM

Just because the crash occurred in NdisFreeMemory doesn't mean that that caused the crash. For example, a bad driver for a USB device could be attempting to access NdisFreeMemory in a way that NdisFreeMemory doesn't know how to handle - then it's the other USB driver that's causing the error even though it crashes NdisFreeMemory.

Also, I find no reference to usb8023.sys in your crash dump - so why do you think that this file is at fault? I did find reference to eacfilt.sys which is also related to this system.

If you're current on Windows Update, you're current on the versions for these files (that's how Windows Update works).

Here's some things to try:
1) Update your motherboard/chipset drivers (IMO these are the most likely source of the problem).
2) Run SFC. EXE /SCANNOW from the Run dialog. Visit Windows Update immediately after the scan in case it replaced some updated files.
3) Run a repair install of Windows XP using this link: http://www.michaelstevenstech.com/XPrepairinstall.htm

Here's a link that describes more about the STOP 0xC2 error: http://aumha.org/win5/kbestop.php#0xc2
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users