Persistent BSOD, Varying Parameters Usually During Gaming Applications

[Scrob]

Hi All,

I've gotten random BSOD for nearly a month now, and I've tried many of the usual suspects with no resolution. I come now to the collective seeking wisdom. Things I've tried thus far with no success (not necessarily in this order);

1. Memtest86. No errors
2. Chkdsk /F No errors
3. Western Digital disk check utility. No errors
3. Antivirus is clean
4. Flash BIOS
5. Replaced power supply
6. Ran Hot CPU Tester Pro for MB errors. No errors
7. GPU torture test (I forget the utility). No errors.
8. Windows reinstall
9. Updated GPU drivers

I'm officially stuck. Any help would be appreciated like you would not believe. I've uploaded the sf diag file. Thanks for your help!

 

[YoYo155]

Hello and welcome .

The dump uploaded is practically useless .

Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
.Unable to add module at ffffffff`ffffffff

BugCheck 7F, {[U][B]8[/B][/U], 80050031, 6f8, fffff80002e95e3f}

What we can tell is is it was a double fault (by looking at the 1st parameter which is 8
of the 0x7F bugcheck code), all it means is that an exception was being handled and while it was
a second exception occurred.

Kernel stack not resident.

Usually I would ask for the Kernel memory dump but I don't think it will help us in this case.
Please run Driver verifier in order to induce a bugcheck which will help us with future diagnosing.

A question, for how many passes did you allow memtest86 go through?

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.

 

[Scrob]

Thanks YoYo155. I'm running driver verifier now and will post a new bugcheck after.

I ran memtest86 overnight and when I was at work the next day. I want to say it ran for something like 16 passes.

 

[YoYo155]

Thanks for the feedback .
Let Driver Verifier crash the machine a couple of times to get an idea of the source.
Also we recommend testing the RAM using the plus version MEMtest86+.

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

 

[Scrob]

Results of Memtest86+, ver. 5.01, 22 passes

Running driver verifier now. Will post new logs after a few crashes. Never rooted for a BSOD to occur before

 

[YoYo155]

Thank for the update, I take it no errors were found ?

 

[Scrob]

No errors, and after 24 hours of driver verify, no crashes. Not sure why my comp decided to stop acting up, but I suppose I'll take it

Should I mark this thread as solved, or keep it open in case the problem reoccurs in the near future?

 

[YoYo155]

Let Driver Verifier run for another day for the sake of extra checking .
After that period disable DV and leave the thread open for another, then if all is well mark as solved.
For any other issues, we are here .

Just to be sure that verifier is running,
Run an elevated command prompt and type in verifier /query.

rb:Start Menu> CMD - right click and Run as administrator.
Type verifier /query hit Enter and post a screenshot of the window.
​

 

[Scrob]

Okay, had a crash tonight while playing Counter Strike:Global Offensive with driver verifier running. Log is attached. Hopefully it will be more helpful than the last one was.

 

[YoYo155]

Thanks .
The dump was a driver writing to the special pool (which is set when enabling the option
when selecting Special pool in Driver verifier) which is used to find drivers that flow over
their allocated space and corrupting other's (drivers) space.

BugCheck C1, {fffff9803e534f10, fffff9803e534d0f, 7500f0, 32}

Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )

0: kd> k
 # Child-SP          RetAddr           Call Site
00 fffff880`03edf3e8 fffff800`03122c73 nt!KeBugCheckEx
01 fffff880`03edf3f0 fffff800`0319b8f3 nt!MiCheckSpecialPoolSlop+0x83
02 fffff880`03edf430 fffff800`031c693b nt!MmFreeSpecialPool+0x1d3
03 fffff880`03edf570 fffff800`030a853e nt!ExDeferredFreePool+0xf33
04 fffff880`03edf620 fffff800`030865d7 nt!IopCompleteRequest+0x5ce
05 fffff880`03edf6f0 fffff800`030897dd nt!KiDeliverApc+0x1c7
06 fffff880`03edf770 fffff800`030960ea nt!KiCommitThreadWait+0x3dd
07 fffff880`03edf800 fffff960`0015a6f0 nt!KeWaitForMultipleObjects+0x272
08 fffff880`03edfac0 fffff960`0015b6b3 win32k!xxxMsgWaitForMultipleObjects+0x108
09 fffff880`03edfb40 fffff960`001150e4 win32k!xxxDesktopThread+0x253
0a fffff880`03edfbc0 fffff960`0019619a win32k!xxxCreateSystemThreads+0x64
0b fffff880`03edfbf0 fffff800`03092e13 win32k!NtUserCallNoParam+0x36
0c fffff880`03edfc20 000007fe`fd6e1eea nt!KiSystemServiceCopyEnd+0x13
0d 00000000`01a6f798 00000000`00000000 0x000007fe`fd6e1eea

DV failed to pinpoint a 3rd party driver, here it blames win32k which interacts with
the graphics drivers.

Please roll back to a more stable release.

Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now.Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Please update your Ethernet controller;

lmvm rt64win7
Browse full module list
start             end                 module name
fffff880`05376000 fffff880`053fb000   Rt64win7   (deferred)             
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U][B]Fri Jun 10 09:33:15 2011[/B][/U][/COLOR]

• Download

Keep Driver Verifier, and post back with the results .

 

[Scrob]

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.

 

[YoYo155]

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.

   Warning

The Following Method Should NOT Be Performed On An SSD!

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 .

 

[Scrob]

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

 

[YoYo155]

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.

 

[Scrob]

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

 

[YoYo155]

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.

 

[YoYo155]

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