Hello, Khaine welcome to the Forums. I will try to help, even though you already have excellent help with Layback Bear. As Layback Bear asked, please fill out your system specs in as much detail as possible and place them under your 'My System Specs' We often have to look up components, so the Manufacturer and model enables us to do that, and with them under My System Specs they are always there in every post. Please include your PSU and CPU cooler too. Hopefully, this will help.
Please fill out your System Specs
Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task.
System Info - See Your System Specs
When you changed Motherboards did you change to the same make and model and did you do a clean install when you changed to the new one?
You have 1 Dump File in the past month when you had 2, then another a couple of weeks before that. All are listing different error codes and different causes.
Code:
Use !analyze -v to get detailed debugging information.
BugCheck D1, {58012a, e, 0, fffff88005a29a47}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+19da47 )
That is your Nvidia Graphics driver. This is the driver you have installed now.
Code:
nvlddmkm
start end module name
fffff880`0588c000 fffff880`062c4000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Wed Apr 08 15:32:37 2015 (55259065)
CheckSum: 009F7AE7
ImageSize: 00A38000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Before that the dump file lists
Code:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa800a7045f0
Arg3: fffff880067c8000
Arg4: fffff8a0042987ce
Then
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffffa800bfe5b80, fffffa800bfc5b80, fffffa800bfe5b80}
Probably caused by : afd.sys ( afd!AfdPoll32+6b2 )
Followup: MachineOwner
That is the Ancillary Function Driver for WinSock driver from Windows Update. Please go to Windows Update and in the Left column click Update History and see how many Updates have Failed. Also check and see if those updates were later installed successfully. Please make sure your updates are current.
The first one you had was
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880079a1f8a, fffff880035d6898, fffff880035d60f0}
Probably caused by : lvrs64.sys ( lvrs64+2f8a )
Followup: MachineOwner
That is your Logitech Camera Driver. You should check the Logitech Web Site and see if there is an updated driver for your Camera. This is the version you have now.
Code:
lvrs64
start end module name
fffff880`0799f000 fffff880`079f2a80 lvrs64 T (no symbols)
Loaded symbol image file: lvrs64.sys
Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
Image name: lvrs64.sys
Timestamp: Wed Jan 18 00:40:36 2012 (4F166964)
CheckSum: 00061E9E
ImageSize: 00053A80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
When you installed Drivers for your Motherboard, did you install them from the Driver Disk or did you go to your Motherboard's web site and download them?
As you will notice, every dump file has a different Bugcheck or Stop code. That is typical for memory problems. Memory problems will cause every dump file to be totally unreliable. You also will notice that every driver listed is different and have nothing to do with each other. That is unusual also. The last dump file has an error code of 7E which often is a hard drive error. So, I know you said you have already run memtest86+, but for my purposes, I would like to have you run it again. It is especially necessary because of the reliability of the dump files, which we depend on, and because one of the dump files specifically mentioned it. These are the directions I would like you to follow.
Please Run Memtest86+
Information
Please download from this site only
http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start,
please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes run at the same session to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.
I would also like you to run Seatools for DOS
SeaTools for DOS and Windows - How to Use. Please run the short and the long test.
If you would, please answer the questions I asked during this too long of a post. It may help us get to the bottom of your problems sooner. If you have any questions or do not understand anything, please do not hesitate to ask. I don't mind at all.
One other point you were discussing in an earlier post. You said you were using MSI Afterburner and another program. It is never a good idea to use 2 monitoring programs at the same time that are measuring the same thing. Afterburner will do everything you need. I would suggest you go into settings and enable a custom fan profile and have the fans spin higher, which will reduce your temps. I use a pretty aggressive profile on my card. It will depend on how loud your fans are and how tolerant you are to the noise. I set my fan profile at 40% until it reaches 40°C. From there I have the fan increase as the temp rises until it gets to 80° where the fans are at 100%. But, by doing that, my card has never seen 80° which means your fans will usually not get that high. On my card the highest temp I get is during a stress test when it gets to 70°. During normal gaming, it will usually run between 45-55°. You can also set Afterburner to display on screen during gaming your Temp, fan speed, FPS, Graphics frequency and almost anything you want to see. You will always be able to know what temps your card is running. I hope that helps a little.
Quote