Windows 7: BSOD: "Reference by Pointer" Need Help!

tijang · 01 Dec 2010

I have some problem on my Toshiba M645 Laptop.
The blue screen "Reference by Pointer" came out when I played the video while doing
another graphic works and P2P uTorrent [HDD read & write hard in the same time].

I was already do "sfc /scannow" in command prompt and it said
"Windows Resource Protection did not find any integrity violations".
Maybe it was caused by driver problem, please check my dump files & help.
Thanks in advance.

Laptop: Toshiba Satellite M645-1014X
OS: Windows 7 Ultimate x64 OEM Toshiba
CPU: Intel Core i5 M560 2.67GHz
RAM: Samsung 4GB 2x2 Dual Channel
HDD: Hitachi 500GB
VGA: Intel HD Graphics, NVIDIA Geforce GT330M 1GB
SOUND: Realtek High Definition Audio

tijang · 01 Dec 2010

May I bump once.
Hope someone can find out what caused my blue screen and the solution.
Thanks.

tijang · 01 Dec 2010

Excuse me, someone check dumpfiles for me please.
Thank you in anticipation.
Sorry for bump twice. m(_ _)m

tijang · 02 Dec 2010

Somebody who read this topic,
please analyze dumpfiles or given some clue.
Thanks again, regards.

wish · 03 Dec 2010

Hello,
Don't use any cleaning registry software unless you know what you are doing because it can mess up your windows.

Your latest dmp = REFERENCE_BY_POINTER (18) = usual caused by 3rd drivers.

Then enable driver verifier to stress out your drivers.
If there is any driver violation your windows will crash, then attach the new files here.
Driver Verifier - Enable and Disable

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa8008dcc790, 2, fffffa80077e7818}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46411 )

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

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8008dcc790, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: fffffa80077e7818, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002e6cfdc to fffff80002ed5740

STACK_TEXT:  
fffff880`033fcb58 fffff800`02e6cfdc : 00000000`00000018 00000000`00000000 fffffa80`08dcc790 00000000`00000002 : nt!KeBugCheckEx
fffff880`033fcb60 fffff800`031c6635 : 00000000`00000000 00000000`00084081 fffffa80`070f5f10 fffffa80`00084081 : nt! ?? ::FNODOBFM::`string'+0x46411
fffff880`033fcbc0 fffff800`02ffd08b : fffffa80`070f5f18 00000000`00000001 00000000`00000000 dfffffff`00000631 : nt!MiSegmentDelete+0xa1
fffff880`033fcc00 fffff800`02ffd6fd : 00000000`00000000 00000000`00000080 fffffa80`040f29e0 fffffeff`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`033fccc0 fffff800`03179c06 : fffdfff7`cd6f6fdb fffffdff`fffffeff cdff99b7`fdffebff ff7fffff`ffffffff : nt!MiDereferenceSegmentThread+0x10d
fffff880`033fcd40 fffff800`02eb3c26 : fffff880`009e9180 fffffa80`0416cb60 fffff880`009f3fc0 dfffffef`bf3effff : nt!PspSystemThreadStartup+0x5a
fffff880`033fcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46411
fffff800`02e6cfdc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46411

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46411

BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46411

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

Windows 7: BSOD: "Reference by Pointer" Need Help!

BSOD: "Reference by Pointer" Need Help! problems?