BSOD Whilst using computer for daily uses eg: browsing web

GCFSA · 29 Dec 2012

Hi guys,

I was just browsing the web when suddenly, my computer went into BSOD (this is not the first time). I would like to know if I could fix it and if so, what steps should I follow.

I have previously tried memory scans, disk scans (chkdsk) and virus scans, these all came back negative and said everything is working normally.

Attatched are the log files of all my previous BSODs.

Thankyou for your time.

bagavan · 29 Dec 2012

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003f3f5e8, fffff88003f3ee40, fffff8000380ea9b}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

Followup: Pool_corruption
---------

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88003f3f5e8
Arg3: fffff88003f3ee40
Arg4: fffff8000380ea9b

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


EXCEPTION_RECORD:  fffff88003f3f5e8 -- (.exr 0xfffff88003f3f5e8)
ExceptionAddress: fffff8000380ea9b (nt!ExDeferredFreePool+0x00000000000001df)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000194f20c
Attempt to read from address 000000000194f20c

CONTEXT:  fffff88003f3ee40 -- (.cxr 0xfffff88003f3ee40)
rax=000000000194f204 rbx=0000000000000002 rcx=fffffa8003c61400
rdx=fffff8a00e8731b0 rsi=0000000000000000 rdi=fffff8a017a23ac0
rip=fffff8000380ea9b rsp=fffff88003f3f820 rbp=0000000000000000
 r8=fffff8a00face5c0  r9=fffff8a00e873000 r10=0000000000000001
r11=fffff8a00e873010 r12=fffffa8003c61280 r13=0000000000000000
r14=000000000000000a r15=0000000000000001
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
nt!ExDeferredFreePool+0x1df:
fffff800`0380ea9b 4c395808        cmp     qword ptr [rax+8],r11 ds:002b:00000000`0194f20c=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000000194f20c

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003911100
GetUlongFromAddress: unable to read from fffff800039111c0
 000000000194f20c Nonpaged pool

FOLLOWUP_IP: 
nt!ExDeferredFreePool+1df
fffff800`0380ea9b 4c395808        cmp     qword ptr [rax+8],r11

FAULTING_IP: 
nt!ExDeferredFreePool+1df
fffff800`0380ea9b 4c395808        cmp     qword ptr [rax+8],r11

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8000380e1a1 to fffff8000380ea9b

STACK_TEXT:  
fffff880`03f3f820 fffff800`0380e1a1 : fffff8a0`12c27500 fffff8a0`15749b30 00000000`00000000 fffff880`03f3f9e1 : nt!ExDeferredFreePool+0x1df
fffff880`03f3f8b0 fffff880`01ea5223 : fffff8a0`15749b40 00000000`00000000 fffffa80`6666744e fffffa80`000003ab : nt!ExFreePoolWithTag+0x411
fffff880`03f3f960 fffff880`01e219b2 : fffff800`0387f280 fffff880`03f3fb01 fffff880`03f3f9e1 fffff8a0`15749b40 : Ntfs!NtfsDeleteFcb+0x3a3
fffff880`03f3f9c0 fffff880`01ea76bc : fffffa80`0aa8a9d0 fffffa80`04a8c180 fffff8a0`15749b40 fffff8a0`15749ed8 : Ntfs!NtfsTeardownFromLcb+0x1e2
fffff880`03f3fa50 fffff880`01e290b2 : fffffa80`0aa8a9d0 fffffa80`0aa8a9d0 fffff8a0`15749b40 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`03f3fad0 fffff880`01eb7223 : fffffa80`0aa8a9d0 fffff800`0387f280 fffff8a0`15749b40 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`03f3fb10 fffff880`01ea63c7 : fffffa80`0aa8a9d0 fffff8a0`15749c70 fffff8a0`15749b40 fffffa80`04a8c180 : Ntfs!NtfsCommonClose+0x353
fffff880`03f3fbe0 fffff800`036eb641 : 00000000`00000000 fffff800`039d4500 fffff800`038e0800 fffffa80`00000005 : Ntfs!NtfsFspClose+0x15f
fffff880`03f3fcb0 fffff800`03978e5a : bace7bdf`fccea1d9 fffffa80`03d3c480 00000000`00000080 fffffa80`03cd7b30 : nt!ExpWorkerThread+0x111
fffff880`03f3fd40 fffff800`036d2d26 : fffff880`03d67180 fffffa80`03d3c480 fffff880`03d720c0 fbc7fdd4`f2e7bbbb : nt!PspSystemThreadStartup+0x5a
fffff880`03f3fd80 00000000`00000000 : fffff880`03f40000 fffff880`03f3a000 fffff880`03f3f9e0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDeferredFreePool+1df

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .cxr 0xfffff88003f3ee40 ; kb

FAILURE_BUCKET_ID:  X64_0x24_nt!ExDeferredFreePool+1df

BUCKET_ID:  X64_0x24_nt!ExDeferredFreePool+1df

Followup: Pool_corruption
---------

STOP 0x00000024: NTFS_FILE_SYSTEM (go to top of page)

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

BSOD Index

Read the "resolving part"

Also

Run this

Driver Verifier - Enable and Disable

Post back the dumps if it BSOD`s

Fill up your system specs

GCFSA · 29 Dec 2012

Thankyou for your reply.

I will try all of the above problems and will report the results in around 24-48 hours time.

Thankyou once again.

GCFSA · 30 Dec 2012

I have run the chkdsk and have also done the verifier check-

here are the new dumps (new and old, aka all previous dumps including new ones)

thankyou very much once again

bagavan · 30 Dec 2012

Found one driver responsible

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {20b, fffff88007291a02, fffff98039e26ee0, 0}

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

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000020b, The caller of IoFreeIrp is freeing an IRP that is stillin use.
Arg2: fffff88007291a02, The address in the driver's code where the error was detected.
Arg3: fffff98039e26ee0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_20b

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  20b

FAULTING_IP: 
btmusb+38a02
fffff880`07291a02 488b5c2440      mov     rbx,qword ptr [rsp+40h]

FOLLOWUP_IP: 
btmusb+38a02
fffff880`07291a02 488b5c2440      mov     rbx,qword ptr [rsp+40h]

IRP_ADDRESS:  fffff98039e26ee0

DEVICE_OBJECT: fffffa80064e6a20

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003b683dc to fffff800036e1fc0

STACK_TEXT:  
fffff880`03d858f8 fffff800`03b683dc : 00000000`000000c9 00000000`0000020b fffff880`07291a02 fffff980`39e26ee0 : nt!KeBugCheckEx
fffff880`03d85900 fffff800`03b7247a : fffff800`03b669f0 fffff880`07291a02 fffff980`39e26ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03d85940 fffff800`03b73483 : 00000000`0000020b 00000000`00000000 fffff980`39e26ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03d85990 fffff800`03b82fc9 : fffffa80`04caeb00 00000000`00000000 fffff980`39e26ee0 00000000`00000000 : nt!VfErrorReport1+0x63
fffff880`03d85a30 fffff800`03b835ec : fffff880`07291a02 fffff980`39e26ee0 fffff880`03d85bd0 fffff980`39e26ee0 : nt!VfIoFreeIrp+0x89
fffff880`03d85a60 fffff880`07291a02 : 00000000`ffffff00 00000000`00000002 fffff980`39e26ee0 fffff880`03d85b00 : nt!IovFreeIrpPrivate+0x5c
fffff880`03d85aa0 00000000`ffffff00 : 00000000`00000002 fffff980`39e26ee0 fffff880`03d85b00 00000000`00000000 : btmusb+0x38a02
fffff880`03d85aa8 00000000`00000002 : fffff980`39e26ee0 fffff880`03d85b00 00000000`00000000 fffffa80`07400180 : 0xffffff00
fffff880`03d85ab0 fffff980`39e26ee0 : fffff880`03d85b00 00000000`00000000 fffffa80`07400180 fffff880`03d85c80 : 0x2
fffff880`03d85ab8 fffff880`03d85b00 : 00000000`00000000 fffffa80`07400180 fffff880`03d85c80 fffff880`072928fb : 0xfffff980`39e26ee0
fffff880`03d85ac0 00000000`00000000 : fffffa80`07400180 fffff880`03d85c80 fffff880`072928fb 00000000`00000002 : 0xfffff880`03d85b00


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  btmusb+38a02

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: btmusb

IMAGE_NAME:  btmusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d5168fc

FAILURE_BUCKET_ID:  X64_0xc9_20b_VRF_btmusb+38a02

BUCKET_ID:  X64_0xc9_20b_VRF_btmusb+38a02

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

The dumps by driver verifier blames ralink driver

Update this driver Ralink/Motorola BC4 Bluetooth 3.0 + HS Adapter Driver (HP)

Ralink-A MEDIATEK COMPANY

GCFSA · 30 Dec 2012

Thankyou very much =]

Is this the only driver causing the BSOD's or are there more that I'll need to fix/update

Thankyou so very much once again!

bagavan · 31 Dec 2012

From the dumps it only blames this.

So updating should most likely solve your issue