Windows 7: Persistent BSOD, Varying Parameters Usually During Gaming Applications

Okay, I was not sure if when you said "Please roll back to a stable release" you were referring to the instructions below, or to an additional step. I followed all the steps listed RE:nVidia and updating my ethernet controller, and things have become much more unstable. I disabled DV. The most recent dump is attached. I did not attempt to do anything with win32k.

Thanks for the update .

By "roll back to a more stable release" I referred to the nvidia quote below.
win32k, is a core Microsoft component nothing should be done regarding it.
Unfortunately the dumps are pretty corrupt again .

Let's run some test.



Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fxkey.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Scanning for infections / corrupt files:

• Download Speccy and upload a Screenshot of the summary tab.
• Download TDSS-Killer and scan for rootkits.
• Download Windows Defender Offline and scan for other types of infections.
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

Post back with the results .

Okay, here we go.

1. Check disk seems clean. File attached.
2. No issue with SeaTools.
3. Speccy screenshot is attached.
4. TDSS-Killer is clean
5. Full scan with WDO found no problems.
6. Scannow was clean.
7. Couple more blue screens. New SF diag file attached.

Thanks for all your help with this. This isn't proving to be a quick fix

I get the same errors while trying to open the last dumps as I had with the others .
I'll ask some else to have a look to see if the technical issues are on my end or the files themselves.

Sounds good. I had a couple more crashes, so here are new dumps in case they might be helpful.

I'm sorry but I'm still getting errors, just to shed some light on the subject it due to a recent
security update Microsoft has released which changed the time stamp of a vital file which they haven't
updated yet in the symbol server.

I can't do much with the dump files at the moment .
All I can see is that they are the same 0xE1 which is generally a driver issue.

Update!

The symbols server is back in working order now (finally!)
So I was able to look at the dumps in a more meaningful manner .

There appears to be some issues with Avast and a Sendori internet security oriented software.
Please remove both programs (at least for troubleshooting purposes) and see how the machine
holding up.

Please use Microsoft Security Essentials as an alternative.

• Microsoft Security Essentials - Microsoft Windows