Three BSODs within the past few days

Sorry for the ridiculously late reply; I've been on vacation for a few weeks.

Just before I left, I did a repair install of the OS in the hopes that it would fix the problem. I got back and used it for some gaming, and it's still BSODing. I ran Data Lifeguard from Western Digital for my HDD (I did the extended test that takes like eight hours), and it found no errors at all. I'm running chkdsk now, and stage 4 (verifying file data) is taking forever (I'm now at 7436 of 152560 files processed after about 20 minutes).

Four more dumps are attached (although they don't appear to have any new information), as well as the screenshots you asked for. My SSD firmware is up-to-date, and Western Digital's site doesn't list any firmware updates for my model (10EARS, Caviar Green).

Code:

BugCheck A, {fffff38000000014, 2, 0, fffff80002094a3c}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+24c )

This bugcheck indicates that driver attempted to access a invalid memory address at a IRQL level which was too high.

Code:

0: kd> lmvm netr28x
start             end                 module name
fffff880`0288a000 fffff880`0294c000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: netr28x.sys
    Image name: netr28x.sys
    Timestamp:        Mon Oct 12 14:42:24 2009 (4AD33240)
    CheckSum:         000BE00F
    ImageSize:        000C2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Ralink RT2860 series Wireless LAN Card seems to be causing a few problems, and is very outdated, please update the driver from here - MediaTek - Downloads Windows

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`07aac000 fffff880`0858d000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun May 12 20:09:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your nVidia graphics card driver also seems to be causing a few problems, ensure you have the latest WHQL version installed:

Version: 320.18
Release Date for Desktops and Notebooks : May 23rd 2013
In Device Manager: 9.18.13.2018

• Latest NVIDIA ForceWare Video Drivers Windows 7

I updated the graphics driver last night as soon as it came up (I believe it was after the BSODs though), so that's all set. I'm updating the wireless card now. I'll let you know if I get more BSODs.

Thank you so much, it really means a ton that you would take so much time to help me over the past two months. This probably sounds corny, but thank you so, so much. I am incredibly appreciative!

Just had another one after updating the wireless card (updated earlier tonight, that is).

Do you have any ideas? We've been through almost every piece of hardware in this system, and everything is up-to-date (I believe) and... I dunno. It's just frustrating. It's not your fault, of course, you guys have been incredibly awesome and helpful. Is this just something I'll have to deal with, or do a full reinstall of Windows to try to fix?

Okay, it's blaming your nVidia graphics card drivers again, can you go into the BIOS and check the voltages for the 3.3V, 5V and 12V settings? Ensure that all the cards and hardware is properly connected and check that the PCI/PCIe slots are free of any dust.

You may want to run this test too:

• NVIDIA/AMD Video Card - Test with OCCT

Your very welcome :)

These observations are from an installer's point of view:

Try turning off the Nvidia software in msconfig>Startup and >Services after hiding all MS Services. You dont' need anything starting up there except AV anyway.

The first thing that should be done after a reinstall is to Run all rounds of Important and Optional Windows Updates after enabling Automatically get recommended drivers and updates for your hardware (Step 3). You can do that now if it's not yet been done, to see if Win7 wants another display driver. As a last resort I'd even uninstall the Nvidia driver and its software, then run Windows Updates to see what WIn7 wants.

Code:

0: kd> lmvm netr28x
start             end                 module name
fffff880`05600000 fffff880`056c8000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: netr28x.sys
    Image name: netr28x.sys
    Timestamp:        Mon Nov 09 04:07:21 2009 (4AF79579)
    CheckSum:         000CFDB3
    ImageSize:        000C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`056d3000 fffff880`061b4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun May 12 20:09:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's still blaming the same two drivers, did the BSODs occur after or before the clean installation of Windows?

I believe, there is a graphics related issue, there seems to be a quite a few functions being called related to DirectX Kernel, however, there also seems to be a few network related calls, maybe a bad motherboard if the crashes occurred after updating the drivers?

Code:

dxgkrnl!DxgNotifyInterruptCB+0x83

The above function is used by the display miniport driver to report a graphics hardware interrupt, therefore I still think there may be something physically wrong with the graphics card itself, or could be the PSU or motherboard.

Do you have a spare graphics card or a onboard graphics card you could revert to?

Run this graphics card stress test - Video Card - Stress Test with Furmark, you may monitor your temperatures with GPU-Z Video card GPU Information Utility

Post a screenshot from the information provided with this program ~ HWMonitor CPUID - System & hardware benchmark, monitoring, reporting