just in time for black friday

wapplez · Nov 29, 2013

i have been getting bsod for awhile now. with black Friday hear i would like to fined out what the problem is. as to get new hardware for a good price while i can. just reformatted hoping it would fix it but nope >,<.View attachment perfmon.rar View attachment Windows7_Vista_jcgriff2.rar
Machine name: KC
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7522
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 CPUs), ~2.7GHz
Memory: 12288MB RAM
Available OS Memory: 12280MB RAM
Page File: 1928MB used, 22630MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode
View attachment DxDiag.txt View attachment 01.rar Driver Verifier

TomasD · Nov 29, 2013

Hello,

It seems to be caused by NVIDIA driver:

Code:

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


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


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




FAULTING_IP: 
nvlddmkm+152e64
fffff880`0ffece64 803d3e81730000  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`10724fa9)],0


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT


BUGCHECK_STR:  0x116


PROCESS_NAME:  System


CURRENT_IRQL:  0


STACK_TEXT:  
fffff880`01f1fa58 fffff880`10b37cbc : 00000000`00000116 fffffa80`0cdb3010 fffff880`0ffece64 00000000`00000000 : nt!KeBugCheckEx
fffff880`01f1fa60 fffff880`10b37a43 : fffff880`0ffece64 fffffa80`0cdb3010 fffffa80`0a5b1950 fffffa80`0c2f6410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`01f1faa0 fffff880`0fe0ff07 : fffffa80`0cdb3010 00000000`00000000 fffffa80`0a5b1950 fffffa80`0c2f6410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`01f1fad0 fffff880`0fe3dd7e : 00000000`ffffffff 00000000`001e3b7b fffff880`01f1fc30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`01f1fbb0 fffff880`0fe0b29e : fffffa80`0c2f6410 ffffffff`feced300 fffffa80`0ccea4a0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`01f1fbf0 fffff880`0fe37e7a : 00000000`00000000 fffffa80`0d621cd0 00000000`00000080 fffffa80`0c2f6410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`01f1fd00 fffff800`02f6b166 : 00000000`fffffc32 fffffa80`0bfa48c0 fffffa80`09cdc890 fffffa80`0bfa48c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`01f1fd40 fffff800`02ca6486 : fffff880`03186180 fffffa80`0bfa48c0 fffff880`031910c0 fffff880`0124ba90 : nt!PspSystemThreadStartup+0x5a
fffff880`01f1fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16




STACK_COMMAND:  .bugcheck ; kb


FOLLOWUP_IP: 
nvlddmkm+152e64
fffff880`0ffece64 803d3e81730000  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`10724fa9)],0


SYMBOL_NAME:  nvlddmkm+152e64


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nvlddmkm


IMAGE_NAME:  nvlddmkm.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  5280da75


FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys


BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys


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

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0fe9a000 fffff880`10adb000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 11 15:24:05 2013 (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Could you please try installing the latest version of the drivers?

wapplez · Nov 29, 2013

had this problem be for i reformatted last night. and i installed the latest nvidia driver after the reformat. but upon your request i have installed the nvidia drivers "clean" once again. should i run any more reports or driver verifiers ?

Patrick · Nov 29, 2013

In addition to Tomas' analysis, enabling Driver Verifier could definitely not hurt and would only provide us with more info:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick

wapplez · Nov 29, 2013

after reinstalling the drivers "clean install" i received a bsod 1 hour later.

TomasD · Nov 29, 2013

wapplez said:
after reinstalling the drivers "clean install" i received a bsod 1 hour later.

Please re-upload the file, since it seems you compressed only a shortcut.

wapplez · Nov 29, 2013

sorry

TomasD · Nov 29, 2013

Thanks.

It's still pointing to NVIDIA drivers.

wapplez · Nov 29, 2013

i don't know what to do then i thought reformatting would fix this but that did not work. new drivers don't work, im at a loss as to what i should try next.

TomasD · Nov 29, 2013

After installing Windows, have you manually installed anything (drivers, software etc.) related to to NVIDIA from the Internet/CD?

wapplez · Nov 29, 2013

after installing windows i let windows do it its updating thing then after that restart i downloaded the same drivers you linked. restarted then i downloaded origins then bf4. and that ends what i have dl/installed on this pc so far. some more info, be for the format, this all started after i did an update . it had been 1 year since the last time i did any updates on my pc. but to play the new bf i had to have update drivers, so i updated everything on my pc. thus it began and after my reformat its still there. oops and i also had to update flash player inorder to wach youtube videos . clicked the dl link they provided.

TomasD · Nov 29, 2013

Could you please try removing everything related to NVIDIA using Add/Remove control panel and then rebooting the machine?

In addition, I see you do not have Service Pack installed. Since you just re-installed Windows, you should have used installation CD with SP1 or install SP1 separately just after installing Windows.

x BlueRobot · Nov 29, 2013

Tomas, be careful with Stop 0x116, although the crash is because of TDR with the graphics card driver. The graphics card driver is always blamed as being the cause the crash.

wapplez · Nov 29, 2013

ok everything is no more. i also went into the device manager and got rid of the card. so atm my screen is ugly and windows is trying its best to update it but im not letting it. although its saying it will update on next restart now. there was 1 thing that i could not get rid of. there are 2 pics 1 of everything that "was" installed and one of the one i could not get rid of. standing by for your orders before i dl install or do anything more.

x BlueRobot · Nov 29, 2013

Code:

[COLOR=#ff0000]BugCheck 116[/COLOR], {fffffa800ad8f280, [COLOR=#0000cd]fffff8800ff8ae64[/COLOR], 0, d}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[COLOR=#ff0000] nvlddmkm.sys[/COLOR] ( nvlddmkm+152e64 )

The second parameter points to the nVidia graphics card driver, as the responsible driver, since the crash is related to the graphics card driver being unable to recover from a hang, and therefore times out.

Code:

nvlddmkm+152e64
[COLOR=#0000cd]fffff880`0ff8ae64[/COLOR] 803d3e81730000  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`106c2fa9)],0

Code:

6: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`01fdf9c8 fffff880`10ad5cbc nt!KeBugCheckEx
01 fffff880`01fdf9d0 fffff880`10ad5a43 [COLOR=#ff0000]dxgkrnl!TdrBugcheckOnTimeout+0xec[/COLOR]
02 fffff880`01fdfa10 fffff880`10b7cf07 dxgkrnl!TdrIsRecoveryRequired+0x21f
03 fffff880`01fdfa40 fffff880`10ba6b75 [COLOR=#ff0000]dxgmms1!VidSchiReportHwHang+0x40b[/COLOR]
04 fffff880`01fdfb20 fffff880`10ba52bb dxgmms1!VidSchiCheckHwProgress+0x71
05 fffff880`01fdfb50 fffff880`10b782c6 dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
06 fffff880`01fdfbf0 fffff880`10ba4e7a dxgmms1!VidSchiScheduleCommandToRun+0x1da
07 fffff880`01fdfd00 fffff800`02f32166 dxgmms1!VidSchiWorkerThread+0xba
08 fffff880`01fdfd40 fffff800`02c6d486 nt!PspSystemThreadStartup+0x5a
09 fffff880`01fdfd80 00000000`00000000 nt!KiStartSystemThread+0x16

Code:

6: kd> [COLOR=#008000]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`0fe38000 fffff880`10a79000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=#ff0000]Mon Nov 11 13:24:05 2013[/COLOR] (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would suggest running Furmark for a few hours, and then report any artifects (screen distortions), I recommend not letting the temperature exceed 90*C.

Are you performing any overclocking?

Code:

6: kd> [COLOR=#008000]!sysinfo cpuspeed[/COLOR]
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: [COLOR=#ff0000]2673[/COLOR]

wapplez · Nov 29, 2013

nope i dont know much about ocing so i stay away from it. so is it ok if i reinstall my drivers ?

x BlueRobot · Nov 29, 2013

Okay, it may be the TurboBoost feature which comes with i5's and i7's.

Install the drivers again, and then run the test.

wapplez · Nov 29, 2013

yes sir will do. thank you both for what you do here for people, i appreciate you sharing your knowledge with us

x BlueRobot · Nov 29, 2013

Welcome, just post a another update when your done :dsmile:

Remember to run for a few hours if able, if it starts to reach 90*C, then stop the test and tell us.

wapplez · Nov 29, 2013

for now going off the time your link said to do this is what i got. but atm i need to go get a few hours of sleep and don't want to leave this running while im not around ^^.

just in time for black friday

Member

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Member

Sysnative Staff

Member

Attachments

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Member

Attachments

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Member

Attachments

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Member

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Administrator

Member

Attachments

Administrator

Member

Administrator

Member

Administrator

Member

Attachments