Minidump crash report: translation needed.

[davidshea]

Hello! I am hoping someone can help tell me what the cause of my computer crashing today and restarting was; I'm including the minidump file. Thank you!

I am running Win 7 64-bit, ASUS mobo that's four years old (but BIOS is updated), on the 590 chipset. 4 Gigs of Corsair RAM, WD Caviar Black 640gig HDD, 8800 GTS eVGA card.

--Dave

 

[wish]

Hi Dave,
Your single dmp indicated REFERENCE_BY_POINTER (18) = usual caused by 3rd driver.
Then I see you have several drivers that need to be updated:

ASACPI.sys   Sun Mar 27 18:30:36 [COLOR=Red]2005[/COLOR] -> [URL="http://support.asus.com/download/download.aspx"]Asus ATK0110 ACPI Utility [/URL]
SiWinAcc.sys Thu Jun 14 17:02:02 2007 -> [URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image driver [/URL]
SiRemFil.sys Wed Jun 20 12:42:10 2007 -> [URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image driver [/URL]
SI3132.sys   Wed Oct 03 11:39:29 2007 -> [URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image driver[/URL]
nvm62x64.sys Fri Oct 17 14:01:06 2008 -> [URL="http://www.nvidia.com/Download/index.aspx"]nVidia Ethernet Networking Driver (nForce chipset driver)[/URL]
ctac32k.sys  Wed Jul 02 01:38:22 2008 -> [URL="http://support.creative.com/"]Creative Audio Driver[/URL]

Uninstall RivaTuner because it have some issue with windows 7.

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

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa8008a5e700, e902, fffffa8008a5f00f}

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

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

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8008a5e700, Object whose reference count is being lowered
Arg3: 000000000000e902, Reserved
Arg4: fffffa8008a5f00f, 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:  SteamService.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001c08fdc to fffff80001c71740

STACK_TEXT:  
fffff880`101ae428 fffff800`01c08fdc : 00000000`00000018 00000000`00000000 fffffa80`08a5e700 00000000`0000e902 : nt!KeBugCheckEx
fffff880`101ae430 fffff800`01f6d329 : fffff880`101aeca0 fffff880`101ae738 00000000`00000003 00000000`0000e406 : nt! ?? ::FNODOBFM::`string'+0x46411
fffff880`101ae490 fffff800`01f93e41 : fffff880`101ae901 fffff800`01f6257a fffffa80`00000001 fffffa80`053db700 : nt!ObpWaitForMultipleObjects+0x2d3
fffff880`101ae960 fffff800`01c70993 : fffffa80`08aea060 fffff800`021ec64c 0000007f`c5adb421 fffff800`01f87414 : nt!NtWaitForMultipleObjects32+0xec
fffff880`101aebb0 00000000`754b2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0074f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x754b2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46411
fffff800`01c08fdc 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
---------