Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\Zevici\Windows_NT6_BSOD_jcgriff2\042312-5772-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`03091650
Debug session time: Mon Apr 23 19:28:12.806 2012 (UTC - 6:00)
System Uptime: 1 days 8:40:58.886
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 18, {fffffa800ca0cc90, fffffa80142f7060, 1, 1}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49228 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: fffffa800ca0cc90, Object type of the object whose reference count is being lowered
Arg2: fffffa80142f7060, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000001, 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 fffff80002e6b091 to fffff80002ec9c80
STACK_TEXT:
fffff880`035d2af8 fffff800`02e6b091 : 00000000`00000018 fffffa80`0ca0cc90 fffffa80`142f7060 00000000`00000001 : nt!KeBugCheckEx
fffff880`035d2b00 fffff800`02ea8da1 : 00000000`00000000 fffffa80`0ca8d680 fffff6fc`4005a3e8 fffff6fc`4005a418 : nt! ?? ::FNODOBFM::`string'+0x49228
fffff880`035d2b40 fffff800`02ed3361 : fffff800`02ea8d08 fffff800`03069310 fffffa80`0ca8d680 00000000`00000000 : nt!PspReaper+0x99
fffff880`035d2b70 fffff800`03163fda : 00000000`00000000 fffffa80`0ca8d680 00000000`00000080 fffffa80`0ca78040 : nt!ExpWorkerThread+0x111
fffff880`035d2c00 fffff800`02eba9c6 : fffff880`03365180 fffffa80`0ca8d680 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035d2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+49228
fffff800`02e6b091 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+49228
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
FAILURE_BUCKET_ID: X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+49228
BUCKET_ID: X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+49228
Followup: MachineOwner
---------
The above crash is typically caused by drivers. The following drivers may need to be updated:
Code:
LHidFilt fffff880`06bba000 fffff880`06bcd000 Wed Jun 17 10:49:39 2009 (4a391ea3) 00014ede LHidFilt.Sys
LMouFilt fffff880`06bcd000 fffff880`06be1000 Wed Jun 17 10:49:43 2009 (4a391ea7) 0001d7ff LMouFilt.Sys
netr28x fffff880`04892000 fffff880`04948000 Fri Jun 19 01:56:06 2009 (4a3b4496) 000b67f9 netr28x.sys
LHidFilt.Sys
LMouFilt.Sys
netr28x.sys
I would especially recommend updating your wireless card drivers from the manufacturer's site.
Post back how the system responds after doing the above.
Your crashes also contained a 0x124 stop. For more information about this stop and some troubleshooting steps: Stop 0x124 - what it means and what to try
Quote