BSOD 7e, 3b, and a primarily while gaming

[Crypt135]

Windows 7 Home Premium, 64bit (Original installed OS).
Full Retail.
System is about a year and a half old (pre/custom built).
Most recent OS installation was probably about a year ago.
Antivirus is Microsoft Security Essentials and Malwarebytes (the system health report says I have none for some reason).
If necessary I can provide my system specs.


I've been trying to troubleshoot my BSOD issues the last 2 months (it seemed like I had been narrowing down the problem) but I'm not sure what to do from here. During prolonged gameplay (usually) my computer will BSOD; sometimes quickly, sometimes not at all, always seemingly random. I've been able to reproduce the blue screens most frequently and reliably playing Battlefield 3, with the quickest occurrence happening ~2 seconds into a match.


A few things I've already done:

Ran memtest on two seperate occasions for about 7 passes. No errors.
Updated my nForce drivers and clean installed my graphics card driver.
Updated my router firmware and network adapter driver.
Updated and then later uninstalled my mouse software/it's related driver (the mouse driver was one of the "causes" of the crashes according to BlueScreenView).
Ran the memory/stress test from OCCT on my graphics card (no problems).


The most relevant BSOD dmp files from the attachment(s) would probably be the newest four. Both a's happened while I was trying driver verifier. The 7e one happened while I was rendering in 3dStudioMax, the 3b along with one of the a's happened while playing Battlefield 3, and the other a happened during startup.


Any help would be appreciated.

Thank you for your time.

 

[scrooge]

what are your temps like?
when was the last time you opened you case up and cleaned it out ?

it may just be dust build up in the case on the fans or something..

scrooge

 

[Crypt135]

Took out my gfx card, ram, and cleaned everything out again. Temps are basically the same as before after trying a few matches of BF3 tonight, ~85-90c on the gfx card (gtx 480, they've always run hot) and ~45-50c on the cpu with max settings. I did not experience a BSOD yet since removing, cleaning, and re-seating everything, but they do seem to occur randomly as I noted before. I'll have to test it more tomorrow.

 

[zigzag3143]

Windows 7 Home Premium, 64bit (Original installed OS).
Full Retail.
System is about a year and a half old (pre/custom built).
Most recent OS installation was probably about a year ago.
Antivirus is Microsoft Security Essentials and Malwarebytes (the system health report says I have none for some reason).
If necessary I can provide my system specs.


I've been trying to troubleshoot my BSOD issues the last 2 months (it seemed like I had been narrowing down the problem) but I'm not sure what to do from here. During prolonged gameplay (usually) my computer will BSOD; sometimes quickly, sometimes not at all, always seemingly random. I've been able to reproduce the blue screens most frequently and reliably playing Battlefield 3, with the quickest occurrence happening ~2 seconds into a match.


A few things I've already done:

Ran memtest on two seperate occasions for about 7 passes. No errors.
Updated my nForce drivers and clean installed my graphics card driver.
Updated my router firmware and network adapter driver.
Updated and then later uninstalled my mouse software/it's related driver (the mouse driver was one of the "causes" of the crashes according to BlueScreenView).
Ran the memory/stress test from OCCT on my graphics card (no problems).


The most relevant BSOD dmp files from the attachment(s) would probably be the newest four. Both a's happened while I was trying driver verifier. The 7e one happened while I was rendering in 3dStudioMax, the 3b along with one of the a's happened while playing Battlefield 3, and the other a happened during startup.


Any help would be appreciated.

Thank you for your time.

Related to skfiltv.sys Audio Driver from Creative Technology Ltd. Yours is from 2008. I would re-install newest.

 

[Crypt135]

Tried a regular update, clean install, and manually deleting the driver, but downloading the newest driver software from Creative always installs the skfiltv.sys 2008 driver version. For some reason, though, even after all of that the corresponding version of the headset driver in the device manager does not match the newest one from their website (even though I just re-installed it 3 times). Mine continues to display the 3/12/2010 driver date and 1.0.0.640 version even though I'm downloading and installing the 6/3/2010 1.01.0004 version.

I'm going to test and see if re-installing the drivers worked anyway.

 

[Crypt135]

Got another BSOD, this time 1E. I'm going to leave my headset unplugged and see if my computer BSOD's again in case skfiltv.sys is still the root cause.

edit: this also happened while playing BF3.

 

[zigzag3143]

Got another BSOD, this time 1E. I'm going to leave my headset unplugged and see if my computer BSOD's again in case skfiltv.sys is still the root cause.

edit: this also happened while playing BF3.

I feel your pain. I am the unfortunate owner of 2 creative products.

Still pointing to the same driver but inconclusive this time.

 

[Crypt135]

Another BSOD without the headset plugged in, this one was 3b.

 

[Crypt135]

I'm still getting the same 3b BSOD since removing the headset. Any suggestions?

 

[Crypt135]

They just keep on coming

Now I'm getting 1e again.

 

[zigzag3143]

Another BSOD without the headset plugged in, this one was 3b.

Related to nvmf6264.sys MCP Networking Function Driver. from NVIDIA Corporation

Ok we can keep doing these crashes one at a time till we finally find the problem. I think a better idea whose time is approaching fast is a clean install. There may be hardware issues but everyone of the previous crashes was from software of some kind.

A clean install will get you going faster.

Your call

 

[Crypt135]

I'd like to try and troubleshoot this a bit more before going with the clean install.

What would be your next suggestion with the blue screen being related to nvmf6264.sys? I recall seeing the MCP Networking Function during the install process of my nForce driver update. Would uninstalling the network adapter driver software from the device manager install a generic driver after reboot (like with the display adapter/gfx card)? Or would that not really accomplish anything in this situation?

 

[Crypt135]

Disregard the last post, I'm going to go ahead and clean install. Hopefully that fixes the issue; I'll post again if it does not.

 

[zigzag3143]

Disregard the last post, I'm going to go ahead and clean install. Hopefully that fixes the issue; I'll post again if it does not.

Smart move. Good luck and let us know if you need help

 

[Crypt135]

Just got another BSOD even after the clean install

 

[zigzag3143]

Just got another BSOD even after the clean install

If this was an absolutely Clean install (just tho OS, no updates, nothing but the OS) and it still BSOD's it probably is hardware.

I would start with Memory.

 

[Crypt135]

I went through the instructions from http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html, let windows take care of its updates and loaded in the drivers from the CD that came with my mobo. Since the BSOD's 99% of the time only occur during games I updated my gfx card driver as well so I could test it with BF3.

I'll run memtest again overnight but I've already done so twice within the last month and no errors have come up.

The dmp files in this and my last post are both from testing for BSOD's in BF3 earlier tonight after the clean install.

 

[Crypt135]

Seven passes with memtest and no errors. What should I try next?

 

[zigzag3143]

Seven passes with memtest and no errors. What should I try next?

Its still a memory exception caused by BF3. Next step is to run Driver verifier to try to trap the actual driver



Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
[/B]

 

[Crypt135]

Ran driver verifier and got this BSOD. I think this was the first time I've seen the BSOD message point specifically to a driver; it looked like an nvidia one, but my computer rebooted too quickly to get a good look at it.