Dj Walker Posted November 6, 2007 Share Posted November 6, 2007 (edited) Hi i recently got a new system its running xp and it seems to be restarting frequentlyi get these errors on restartBCCode : 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.dmpC:\DOCUME~1\THEDEV~1\LOCALS~1\Temp\WER73b4.dir00\sysdata.xmlBCCode : fe BCP1 : 00000002 BCP2 : 855D0438 BCP3 : 85670008 BCP4 : 8642AF30 OSVer : 5_1_2600 SP : 2_0 Product : 256_1so i tried searching the errors and found this site did a reading 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 November 6, 2007 by Dj Walker Link to comment Share on other sites More sharing options...
cluberti Posted November 6, 2007 Share Posted November 6, 2007 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? Link to comment Share on other sites More sharing options...
Dj Walker Posted November 7, 2007 Author Share Posted November 7, 2007 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 settingshow should i do this can you please explain? Link to comment Share on other sites More sharing options...
cluberti Posted November 7, 2007 Share Posted November 7, 2007 Try start > run > verifier.exe > click OKCheck the box for "Special Pool"Select "Verify all Drivers"click Apply and then ExitThen 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 . Link to comment Share on other sites More sharing options...
Dj Walker Posted November 7, 2007 Author Share Posted November 7, 2007 (edited) Try start > run > verifier.exe > click OKCheck the box for "Special Pool"Select "Verify all Drivers"click Apply and then ExitThen 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 November 7, 2007 by Dj Walker Link to comment Share on other sites More sharing options...
cluberti Posted November 7, 2007 Share Posted November 7, 2007 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 Next2. Click "Select individual settings from a full list", then Next3. Click the box for "Special pool", then Next4. Click "Automatically select all drivers installed on this computer", then Finish Link to comment Share on other sites More sharing options...
Dj Walker Posted November 7, 2007 Author Share Posted November 7, 2007 (edited) hope i got this right lolheres the minidumpMini110707_19.zip Edited November 7, 2007 by Dj Walker Link to comment Share on other sites More sharing options...
cluberti Posted November 7, 2007 Share Posted November 7, 2007 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 bugcheck8055621c 000000c280556220 0000000780556224 00000cd480556228 020a00038055622c 86ef849880556230 0000000080556234 80556284 nt+0x7f284 // Driver verifier80556238 80550fc5 nt+0x79fc5 // The pool free call8055623c 000000c280556240 0000000780556244 00000cd480556248 020a00038055624c 86ef849880556250 86ef849880556254 87145f5080556258 000000008055625c 870a37b080556260 870a378880556264 0000000080556268 86ef84e08055626c 0000000080556270 f7586ed0 NDIS!NdisAcquireSpinLock+0x1180556274 f7586eee NDIS!NdisReleaseSpinLock+0x11 // The call into ndis from the driver80556278 80556290 nt+0x7f2908055627c 0000000080556280 0000000180556284 80556294 nt+0x7f29480556288 805503e3 nt+0x793e38055628c 86ef849880556290 0000000080556294 805562d4 nt+0x7f2d480556298 f7c4d135 NetMotCM+0x2135 // The driver that likely is the problem8055629c 86ef8498805562a0 86ffc9b7805562a4 86ffc8d8805562a8 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 ebp8055623b 80c200 add dl,08055623e 0000 add byte ptr [eax],al80556240 07 pop es80556241 0000 add byte ptr [eax],al80556243 00d4 add ah,dl80556245 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],ah80556237 80c50f add ch,0Fh8055623a 55 push ebp8055623b 80c200 add dl,08055623e 0000 add byte ptr [eax],al80556240 07 pop es80556241 0000 add byte ptr [eax],al80556243 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,98F7C4D1h8055629d 84ef test bh,ch8055629f 86b7c9ff86d8 xchg dh,byte ptr [edi-27790037h]805562a5 c8ff86ff enter 86FFh,0FFh805562a9 184e80 sbb byte ptr [esi-80h],cl805562ac 0000 add byte ptr [eax],al805562ae 0000 add byte ptr [eax],al805562b0 d8c8 fmul st,st(0)// NetMotCM looks like a driver compiled just after XP RTM'ed (before SP1, even):0: kd> lmvm NetMotCMstart end module namef7c4b000 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.04e0I'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. Link to comment Share on other sites More sharing options...
Dj Walker Posted November 7, 2007 Author Share Posted November 7, 2007 (edited) 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 November 7, 2007 by Dj Walker Link to comment Share on other sites More sharing options...
cluberti Posted November 7, 2007 Share Posted November 7, 2007 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 918837Product is Windows XPPlatform is x86Language is probably English from your flagEmail address is your email address you want Microsoft to send the link to download the file to Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now