OK, you have 2 dump files. They both say the same thing:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C5, {200000001, 2, 0, fffff800035ff9cc}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys[/COLOR]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
Followup: Pool_corruption
BUGCHECK_STR: 0xC5_2
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExDeferredFreePool+100
fffff800`035f69cc 4c8b02 mov r8,qword ptr [rdx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: [COLOR=red]PrecisionX_x64[/COLOR]
Both are blaming your Graphics driver and both are listing Precision X as the process which was running at the time. Basically, it looks like you have a corrupted driver. It may or may not be those listed, but since they are listed twice, lets try them first.
First, Please uninstall Precision X. Next I would like you to reinstall the Graphics driver, but I would like you to follow this tutorial to do it, and only install the Graphics Driver and PhysX.
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html If you can do without Precision X for a while please do so. If you have no problems, we will install it later. That way if you start having problems, we would know that there is a good chance it is Precision X.
Also, if you are Overclocking anything, please set everything to default levels. I am not opposed to overclocking, but while trying to get you stable, it just confuses the process and makes it difficult to impossible to do.
After that Please, open an elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Let me know how it goes after that.
