Help with BSOD, computer was just built!!!

[PHRESHKHID]

I built this PC a couple months ago, and ever since I having random BSOD, mostly while I play games. (i.e. SWTOR, BF3). And once or twice while just web browsing. Below I have attached the required information. I took it to a buddy's house and it ran find for about 40 mins, but its hard to say cause that also happens to me where it will be fine for a period of time then it crashes. Or it just crashed after a few mins. It happens mostly when I am doing a few task at once as well.

MOBO: Asus P8Z68-V
CPU: I7 2600K
GPU: NVIDIA Geforce GTX 560 TI 448 Core
RAM: CORSAIR Vengeance 8GB
SSD: Corsair Force Series GT 120GB
HDD: Seagate 500GB ( I think or something a friend gave to me)
PSU: CORSAIR Professional Series HX850
OS: Microsoft Windows 7 Home Premium SP1 64-bit - OEM


Hopefully someone can give me a hand.

Thank you for your time.

 

[zigzag3143]

Two issues

1-You have a driver from 2005 that is a HUGE cause of BSOD's in win 7 called RTCORE64.SYS, it is the msi afterburner driver (used in overclocking). It needs at least to be updated and if it cant it needs to be removed.

2-When that is removed your crashes are releated to a memory exception (Probably related to your DirectX) Please run the below tests to find which driver and test your memory.




* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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. You did create a restore point didnt you?

Sysnative Forums

Using Driver Verifier (Windows Drivers)

 

[PHRESHKHID]

I ran RamTest today before heading to work, it had 9 passes by the time I got home. Their were no errors reported. I am now trying The Verifier step. I am suppose to just use the computer how I normally use it when it crashes correct? (Of course after doing the steps in Verifier).

 

[PHRESHKHID]

Here is the attached file of the Minidump. Hope this helps you to help me!!! Thanks for all the help so far!

 

[zigzag3143]

Here is the attached file of the Minidump. Hope this helps you to help me!!! Thanks for all the help so far!

Driver verified and Related to nvlddmkm.sys nVidia Display Driver. I would re-install newest driver using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver.

In order to do that we recommend using
Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[PHRESHKHID]

I did what you recommended, and I am still receiving the BSOD.

 

[zigzag3143]

I did what you recommended, and I am still receiving the BSOD.

Please upload the new dmps

 

[PHRESHKHID]

Here we go, thanks again.

 

[yowanvista]

Your Intel(R) 82579V Gigabit Network Connection driver was the cause, you should update it
http://downloadcenter.intel.com/

 

[Influx]

The dumps point to e1c62x64.sys as the probable cause.
e1c62x64.sys is related to Intel(R) 82579V Gigabit, your Network Adapter.

In order to eradicate the BSOD, please try to do the following:
Update your Network Adapter Driver to the latest version.

 

[PHRESHKHID]

Updated the drivers, did my usual for about 40mins then anther BSOD. Im going to get some sleep now >.<

Could it be a bad Motherboard? At this point im just ready to replace whatever is causing the issue, I just don't know what it is.

 

[yowanvista]

Updated the drivers, did my usual for about 40mins then anther BSOD. Im going to get some sleep now >.<

Could it be a bad Motherboard? At this point im just ready to replace whatever is causing the issue, I just don't know what it is.

Nope, the latest dump file now points to your Nvidia Driver, that shall be reinstalled. This is basically the same thing that zigzag3143 pointed out
http://www.sevenforums.com/crashes-debugging/224179-help-bsod-computer-just-built.html#post1880279

 

[PHRESHKHID]

Hmm I did that, maybe I did it incorrectly. Ill attempt it again in a bit. Need to get some sleep.

 

[PHRESHKHID]

Before I do it, I want to make sure I select the correct ones. Last time I only did NVIDIA - Display. Was that correct?

 

[PHRESHKHID]

The first time I did just the display drivers, this time I did all 3. Going to play and test it now.

 

[PHRESHKHID]

Did the above, and got anther BSOD, not sure what to do anymore. This is getting out of hand.

 

[yowanvista]

Did the above, and got anther BSOD, not sure what to do anymore. This is getting out of hand.

nvlddmkm.sys, the Nvidia Display driver is the cause, the problem could possibly lie in your graphics card. Try to insert it in another PC to replicate the issue, if the same things shall happen a RMA shall be the only option left.