Three BSODs within the past few days

[icefall5]

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).

 

[x BlueRobot]

[COLOR="Red"]BugCheck A[/COLOR], {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.

0: kd> [COLOR="SeaGreen"]lmvm netr28x[/COLOR]
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:        [COLOR="red"]Mon Oct 12 14:42:24 2009[/COLOR] (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

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
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:        [COLOR="Red"]Sun May 12 20:09:45 2013[/COLOR] (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

• http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html

 

[icefall5]

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!

 

[icefall5]

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?

 

[x BlueRobot]

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:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

Your very welcome

 

[gregrocker]

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.

 

[Layback Bear]

From gregs post #26
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.

 

[ICIT2LOL]

May I be real simple and without reading from post#1 ask what the temps are?

 

[icefall5]

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:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

Your very welcome

Ran the test, returned no issues. Not sure how to check those voltage levels, however. I've attached a screenshot of MSI Control Center; it gives a bunch of voltages. If I run Afterburner, it says my GPU voltage is 0.850 when not in use. It maxes out at 1.050 when I open WoW (ultra settings). Slots are all clean. (If it matters in any way, the PSU connects directly to the GPU). I had to downgrade to the old wifi card driver, as the new one is broken and causes issues with Steam and other programs.

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.

I've uninstalled and switched to the Windows Update driver before (a hardcore clean install), but I continued to have the problem.

May I be real simple and without reading from post#1 ask what the temps are?

Temps are all normal, I've done extensive monitoring of them with the Galaxy support team (GPU manufacturer) and no issues were found.

EDIT: Another dump posted.

 

[x BlueRobot]

0: kd> [COLOR="SeaGreen"]lmvm netr28x[/COLOR]
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:        [COLOR="Red"]Mon Nov 09 04:07:21 2009[/COLOR] (4AF79579)
    CheckSum:         000CFDB3
    ImageSize:        000C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd>[COLOR="SeaGreen"] lmvm nvlddmkm[/COLOR]
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:        [COLOR="Red"]Sun May 12 20:09:45 2013[/COLOR] (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?

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 - http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html, 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

 

[icefall5]

I did a clean installation back in... January, I think? The problems started in mid-March. As part of my troubleshooting with Galaxy, I did swap out my GPU with my older Radeon HD 5450 (after hardcore uninstalling all of the NVidia drivers first), but it still blue screened.

I never marked it explicitly here (for some reason), but I believe the dump from this earlier post happened while the old card was in.

EDIT: Took the screenshot, forgot to post it. Also attached a dump that just happened.

DOUBLE EDIT: Another dump posted....

 

[gregrocker]

Compare the reinstall you did to the steps recommended to get and keep a perfect Clean Reinstall - Factory OEM Windows 7 which work the same for retail.

If you'll stick with the tools and methods given then you'll get and keep a perfect install for as long as you do.

Other Troubleshooting Steps for Windows 7 to go over your install and hardware.

 

[x BlueRobot]

The 5V and the 12V rails don't look normal to me, it could either be the program not reporting the voltages right or a bad PSU. Does anyone know how the good the reputation of Cooler Master is?

The two drivers are still being blamed:

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`05045000 fffff880`05b26000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:       [COLOR="Red"] Sun May 12 20:09:45 2013[/COLOR] (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> [COLOR="SeaGreen"]lmvm netr28x[/COLOR]
start             end                 module name
fffff880`05b26000 fffff880`05bee000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: netr28x.sys
    Image name: netr28x.sys
    Timestamp:        [COLOR="Red"]Mon Nov 09 04:07:21 2009 [/COLOR](4AF79579)
    CheckSum:         000CFDB3
    ImageSize:        000C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Microsoft Network Inspection System Driver seems to be being blamed in the raw stack text:

0: kd> [COLOR="SeaGreen"]lmvm NisDrvWFP[/COLOR]
start             end                 module name
fffff880`0bcb0000 fffff880`0bcd1000   NisDrvWFP T (no symbols)           
    Loaded symbol image file: NisDrvWFP.sys
    Image path: NisDrvWFP.sys
    Image name: NisDrvWFP.sys
    Timestamp:        [COLOR="Red"]Wed Oct 31 22:43:30 2012[/COLOR] (5091A992)
    CheckSum:         00022C97
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[ICIT2LOL]

The 5V and the 12V rails don't look normal to me, it could either be the program not reporting the voltages right or a bad PSU. Does anyone know how the good the reputation of Cooler Master is?

The two drivers are still being blamed:

0: kd> [COLOR=seagreen]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`05045000 fffff880`05b26000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:       [COLOR=red] Sun May 12 20:09:45 2013[/COLOR] (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> [COLOR=seagreen]lmvm netr28x[/COLOR]
start             end                 module name
fffff880`05b26000 fffff880`05bee000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: netr28x.sys
    Image name: netr28x.sys
    Timestamp:        [COLOR=red]Mon Nov 09 04:07:21 2009 [/COLOR](4AF79579)
    CheckSum:         000CFDB3
    ImageSize:        000C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Microsoft Network Inspection System Driver seems to be being blamed in the raw stack text:

0: kd> [COLOR=seagreen]lmvm NisDrvWFP[/COLOR]
start             end                 module name
fffff880`0bcb0000 fffff880`0bcd1000   NisDrvWFP T (no symbols)           
    Loaded symbol image file: NisDrvWFP.sys
    Image path: NisDrvWFP.sys
    Image name: NisDrvWFP.sys
    Timestamp:        [COLOR=red]Wed Oct 31 22:43:30 2012[/COLOR] (5091A992)
    CheckSum:         00022C97
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hum my own experience with Coolermasters have not been too bad in fact I would buy them if I were not an out and out Corsair person.
I am curious to know what volts are being reported by the BIOS and as well why not get get a good multimeter and test them using the tutorial http://www.sevenforums.com/tutorials/86648-psu-jump-start.html bbut care must be taken anywhere near the PSU casing itself!!

 

[x BlueRobot]

Thanks for the information, and checking the voltages will be much more reliable, as well as, a multimeter to measure the voltages.

 

[ICIT2LOL]

Thanks for the information, and checking the voltages will be much more reliable, as well as, a multimeter to measure the voltages.

Yeah Blue but remember that correct volts don't necessarily mean correct current unfortunately.

Think of it like a car that has 12-13v showing on the meter but has no current capacity for turning th engine over

 

[x BlueRobot]

Thanks again

 

[icefall5]

Completely forgot--I began having the issue before I bought the PSU. I bought this new PSU in the hopes that it was a wattage problem (my old PSU was only 300W), but the problem has persisted.

I'm throwing in the towel and doing a clean install tonight. I'll update you guys after it's done, then we'll really know if it's a hardware or a software issue.

 

[ICIT2LOL]

ON thing you can do Icefall is get something like this Power Meter – Measure Energy Consumption and Cost | Steplight if you want to be able to work out what the machine/s are pulling in watts.

Just because the PSU is say a 500 watt rating dos not mean it is pulling that all the time it depends on the usage of the machine at the time so at high end gaming use for example the PSU might have to belt out 450 watts but at idle it can fall back to 200 watts.

 

[icefall5]

*sigh* Clean install did not fix the problem. Here's today's dump. (My WoW client crashed with an ACCESS_VIOLATION error prior to this BSoD, if that helps.)