Sudden bluescreen when gaming

Status
Not open for further replies.

Joeyboy

Daemon Poster
Messages
605
Location
England
Right ok i've had has comp for a few weeks, had no issues apart from some black lines in games which were sorted after i changed the drivers and re-installed the game, last week no problems at all. But just now i was playing Dawn of War:soul storm and in the middle of a small battle it suddenly froze, sound repeating too as in " BRRRRRRR", then a bluescreen came up full of writing, talking about windows shutting down my comp for safety or something and if this is my first time seeing this... but it went away before i could read much of anything and my comp re-booted. When it started again a message talked about how windows shut down unexpectedly and it gave me this small error report, can anyone tell me what just happened?:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80001F84369
BCP3: FFFFFA6006FE7E90
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini101708-01.dmp
C:\Users\Joe\AppData\Local\Temp\WER-90792-0.sysdata.xml
C:\Users\Joe\AppData\Local\Temp\WER64DA.tmp.version.txt
 
whats the STOP error? Will i have to do what is said in that link and wait for it to bluescreen again to get this STOP error?
 
First this should be in the Windows area. Please make sure to post in the right area next time or the thread could be deleted without warning.

http://www.techist.com/forums/f4/policy-change-forums-181028/

The Stop error code looks like this:

STOP 0X000000ZZ where ZZ is a alpha numeric combination. This will allow us to help diagnose the problem and help find a solution.

Most time a couple lines down you will see a line in all CAPS. This line will be helpful as well.

Blue-screen-2.jpg

This is the Stop Error code. The red boxes show the info we need.
 
You could also just upload the minidump file it produced and we can try to figure it out from there as well.

C:\Windows\Minidump\Mini101708-01.dmp
 
First this should be in the Windows area. Please make sure to post in the right area next time or the thread could be deleted without warning.


Sorry i just assumed that since my computer crashed for some reason it counted as a hardware problem, wasn't sure it counted as an operating system related thread.

I assume to get the above info the comp must crash again? Been playing for over anh our and it hasn't crashed this time and like i said it hadn't before, if it does it again i'll post it, for now i'll look into posting the details from the minidump file that was created.:happy:
 
Yes next time it crashes get that info for us. From there we can help.
 
He's planning on sending the minidump to me when he gets back on MSN; I'll post that for him when I get it ran through Windbg.
 
Code:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Chase\Desktop\Mini101708-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
Executable search path is: 
Windows Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Kernel base = 0xfffff800`01e51000 PsLoadedModuleList = 0xfffff800`02016db0
Debug session time: Fri Oct 17 14:34:19.808 2008 (GMT-5)
System Uptime: 0 days 6:07:38.101
Loading Kernel Symbols
...........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80001f84369, fffffa6006fe7e90, 0}



Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::OpenLocalAllocation+144 )

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

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

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

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




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!ExAllocatePoolWithTag+359
fffff800`01f84369 48895808        mov     qword ptr [rax+8],rbx

CONTEXT:  fffffa6006fe7e90 -- (.cxr 0xfffffa6006fe7e90)
rax=0000000000000001 rbx=fffffa800395c158 rcx=fffff8800cebc5c0
rdx=0000000000000004 rsi=fffff80001fe4160 rdi=fffffa800395c090
rip=fffff80001f84369 rsp=fffffa6006fe86f0 rbp=0000000000000000
 r8=0000000000000001  r9=fffff80001e51000 r10=0000000000000001
r11=0000000000000002 r12=0000000000000002 r13=0000000000000001
r14=000000006d4d6956 r15=0000000000000009
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
nt!ExAllocatePoolWithTag+0x359:
fffff800`01f84369 48895808        mov     qword ptr [rax+8],rbx ds:002b:00000000`00000009=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Soulstorm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffffa600391364c to fffff80001f84369

STACK_TEXT:  
fffffa60`06fe86f0 fffffa60`0391364c : 00000000`6d4d6956 00000000`00001000 fffff880`0b839570 fffff800`00000002 : nt!ExAllocatePoolWithTag+0x359
fffffa60`06fe87c0 fffffa60`0390ef33 : 00000000`00000000 fffffa80`055e0f10 00000000`00000000 00000000`00000174 : dxgkrnl!VIDMM_GLOBAL::OpenLocalAllocation+0x144
fffffa60`06fe8850 fffffa60`039185ff : fffffa80`07428000 fffff880`0ab67960 fffffa80`0518e090 00000000`00000000 : dxgkrnl!VIDMM_GLOBAL::OpenOneAllocation+0x20f
fffffa60`06fe8930 fffffa60`039104fb : 00000000`00000000 00000000`00000000 fffff880`0b839570 00000000`00000000 : dxgkrnl!VIDMM_GLOBAL::GrowMultiAllocation+0x2d7
fffffa60`06fe8a00 fffffa60`038b4bd2 : 00000000`00000000 00000000`00000000 fffff880`0a885340 fffff880`0a22c000 : dxgkrnl!VIDMM_GLOBAL::BeginCPUAccess+0x79b
fffffa60`06fe8ac0 fffffa60`038b51ca : fffffa80`04281bb0 fffffa80`04281bb0 fffffa60`06fe8ca0 fffffa80`04281bb0 : dxgkrnl!DXGDEVICE::Lock+0x242
fffffa60`06fe8b20 fffff960`001c2432 : 00000000`0007e560 00000000`75803380 00000000`000007db fffff880`0a22c000 : dxgkrnl!DxgkLock+0x252
fffffa60`06fe8bf0 fffff800`01ea5df3 : 00000000`00000001 00000000`0189e81c fffffa60`00000001 00000000`00000000 : win32k!NtGdiDdDDILock+0x12
fffffa60`06fe8c20 00000000`758eb6ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007e538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x758eb6ea


FOLLOWUP_IP: 
dxgkrnl!VIDMM_GLOBAL::OpenLocalAllocation+144
fffffa60`0391364c 488bf0          mov     rsi,rax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!VIDMM_GLOBAL::OpenLocalAllocation+144

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4893b63f

STACK_COMMAND:  .cxr 0xfffffa6006fe7e90 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!VIDMM_GLOBAL::OpenLocalAllocation+144

BUCKET_ID:  X64_0x3B_dxgkrnl!VIDMM_GLOBAL::OpenLocalAllocation+144

Followup: MachineOwner

There's his minidump.
 
Status
Not open for further replies.
Back
Top Bottom