Multiple BSOD's, random circumstances

taboexa · 09 Nov 2012

Hey guys,
Ive been looking through this forum trying to find a solution to my problem, but all the posts i saw had problems with only one BSOD. My problem encompasses a list of BSOD's and they arent caused by any particular action taken on the computer. Ive already had 4 in the time time it took to put up this post! (composed it in notepad lol). Ive run windows check disk and memory test with no results, id have run memtest86 but my computer simply wont run for that long.

Any insight from anybody would be welcome as my limited computer troubleshooting abilities are insufficient for this.

Here is the aforementioned list:
bad pool header
cfn list corrupt
memory management
page fault in non paged area
system service exception
bad pool caller
apc index mismatch
irqs not less or equal
dxgkrnl
the video memory manager has encountered an unexpected fatal error

Also some untitled BSOD's but with 'problem' files:
atikmdag.sys
win32k.sys
ntfs.sys

comp specs:
windows 7 pro 64bit
gigabyte GA-MA770TA-UD3
AMD phenom II X4 quad core (3.2 ghz) black edition
corsair 8gb (4x2gb) ram
xfx ati HD5850 xX edition pci-e
creative X-fi titanuium pci-e fatal1ty

Any extra info required please let me know

Cheers in advance for everyones help

Michael.

marsmimar · 10 Nov 2012

Hello Michael and welcome to Seven Forums.

From the dump files you provided it appears that your computer is having some driver problems. Specifically, dxgkrnl.sys (DirectX Graphics Kernel, updated through Windows Update); atikmpag.sys and atikmdag.sys (both ATI Video drivers, recommended to remove the Catalyst Control Center and only install the Display Driver); win32k.sys (a multi-users win32 driver, updated through Windows Update); and dxgmms1.sys (another DirectX Graphics driver).

There may also be an issue with Faster Than Light (FLTgame.exe). Apparently ESET is giving false positives. It renders the game unplayable and could result in BSODs unless you set ESET to ignore the FTLgame.exe. So if you have FLT and ESET...

AMD Support & Drivers

FTLgame.com • View topic - Update v1.0 & v1.01 - Very few changes

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880052f1614, fffff8800b3e70a0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::ProcessTerminationList+58 )

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

0: 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: fffff880052f1614, Address of the instruction which caused the bugcheck
Arg3: fffff8800b3e70a0, 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: 
dxgkrnl!DXGDEVICE::ProcessTerminationList+58
fffff880`052f1614 488b5618        mov     rdx,qword ptr [rsi+18h]

CONTEXT:  fffff8800b3e70a0 -- (.cxr 0xfffff8800b3e70a0)
rax=fffffa800adc4000 rbx=fffff8a012694000 rcx=fffff8a014546241
rdx=fffff8a01165a421 rsi=fa800aa8f72004c0 rdi=fffff8a012615300
rip=fffff880052f1614 rsp=fffff8800b3e7a70 rbp=fffff8a012695300
 r8=fffff8a01165a420  r9=0000000000000050 r10=fffff8000360a480
r11=fffff8a014546240 r12=0000000000000001 r13=fffff8a00231e400
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgkrnl!DXGDEVICE::ProcessTerminationList+0x58:
fffff880`052f1614 488b5618        mov     rdx,qword ptr [rsi+18h] ds:002b:fa800aa8`f72004d8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  FTLGame.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880052f724b to fffff880052f1614

STACK_TEXT:  
fffff880`0b3e7a70 fffff880`052f724b : 00000000`00000799 00000000`00000001 fffff880`0b3e7ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x58
fffff880`0b3e7ac0 fffff960`001efe82 : 00000000`0008e2d0 00000000`40000740 00000000`7efdb000 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b
fffff880`0b3e7bf0 fffff800`0348e293 : fffffa80`09f4dad0 fffff880`0b3e7ca0 00000000`00000000 fffffa80`0b19d230 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0b3e7c20 00000000`752e13aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752e13aa


FOLLOWUP_IP: 
dxgkrnl!DXGDEVICE::ProcessTerminationList+58
fffff880`052f1614 488b5618        mov     rdx,qword ptr [rsi+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgkrnl!DXGDEVICE::ProcessTerminationList+58

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa1a0

STACK_COMMAND:  .cxr 0xfffff8800b3e70a0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGDEVICE::ProcessTerminationList+58

BUCKET_ID:  X64_0x3B_dxgkrnl!DXGDEVICE::ProcessTerminationList+58

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff800036c6000
THREAD fffffa8009f4dad0  Cid 19d8.1b10  Teb: 000000007efdb000 Win32Thread: fffff900c3139830 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80003604ba4
Owning Process            fffffa800a6cb060       Image:         FTLGame.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      204617       
Context Switch Count      278392                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000000000070c2ee
Stack Init fffff8800b3e7db0 Current fffff8800b3e7aa0
Base fffff8800b3e8000 Limit fffff8800b3df000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0b3e67d8 fffff800`0348e5a9 : 00000000`0000003b 00000000`c0000005 fffff880`052f1614 fffff880`0b3e70a0 : nt!KeBugCheckEx
fffff880`0b3e67e0 fffff800`0348defc : fffff880`0b3e7838 fffff880`0b3e70a0 00000000`00000000 fffff880`052cedec : nt!KiBugCheckDispatch+0x69
fffff880`0b3e6920 fffff800`034b475d : fffff960`00350840 fffff960`003166fc fffff960`00060000 fffff880`0b3e7838 : nt!KiSystemServiceHandler+0x7c
fffff880`0b3e6960 fffff800`034bbdd0 : fffff800`035de0f0 fffff880`0b3e69d8 fffff880`0b3e7838 fffff800`0341f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0b3e6990 fffff800`034c8dff : fffff880`0b3e7838 fffff880`0b3e70a0 fffff880`00000000 fffff8a0`12615300 : nt!RtlDispatchException+0x410
fffff880`0b3e7070 fffff800`0348e682 : fffff880`0b3e7838 fffff8a0`12694000 fffff880`0b3e78e0 fa800aa8`f72004c0 : nt!KiDispatchException+0x16f
fffff880`0b3e7700 fffff800`0348cf8a : fffff880`0b3e7940 fffff880`03f58bfa 00000000`00000001 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`0b3e78e0 fffff880`052f1614 : 00000000`00000701 00000000`00000000 fffff8a0`4b677844 00000000`00000799 : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff880`0b3e78e0)
fffff880`0b3e7a70 fffff880`052f724b : 00000000`00000799 00000000`00000001 fffff880`0b3e7ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x58
fffff880`0b3e7ac0 fffff960`001efe82 : 00000000`0008e2d0 00000000`40000740 00000000`7efdb000 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b
fffff880`0b3e7bf0 fffff800`0348e293 : fffffa80`09f4dad0 fffff880`0b3e7ca0 00000000`00000000 fffffa80`0b19d230 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0b3e7c20 00000000`752e13aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0b3e7c20)
00000000`0008e288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752e13aa

taboexa · 11 Nov 2012

Thanks for the quick reply marsmimar, do i have to wait for the ones you have labeled as windows updates to appear in windows updates? Or is there a way i can do it manually? DirectX always does some sort of setup everytime i install a game via steam, could this be an issue? Also im not running ESET and i cant find any evidence of it on my system. I am running avg, should i tell it to ignore FTL? And one last note, AMD arent allowing me to download the driver on its own like they used to. Would it be worth finding an older driver that isnt attached to the catalyst control center?
Thanks again for your time, Michael.

marsmimar · 11 Nov 2012

DirectX is included by default as part of the Windows 7 operating system. As such, you shouldn't ever really need to "install", "uninstall", or "repair" DirectX as a software program, per se. However, sometimes operating system files become damaged or corrupt. You could try running a system file checker scan from an elevated command prompt (option two.) If any problems are found, run the scan 3 times and reboot the computer after each scan.

SFC /SCANNOW Command - System File Checker

Microsoft frequently releases updated versions of DirectX and installing the latest updates may be the fix to a DirectX problem you're having or may give performance increases in your games and graphics programs. Normally that's done thorugh Windows Updates, but you could search for the latest version on Microsoft's website.

Typically, the DirectX End-User Runtime Web Installer link will be your best option since it's the latest release and only installs the DirectX files you are missing. Some users prefer to download and install the entire DirectX package by choosing the DirectX End-User Runtimes (MONTH YEAR) link with the latest month and year available. Note: The DirectX SDK download options are NOT recommended.

Search results - Microsoft Download Center

After any installs restart your computer, even if you're not prompted to do so. After restarting your computer, test to see if updating to the latest version of DirectX corrected the problems you were having.

Assuming you do have FTL installed, it wouldn't hurt to tell AVG to ignore it.

As far as the AMD drivers, you could always try an older driver to see how it performs. Sometimes "newest" doesn't always mean "best" when it comes to drivers.

Warning

Strongly suggest making a restore point before installing DirectX End-User Runtime Installers or any drivers. Better yet, make a system image.
System Restore Point - Create