BSODs, Have already RMA'd a few parts.

ipwnatlyfe · 09 Nov 2010

I believe I completely removed those drivers, I just got another crash a minute ago though. Does everything point to needing new memory even though I passed many memory tests? Or is the motherboard still under suspicion?

wish · 10 Nov 2010

Hi again,
Your latest dump have 0x50 bugcheck = PAGE_FAULT_IN_NONPAGED_AREA usual cause by driver or RAM.

Another dump have CODE_CORRUPTION error during play War of Warcraft, and the other game (Star Wars) also crash as well.
That could be hardware fault (RAM, VGA card, CPU or Motherboard) or the game itself that make impact to OS corruption.
Make sure that you have proper game installer not corrupted or infected by virus/trojan. So the test that you can do is perform clean install and don't install any games/software. Then do some normal activity like browsing or play video and see if the problem persist. (since in first post you mentioned random BSOD occurred during game and browsing).

If you think the software is fine then your hardware could be the culprit, try some hardware test:
- RAM test with memtest86
- Video card stress with Furmark
- CPU stress with Prime95
- motherboard --> I dont know how to test it

Code:

Win32 Start Address 0x0000000001391310
Stack Init fffff88007f59db0 Current fffff88007f59900
Base fffff88007f5a000 Limit fffff88007f4f000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`07f59218 fffff800`02d4f8c1 : 00000000`00000050 fffff900`4df958fc 00000000`00000001 fffff880`07f59380 : nt!KeBugCheckEx
fffff880`07f59220 fffff800`02cce82e : 00000000`00000001 fffff900`c2b13010 fffff900`c0219500 fffff900`c1d97250 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`07f59380 fffff960`0031d0ac : fffff960`0027a9c2 fffff8a0`0889fae0 fffff8a0`077351d0 fffff880`07f59930 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`07f59380)
fffff880`07f59518 fffff960`0027a9c2 : fffff8a0`0889fae0 fffff8a0`077351d0 fffff880`07f59930 fffff880`07f598c8 : win32k!MulAccumulateD3DDirtyRect
fffff880`07f59520 fffff880`03f2246e : fffff8a0`0889fae0 fffff880`07f598c8 00000000`620108cc fffff900`c0107010 : win32k!DxgkEngAddRedirBitmapD3DDirtyRgn+0x6a
fffff880`07f59560 fffff880`03f1ed73 : fffff8a0`800141c0 fffff8a0`00000690 fffff880`07f598c0 fffff880`07f598f0 : dxgkrnl!DXGCONTEXT::Present+0x30f2
fffff880`07f59880 fffff960`0027baf0 : fffffa80`047f0060 00000000`7efdb000 fffff8a0`0953bcb0 00000000`00000010 : dxgkrnl!DxgkPresent+0x543
fffff880`07f59bf0 fffff800`02ccf993 : fffffa80`047f0060 00000000`00002514 fffff880`07f59bf8 fffffa80`0420bc80 : win32k!NtGdiDdDDIPresent+0x18
fffff880`07f59c20 00000000`74d213ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`07f59c20)
00000000`0015e058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74d213ca
3: kd> u 0x0000000001391310
00000000`01391310 ??              ???
                          ^ Memory access error in 'u 0x0000000001391310'

ipwnatlyfe · 10 Nov 2010

I've tried all those hardware tests already, and I did most the testing off a clean install of windows. Like I also said before, I've already RMA'd my video card and processor and got a new one of each. Everything points to the RAM even though I've tested it for days with both prime95 and memtest86.

richc46 · 10 Nov 2010

You may want to test the MB. Take a known good stick and test each slot, using memtest86.

wish · 10 Nov 2010

Have you tried Prime95 --> Blend test?
Not "Small FFT" test

yowanvista · 10 Nov 2010

ipwnatlyfe said:

I've tried all those hardware tests already, and I did most the testing off a clean install of windows. Like I also said before, I've already RMA'd my video card and processor and got a new one of each. Everything points to the RAM even though I've tested it for days with both prime95 and memtest86.

This sounds like a bad mobo, ensure that there are no scratches on it. You could clean up the dust in your PC

ipwnatlyfe · 10 Nov 2010

I didn't see any scratches on the motherboard and there is almost no dust in there as this is a fairly new system. The blend test is the one I tried with prime95.

ipwnatlyfe · 10 Nov 2010

Here are a couple more dmp files. I might just decide to buy some new RAM or borrow some to try it out.

Jonathan_King · 10 Nov 2010

Install the latest drivers for your network card here: RALINK SOFTWARE END USER LICENSE AGREEMENT

Remove Magicdisc:

Code:

mcdbus.sys             Tue Feb 24 05:34:07 2009 (49A3CD1F)

...Summary of the dumps

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 10 16:43:12.739 2010 (UTC - 5:00)
System Uptime: 0 days 2:50:14.456
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+8f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+8f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 22:49:13.565 2010 (UTC - 5:00)
System Uptime: 0 days 1:44:15.282
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Xfire.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 20:50:37.027 2010 (UTC - 5:00)
System Uptime: 0 days 7:26:09.370
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c8171 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k+c8171
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 03:51:46.753 2010 (UTC - 5:00)
System Uptime: 0 days 5:06:38.095
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ipwnatlyfe · 10 Nov 2010

Alright, trying those things. There weren't any recent drivers on my manufacture's website but hopefully these help. Earlier in this thread it was said that magicdisc would be an okay alternative to use to daemon tools? Is that not the case?