Windows 7: BSOD playing WoW and different BSODs while doing other stuff

Mangaza · 31 Oct 2013

Quote: Originally Posted by YoYo155

Hi, thanks for the update

.
That's odd, we cleared the CMOS four-weeks ago it should have been defaulted to those settings...
(Post #14).

4 weeks ago was before I changed nearly all of my parts on my computer + reinstalled windows/reformatted. I should be doing the memtest tonight since I will be gone for a bit tomorrow so I'll have an extended window to run the memtest

YoYo155 · 31 Oct 2013

Ahh right ! (long gaps

).
That's is even more odd! on a stock fresh motherboard

...
Since you bumped the voltage, did it crash again?

Mangaza · 01 Nov 2013

Quote: Originally Posted by YoYo155

Ahh right ! (long gaps

).
That's is even more odd! on a stock fresh motherboard

...
Since you bumped the voltage, did it crash again?

I haven't gotten any bsods since 10/26 and I haven't gotten any crashes since I made voltage what it should be at 1.65v.

Here is a memtest that I ran for 11+ hours: https://i.imgur.com/hVzOebE.jpg

YoYo155 · 01 Nov 2013

Thanks for the update

.
Great news !
Did you do all the usual things you normally do?

Mangaza · 01 Nov 2013

Quote: Originally Posted by YoYo155

Thanks for the update

.
Great news !
Did you do all the usual things you normally do?

Yeah it's the same thing every day basically

YoYo155 · 01 Nov 2013

I believe the thread is now solved, do you feel the same?

Mangaza · 02 Nov 2013

Quote: Originally Posted by YoYo155

I believe the thread is now solved, do you feel the same?

Yeah

but I will reopen this once the problem comes back, and given my past history of problems, it's more than likely I'll have problems in the near future

YoYo155 · 02 Nov 2013

Quote: Originally Posted by Mangaza

Yeah

but I will reopen this once the problem comes back, and given my past history of problems, it's more than likely I'll have problems in the near future

I would like to think otherwise

.
Either way you know where to find us, enjoy your stay.

Mangaza · 08 Nov 2013

I had a BSOD today. This time, I had something else open -- blizzcon live stream virtual ticket, got a bsod with the message: pfn_list_corrupt in all caps. Attached is the minidump

YoYo155 · 09 Nov 2013

This bug check is usually bad drivers although given the stack trace and the history of the PC
I tend towards RAM issues more at the moment.

Code:

BugCheck 4E, {99, 0, 0, 0}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

               rsp : 0xfffff88003739918 : 0xfffff8000334da4c : nt!MiBadShareCount+0x4c
0xfffff88003739918 : 0xfffff8000334da4c : nt!MiBadShareCount+0x4c
0xfffff880037399a8 : 0xfffff800032776c4 : nt!MiOutPageSingleKernelStack
0xfffff880037399d8 : 0xfffff80003277d52 : nt!KeEnumerateKernelStackSegments+0x5a
0xfffff88003739a68 : 0xfffff80003277cc8 : nt!MmOutPageKernelStack+0x34
0xfffff88003739ac8 : 0xfffff800032c422a : nt!KiDeferredReadyThread+0x31a
0xfffff88003739ad8 : 0xfffffa800cd82148 : 0xfffff800034bf2c8 : nt!KiSwapEvent+0x8
0xfffff88003739b08 : 0xfffff800032aa69e : nt!KiDecrementProcessStackCount+0x10a
0xfffff88003739b48 : 0xfffff80003277c6c : nt!KiOutSwapKernelStacks+0x11c
0xfffff88003739ba0 : 0xfffff800032f2520 : nt!KeSwapProcessOrStack
0xfffff88003739bb8 : 0xfffff800032f2568 : nt!KeSwapProcessOrStack+0x48
0xfffff88003739bf8 : 0xfffff8000355b2ea : nt!PspSystemThreadStartup+0x5a
0xfffff88003739c38 : 0xfffff800032af8e6 : nt!KxStartSystemThread+0x16

I checked and your RAM (CMX4GX3M1A1600C9) and it is not listed in the QVL (Qualified Vendor's List)
for that Motherboard (GA-Z87-D3HP).
Your RAM specifications are listed in this webpage - XMS3 4GB DDR3 Memory Module (CMX4GX3M1A1600C9) (Tech Specs).
I can see that the RAM is currently running at 1333MHz, please make sure that the timings and voltages
are correct as well.

Code:

Tested Latency                 9-9-9-24 
SPD Latency                     9-9-9-24
Tested Voltage                  1.65     
SPD Voltage                      1.5     
SPD Speed                        1333MHz     
Tested Speed                    1600Mhz

In the mean time I can offer you this.

Quote: Originally Posted by Arc

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Quote: Originally Posted by Arc

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test	Slot1	Slot2
RAM1	Error	Error
RAM2	Good	Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test	Slot1	Slot2
RAM1	Error	Good
RAM2	Error	Good

It is a motherboard issue. The particular slot is bad.

If memtest comes free from errors, 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.