BSOD: BCCode d1; BCP1:1; BCP2:2; BCP3:0; BCP4:FFFFF8800737F02F

[rifaats]

Hi

I'd like to ask for help on the BOSD problem occurred with the following Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: 0000000000000001
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800737F02F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Appreciate any help to identify the cause of such problem.

attached: SF_07-12-2013.zip and SF_07-12-2013-old.zip for more details

Thanks

Rifaat

 

[Arc]

Hi rifaats.

Uninstall McAfee Security Scan Plus. It is a harmful bundled junk comes with various dounloads including Adobe Flash player. From teh next time, if you update flash player manually, make it sure that you are unchecking the download option for McAfee Security Scan Plus.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

The latest BSOD is a BUGCODE_USB_DRIVER, BugCheck FE. So some of the USB drivers are causing the issue there.

The just previous one directly identifies applebmt.sys, Apple Wireless Mouse driver (c:\windows\system32\drivers\applebmt.sys) as the cause of the DSOD. And the driver is old enough, of 2011. Update the driver from Apple - Support . As I have almost nil knowledge about MCA/apple, unfortunately I cannot be any more specific about to what is to download exactly. If there is no feasible update, better you try with another mouse and observe the situation.

Also, try to delete the following, devices. So many of them modems are always problematic.

• SAMSUNG Mobile USB Modem
• Nokia N900 USB Modem
• ZTE Proprietary USB Modem
• HUAWEI Mobile Connect - 3G Network Card
• HTC Remote NDIS based Device

And update the following drivers, if you use bluetooth; otherwise better to disable those, too.

• AM USB Stroage Driver, DS card controller from ALCOR MICRO - Storage Product > SD Card Controller
• Broadcom Bluetooth USB LD Filter from Bluetooth Software Download | Broadcom

Let us know the results.
_________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa800a1cc1a0, 80863b3c, fffffa800aa2ac48}

Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: fffffa800a1cc1a0, Device extension pointer of the host controller
Arg3: 0000000080863b3c, PCI Vendor,Product id for the controller
Arg4: fffffa800aa2ac48, Pointer to Endpoint data structure

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88004073fea to fffff80003a90bc0

STACK_TEXT:  
fffff880`033fda58 fffff880`04073fea : 00000000`000000fe 00000000`00000005 fffffa80`0a1cc1a0 00000000`80863b3c : nt!KeBugCheckEx
fffff880`033fda60 fffff880`0403afac : 00000000`bb007200 fffffa80`0a1cd6a0 00000000`00000000 fffffa80`0aa2aee0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`033fdaa0 fffff880`0403ab73 : fffffa80`0aa2ac48 fffffa80`06ce3c00 fffffa80`0aa2aee0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
fffff880`033fdb30 fffff880`0403fe65 : fffffa80`0aa2ac48 00000000`00000000 00000000`00000000 00000000`00000003 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff880`033fdb70 fffff880`04047e8b : 00000000`00000002 fffffa80`0a1cc1a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0x41
fffff880`033fdbb0 fffff880`0404c9dd : 00000000`00000040 00000000`00000004 fffffa80`0aa2aa00 fffffa80`0a1cc050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`033fdbe0 fffff880`04058077 : fffffa80`0a1cc1a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`033fdc40 fffff880`04048f89 : fffffa80`0a1cc050 00000000`00000000 fffffa80`0a1cca02 fffffa80`0a1cca18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`033fdca0 fffff800`03a9b30c : fffff880`033d5180 fffffa80`0a1cca18 fffffa80`0a1cca30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`033fdcd0 fffff800`03a888ca : fffff880`033d5180 fffff880`033e00c0 00000000`00000000 fffff880`04048db0 : nt!KiRetireDpcList+0x1bc
fffff880`033fdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_sMode_PollEndpointSlot+6c
fffff880`0403afac 4533c9          xor     r9d,r9d

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5227237f

FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c

BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c

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

3: kd> lmvm usbehci
start             end                 module name
fffff880`04035000 fffff880`04046000   usbehci    (pdb symbols)          c:\symbols\usbehci.pdb\DA3C121440AF4C048BFBCB09271432AF1\usbehci.pdb
    Loaded symbol image file: usbehci.sys
    Mapped memory image file: c:\symbols\usbehci.sys\5227237F11000\usbehci.sys
    Image path: \SystemRoot\system32\drivers\usbehci.sys
    Image name: usbehci.sys
    Timestamp:        Wed Sep 04 17:41:43 2013 (5227237F)
    CheckSum:         000145DA
    ImageSize:        00011000
    File version:     6.1.7601.18251
    Product version:  6.1.7601.18251
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     USBEHCI.sys
    OriginalFilename: USBEHCI.sys
    ProductVersion:   6.1.7601.18251
    FileVersion:      6.1.7601.18251 (win7sp1_gdr.130903-1532)
    FileDescription:  EHCI eUSB Miniport Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1, 2, 0, fffff88007e8a02f}

*** WARNING: Unable to verify timestamp for applebmt.sys
*** ERROR: Module load completed but symbols could not be loaded for applebmt.sys
Probably caused by : applebmt.sys ( applebmt+902f )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007e8a02f, address which referenced memory

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cc0100
GetUlongFromAddress: unable to read from fffff80003cc01c0
 0000000000000001 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
applebmt+902f
fffff880`07e8a02f 8a4301          mov     al,byte ptr [rbx+1]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033fcce0 -- (.trap 0xfffff880033fcce0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a48a900 rbx=0000000000000000 rcx=fffffa8009d906f0
rdx=fffffa800a48af28 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007e8a02f rsp=fffff880033fce70 rbp=0000000000000000
 r8=fffff88007e8e140  r9=0000057ff4f50ff8 r10=fffffa8006d38710
r11=fffff880033fcdf8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
applebmt+0x902f:
fffff880`07e8a02f 8a4301          mov     al,byte ptr [rbx+1] ds:00000000`00000001=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a88169 to fffff80003a88bc0

STACK_TEXT:  
fffff880`033fcb98 fffff800`03a88169 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033fcba0 fffff800`03a86de0 : 00000000`00000004 fffff880`033fcd70 fffffa80`0ae93c10 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`033fcce0 fffff880`07e8a02f : fffffa80`09d906f0 fffffa80`0a48a900 fffff880`033fced0 fffffa80`09b3c8b0 : nt!KiPageFault+0x260
fffff880`033fce70 fffffa80`09d906f0 : fffffa80`0a48a900 fffff880`033fced0 fffffa80`09b3c8b0 00000000`00000000 : applebmt+0x902f
fffff880`033fce78 fffffa80`0a48a900 : fffff880`033fced0 fffffa80`09b3c8b0 00000000`00000000 fffffa80`0b0b18b0 : 0xfffffa80`09d906f0
fffff880`033fce80 fffff880`033fced0 : fffffa80`09b3c8b0 00000000`00000000 fffffa80`0b0b18b0 fffffa80`0b0b18b0 : 0xfffffa80`0a48a900
fffff880`033fce88 fffffa80`09b3c8b0 : 00000000`00000000 fffffa80`0b0b18b0 fffffa80`0b0b18b0 fffff880`00ec0ce7 : 0xfffff880`033fced0
fffff880`033fce90 00000000`00000000 : fffffa80`0b0b18b0 fffffa80`0b0b18b0 fffff880`00ec0ce7 fffffa80`09d906f0 : 0xfffffa80`09b3c8b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
applebmt+902f
fffff880`07e8a02f 8a4301          mov     al,byte ptr [rbx+1]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  applebmt+902f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: applebmt

IMAGE_NAME:  applebmt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddcaed2

FAILURE_BUCKET_ID:  X64_0xD1_applebmt+902f

BUCKET_ID:  X64_0xD1_applebmt+902f

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

3: kd> lmvm applebmt
start             end                 module name
fffff880`07e81000 fffff880`07e94000   applebmt T (no symbols)           
    Loaded symbol image file: applebmt.sys
    Image path: \SystemRoot\system32\DRIVERS\applebmt.sys
    Image name: applebmt.sys
    Timestamp:        Wed May 25 12:55:06 2011 (4DDCAED2)
    CheckSum:         00014242
    ImageSize:        00013000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[rifaats]

Hi Arc

Following your guiding steps, BSOD stopped happening, I will monitor for more 2 days just to be sure.

As for the McAfee, what is your recommendation for the best replacement?

Thanks a lot for your help

Rifaat

 

[Arc]

As for the McAfee, what is your recommendation for the best replacement?

I personally use Microsoft Security Essentials with windows inbuilt firewall, and free MBAM as the on demand scanner.

As I use this combination, obviously I believe that it is enough of security