Intermittent BSOD

By iceecat
Apr 12, 2008
Topic Status:
Not open for further replies.
  1. ok guys looking for a little assistance. I just built this machine so everything is new and clean install. this is the most recent BSOD event. Attached is the .xml file with all info on problem and computer set up. Most are BCCode 44 and I cannot figure the driver problem that is occurring. All drivers are the latest downloaded from nvidia and vista certified. The only driver I installed with the actual MB disk was the onboard sound. ALL other MB drivers came from Nvidia website as well as video drivers although problem occurred before video drivers were installed.

    Problem Event Name: BlueScreen
    OS Version: 6.0.6000.2.0.0.768.3
    Locale ID: 1033
    BCCode: 44
    BCP1: 84A76DE0
    BCP2: 00000E71
    BCP3: 00000000
    BCP4: 00000000
    OS Version: 6_0_6000
    Service Pack: 0_0
    Product: 768_1
    Server information: 08ba847e-1421-434b-9977-c7bed1d52feb
  2. raybay

    raybay TechSpot Evangelist Posts: 10,716   +6

    Memory error? Are you using mixed modules? Any value ram or other budget memory? This is a VISTA machine with what nVidia card?
  3. Matthew

    Matthew TechSpot Staff Posts: 6,043   +84 Staff Member

    Try posting the .dmp files located in C:\Windows\Minidump.
  4. iceecat

    iceecat Newcomer, in training Topic Starter

    mini dump attachements

    attempted to attach the minidump files which are ~135 to 140k files. This board wont let me attach them?? says 100k is the limit on the file space. Somewhere else I can send them perhaps?? Or give me another way of opening and sending them??

    Also thanks for the response fellas!!!! I appreciate it
    chris
  5. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    You can zip them first and then you'll be able to attach up to 5 per zip.
  6. iceecat

    iceecat Newcomer, in training Topic Starter

    gunna have to download a zip program....just built this machine and it does not have much to it yet....another quick suggestion perhaps

    I guess I could debug them and post the info
  7. Matthew

    Matthew TechSpot Staff Posts: 6,043   +84 Staff Member

    Highlight the files > Right click on them > Send To > Compressed (zipped) Folder.

    That will do what needs to be done...
  8. iceecat

    iceecat Newcomer, in training Topic Starter

    here is the latest dmp file that occured while I was attempting to post this post. It points to my cable modem driver??? I have the most current driver for this although it is 2003 in date?? New modem perhaps. Although a couple of the other minidumps discuss other drivers this is the most prominent one. Any suggestions??



    if you need more dumps I will post them out ......you guys are great!!!!


    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini041208-04.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is:
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16584.x86fre.vista_gdr.071023-1545
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Sat Apr 12 14:52:12.672 2008 (GMT-7)
    System Uptime: 0 days 7:22:05.718
    Loading Kernel Symbols
    ....................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 44, {85e623a8, e71, 0, 0}

    *** WARNING: Unable to verify timestamp for BEFCM3XP.sys
    *** ERROR: Module load completed but symbols could not be loaded for BEFCM3XP.sys
    Unable to load image \SystemRoot\system32\DRIVERS\netimflt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for netimflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for netimflt.sys


    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MULTIPLE_IRP_COMPLETE_REQUESTS (44)
    A driver has requested that an IRP be completed (IoCompleteRequest()), but
    the packet has already been completed. This is a tough bug to find because
    the easiest case, a driver actually attempted to complete its own packet
    twice, is generally not what happened. Rather, two separate drivers each
    believe that they own the packet, and each attempts to complete it. The
    first actually works, and the second fails. Tracking down which drivers
    in the system actually did this is difficult, generally because the trails
    of the first driver have been covered by the second. However, the driver
    stack for the current request can be found by examining the DeviceObject
    fields in each of the stack locations.
    Arguments:
    Arg1: 85e623a8, Address of the IRP
    Arg2: 00000e71
    Arg3: 00000000
    Arg4: 00000000

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




    IRP_ADDRESS: 85e623a8

    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x44

    PROCESS_NAME: Idle

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 81caceae to 81cd8681

    STACK_TEXT:
    8248b47c 81caceae 00000044 85e623a8 00000e71 nt!KeBugCheckEx+0x1e
    8248b4bc 8cc2d79e 85e623a8 4f445048 8248b4e0 nt!IopfCompleteRequest+0x4ac
    8248b4cc 8cc09c92 874b8030 85e623a8 874b8030 usbhub!UsbhPdoSuccess+0x3e
    8248b4e0 81c27f83 874b8030 85e623a8 87330438 usbhub!UsbhGenDispatch+0x4a
    8248b4f8 8e3ea350 8736510c 87361f70 87365008 nt!IofCallDriver+0x63
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8248b51c 8e3e8b05 00000001 8736510c 00000036 BEFCM3XP+0x2350
    8248b550 8e3e9036 00000036 868fe0e8 868fe0e8 BEFCM3XP+0xb05
    8248b56c 81bc68eb 00000001 8248b5ec 00000001 BEFCM3XP+0x1036
    8248b594 81bc40a7 8248b5f0 8248b5ec 00000001 ndis!ndisMSendPacketsXToMiniport+0x141
    8248b5cc 81bc4e2a 876f6098 8248b5ec 00000001 ndis!ndisMSendPackets+0x1b4
    8248b5e0 81bc772b 876f6098 85df5e58 8248b620 ndis!ndisMSend+0x13
    8248b5f0 8ccb2fac 8248b614 876f6098 85df5e58 ndis!NdisSend+0xf
    8248b620 8ccb057c 87718740 84c13e28 86c26488 netimflt+0xafac
    8248b644 81bc68eb 8733d528 8248b68c 00000001 netimflt+0x857c
    8248b66c 81bc6732 8248b690 8248b68c 00000001 ndis!ndisMSendPacketsXToMiniport+0x141
    8248b6d4 81affae4 86c26488 85bedb60 00000000 ndis!ndisMSendNetBufferListsToPackets+0x84
    8248b6f4 81affb98 85bedb60 85bedb60 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
    8248b70c 8d80ae58 873633e8 85bedb60 00000000 ndis!NdisFSendNetBufferLists+0x18
    8248b788 81affb76 8771d6f8 85bedb60 00000000 pacer!PcFilterSendNetBufferLists+0x232
    8248b7a4 81bc364a 85bedb60 85bedb60 00000000 ndis!ndisSendNBLToFilter+0x87
    8248b7c8 8d8c84df 874c4c58 85bedb60 00000000 ndis!NdisSendNetBufferLists+0x4f
    8248b860 8d8c69c1 8771a680 00000000 8248b9e4 tcpip!FlSendPackets+0x4b7
    8248b8a0 8d8c7ff6 8d9119c8 00000000 00000000 tcpip!IppFragmentPackets+0x203
    8248b8d8 8d8c768d 8d9119c8 8248b9e4 8d9119c8 tcpip!IppDispatchSendPacketHelper+0x259
    8248b970 8d8c6e8d 0048b9e4 8248bb20 84adad60 tcpip!IppPacketizeDatagrams+0x7ea
    8248bac8 8d8c9376 00000000 00000007 8d9119c8 tcpip!IppSendDatagramsCommon+0x4ab
    8248bae8 8d89860e 86b97458 8248bb00 86b97458 tcpip!IpNlpSendDatagrams+0x4b
    8248bb70 8d89856a 86b97458 8248bc50 00000000 tcpip!IppSlowSendDatagram+0x3e
    8248bbc0 8d8ce114 86b97458 8248bc01 8248bc50 tcpip!IpNlpFastSendDatagram+0x3fd
    8248bc88 8d8bd4f5 00000000 87f810c0 00000002 tcpip!TcpTcbHeaderSend+0x434
    8248bcb8 8d8bc74c 8249b120 8248bd40 87277410 tcpip!TcpFlushDelay+0x122
    8248bce8 81ca93ae 87277410 00000001 76eb5452 tcpip!TcpPeriodicTimeoutHandler+0x3be
    8248bd50 81c913ee 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
    8248bd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    BEFCM3XP+2350
    8e3ea350 ?? ???

    SYMBOL_STACK_INDEX: 5

    SYMBOL_NAME: BEFCM3XP+2350

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: BEFCM3XP

    IMAGE_NAME: BEFCM3XP.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 3eae3f47

    FAILURE_BUCKET_ID: 0x44_BEFCM3XP+2350

    BUCKET_ID: OLD_IMAGE_BEFCM3XP.sys

    Followup: MachineOwner
  9. Matthew

    Matthew TechSpot Staff Posts: 6,043   +84 Staff Member

    Please, it's much easier for us (or me anyway) if you just attach the .dmp files.
  10. iceecat

    iceecat Newcomer, in training Topic Starter

    minidump files

    here are the dmp files for the last 3 days as well as the one that just occured...grrr...again

    thanks again guys
    chris
  11. Matthew

    Matthew TechSpot Staff Posts: 6,043   +84 Staff Member

    Minidump 040908-01:

    BugCheck 44, {892c37f0, e71, 0, 0}
    Probably caused by : USBPORT.SYS (USBPORT!USBPORT_Core_iCompleteDoneTransfer+6cb)

    -------------------------------------------------------------------------
    Minidump 040908-02:

    BugCheck 44, {84788008, e71, 0, 0}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

    -------------------------------------------------------------------------
    Minidump 040908-03:

    BugCheck 44, {84673e20, e71, 0, 0}
    Probably caused by : USBPORT.SYS (USBPORT!USBPORT_Core_iCompleteDoneTransfer+6cb)

    -------------------------------------------------------------------------
    Minidump 041108-01:

    BugCheck 44, {892c37f0, e71, 0, 0}
    Probably caused by : USBPORT.SYS (USBPORT!USBPORT_Core_iCompleteDoneTransfer+6cb)

    -------------------------------------------------------------------------
    Minidump 041108-02:

    BugCheck 44, {85c76de0, e71, 0, 0}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

    -------------------------------------------------------------------------
    Minidump 041108-03:

    BugCheck 44, {892c37f0, e71, 0, 0}
    Probably caused by : USBPORT.SYS (USBPORT!USBPORT_Core_iCompleteDoneTransfer+6cb)

    -------------------------------------------------------------------------
    Minidump 041108-04:

    BugCheck 44, {84bfd968, e71, 0, 0}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

    -------------------------------------------------------------------------
    Minidump 041108-03:

    BugCheck 44, {892c37f0, e71, 0, 0}
    Probably caused by : USBPORT.SYS (USBPORT!USBPORT_Core_iCompleteDoneTransfer+6cb)

    -------------------------------------------------------------------------
    Minidump 041208-01:

    BugCheck 44, {8467c008, e71, 0, 0}
    Probably caused by : USBPORT.SYS (USBPORT!USBPORT_Core_iCompleteDoneTransfer+6cb)

    -------------------------------------------------------------------------
    Minidump 041208-02:

    BugCheck 44, {84a76de0, e71, 0, 0}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

    -------------------------------------------------------------------------
    Minidump 041208-03:

    BugCheck 44, {84b04808, e71, 0, 0}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

    -------------------------------------------------------------------------
    Minidump 041208-04:

    BugCheck 44, {85e623a8, e71, 0, 0}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+2350 )

    -------------------------------------------------------------------------
    Minidump 041208-06:

    BugCheck A, {0, 2, 0, 81c27fa1}
    Probably caused by : BEFCM3XP.sys ( BEFCM3XP+1fa8 )

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

    Details behind BEFCM3XP.sys according to runscanner.net:

    Company: Linksys Corporation.
    Product: Linksys BEFCMU10 EtherFast Cable Modem
    Description: NDIS5.1 miniport driver v1.10 Build 002

    Points to your modem indeed...
     
  12. iceecat

    iceecat Newcomer, in training Topic Starter

    yeah....thanks lynksys. Well very cool then I am on the right track. I appreciate the feedback so very much.

    I will have to do some work on the lynksys thing. Their driver/support on the web is rather crappy, but I will deal with that for now and see what I can do.

    thanks again
    chris
  13. Matthew

    Matthew TechSpot Staff Posts: 6,043   +84 Staff Member

    You're welcome, iceecat.

    You could try updating it's firmware (should be done anyway) and reinstalling your USB drivers. Not sure what good it'd do but, never know I guess.
  14. iceecat

    iceecat Newcomer, in training Topic Starter

    Thanks again Zenosincks....I just went ahead and rid the computer of the drivers all together and just plugged in the ethernet chord. It corrected the problem. Problem free and might even think Vista is alright.....just thinking though
  15. Matthew

    Matthew TechSpot Staff Posts: 6,043   +84 Staff Member

    :) Good for you. Hopefully that solved it eh?
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.