BSODs just while playing FFXIV.

Hi guys,

this is my current spec.

CPU: AMD Phenom II 965 X4 Quad Core 3.4Ghz Black Ed. 125W AM3
PSU : Corsair VX550W
RAM : Mushkin Redline DDR2 PC2-8000 4GB 2x2GB 5-5-5-15
MB : Gigabyte GA-MA78G-DS3H Socket AM2+
GPU : ATI HD6950 2Gb
Monitor : Samsung SyncMaster 2333HD
O.S.:Windows 7 Ultimate x64

I bought the CPU and GPU a week ago.

I have constant crashes and BSOD's while playing FFXIV.
Some of the BSOD's are:
0x03B related to atikmdag.sys
0X0D1 related to dxgmms1.sys, netr7364.sys or hidclass.sys (Three different BSOD's)

At first I thought it could be that the PSU was insufficient, but I've changed the GPU for my old HD4850, and yet the BSOD's and crashes persist, so it's not a GPU related thing, nor a PSU problem.
I've also tested with different RAM modules, yet having the same problem.

Surprisingly, I've run FurMark at its top options for +2hours... and no crashes nor BSOD's at all!!!
I've also played Dead Space 2 without any crash.

So.. I think it's not a hardware related thing, but a FFXIV issue.
I'll config the game, and play on its lowest options, to see if it helps, since I usually play at 1920x1080, with every option at max except for DoF and ambient occlusion.

I've also reformatted, to see if it was a registry issue, but got no lucky at all.
All my drivers are up to date.

The last thing I did today, was deinstall the GPU drivers, run a registry cleaner, then reinstall the drivers again, but got no lucky either.

Actually, I'm going to try 11-1 drivers instead of 11-2.

I'll post two of those BSODs dumps with WinDbg, and two screenies of the same errors from Blue Screen Viewer.


The dxgmms1.sys one.

Code:

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


Loading Dump File [C:\Windows\Minidump\030711-19094-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c8ee50
Debug session time: Mon Mar  7 21:24:48.916 2011 (GMT+1)
System Uptime: 0 days 1:06:58.633
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88007020d90, fffff880023b96a8, fffff880023b8f10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007020d90, The address that the exception occurred at
Arg3: fffff880023b96a8, Exception Record Address
Arg4: fffff880023b8f10, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`07020d90 8b4810          mov     ecx,dword ptr [rax+10h]

EXCEPTION_RECORD:  fffff880023b96a8 -- (.exr 0xfffff880023b96a8)
ExceptionAddress: fffff88007020d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880023b8f10 -- (.cxr 0xfffff880023b8f10)
rax=0087000000000000 rbx=fffff8a007c44d60 rcx=fffffa80056cd000
rdx=fffffa800465c0d0 rsi=fffffa80056cd000 rdi=fffffa80056cd000
rip=fffff88007020d90 rsp=fffff880023b98e0 rbp=fffffa8004bec5d8
 r8=fffffa800472d901  r9=0000000000000000 r10=0000000000000000
r11=0000000000000144 r12=fffffa800465c0d0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`07020d90 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:00870000`00000010=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf90e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`07020d90 8b4810          mov     ecx,dword ptr [rax+10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800701ded3 to fffff88007020d90

STACK_TEXT:  
fffff880`023b98e0 fffff880`0701ded3 : 00000000`00000000 fffffa80`061cf1f0 00000000`00000106 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`023b9910 fffff880`0703865d : 00000000`00000000 fffff8a0`082dffa0 fffffa80`00000000 fffffa80`0472d910 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`023b9ae0 fffff880`07038398 : fffff800`00b96080 fffff880`07037d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`023b9cd0 fffff880`07037e96 : 00000000`00000000 fffffa80`057cb010 00000000`00000080 fffffa80`05633410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`023b9d00 fffff800`02d647c6 : 00000000`02a8d6b1 fffffa80`053bd8c0 fffffa80`0396e890 fffffa80`053bd8c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`023b9d40 fffff800`02a9fc26 : fffff800`02c3be80 fffffa80`053bd8c0 fffff800`02c49c40 fffff880`0101ea90 : nt!PspSystemThreadStartup+0x5a
fffff880`023b9d80 00000000`00000000 : fffff880`023ba000 fffff880`023b4000 fffff880`023b9690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

STACK_COMMAND:  .cxr 0xfffff880023b8f10 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

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

0: kd> lmvm dxgmms1
start             end                 module name
fffff880`07000000 fffff880`07046000   dxgmms1    (pdb symbols)          c:\windows\symbols\dxgmms1.pdb\99F64A64B8C94E04BB4C7562EDDFA8671\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\Windows\symbols\dxgmms1.sys\4D3FA17446000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Wed Jan 26 05:22:12 2011 (4D3FA174)
    CheckSum:         0004ECED
    ImageSize:        00046000
    File version:     6.1.7600.16748
    Product version:  6.1.7600.16748
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16748
    FileVersion:      6.1.7600.16748 (win7_gdr.110125-1530)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

The atikmdag.sys one.

Code:

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


Loading Dump File [C:\Windows\Minidump\030711-23899-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Mon Mar  7 01:04:05.130 2011 (GMT+1)
System Uptime: 0 days 0:07:15.909
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800762b84e, fffff880028407a0, 0}

Probably caused by : atikmdag.sys ( atikmdag+3b684e )

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: fffff8800762b84e, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880028407a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

FAULTING_IP: 
atikmdag+3b684e
fffff880`0762b84e 8178083000bebe  cmp     dword ptr [rax+8],0BEBE0030h

CONTEXT:  fffff880028407a0 -- (.cxr 0xfffff880028407a0)
rax=fa800491ea0004c0 rbx=fffffa80046ea158 rcx=fffff8a0002c2df0
rdx=fffffa8005ef0040 rsi=fffff88002841430 rdi=fffff8a007798d00
rip=fffff8800762b84e rsp=fffff88002841178 rbp=0000000000000000
 r8=fffffa80046ea158  r9=000000000001bc10 r10=0000000000000000
r11=fffff8a007798cb8 r12=fffffa8005ef0040 r13=fffff8a007798d00
r14=00000000000001e0 r15=fffffa8003bc2438
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
atikmdag+0x3b684e:
fffff880`0762b84e 8178083000bebe  cmp     dword ptr [rax+8],0BEBE0030h ds:002b:fa800491`ea0004c8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  ffxivgame.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800762b84e

STACK_TEXT:  
fffff880`02841178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x3b684e


FOLLOWUP_IP: 
atikmdag+3b684e
fffff880`0762b84e 8178083000bebe  cmp     dword ptr [rax+8],0BEBE0030h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+3b684e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d40a4bc

STACK_COMMAND:  .cxr 0xfffff880028407a0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3b684e

BUCKET_ID:  X64_0x3B_atikmdag+3b684e

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

3: kd> lmvm atikmdag
start             end                 module name
fffff880`07275000 fffff880`07b71000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Jan 26 23:48:28 2011 (4D40A4BC)
    CheckSum:         008B6C01
    ImageSize:        008FC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you guys need anything else, just ask it.

Any help will be much appreciated,

n0cks.

Update:
As I said, I just downgraded the GPU drivers, just to run into another 0x03B BSOD related to atikmdag.sys

- Boot into Safe Mode with Networking
- Uninstall the Display Drivers including Catalyst Control Center
- Use Driver Sweeper to sweep the traces of the driver Guru3D - Driver Sweeper
- Install the latest version ATI Radeon
- Reboot into normal mode

Regards...
Dean

usasma said:

Since you reformatted and still have the problem - this is most likely a hardware issue.
The different causes/blames in the BSOD's also tend to support this conclusion.

So, let's start with these free diagnostics/stress tests:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

Please provide these reports so we can look at the system in-depth: https://www.sevenforums.com/crashes-d...tructions.html

I already run FurMark for 2hours with this options enabled:
Fullscreen
1920x1080
Dynamic background
Burn-in
Post FX
Then I clicked the BURN-IN test button.

As I said, I had no problem at all, so that's why I thought it wouldn't be a hardware issue :s
Anyway, I had constant FPS and the temperature didn't go over 60/65º.
I'll run the other tests and provide results, as demanded.

DeanP said:

- Boot into Safe Mode with Networking
- Uninstall the Display Drivers including Catalyst Control Center
- Use Driver Sweeper to sweep the traces of the driver Guru3D - Driver Sweeper
- Install the latest version ATI Radeon
- Reboot into normal mode

Regards...
Dean

I have already done that. Twice. Also, when done this way, when the installation is completed, it says "Completed with warnings"



By the way, I also found this.
I'm going to test it right now.

UPDATE:
Adding dump.
I found no PERFMON HTML file. It just seems to be an .exe in my system32 folder :x

Update:
I already tried to uninstall the CCC, as suggested in here, but I still have the same BSOD (0x03B atikmdag.sys)

I tried to use Memtest86+ from a USB key, unsuccessfully.
I've tried to run it as USB-HDD, USB-FDD, USB-ZIP and USB-CDROM, but it wouldn't load it.

When I selected USB-ZIP, instead of loading windows, it remains on the screen before that (where the sentence "Press a key to load from CD" usually appears), but nothing happens.

I'll try to burn it into a CD.

Update:
I finally run Memtest86+ from a bootable CD.
The memories passed 4 tests without a single error, so they are fine.
I will test the HDD now.
Will tell you the results.