Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSODs just while playing FFXIV.

08 Mar 2011   #1

Windows 7 Ultimate x64
 
 
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.


My System SpecsSystem Spec
.

08 Mar 2011   #2

Windows 7 Ultimate x64
 
 

Update:
As I said, I just downgraded the GPU drivers, just to run into another 0x03B BSOD related to atikmdag.sys
My System SpecsSystem Spec
08 Mar 2011   #3
Microsoft MVP

 
 

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:
Quote:
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:
Quote:
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:
Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90บC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit
Quote:
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95
Quote:
Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / VMT
Artifact Locator - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / Artifact Locator
Sorry, but I don't read the language that this website is made in.
Quote:
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: http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
.


08 Mar 2011   #4

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

- 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
My System SpecsSystem Spec
09 Mar 2011   #5

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by usasma View Post
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:
Quote:
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:
Quote:
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:
Quote:
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: http://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.

Quote   Quote: Originally Posted by DeanP View Post
- 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
My System SpecsSystem Spec
09 Mar 2011   #6

Windows 7 Ultimate x64
 
 

Update:
I already tried to uninstall the CCC, as suggested in here, but I still have the same BSOD (0x03B atikmdag.sys)
My System SpecsSystem Spec
09 Mar 2011   #7

Windows 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
09 Mar 2011   #8

Windows 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
09 Mar 2011   #9
Microsoft MVP

 
 

Just because you "passed" Furmark that doesn't mean that there aren't any problems with your video card - just that there weren't any problems with the burn-in.

You're supposed to run the perfmon.exe file and save a report as perfmon.html Don't bother with it yet. If it's needed I'll request it from you later on.

Please visit Windows Update and ensure that you have all needed updates. Then check the Important Updates for Service Pack 1 and install that.

The sptd.sys driver for Daemon Tools is known to cause BSOD's. Please uninstall Daemon Tools, then use this free tool to remove the troublesome sptd.sys driver: DuplexSecure - FAQ - Remove 64 bit sptd.sys

As you've observed, the BSOD's point primarily to your video drivers. This most likely means that there's a problem in the video sub-system of your computer. I think that the most significant point here is that you get errors when installing/removing the drivers. To me that points to the video card sub-system, and the string of BSOD's tends to confirm that. While the STOP 0x3B's could be anything video-related, the STOP 0x119 is more closely related to hardware issues (but not always).

Since you just purchased the GPU, I would see about returning it for another one as soon as you can. That way you can test another video card without having to spend more money.

Beyond that you'll have to try and install the latest drivers from nVidia if you haven't already done that. If the errors continue, then it's time to test with another video card. to see if you get the same errors. While the video card is the most likely suspect, there's also a possibility that the motherboard may be having issues - and trying another video card will tell us where the error is.

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:
Quote:
Code:

AtiPcie.sys     Tue May 05 11:00:22 2009 (4A005486)
avipbb.sys      Mon Feb 22 05:08:50 2010 (4B8257B2)
LMouFilt.Sys    Tue Aug 24 13:21:43 2010 (4C73FFA7)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
Rt64win7.sys    Thu Feb 26 04:04:13 2009 (49A65B0D)
netr7364.sys    Thu Mar 12 23:13:08 2009 (49B9CF44)
LHidFilt.Sys    Tue Aug 24 13:21:36 2010 (4C73FFA0)
RtHDMIVX.sys    Mon May 24 08:07:55 2010 (4BFA6C1B)
MijXfilt.sys    Fri Dec 31 02:54:06 2010 (4D1D8C1E)
xusb21.sys      Wed Apr 08 10:28:44 2009 (49DCB49C)
avgntflt.sys    Thu Nov 11 10:59:48 2010 (4CDC12F4)
RTKVHD64.sys    Wed Jul 28 06:01:36 2010 (4C500000)
dtsoftbus01.sys Thu Jan 13 03:27:08 2011 (4D2EB75C)

http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#avipbb.sys
http://www.carrona.org/dvrref.html#LMouFilt.Sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#netr7364.sys
http://www.carrona.org/dvrref.html#LHidFilt.Sys
http://www.carrona.org/dvrref.html#RtHDMIVX.sys
http://www.carrona.org/dvrref.html#MijXfilt.sys
http://www.carrona.org/dvrref.html#xusb21.sys
http://www.carrona.org/dvrref.html#avgntflt.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#dtsoftbus01.sys
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 18:41:29.640 2011 (UTC - 5:00)
System Uptime: 0 days 0:16:21.434
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c
Bugcheck code 00000119
Arguments 00000000`07000000 fffffa80`05534410 fffffa80`066948f0 fffffa80`03e6d900
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 18:23:34.169 2011 (UTC - 5:00)
System Uptime: 0 days 2:58:30.948
Probably caused by : atikmdag.sys ( atikmdag+3f058b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3f058b
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0743b58b fffff880`0a3ee7b0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 15:02:28.151 2011 (UTC - 5:00)
System Uptime: 0 days 0:24:56.556
Probably caused by : atikmdag.sys ( atikmdag+3a956e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3a956e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0744c56e fffff880`0907a7b0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 14:10:52.047 2011 (UTC - 5:00)
System Uptime: 0 days 1:36:14.826
Probably caused by : atikmdag.sys ( atikmdag+3b684e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3b684e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`073ea84e fffff880`03aa27a0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 12:31:33.500 2011 (UTC - 5:00)
System Uptime: 0 days 1:57:31.279
Probably caused by : atikmdag.sys ( atikmdag+3f058b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3f058b
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0742958b fffff880`0bd657b0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
  
My System SpecsSystem Spec
09 Mar 2011   #10

Windows 7 Ultimate x64
 
 

I'll answer you in bold red.
Quote   Quote: Originally Posted by usasma View Post
Just because you "passed" Furmark that doesn't mean that there aren't any problems with your video card - just that there weren't any problems with the burn-in.
Yeah, but the longest I've played FFXIV is 30 min/1 hour without crashing, so it was really suprising to run it for 2 hours without any problem.

You're supposed to run the perfmon.exe file and save a report as perfmon.html Don't bother with it yet. If it's needed I'll request it from you later on.
Ok. Just tell me when to do so.

Please visit Windows Update and ensure that you have all needed updates. Then check the Important Updates for Service Pack 1 and install that.
No updates avalaible.

The sptd.sys driver for Daemon Tools is known to cause BSOD's. Please uninstall Daemon Tools, then use this free tool to remove the troublesome sptd.sys driver: DuplexSecure - FAQ - Remove 64 bit sptd.sys
The problems have begun way before installing Daemon Tools. Anyway, I will uninstall it, just to be sure.

As you've observed, the BSOD's point primarily to your video drivers. This most likely means that there's a problem in the video sub-system of your computer. I think that the most significant point here is that you get errors when installing/removing the drivers. To me that points to the video card sub-system, and the string of BSOD's tends to confirm that. While the STOP 0x3B's could be anything video-related, the STOP 0x119 is more closely related to hardware issues (but not always).

Since you just purchased the GPU, I would see about returning it for another one as soon as you can. That way you can test another video card without having to spend more money.

Beyond that you'll have to try and install the latest drivers from nVidia if you haven't already done that. If the errors continue, then it's time to test with another video card. to see if you get the same errors. While the video card is the most likely suspect, there's also a possibility that the motherboard may be having issues - and trying another video card will tell us where the error is.
It's an Ati GPU. I got the latest drivers installed(11-2). I've also tested it with the 11-1 ones, and I had the same crashes.
I already removed my new GPU (HD6950) and tested it with my old HD4850 which gave me also the same crashes while playing FFXIV.
I also thought it could be the motherboard... but is there any way to test it without having to totally replace it for another one?
The motherboard has its latest BIOS installed, too.


OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:
Quote:
Code:

AtiPcie.sys     Tue May 05 11:00:22 2009 (4A005486)
avipbb.sys      Mon Feb 22 05:08:50 2010 (4B8257B2)
LMouFilt.Sys    Tue Aug 24 13:21:43 2010 (4C73FFA7)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
Rt64win7.sys    Thu Feb 26 04:04:13 2009 (49A65B0D)
netr7364.sys    Thu Mar 12 23:13:08 2009 (49B9CF44)
LHidFilt.Sys    Tue Aug 24 13:21:36 2010 (4C73FFA0)
RtHDMIVX.sys    Mon May 24 08:07:55 2010 (4BFA6C1B)
MijXfilt.sys    Fri Dec 31 02:54:06 2010 (4D1D8C1E)
xusb21.sys      Wed Apr 08 10:28:44 2009 (49DCB49C)
avgntflt.sys    Thu Nov 11 10:59:48 2010 (4CDC12F4)
RTKVHD64.sys    Wed Jul 28 06:01:36 2010 (4C500000)
dtsoftbus01.sys Thu Jan 13 03:27:08 2011 (4D2EB75C)

http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#avipbb.sys
http://www.carrona.org/dvrref.html#LMouFilt.Sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#netr7364.sys
http://www.carrona.org/dvrref.html#LHidFilt.Sys
http://www.carrona.org/dvrref.html#RtHDMIVX.sys
http://www.carrona.org/dvrref.html#MijXfilt.sys
http://www.carrona.org/dvrref.html#xusb21.sys
http://www.carrona.org/dvrref.html#avgntflt.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#dtsoftbus01.sys
I will update them right now.

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 18:41:29.640 2011 (UTC - 5:00)
System Uptime: 0 days 0:16:21.434
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c
Bugcheck code 00000119
Arguments 00000000`07000000 fffffa80`05534410 fffffa80`066948f0 fffffa80`03e6d900
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 18:23:34.169 2011 (UTC - 5:00)
System Uptime: 0 days 2:58:30.948
Probably caused by : atikmdag.sys ( atikmdag+3f058b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3f058b
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0743b58b fffff880`0a3ee7b0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 15:02:28.151 2011 (UTC - 5:00)
System Uptime: 0 days 0:24:56.556
Probably caused by : atikmdag.sys ( atikmdag+3a956e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3a956e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0744c56e fffff880`0907a7b0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 14:10:52.047 2011 (UTC - 5:00)
System Uptime: 0 days 1:36:14.826
Probably caused by : atikmdag.sys ( atikmdag+3b684e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3b684e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`073ea84e fffff880`03aa27a0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 12:31:33.500 2011 (UTC - 5:00)
System Uptime: 0 days 1:57:31.279
Probably caused by : atikmdag.sys ( atikmdag+3f058b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ffxivgame.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3f058b
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0742958b fffff880`0bd657b0 00000000`00000000
BiosVersion = FDf
BiosReleaseDate = 07/12/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA78G-DS3H
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
  
I already ran the HDD tests, and it's totally Ok. I had 0 errors.
I also ran an antimalware and an antispyware test, having 0 infections.


Update:
I've revised all the drivers. I've installed some "new" ones. Most of them are up to date.

What free Antivirus do you recommend me? I'm currently using Avira, as you see, and have had 0 problems with it.
My System SpecsSystem Spec
Reply

 BSODs just while playing FFXIV.




Thread Tools



Similar help and support threads for2: BSODs just while playing FFXIV.
Thread Forum
BSOD While playing FFXI/FFXIV + more. BSOD Help and Support
BSOD playing FFXIV ARR, hal.dll error 0x00000124 BSOD Help and Support
BSOD playing FFXIV (Final Fantasy 14), not sure of error code BSOD Help and Support
Frequent BSOD playing FFXIV:ARR + BF3 BSOD Help and Support
BSOD playing 3D games (The Witcher 2, FFXIV beta, SC5) various errors BSOD Help and Support
BSOD - Playing NBA2k13, FFXIV, Borderlands 2, etc BSOD Help and Support
random bsods when playing wow or playing movies BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

ฉ Designer Media Ltd

All times are GMT -5. The time now is 08:07 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33