BSOD Apparantly random

As far as I can see, it does not look bad.

Now use the computer normally. Dont install the latest nvidia driver back. Report us for any further BSOD.

Same BSOD with multiple versions of display driver.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.
___________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8011b33010, fffff880100237a0, ffffffffc000009a, 4}

*** 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+9a57a0 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8011b33010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880100237a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+9a57a0
fffff880`100237a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0fef86a0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`044dea48 fffff880`0510a134 : 00000000`00000116 fffffa80`11b33010 fffff880`100237a0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`044dea50 fffff880`050dd867 : fffff880`100237a0 fffffa80`10356000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`044dea90 fffff880`05109f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`11b33010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`044deb40 fffff880`051da03d : fffffa80`0fdc0310 00000000`00000080 00000000`00000000 fffffa80`0fd9c410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`044debc0 fffff800`0371173a : 00000000`023a2996 fffffa80`10306b50 fffffa80`09765450 fffffa80`10306b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`044dec00 fffff800`034668e6 : fffff800`035f0e80 fffffa80`10306b50 fffff800`035fecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`044dec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9a57a0
fffff880`100237a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0fef86a0)]

SYMBOL_NAME:  nvlddmkm+9a57a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

Followup: MachineOwner
---------

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f67e000 fffff880`1030c000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

No overclocking. Have a 750w Cooler Master PSU.

Computers not hot at all. Cool if anything.

Speccy Analysis: http://speccy.piriform.com/results/b...O34voxyJf7dJY0

EDIT:
I'm not sure if this issue is related at all, but I'm also unable to install two specific Windows Updates:
Security Update for Windows 7 for x64-based Systems (KB2984976)
Security Update for Windows 7 for x64-based Systems (KB2984972)

Error code: 800B0100

Owen Arc has asked so my stab in the dark mate I would like to see the rail voltage on the PSU so do this.

UsingHW Info PSU

Download HW Info and pick the right bit version - HWiNFO, HWiNFO32/64 -Download -(copyand paste this site into the search bar) If you donot need the runninginformation in the smaller right hand panel close it. Inthe left hand windowclick on the + for the individual device groupings and theywill open out tothe various components.

Go on opening out further until you get to the device itself. click on it anditwill highlight. In the right hand window there will be a verydetaileddescription of that device as in brand, speeds model number etc etcThese arevery detailed and are just what is needed for searching for driversetc.

To getthe PSU volts you need to select the Sensor button circled in yellow inthe picfor PSU testing do the same and scroll down the readout as in my pic towhereit has Nuvoton = yours might be a different section name / title. Postback apic of that please.

If you want a more definitive test see this https://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html butleaseonly use a digital multimeter and not an analogue as they injecttypically 9vinto a circuit to test and into a 3.3v or 5v rail - not a good idea!!see thepartial pic of the correct sort of meter in that tutorial. details ifyou scrolldown that listing.

Now a good reference article is this
Voltage Rails - Power Supply 101: AReference Of Specifications it will explain in detail what thevoltages are and functions of the PSU/
In my pic is what you will see for your Asus because this is my Asus Ivy Bridge readout - Nuovoton

Thanks John!

Owen27, do you have a GPU temp monitoring program that will allow a custom fan profile? As best as I can tell, your temps were 89C during Furmark. That is too high, for me. Set a pretty aggressive fan profile to stop it from getting the temps so high.

Also try reinstalling your current driver using this guide. Install the Display Driver and PhysX only.
NVIDIA Drivers - Avoid Problems

Then run Furmark again and wait until the temp levels out and take a screenshot then stop the test. When you run Furmark, your temps will rise very quickly, but will level out at a certain point and will stop rising.. that is where you need to take the screenshot and then stop the test. Also, look for any Artifacts during the test.

Thank you Steve!