BSOD on resource-intensive tasks

alanblack · 04 Jul 2014

Hi Guys,

I've been having BSODs for a few months now and finally got round to trying to sort it. It seems to happen when I perform resource-intensive tasks, such as playing Starcraft II or streaming high-quality films. I've had the computer for about 3 and a half years and it has been fine until this current problem.

I've tried updating and reinstalling drivers and also wiping the hard-drive and reinstalling windows. I have also opened the box and checked the components for any obvious damage. I am running out of ideas and would be very grateful for any advice - From what I can deduce it seems likely to be a hardware problem?

Many thanks, Alan.

HarriePateman · 04 Jul 2014

Okay i have had a look:

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff880633a62a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880633a62a0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031090e0
GetUlongFromAddress: unable to read from fffff80003109198
 fffff880633a62a0 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
+4a42c3471459359
fffff880`633a62a0 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  SearchIndexer.

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

DPC_STACK_BASE:  FFFFF880030B7FB0

TRAP_FRAME:  fffff880030b7cd0 -- (.trap 0xfffff880030b7cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000acc94a6d rbx=0000000000000000 rcx=fffffa800882d050
rdx=fffffa800882dd28 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880633a62a0 rsp=fffff880030b7e68 rbp=0000000000000000
 r8=0000000043787254  r9=00000000ffffffff r10=fffffa800882d1a0
r11=0000000000026161 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff880`633a62a0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed0de9 to fffff80002ed1880

FAILED_INSTRUCTION_ADDRESS: 
+4a42c3471459359
fffff880`633a62a0 ??              ???

STACK_TEXT:  
fffff880`030b7b88 fffff800`02ed0de9 : 00000000`0000000a fffff880`633a62a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`030b7b90 fffff800`02ecfa60 : fffffa80`0b2b6290 fffffa80`0882d050 fffffa80`08c62ae0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b7cd0 fffff880`633a62a0 : fffff880`06b11a13 fffffa80`0882d050 fffffa80`0882dd02 fffff880`030b7ed8 : nt!KiPageFault+0x260
fffff880`030b7e68 fffff880`06b11a13 : fffffa80`0882d050 fffffa80`0882dd02 fffff880`030b7ed8 fffffa80`0882d1a0 : 0xfffff880`633a62a0
fffff880`030b7e70 fffffa80`0882d050 : fffffa80`0882dd02 fffff880`030b7ed8 fffffa80`0882d1a0 fffffa80`0882dd28 : USBPORT!USBPORT_Xdpc_iBegin+0x3
fffff880`030b7e78 fffffa80`0882dd02 : fffff880`030b7ed8 fffffa80`0882d1a0 fffffa80`0882dd28 fffff880`06b115c2 : 0xfffffa80`0882d050
fffff880`030b7e80 fffff880`030b7ed8 : fffffa80`0882d1a0 fffffa80`0882dd28 fffff880`06b115c2 00000000`00000000 : 0xfffffa80`0882dd02
fffff880`030b7e88 fffffa80`0882d1a0 : fffffa80`0882dd28 fffff880`06b115c2 00000000`00000000 00000000`00000022 : 0xfffff880`030b7ed8
fffff880`030b7e90 fffffa80`0882dd28 : fffff880`06b115c2 00000000`00000000 00000000`00000022 00000000`00000000 : 0xfffffa80`0882d1a0
fffff880`030b7e98 fffff880`06b115c2 : 00000000`00000000 00000000`00000022 00000000`00000000 00000000`ffffffff : 0xfffffa80`0882dd28
fffff880`030b7ea0 fffff880`06b11f89 : fffffa80`0882d050 00000000`00000000 fffffa80`0882dd02 fffffa80`0882dd28 : USBPORT!USBPORT_Xdpc_iSetState+0x2a
fffff880`030b7ed0 fffff800`02edcf7c : fffff880`03088180 fffffa80`0882dd28 fffffa80`0882dd40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b7f00 fffff800`02ed7a05 : 0000058a`00000000 fffffa80`0a81e6a0 00000000`00000000 fffff880`06b11db0 : nt!KiRetireDpcList+0x1bc
fffff880`030b7fb0 fffff800`02ed781c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0b041890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Xdpc_iBegin+3
fffff880`06b11a13 2408            and     al,8

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  USBPORT!USBPORT_Xdpc_iBegin+3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0a97

IMAGE_VERSION:  6.1.7600.16788

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_Xdpc_iBegin+3

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_Xdpc_iBegin+3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_code_av_bad_ip_usbport!usbport_xdpc_ibegin+3

FAILURE_ID_HASH:  {684f68d5-1320-383b-912b-d27eccd3c7a9}

Followup: MachineOwner

I have a little more information on the failing driver:

Code:

start             end                 module name
fffff880`06b0f000 fffff880`06b65000   USBPORT    (pdb symbols)          c:\symbols\usbport.pdb\1DE3AFFF2AC64012A33AAD1F9FB890661\usbport.pdb
    Loaded symbol image file: USBPORT.SYS
    Mapped memory image file: c:\symbols\USBPORT.SYS\4D8C0A9756000\USBPORT.SYS
    Image path: \SystemRoot\system32\DRIVERS\USBPORT.SYS
    Image name: USBPORT.SYS
    Timestamp:        Fri Mar 25 03:23:03 2011 (4D8C0A97)
    CheckSum:         00055BEF
    ImageSize:        00056000
    File version:     6.1.7600.16788
    Product version:  6.1.7600.16788
    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:     usbport.sys
    OriginalFilename: usbport.sys
    ProductVersion:   6.1.7600.16788
    FileVersion:      6.1.7600.16788 (win7_gdr.110324-1506)
    FileDescription:  USB 1.1 & 2.0 Port Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Please update your USB Driver.

If this does not resolve the Problem We will do a driver verifier.

Also please install service pack 1:

Code:

OS Version:                6.1.7600 N/A Build 7600

This is the report from one of your DMP's, I'm just looking through the others as we speak,

I have noticed a bug check 0x124 normally hardware error. But if we try these resolutions first.