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

BSoD after switching from vista to XP


  • Please log in to reply
6 replies to this topic

#1 Kodi Anderson

Kodi Anderson

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:03 AM

Posted 09 May 2009 - 08:11 PM

a few months ago I switched my laptop from vista to XP. I got all the appropriate drivers, and slipstreamed them into my installation disk. Everything went fine at first, then a few weeks after switching I began to blue screen. was only once a week or so, and wasnt a big deal at the time, so I didn't mind it. lately it has been happening 3-4 times a day. I am using Windows XP Pro SP3.
the stop code I get is:
STOP: 0x0000010D (0x00000002, 0x88EE8054, 0x00000000, 0x896A2E38)
I thought it might be that a critical driver might be out of date, but I checked them all, and they all seemed to be up to date..
Any and all help is greatly appreciated!

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,726 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 AM

Posted 09 May 2009 - 08:48 PM

http://www.faultwire.com/solutions/fatal_e...rk+has+detected

http://www.bleepingcomputer.com/forums/t/141725/keep-getting-bsods-happening-more-and-more-frequently/

http://www.bleepingcomputer.com/forums/t/203313/windows-driver-framework-stop-error-bsod-fun/

I suggest following the approach suggested by USASMA and posting results here.

Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Louis

#3 Kodi Anderson

Kodi Anderson
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:03 AM

Posted 09 May 2009 - 09:32 PM

First off, that was an extremely fast response, thank you!
according to faultwire, my stop code means this : "An attempt is being made to acquire a lock that is currently being held. "
I'm not exactly sure what that means, though..
dump file analysis report:

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

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 00000002, An attempt is being made to acquire a lock that is currently
being held. The lock in question can be determined by examining
the caller's stack.
Arg2: 89259054, Reserved.
Arg3: 00000000, Reserved.
Arg4: 8988c210, Reserved.

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


BUGCHECK_STR: 0x10D_2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from a44a1e81 to 80537672

STACK_TEXT:
80556d40 a44a1e81 0000010d 00000002 89259054 nt!KeBugCheckEx+0x1b
80556d5c a44ac517 8988c210 00000002 89259054 Wdf01000!FxVerifierBugCheck+0x24
80556d7c a4490aa6 80556d9f 892591c8 88fd12b0 Wdf01000!FxCallbackSpinLock::Lock+0x63
80556d94 f77513c5 8988c2c8 89259000 89a8e030 Wdf01000!imp_WdfObjectAcquireLock+0xaa
WARNING: Stack unwind information not available. Following frames may be wrong.
80556db4 a44ab680 76da6ff8 88fd13d4 88df54c0 motmodem+0x23c5
80556dd4 a44abd4d 88fd12b0 80556e04 804e13c9 Wdf01000!FxDevice::PreprocessIrp+0x7b
80556de0 804e13c9 89a8e030 88fd12b0 88fd12b0 Wdf01000!FxDevice::Dispatch+0x32
80556df0 ab3a8ce4 88fd12b0 89aaf268 89029008 nt!IopfCallDriver+0x31
80556e04 804e13c9 88fd13d4 88fd12b0 893faac8 Modem!UniRead+0x4a
80556e14 a5044dbf 89029008 893faac8 00000000 nt!IopfCallDriver+0x31
80556e2c a5044e4d 88eb7028 88fd13d7 88fd12b0 asyncmac!AsyncPPPRead+0x12f
80556e44 804e18ef 00000000 88fd12b0 893faac8 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b
80556e74 ab3a470c 80556e9c ab3a9122 00000009 nt!IopfCompleteRequest+0xa2
80556e7c ab3a9122 00000009 88fd12b0 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c
80556e9c ab3a8450 88df5408 88df54c8 88df5514 Modem!UniGetNextIrp+0x58
80556edc ab3a9096 88df54c0 88df5408 001b0048 Modem!UniMaskStarter+0x29a
80556ef4 ab3a9211 88df54c0 88df54c8 88fd12b0 Modem!UniStartOrQueue+0x5e
80556f1c ab3a7a76 88df5408 88fd12b0 88fd12b0 Modem!UniCheckPassThrough+0x73
80556f50 804e13c9 88df5408 88fd12b0 893faac8 Modem!UniIoControl+0x60e
80556f60 a5044ae9 890290b9 890290f5 893faac8 nt!IopfCallDriver+0x31
80556f74 a5044c7e 893faac8 00000000 8924e12f asyncmac!AsyncPPPWaitMask+0x53
80556f9c 804e18ef 00000000 890290b8 00000001 asyncmac!AsyncPPPCompletionRoutine+0x188
80556fcc f7751454 89a8e030 00000003 88df5403 nt!IopfCompleteRequest+0xa2
80556fe4 a44ab680 76da6ff8 0000003c 88df54c0 motmodem+0x2454
80557004 a44abd4d 8924e008 80557034 804e13c9 Wdf01000!FxDevice::PreprocessIrp+0x7b
80557010 804e13c9 89a8e030 8924e008 8924e008 Wdf01000!FxDevice::Dispatch+0x32
80557020 ab3a8ce4 8924e008 89aaf268 89029008 nt!IopfCallDriver+0x31
80557034 804e13c9 8924e12c 8924e008 893faac8 Modem!UniRead+0x4a
80557044 a5044dbf 89029008 893faac8 00000000 nt!IopfCallDriver+0x31
8055705c a5044e4d 88eb7028 8924e12f 8924e008 asyncmac!AsyncPPPRead+0x12f
80557074 804e18ef 00000000 8924e008 893faac8 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b
805570a4 ab3a470c 805570cc ab3a7d95 00000005 nt!IopfCompleteRequest+0xa2
805570ac ab3a7d95 00000005 8924e008 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c
805570cc ab3a8f1f 88df54c0 80557134 00000001 Modem!UniRundownShuttledWait+0xa3
805570fc ab3a97ce 88df5402 00000002 00000002 Modem!UniPostProcessShuttledWaits+0x43
80557164 804e18ef 88df5408 88fa1e02 00000002 Modem!UniSniffWaitComplete+0xe6
80557194 a44da6b4 88f16578 805571cc a44a5994 nt!IopfCompleteRequest+0xa2
805571a0 a44a5994 00000002 a44e0118 88f16578 Wdf01000!FxIrp::CompleteRequest+0x13
805571cc a44a7938 00000000 00000002 8988c210 Wdf01000!FxRequest::CompleteInternal+0x4e9
805571e8 a44a795c 00000000 00000002 80557214 Wdf01000!FxRequest::Complete+0xb3
805571f8 a4490fd4 00000000 00000004 80557250 Wdf01000!FxRequest::CompleteWithInformation+0x18
80557214 f7751c43 88f16578 770e9a80 00000000 Wdf01000!imp_WdfRequestCompleteWithInformation+0x7f
8055726c a448c426 7675f9a8 89255048 0000003c motmodem+0x2c43
8055729c a44ad245 77132328 7675f9a8 8995533c Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+0x3e
805572c4 a44845d3 891b84fb 898a0650 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x89
805572e0 a448468d 01ecdcd0 8951d3e8 8055730c Wdf01000!FxIoTarget::RequestCompletionRoutine+0x195
805572f0 8050da17 00000000 891b8440 88ecdcd0 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8055730c 804e18ef 00000000 891b8440 8951d3e8 nt!IopUnloadSafeCompletion+0x1d
8055733c b61140d5 891b8440 88e99ec8 899c0028 nt!IopfCompleteRequest+0xa2
805573a4 b6114d47 89955384 00000000 899c07d8 USBPORT!USBPORT_CompleteTransfer+0x373
805573d4 b6115944 026e6f44 899c0028 899c00e0 USBPORT!USBPORT_DoneTransfer+0x137
8055740c b6115e98 899c0028 80561f20 ffdff9c0 USBPORT!USBPORT_FlushDoneTransferList+0x16c
80557428 804dcd12 899c066c 2b667274 00000000 USBPORT!USBPORT_TransferFlushDpc+0x9a
80557450 804dcbf7 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80557454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
motmodem+23c5
f77513c5 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: motmodem+23c5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: motmodem

IMAGE_NAME: motmodem.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4611b85d

FAILURE_BUCKET_ID: 0x10D_2_motmodem+23c5

BUCKET_ID: 0x10D_2_motmodem+23c5

Followup: MachineOwner
---------

EDIT: I forgot to mention, I have been using Ccleaner to well, clean things up as a result I didnt have any .dmps, so I had to wait for it to BSOD again, which wasnt long..

Edited by Kodi Anderson, 09 May 2009 - 09:35 PM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,726 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 AM

Posted 10 May 2009 - 12:16 PM

Looks like this file is your problem, http://www.prevx.com/filenames/27188897867...TMODEM.SYS.html

I would try uninstalling it (do a search of your system to ensure that it's there and check the device it supports) via Device Manager...then reinstalling.

Louis

#5 Kodi Anderson

Kodi Anderson
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:03 AM

Posted 10 May 2009 - 09:31 PM

Hmm, motmodem.sys is on my computer in 4 different locations. I get my internet from alltel, and I get it by hooking my motorolla phone to my computer, so these are drivers I need to access the internet..I clicked the "motorola driver installation" item that was in my add or remove programs list, and it told me that it wasnt working properly, heh. I'll download the latest drivers and report back!

#6 Kodi Anderson

Kodi Anderson
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:03 AM

Posted 10 May 2009 - 11:59 PM

After replacing the driver in question, the BSoD's have stopped! Thank you very much Louis for all of your help!

#7 hamluis

hamluis

    Moderator


  • Moderator
  • 55,726 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 AM

Posted 11 May 2009 - 09:49 AM

LOL, sometimes I get lucky...happy computing :thumbsup:.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users