Blue screen during game

Status
Not open for further replies.
Ahh the file is gone, must have been deleted after a ccleaner scan. When it happens again I'll post it right away.
 
Ok here we go... I think it only happens when I use AMD Fusion.. it won't let me upload the dmp file though.. even after it's RARed

Imageshack - dsc00458np

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3d
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: FFFFF80001C961B4
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini091809-01.dmp
C:\Users\Ivan\AppData\Local\Temp\WER-56113-0.sysdata.xml
C:\Users\Ivan\AppData\Local\Temp\WER8C57.tmp.version.txt
 
Upload it to Rapidshare, Megaupload or SendSpace. That will be the only way i can help.
 
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff80001c961b4

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3D

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001c691ee to fffff80001c69450

STACK_TEXT:
fffffa60`01921ca8 fffff800`01c691ee : 00000000`0000003d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpSysVolTakeOwnership+0x64
fffffa60`01921cb0 00000000`0000003d : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`01c961b4 : nt!RtlAssert2+0xaa
fffffa60`01921cb8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff800`01c961b4 00000000`00000019 : 0x3d


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!RtlpSysVolTakeOwnership+64
fffff800`01c69450 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!RtlpSysVolTakeOwnership+64

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f

FAILURE_BUCKET_ID: X64_0x3D_nt!RtlpSysVolTakeOwnership+64

BUCKET_ID: X64_0x3D_nt!RtlpSysVolTakeOwnership+64

Followup: MachineOwner

There it is. From what i see it is a issue with the Kernel trying to take ownership of a system volume. It is a driver fault that is behind all of it. So i would gather that it would have to do with the Fusion. At best i would say make sure you have all the latest mobo drivers and everything for the system.
 
Status
Not open for further replies.
Back
Top Bottom