• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
Dj Walker

System Error

10 posts in this topic

Hi :hello:

i recently got a new system its running xp and it seems to be restarting frequently

i get these errors on restart

BCCode : c2 BCP1 : 00000007 BCP2 : 00000CD4 BCP3 : 020A0001

BCP4 : 863AB180 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

C:\DOCUME~1\THEDEV~1\LOCALS~1\Temp\WER73b4.dir00\Mini110607-14.dmp

C:\DOCUME~1\THEDEV~1\LOCALS~1\Temp\WER73b4.dir00\sysdata.xml

BCCode : fe BCP1 : 00000002 BCP2 : 855D0438 BCP3 : 85670008

BCP4 : 8642AF30 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

so i tried searching the errors and found this site did a reading :thumbup

im going to attach my minidumps if that will help me figure out whats going on and what the problem is hopefully so i can fix this.

Edited by Dj Walker
0

Share this post


Link to post
Share on other sites

A STOP 0xC2 means that this is a bad pool caller bugcheck, so honestly, without driver verifier enabled on the box we won't be able to tell what caused this. Perhaps you can enable that and get another bugcheck, then attach that minidump for us to look at?

0

Share this post


Link to post
Share on other sites
A STOP 0xC2 means that this is a bad pool caller bugcheck, so honestly, without driver verifier enabled on the box we won't be able to tell what caused this. Perhaps you can enable that and get another bugcheck, then attach that minidump for us to look at?

im sorry i looked at the link and tried to enable this but i must of did something wrong because my computer kept restarting at the winxp load up had to load last known good settings

how should i do this can you please explain?

0

Share this post


Link to post
Share on other sites

Try start > run > verifier.exe > click OK

Check the box for "Special Pool"

Select "Verify all Drivers"

click Apply and then Exit

Then reboot and see what happens - note that we EXPECT the machine to bugcheck at this point, so making sure that a reboot after a bugcheck is disabled while you're in safe mode is probably also a good idea, to make sure we see the bugcheck when it happens. Once you're done, reboot and cross your fingers :).

0

Share this post


Link to post
Share on other sites
Try start > run > verifier.exe > click OK

Check the box for "Special Pool"

Select "Verify all Drivers"

click Apply and then Exit

Then reboot and see what happens - note that we EXPECT the machine to bugcheck at this point, so making sure that a reboot after a bugcheck is disabled while you're in safe mode is probably also a good idea, to make sure we see the bugcheck when it happens. Once you're done, reboot and cross your fingers :).

ok where do i go from HERE to see special pool and verify all drivers

:)

amd before this you need me to set up and do everything in that reboot after a bugcheck is disabled thread right?

Edited by Dj Walker
0

Share this post


Link to post
Share on other sites
amd before this you need me to set up and do everything in that reboot after a bugcheck is disabled thread right?

Correct :)

As to what to do with this newer version of verifier:

1. Click "Create custom settings", then Next

2. Click "Select individual settings from a full list", then Next

3. Click the box for "Special pool", then Next

4. Click "Automatically select all drivers installed on this computer", then Finish

0

Share this post


Link to post
Share on other sites

OK, since the symbols for ntoskrnl.exe from 931784 aren't anywhere I can find (that's the version of the kernel you have on your box, which is the latest available), I'll have to do this manually in assembly without stacks - sorry, this won't be as easily readable as some of my other debugs here:

// This is the stack where the problem occurred:
0: kd> dds 80556218 805562a8
80556218 8053753a nt+0x6053a // The bugcheck
8055621c 000000c2
80556220 00000007
80556224 00000cd4
80556228 020a0003
8055622c 86ef8498
80556230 00000000
80556234 80556284 nt+0x7f284 // Driver verifier
80556238 80550fc5 nt+0x79fc5 // The pool free call
8055623c 000000c2
80556240 00000007
80556244 00000cd4
80556248 020a0003
8055624c 86ef8498
80556250 86ef8498
80556254 87145f50
80556258 00000000
8055625c 870a37b0
80556260 870a3788
80556264 00000000
80556268 86ef84e0
8055626c 00000000
80556270 f7586ed0 NDIS!NdisAcquireSpinLock+0x11
80556274 f7586eee NDIS!NdisReleaseSpinLock+0x11 // The call into ndis from the driver
80556278 80556290 nt+0x7f290
8055627c 00000000
80556280 00000001
80556284 80556294 nt+0x7f294
80556288 805503e3 nt+0x793e3
8055628c 86ef8498
80556290 00000000
80556294 805562d4 nt+0x7f2d4
80556298 f7c4d135 NetMotCM+0x2135 // The driver that likely is the problem
8055629c 86ef8498
805562a0 86ffc9b7
805562a4 86ffc8d8
805562a8 804e18ff nt+0xa8ff

// This looks like the pool free call on edi:
0: kd> u 80556238
nt+0x7f238:
80556238 c50f lds ecx,fword ptr [edi]
8055623a 55 push ebp
8055623b 80c200 add dl,0
8055623e 0000 add byte ptr [eax],al
80556240 07 pop es
80556241 0000 add byte ptr [eax],al
80556243 00d4 add ah,dl
80556245 0c00 or al,0

// This looks like driver verifier checking the call:
0: kd> u 80556234
nt+0x7f234:
80556234 846255 test byte ptr [edx+55h],ah
80556237 80c50f add ch,0Fh
8055623a 55 push ebp
8055623b 80c200 add dl,0
8055623e 0000 add byte ptr [eax],al
80556240 07 pop es
80556241 0000 add byte ptr [eax],al
80556243 00d4 add ah,dl

// This is the NetMotCM disassembly - I think the xchg call to the byte ptr in edi is incorrect
// math, causing the invalid pool call:
0: kd> u 80556298
nt+0x7f298:
80556298 35d1c4f798 xor eax,98F7C4D1h
8055629d 84ef test bh,ch
8055629f 86b7c9ff86d8 xchg dh,byte ptr [edi-27790037h]
805562a5 c8ff86ff enter 86FFh,0FFh
805562a9 184e80 sbb byte ptr [esi-80h],cl
805562ac 0000 add byte ptr [eax],al
805562ae 0000 add byte ptr [eax],al
805562b0 d8c8 fmul st,st(0)

// NetMotCM looks like a driver compiled just after XP RTM'ed (before SP1, even):
0: kd> lmvm NetMotCM
start end module name
f7c4b000 f7c4e800 NetMotCM T (no symbols)
Loaded symbol image file: NetMotCM.sys
Image path: \SystemRoot\system32\DRIVERS\NetMotCM.sys
Image name: NetMotCM.sys
Timestamp: Mon Feb 25 15:55:17 2002 (3C7AA4B5)
CheckSum: 0000ABF2
ImageSize: 00003800
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

I'm going to strongly suggest you update that Motorola driver to the latest version, but I'm also going to suggest you download and install the latest ndis.sys from 918837, just in case. You can request the hotfix from here.

The reason I say this is because I've seen this behavior before, on NDIS 4.0 driver code that was ported from NDIS 4.0 to NDIS 5.x (the Motorola driver), and given the age of that driver I'll bet it was originally coded against NDIS 4.0 (especially if the code was originally written to run on Win95 or NT4 - that had NDIS 4.0 only, so drivers had to meet NDIS 4.0 without 5.0 extensions to run there properly). Also, it looks like you have the driver attached over the USB bus (there are some USB calls further down the stack I saw, so I'm making a guess that your surfboard is connected to the PC via USB) - you may want to try using a CAT5 cable and connect it to a real network card if you can, as there are many other posts out there about problems with this driver, only when USB-connected.

Upgrade the driver (if possible), and also upgrade ndis.sys to be safe.

0

Share this post


Link to post
Share on other sites

great thnx, yea its connected usb i have to get another cable i misplaced my original...i updated the motorola driver to i think the latest driver available for it now how do i fill out the form to request the hotifx?

what do i put for kb article number and product version affected?

Edited by Dj Walker
0

Share this post


Link to post
Share on other sites
great thnx, yea its connected usb i have to get another cable i misplaced my original...i updated the motorola driver to i think the latest driver available for it now how do i fill out the form to request the hotifx?

what do i put for kb article number and product version affected?

KB is 918837

Product is Windows XP

Platform is x86

Language is probably English from your flag

Email address is your email address you want Microsoft to send the link to download the file to

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.