Solved BSOD playing WoW - happens occasionally

[Deception]

Anyone? Guys I really need some help. BSOD just occurred again: 3 and counting...

 

[writhziden]

Your new crashes are no longer related to your original crashes since you changed out some hardware. I would suggest starting a new thread to get the new problems resolved.

 

[Deception]

I was told to not start a new thread according to the rules on this site/forum. Soo how bout I get some help.. lol

 

[writhziden]

I was told to not start a new thread according to the rules on this site/forum. Soo how bout I get some help.. lol

We'll do our best. Part of why I suggested a new thread is those who were helping may no longer be subscribed to this thread and may not have noticed you posted. Since it is a longer thread, it may also be missed by people thinking it already received help. I just happened on it by chance last night when I was going through each new thread.

If no one gets back to you who had been helping previously, I will read through the thread and analyze all your files and get back to you later today or tomorrow.

Edit: Tried to take a look at your logs, and you did not include the crash report, just the executable for generating it.

 

[Deception]

I was told to not start a new thread according to the rules on this site/forum. Soo how bout I get some help.. lol

We'll do our best. Part of why I suggested a new thread is those who were helping may no longer be subscribed to this thread and may not have noticed you posted. Since it is a longer thread, it may also be missed by people thinking it already received help. I just happened on it by chance last night when I was going through each new thread.

If no one gets back to you who had been helping previously, I will read through the thread and analyze all your files and get back to you later today or tomorrow.

Edit: Tried to take a look at your logs, and you did not include the crash report, just the executable for generating it.

I can't figure out where it throws my file/folder when I do the executable. :|

 

[writhziden]

It should put it in the same folder the executable is saved in. You should save the executable in your documents folder so it generates the crash files in the documents folder with it.

 

[Deception]

Here are the files.. hopefully someone can help out!

 

[writhziden]

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


Loading Dump File [F:\Kingston\BSODDmpFiles\Deception\Windows_NT6_BSOD_jcgriff2\013012-10124-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e46670
Debug session time: Mon Jan 30 18:09:48.025 2012 (GMT-7)
System Uptime: 0 days 0:56:50.820
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880032a07b0, 0, fffff8800482fbf0, 0}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880032a07b0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800482fbf0, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb0100
 fffff880032a07b0 

FAULTING_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430
fffff880`0482fbf0 44846920        test    byte ptr [rcx+20h],r13b

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006bd8830 -- (.trap 0xfffff88006bd8830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007de6b00 rbx=0000000000000000 rcx=fffff880032a0790
rdx=fffff8a00f1391f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800482fbf0 rsp=fffff88006bd89c0 rbp=fffffa8008196000
 r8=0000000000000000  r9=fffff88006bd8b10 r10=fffff8a00cdfeff0
r11=fffff88005305a08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x430:
fffff880`0482fbf0 44846920        test    byte ptr [rcx+20h],r13b ds:0003:fffff880`032a07b0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c299fc to fffff80002c7dc40

STACK_TEXT:  
fffff880`06bd86c8 fffff800`02c299fc : 00000000`00000050 fffff880`032a07b0 00000000`00000000 fffff880`06bd8830 : nt!KeBugCheckEx
fffff880`06bd86d0 fffff800`02c7bd6e : 00000000`00000000 fffff880`032a07b0 fffffa80`0817e000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`06bd8830 fffff880`0482fbf0 : 00000000`00080000 fffff8a0`0f1391f0 fffffa80`07dff820 00000098`00000098 : nt!KiPageFault+0x16e
fffff880`06bd89c0 fffff880`0482025d : fffffa80`07de69c0 fffff8a0`0f1391f0 fffffa80`096a1800 fffffa80`08196000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x430
fffff880`06bd8b30 fffff880`0481b358 : fffffa80`09298a70 00000000`00000000 00000000`00000000 fffff880`06bd8ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`06bd8c50 fffff880`0483916d : fffffa80`00000000 fffffa80`080f2410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`06bd8ca0 fffff880`048383f8 : fffff800`00b96080 fffffa80`095128e0 00000000`00000000 fffffa80`080f2410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`06bd8cd0 fffff880`04837e96 : 00000000`00000000 fffffa80`095128e0 00000000`00000080 fffffa80`080f2410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`06bd8d00 fffff800`02f18fee : 00000000`fffffc32 fffffa80`07de6b60 fffffa80`06a06040 fffffa80`07de6b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06bd8d40 fffff800`02c6f5e6 : fffff800`02df3e80 fffffa80`07de6b60 fffff800`02e01cc0 fffff880`01232384 : nt!PspSystemThreadStartup+0x5a
fffff880`06bd8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430
fffff880`0482fbf0 44846920        test    byte ptr [rcx+20h],r13b

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

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

Your crash was DirectX/Graphics card related. Other possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

I do know that I only have a 600watt Power Supply and when most people have this GPU.. they run with like 850w and what not. Let me know if there is a way to test this and figure this out because honestly it might be the issue. It also might NOT be soooo help me figure this out people so I know if I need to return this card or not! Got 60days usually.

550 Watt or greater power supply. You are pushing the limits here a little. 750W would probably be better.

Try these steps to test the graphics card and what it can handle and what your computer can handle.

• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

 

[Deception]

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


Loading Dump File [F:\Kingston\BSODDmpFiles\Deception\Windows_NT6_BSOD_jcgriff2\013012-10124-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e46670
Debug session time: Mon Jan 30 18:09:48.025 2012 (GMT-7)
System Uptime: 0 days 0:56:50.820
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880032a07b0, 0, fffff8800482fbf0, 0}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880032a07b0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800482fbf0, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb0100
 fffff880032a07b0 

FAULTING_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430
fffff880`0482fbf0 44846920        test    byte ptr [rcx+20h],r13b

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006bd8830 -- (.trap 0xfffff88006bd8830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007de6b00 rbx=0000000000000000 rcx=fffff880032a0790
rdx=fffff8a00f1391f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800482fbf0 rsp=fffff88006bd89c0 rbp=fffffa8008196000
 r8=0000000000000000  r9=fffff88006bd8b10 r10=fffff8a00cdfeff0
r11=fffff88005305a08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x430:
fffff880`0482fbf0 44846920        test    byte ptr [rcx+20h],r13b ds:0003:fffff880`032a07b0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c299fc to fffff80002c7dc40

STACK_TEXT:  
fffff880`06bd86c8 fffff800`02c299fc : 00000000`00000050 fffff880`032a07b0 00000000`00000000 fffff880`06bd8830 : nt!KeBugCheckEx
fffff880`06bd86d0 fffff800`02c7bd6e : 00000000`00000000 fffff880`032a07b0 fffffa80`0817e000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`06bd8830 fffff880`0482fbf0 : 00000000`00080000 fffff8a0`0f1391f0 fffffa80`07dff820 00000098`00000098 : nt!KiPageFault+0x16e
fffff880`06bd89c0 fffff880`0482025d : fffffa80`07de69c0 fffff8a0`0f1391f0 fffffa80`096a1800 fffffa80`08196000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x430
fffff880`06bd8b30 fffff880`0481b358 : fffffa80`09298a70 00000000`00000000 00000000`00000000 fffff880`06bd8ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`06bd8c50 fffff880`0483916d : fffffa80`00000000 fffffa80`080f2410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`06bd8ca0 fffff880`048383f8 : fffff800`00b96080 fffffa80`095128e0 00000000`00000000 fffffa80`080f2410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`06bd8cd0 fffff880`04837e96 : 00000000`00000000 fffffa80`095128e0 00000000`00000080 fffffa80`080f2410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`06bd8d00 fffff800`02f18fee : 00000000`fffffc32 fffffa80`07de6b60 fffffa80`06a06040 fffffa80`07de6b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06bd8d40 fffff800`02c6f5e6 : fffff800`02df3e80 fffffa80`07de6b60 fffff800`02e01cc0 fffff880`01232384 : nt!PspSystemThreadStartup+0x5a
fffff880`06bd8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430
fffff880`0482fbf0 44846920        test    byte ptr [rcx+20h],r13b

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

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

Your crash was DirectX/Graphics card related. Other possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

I did all of this the other day when I was first experiencing the issue. Everything is 100% fine, nothing is wrong with DirectX.

So.. with that said I will work on running the 3 tests that you have told me to!

 

[writhziden]

Any results from the graphics card/hardware tests?

 

[Deception]

I know that this took awhile to do but I have still been blue screening with that direct x error..

I ran the Prime 95 test for 3 minutes and had no errors BUT my CPU temps were getting way to high. Around 70Degrees for the individual cores. I'm going to attempt to reseat it with some new thermal paste (this processor has never been reseated and it's 5 years old) so I will try running the test again after this!

 

[Deception]

Just reseated the processor and running the Prime 95 Test again (FFT's portion -- that's what I ran before as well)

Currently my temperatures are about max of 67 degrees celsius at like 5minutes in. It really isn't climbing much higher than that -- very slowly if anything. SO YES it is a lot better but still hot. I don't know if this could cause the Directx BSOD when i'm intense gaming/multitasking but it does seem like a slight issue... I will run the rest of the prime 95 tests and the other ones you mentioned..

 

[Deception]

9 Minutes in, 0 Errors, 0 warnings - I'm stopping it because I hit 69 Degrees Celsius on one of my cores and I am going out for the night so I don't want to leave it on without me here.

Definitely a significant increase in performance after reseating the processor. I hope this solves my BSOD issue but like I said before, I will run the other tests.

LOL here... look at the 5 years of amazingness

 

[writhziden]

When you re-seated, did you re-apply the thermal paste? Did you remove the old paste first? If not, you may want to get the equipment to do so and look at Thermal Paste and How To Use It | techPowerUp

 

[Deception]

When you re-seated, did you re-apply the thermal paste? Did you remove the old paste first? If not, you may want to get the equipment to do so and look at Thermal Paste and How To Use It | techPowerUp

Yes, yes I did. I used Arctic Silver 5.

 

[writhziden]

Alright, let us know how things are responding in a few days. Looks like you did everything right, and it did sound like you had improved stability, so we just need to monitor and wait for a bit.