BSOD playing WoW and different BSODs while doing other stuff

The last two bug checks usual causes are drivers / RAM.
In one the running process is a Bittorrent client so again network related, the other
listed Speccy and the previously suspected rax register.

Code:

FOLLOWUP_IP: 
disk!DiskIoctlSmartReceiveDriveData+219
fffff880`01645479 488be8          mov     rbp,rax

FAILURE_BUCKET_ID:  X64_0xC5_2_disk!DiskIoctlSmartReceiveDriveData+219

I don't see any Anti-Virus monitoring software installed, are you not using any?
(MalwareBytes is not an AV)

Clean up your startup by following this tutorial:

• Troubleshoot Application Conflicts by Performing a Clean Startup

Make sure that both SSD's are running the latest firmware.

Code:

Model    INTEL SSDSC2MH120A2 ATA Device
Model    KINGSTON SVP100S296G ATA Device

Remove any trace of this Wireless adapter if not in use, via RevoUninstaller.

Code:

Product Type    Belkin Play Wireless USB Adapter

Enable Driver Verifier:

Arc said:

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Mangaza said:

I only use malwarebytes, no other anti-virus software. I don't download anything much and haven't had a problem with just malwarebytes in the past 2-3 years now.

That is not a true protection solution.

Please scan for possible infection and file corruption.

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Download Malwarebytes and DON'T activate the trail (uncheck the box at the end of the installation)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)

Mangaza said:

I went into Device Manager and tried to update both ssd's and both give me the message saying it's up to date, unless device manager is inaccurate?

The device manager is unaware of the SSD's firmware nor is anything in Windows, this has to be check and updated via their respectable software, for example Samsung has their Magician. Each manufacturer
has their own utility you have to use.

Post back with the results.

Thanks for the update :).
So will I .

YoYo155 said:

Thanks for the update :).
So will I .

For the past 3-4 hours, I got 2-3 "Desktop Window Manager has stopped working" if that matters at all with verifier working, and I just got a bsod less than 5 minutes ago at the time of this post that gave me the error message of: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION - I think this means my RAM is defective and needs to be replaced if I want the BSODs to go away? I attached a new file using the SF tool that includes the latest minidump of the BSOD for you to check!

Also, here's a screenshot of the BSOD message: https://i.imgur.com/bFrAARa.jp

Let me know what you're able to come up with - the root/cause & solution! please :)

Thanks for the update.
Verifier seems to blame the nVidia driver, although I'm not completely sold on it,
physically remove it for troubleshooting purposes and use the integrated graphics.

Code:

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff9802263efb0, address trying to free
Arg2: fffff9802263e298, address where one bit is corrupted
Arg3: 0000000000cd4058, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+d2c5d )

lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff880`0f27c000 fffff880`0feb3000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Oct 23 09:21:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Keep Driver Verifier enabled for a few days and update with new dumps if any.

I'm pretty sure I reinstalled the graphics card driver successfully - are you able to determine that in the file I attached? I don't think I can remove the graphics card physically because I remember a few pages back that I removed the integrated graphics/deleted the driver? I'll keep driver verifier enabled and see what happens. Alternatively, maybe I can uncheck the nvidia driver for verifier instead of removing it or is it not the same? Would prefer not to remove graphics card (I know it's easy to remove/put in, but I actually haven't done it before without breaking the unlock handle on my old graphics card - would do it as a last resort option if there are no alternative options available, however) The graphics card is relatively new too .

If it matters, I was watching a tv show episode 1080p on my computer when I got my first bsod with verifier running.

Update: Approximately 5-6 hours after enabling verifier again, I get another BSOD. I had the following open: Hearthstone beta (low system requirements game) and a 720p hd tv show open with a video player along with other small applications open like Skype. I have the nvidia driver checked in verifier for this bsod. I just went over some stuff, and I left my internet connected when I was uninstalling / removing / cleaning the graphics card drivers, so I am not completely sure if windows automatically installed the latest graphics driver, but I did do a clean installation with the 331.65 latest one and my control panel says I have the 331.65 driver installed + physx

2nd update: I got another bsod ~2 hours ago with nothing running besides skype, I attached the new zipped file that I got from the SF tool. I'm going to turn off verifier now since I need to do some stuff, and that might be better since we've got BSODs with verifier and now you can compare bsods with verifier running and to those without verifier running after I updated the graphics card and other drivers? I reinstalled the graphics driver again - this time, cut off internet connectivity during reinstall to ensure that windows can't try to automatically search for a driver online and install during the manual reinstall.

In addition to all of the above, I thought this new appcrash thing was an isolated incident, but it's not. For the past few days, I've been getting game freezes randomly for just about any game, where the game would completely freeze or give me an error saying appcrashed / game screen would completely freeze / not responding and tell me I need to restart/close the game or check online for a solution.

3rd update: So I turned off verifier and tried to do my stuff, 2-3 hours of running computer normally without verifier enabled (but had 4 sticks of ram, removed it after getting a bsod), my comp gets a bsod and restarts immediately after. The attached file contains the bsods with verifier enabled and a bsod without that just happened. I'm gonna go ahead and order some new ram that's listed under my motherboard's supported ram and see if that fixes problems. Every computer part is new besides RAM/SSD/HDD, and since RAM is more prone to causing crashes/bsods, I think I'm going to replace RAM and see if the problem fixes itself...hopefully

Thanks for the updates. Sorry, I couldn't respond sooner.

Driver verifier is determine on blaming the graphics of the equation, at this point I'm inclined to agree.

Code:

0xfffff8800716e488 : 0xfffff800032a2d12 : nt!RtlpLookupFunctionEntryForStackWalks+0x32
0xfffff8800716e598 : 0xfffff8800fe6803c : "dxgkrnl!_fastflag <PERF> (dxgkrnl+0x2003c)"
0xfffff8800716e5a8 : 0xfffff8800fe48000 : "dxgkrnl!DXGADAPTER::AcquireDdiSync <PERF> (dxgkrnl+0x0)"
0xfffff8800716e698 : 0xfffff800032a2d12 : nt!RtlpLookupFunctionEntryForStackWalks+0x32
0xfffff8800716e6a8 : 0xfffff8800716e850 : 0xfffff8800f211000 : nvlddmkm
0xfffff8800716e708 : 0xfffff8000338c376 : nt!RtlpWalkFrameChain+0x2e6
0xfffff8800716e748 : 0xfffff8000338c376 : nt!RtlpWalkFrameChain+0x2e6
0xfffff8800716e7b8 : 0xfffff8800f211000 : nvlddmkm
0xfffff8800716e850 : 0xfffff8800f211000 : nvlddmkm
0xfffff8800716e8a8 : 0xfffff8800ff3de88 : dxgmms1!VidMmCloseAllocation
0xfffff8800716e8b0 : 0xfffff8800ff76b37 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1f3
0xfffff8800716e8b8 : 0xfffff8800ff3c000 : "dxgmms1!DXGADAPTER::DdiQueryAdapterInfo <PERF> (dxgmms1+0x0)"
0xfffff8800716e8c0 : 0xfffff8800ff52e04 : "dxgmms1!gulSyncObjTimeouted <PERF> (dxgmms1+0x16e04)"
0xfffff8800716e8c8 : 0xfffff8800ff3c000 : "dxgmms1!DXGADAPTER::DdiQueryAdapterInfo <PERF> (dxgmms1+0x0)"
0xfffff8800716e8d0 : 0xfffff8800ff52ac8 : "dxgmms1!gulSyncObjTimeouted <PERF> (dxgmms1+0x16ac8)"
0xfffff8800716e8d8 : 0xfffff8800ff3c000 : "dxgmms1!DXGADAPTER::DdiQueryAdapterInfo <PERF> (dxgmms1+0x0)"
0xfffff8800716e8e0 : 0xfffff8800ff52a74 : "dxgmms1!gulSyncObjTimeouted <PERF> (dxgmms1+0x16a74)"
0xfffff8800716e8e8 : 0xfffff8800ff3c000 : "dxgmms1!DXGADAPTER::DdiQueryAdapterInfo <PERF> (dxgmms1+0x0)"

If you're not inclined to fiddle around with the hardware it's up to you but
it's also out of my online reach :\ .

Another thing is, it also bug checked twice with (again!) network activity on the stack, your driver is the latest that Intel offers, this is also inline with the faults we saw earlier on teamspeak.
let's try the latest driver offered by your motherboard's OEM.

Code:

k
Child-SP          RetAddr           Call Site
fffff880`08bb1928 fffff800`0336a1bb nt!KeBugCheckEx
fffff880`08bb1930 fffff800`0332bd18 nt!KipFatalFilter+0x1b
fffff880`08bb1970 fffff800`03303cdc nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`08bb19b0 fffff800`0330375d nt!_C_specific_handler+0x8c
fffff880`08bb1a20 fffff800`03302535 nt!RtlpExecuteHandlerForException+0xd
fffff880`08bb1a50 fffff800`033134c1 nt!RtlDispatchException+0x415
fffff880`08bb2130 fffff800`032d8242 nt!KiDispatchException+0x135
fffff880`08bb27d0 fffff800`032d6b4a nt!KiExceptionDispatch+0xc2
fffff880`08bb29b0 fffff800`032e1dac nt!KiGeneralProtectionFault+0x10a
fffff880`08bb2b40 fffff880`02f485b0 nt!ObfDereferenceObject+0x2c
fffff880`08bb2ba0 fffff880`02f39448 afd!AfdCompletePollIrp+0xa0
fffff880`08bb2c00 fffff880`02efa754 afd!AfdIndicatePollEvent+0x138
fffff880`08bb2c50 fffff880`02f3e699 afd!AfdReceiveDatagramEventCommonHandler+0x264
fffff880`08bb2cf0 fffff880`01a85ca5 afd!AfdTLDgramReceiveEventHandler+0xe9
fffff880`08bb2d80 fffff880`01a8021b tcpip!UdpDeliverDatagrams+0x155
fffff880`08bb2f10 fffff880`01a469c3 tcpip!UdpReceiveDatagrams+0x21b
fffff880`08bb2fb0 fffff880`01a576f2 tcpip!IpFlcReceivePreValidatedPackets+0x923
fffff880`08bb3110 fffff800`032e4878 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2
fffff880`08bb3160 fffff880`01a57e22 nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`08bb3240 fffff880`019580eb tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`08bb32b0 fffff880`01921ad6 ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`08bb3320 fffff880`0189bac1 ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`08bb37a0 fffff880`040257c3 ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`08bb37f0 fffffa80`076ea000 e1d62x64+0x257c3
fffff880`08bb37f8 00000000`00000001 0xfffffa80`076ea000
fffff880`08bb3800 fffffa80`07d03520 0x1
fffff880`08bb3808 fffffa80`076eae00 0xfffffa80`07d03520
fffff880`08bb3810 00000000`00000801 0xfffffa80`076eae00
fffff880`08bb3818 00000000`00000001 0x801
fffff880`08bb3820 00000000`00000001 0x1
fffff880`08bb3828 fffff880`04025991 0x1
fffff880`08bb3830 00000000`00000001 e1d62x64+0x25991
fffff880`08bb3838 fffffa80`07d03520 0x1
fffff880`08bb3840 fffffa80`07d03520 0xfffffa80`07d03520
fffff880`08bb3848 fffffa80`076ea000 0xfffffa80`07d03520
fffff880`08bb3850 fffffa80`00000000 0xfffffa80`076ea000
fffff880`08bb3858 fffffa80`076ea0cc 0xfffffa80`00000000
fffff880`08bb3860 0000000a`00000001 0xfffffa80`076ea0cc
fffff880`08bb3868 00000000`00000000 0x0000000a`00000001

• Download

Also I see a new BIOS has recently been released with regards to PCI-e compatibility,
are you comfortable performing a BIOS flash?