BSOD playing WoW and different BSODs while doing other stuff

OK thanks :) .

What drivers did you select?

Hi :) .

It's the second bugcheck that lists ts3client_win64 as the active process on that thread.

Code:

ts3client_win64.exe    c:\program files\teamspeak 3 client\ts3client_win64.exe

Both bugcheck codes are usually due to bad drivers which I too suspect is the issue in this case
especially if we consider the fact that auto-driver installers where involved.

If you're reluctant to use Driver Verifier the very least you can do is undo any bad driver installation
that might took place.
I suggest you go to the manufacturer's website and properly install the drivers.

• GA-Z87-D3HP

Yes the possibility of an issue specifically with TeamSpeak is real.
But it can also be the drivers it's calling (LAN, Audio etc...).

Please make sure you select Windows 7 64bit for the driver list and download the following:

   Note

Install the drivers in the order they appear.

Intel INF installation
Intel Management Engine Interface
Intel LAN Driver
Realtek HD Audio Driver
Intel VGA Driver
Intel USB 3.0 Driver

I assume that you at least downloaded the GPU driver from nVidia's website and installed
it the correct way via the installer?

As for the the other options DON'T install any utilities!
You can update the BIOS:

   Warning

Flashing the BIOS is a risky procedure. If you are uncomfortable
performing it yourself have a technician perform it for you.
Regardless, flashing is at your own risk.

No code has to be inserted here.

Mangaza said:

Yeah :)

After reading similar experiences from different people via Googling, it looks like there might be a possible RAM issue (I never replaced RAM, is it possible it got damaged when the motherboard/cpu went way overheated?) that caused the PAGE_FAULT_IN_NONPAGED_AREA BSOD. Tonight, I had a random computer complete freeze where I had to forcibly hold down the power button to restart the computer, similar experience here: Computer "freezes," requiring forced restart. - Homebuilt - Systems suggesting that RAM sticks might be the cause. If I choose to replace my RAM, any suggestions on what RAM I should be looking for? Any incompatibility issues with certain RAM that I should avoid?

I don't think I want to take the risk of flashing bios after reading about it. Can't really afford to take risks at the moment. I haven't gotten any bsods in the past 48hours. I will re-install the drivers sometime next weekend or so, cause I have to do wow raiding on tues-thurs, and don't want to take any risks of something bad happening which is probably unlikely from reinstalling the drivers.

I will post back here when I have an update :)

Thanks!

No rush on the BIOS update
(or anything for that matter it's your decision to take at the end of the day) :) .

As for the RAM you can test it if you would like to invest the time doing so, if you mind isn't
already set to replacing the kit.
As to what model it's a good rule of thumb to first look at the QVL (Qualified Vendor List) for your motherboard and see if you find something you fancy, if not it's most probable that models that
are not listed on there will also comply.

If you want my advice as to which I would take, it's as follow.
I would grab a 8GBx2 kit at 1600MHz (not more 1866) and from your MB QVL I would
go with Corsair / G.Skill / ADATA.

• Z87-D3HP - RAM QVL

If you feel like it:

Arc said:

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.

Arc said:

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:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

I'll definitely do a MemTest sometime this week to see if there are any errors. Today, I just got a random complete lockout (where I had to reset power to restart the PC), as I was surfing the web with nothing really open. Similar to the other day when I exited diablo 3 game and my computer just completely froze. I read that it might be a ram issue or a voltage to ram issue.

My default motherboard to ram voltage was set to 1.5v, and my ram needs 1.65v or 1.7v to run. I googled and stuff and now I changed my ram voltage to 1.65v and see if anything changes before I look more into replacing my ram.

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