Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bsod randomly

15 Mar 2014   #1

Windows 7
 
 
Bsod randomly

I have been having some problems with my computer when loading stuff it will freeze for a few minutes randomly. Yesterday, I was online surfing the internet, and my computer froze up and I heard a constant beeping sound then I got a BSOD.



Attached Files
File Type: rar zavh-SF_15-03-2014.rar (861.7 KB, 6 views)
My System SpecsSystem Spec
.

15 Mar 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Hi zavh.

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

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

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 .

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Install the NVIDIA DRIVERS 314.22WHQL only, as a test.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.
_________________________________________________
Code:
******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80077a74e0, fffff8800f24f034, ffffffffc00000b5, a}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** 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+153034 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+153034
fffff880`0f24f034 803dee1a730000  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0f980b29)],0

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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`023f2918 fffff880`0453f140 : 00000000`00000116 fffffa80`077a74e0 fffff880`0f24f034 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`023f2920 fffff880`0453ef1b : fffff880`0f24f034 fffffa80`077a74e0 fffffa80`07f889a0 fffffa80`089db410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023f2960 fffff880`0440ff13 : fffffa80`077a74e0 00000000`c00000b5 fffffa80`07f889a0 fffffa80`089db410 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`023f2990 fffff880`0443ded6 : fffffa80`ffffffff 00000000`000bd4a4 fffff880`023f2af0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023f2a70 fffff880`0440b2aa : fffffa80`089db410 ffffffff`feced300 fffffa80`07f889a0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`023f2ab0 fffff880`04437ff6 : 00000000`00000000 fffffa80`07f889a0 00000000`00000080 fffffa80`089db410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`023f2bc0 fffff800`031602ea : 00000000`03691e52 fffffa80`0885c8b0 fffffa80`06731740 fffffa80`0885c8b0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023f2c00 fffff800`02eb48e6 : fffff880`02f65180 fffffa80`0885c8b0 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`023f2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+153034
fffff880`0f24f034 803dee1a730000  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0f980b29)],0

SYMBOL_NAME:  nvlddmkm+153034

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52676afe

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0fc000 fffff880`0fd33000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 23 11:51:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
15 Mar 2014   #3

Windows 7
 
 

All of my stuff is at factory settings, nothing is overclocked.
My psu wattage is 530watt.
I didn't get any errors with furmark.
I installed the new driver.
Here is my speccy system specs publish
http://speccy.piriform.com/results/m...cxLkzWuIPrVwgL

Below is the screenshot of speccy summary tAB.


Attached Thumbnails
Bsod randomly-speccy.png  
My System SpecsSystem Spec
.


16 Mar 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

OK, let us know how it is running.
My System SpecsSystem Spec
16 Mar 2014   #5

Windows 7
 
 

I will play for a few days and see how it's doing. Thank you for your help so far.
My System SpecsSystem Spec
Reply

 Bsod randomly




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:12 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33