Sudden BSOD

JantjeZ · 30 Oct 2010

Hello,

My father has the same occuring BSOD once in a while.
Now i was wondering where the problem came from. So i searched using Google and finally came to this site.
I hope you guys can help us with this problem.

I've attached the dump.
Information about the system:

Win7 Ultimate x64(Originally Windows Vista Home Premium x86)
Sony VAIO VGN-AR71M(About a year and a half)

Thanks in advance

zigzag3143 · 30 Oct 2010

JantjeZ said:

Hello,

My father has the same occuring BSOD once in a while.
Now i was wondering where the problem came from. So i searched using Google and finally came to this site.
I hope you guys can help us with this problem.

I've attached the dump.
Information about the system:

Win7 Ultimate x64(Originally Windows Vista Home Premium x86)
Sony VAIO VGN-AR71M(About a year and a half)

Thanks in advance

Easy the camera driver R5U870FLamd64.sys. Update or remove it.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\103010-28173-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Sat Oct 30 14:06:41.424 2010 (GMT-4)
System Uptime: 0 days 1:17:34.453
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000046, fffff80002cf1034, fffff880091750b0, 0}

Unable to load image \SystemRoot\System32\Drivers\R5U870FUamd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for R5U870FUamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for R5U870FUamd64.sys
Probably caused by : R5U870FUamd64.sys ( R5U870FUamd64+3ba0 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000046, Exception code that caused the bugcheck
Arg2: fffff80002cf1034, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880091750b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`02cf1034 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

CONTEXT:  fffff880091750b0 -- (.cxr 0xfffff880091750b0)
rax=0000000000000000 rbx=00000000c0000046 rcx=fffff880091750b0
rdx=0000000000000001 rsi=0000000000000001 rdi=fffff80002e3ce80
rip=fffff80002cf1034 rsp=fffff88009174ff0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000200 r10=fffff80002c52000
r11=fffff880091755c0 r12=0000000000000000 r13=0000000000000000
r14=fffffa80046c2660 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!RtlRaiseStatus+0x18:
fffff800`02cf1034 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h] ss:0018:fffff880`091751a8=fffff80002cf1034
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ccb610 to fffff80002cf1034

STACK_TEXT:  
fffff880`09174ff0 fffff800`02ccb610 : 00000000`00000000 fffffa80`049f2920 00000001`04060001 fffff880`091755a8 : nt!RtlRaiseStatus+0x18
fffff880`09175590 fffff880`08a45ba0 : fffffa80`00000001 fffffa80`00000001 fffffa80`04130b00 00000000`00000000 : nt!KeReleaseMutant+0x260
fffff880`09175640 fffffa80`00000001 : fffffa80`00000001 fffffa80`04130b00 00000000`00000000 00000000`00000000 : R5U870FUamd64+0x3ba0
fffff880`09175648 fffffa80`00000001 : fffffa80`04130b00 00000000`00000000 00000000`00000000 fffff880`058be5fb : 0xfffffa80`00000001
fffff880`09175650 fffffa80`04130b00 : 00000000`00000000 00000000`00000000 fffff880`058be5fb fffffa80`04fc0908 : 0xfffffa80`00000001
fffff880`09175658 00000000`00000000 : 00000000`00000000 fffff880`058be5fb fffffa80`04fc0908 fffff8a0`0300fb20 : 0xfffffa80`04130b00


FOLLOWUP_IP: 
R5U870FUamd64+3ba0
fffff880`08a45ba0 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  R5U870FUamd64+3ba0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: R5U870FUamd64

IMAGE_NAME:  R5U870FUamd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4610813b

STACK_COMMAND:  .cxr 0xfffff880091750b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_R5U870FUamd64+3ba0

BUCKET_ID:  X64_0x3B_R5U870FUamd64+3ba0

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

And old drivers

Code:

R5U870FUamd64.sys        fffff880`08bcd000    fffff880`08bd8280    0x0000b280    0x4610813b    4/2/2007 00:06:19                        
R5U870FLamd64.sys        fffff880`08b8b000    fffff880`08b9e200    0x00013200    0x4610813e    4/2/2007 00:06:22                        
SFEP.sys        fffff880`059a4000    fffff880`059a6c80    0x00002c80    0x46b2beb9    8/3/2007 01:35:53                        
ti21sony.sys        fffff880`058d0000    fffff880`059a4000    0x000d4000    0x471764cb    10/18/2007 09:51:07                        
VSTCNXT6.SYS        fffff880`08a1d000    fffff880`08ae8000    0x000cb000    0x48f69046    10/15/2008 20:52:22                        
VSTAZL6.SYS        fffff880`03a3d000    fffff880`03a8f000    0x00052000    0x48f69096    10/15/2008 20:53:42                        
VSTDPV6.SYS        fffff880`0882c000    fffff880`089a0000    0x00174000    0x48f69189    10/15/2008 20:57:45                        
yk62x64.sys        fffff880`05367000    fffff880`053ca000    0x00063000    0x49a2ba83    2/23/2009 11:02:27                        
netw5v64.sys        fffff880`03e7c000    fffff880`043b7000    0x0053b000    0x49cbab84    3/26/2009 12:21:24                        
spldr.sys        fffff880`015e2000    fffff880`015ea000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`059e3000    fffff880`059f0000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`01072000    fffff880`0107d000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
hcw66x64.sys        fffff880`0a4ed000    fffff880`0a5a4f00    0x000b7f00    0x4a26df61    6/3/2009 16:38:57

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads