BSOD while streaming video from Netflix

[Putumayo]

BSOD while streaming video from Netflix - 0x00000116 - Win7 64

My brand new system is suffering BSOD while streaming video from Netflix. ONLY while streaming video from Netflix, and always 0x00000116

BlueScreenViewer shows the following info (see image below):

102811-21247-01.dmp 10/28/2011 7:13:55 PM 0x00000116 fffffa80`05fdc4e0 fffff880`0420745c 00000000`00000000 00000000`00000002 dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\102811-21247-01.dmp 4 15 7601 304,960

Win 7 Home Prem
Asus M4A89GTD PRO
Phenom II X4 970
Gigabyte Radeon HD 6870
Corsair Vangance 4GB 9-9-9-24 (being replaced w/ G.Skill CL7 8GB)
OCZ GameXStream 700w

No OC

Thanks!
View attachment 181299

 

[zigzag3143]

My brand new system is suffering BSOD while streaming video from Netflix. ONLY while streaming video from Netflix.

BlueScreenViewer shows the exact same info for each crash:

102811-21247-01.dmp 10/28/2011 7:13:55 PM 0x00000116 fffffa80`05fdc4e0 fffff880`0420745c 00000000`00000000 00000000`00000002 dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\102811-21247-01.dmp 4 15 7601 304,960

Win 7 Home Prem
Asus M4A89GTD PRO
Phenom II X4 970
Gigabyte Radeon HD 6870
Corsair Vangance 4GB 9-9-9-24 (being replaced w/ G.Skill CL7 8GB)
OCZ GameXStream 700w

No OC

Thanks!

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[Putumayo]

Thank you for your reply.

This machine is only a few days old - no dust. It has 4ea 120mm case fans, plus 1ea 200mm case fan, and one 120MM PSU fan drawing from inside, blowing out. Additionally, the GPU itself has 3ea 80mm fans with a substantial heatsink system built onto it. The case itself has NO wiring running through it - it was painstakenly routed between the inner case wall and outer, so airfloe is excellent.

I have GPU-Z (plus CPU-Z, MSI Aftewrburner, HWMonitor, etc...). CPU-Z shows the following temps - one for each fan point on the GPU: 42.5c, 38.5c, 42.5c. These seem reasonable, or am I wrong?

FWIW, I have the fan ramp-up set to increase fan speed earlier/at cooler temps than the "stock" settings.



I've read on this forum that AVG can cause problems. Might this be the issue?

Sincere gratitude for the assistance!

 

[Putumayo]

FWIW, after running FurMark 1.9.1 on 1920x1080 (42") for 40 minutes GPU-Z shows temps of: 78c, 83.5c, 93c @ fans, and 78C "on die" temp. See attached image.

Edit: I've since modified the fan layout, and in many tests over many days have seen temps no higher than 73*c.

 

[zigzag3143]

Thank you for your reply.

This machine is only a few days old - no dust. It has 4ea 120mm case fans, plus 1ea 200mm case fan, and one 120MM PSU fan drawing from inside, blowing out. Additionally, the GPU itself has 3ea 80mm fans with a substantial heatsink system built onto it. The case itself has NO wiring running through it - it was painstakenly routed between the inner case wall and outer, so airfloe is excellent.

I have GPU-Z (plus CPU-Z, MSI Aftewrburner, HWMonitor, etc...). CPU-Z shows the following temps - one for each fan point on the GPU: 42.5c, 38.5c, 42.5c. These seem reasonable, or am I wrong?

FWIW, I have the fan ramp-up set to increase fan speed earlier/at cooler temps than the "stock" settings.



I've read on this forum that AVG can cause problems. Might this be the issue?

Sincere gratitude for the assistance!

Avg is a known problem but not for this particular error code. Are you overclocking anything?

If you want to test you can remove avg and replace with Microsoft Security essentials at least to test.

 

[Putumayo]

Avg is a known problem but not for this particular error code. Are you overclocking anything?

If you want to test you can remove avg and replace with Microsoft Security essentials at least to test.

I disabled AVG, still BSOD'd while streaming from Netflix.

Drivers are such a pain: ATI has drivers for "6000 series". Gigabyte has a driver specifically for their build. Win 7 installed the last driver, from who knows where... I just installed a more recent driver from Gigabyte - release shortly after the driver Win 7 had installed. Due to work schedule, I will not be home for a few days to try it out. I'll post then

Thanks again for the help!

 

[Putumayo]

Situation update:

I've been @ the Grand Canyon a lot lately, so little PC time logged.

Found a newer driver for GPU and installed it.

I also installed new RAM: G.Skill Ripjaws F3-12800CL7D-8GBXH 2x4gb. Timings in bios are set to 7-8-7-24. Games are playing beautifully!

Streamed a documentary last night via Netflix. After about 20 min came the BSOD. To be clear, every one of these BSOD have been followed by reboot.

Details of event: Video will simply freeze, then after about 5 seconds frozen, screen goes grey and simultaneously a loud buzz fills the room. This lasts for aprox 2-3 seconds, then reboot begins. Every event is identical.


Immediately following reboot I conducted FurMark 1.9.1 extreme burn-in. Peak temps were 73*C @ lowest (manual) fan settings. I let it run @ this temp for 1 hour - to duplicate worst case scenario. No issues occured.

Ran Video Memory tress Test (VMT) and all passed.

Completed Prime95 Stress Test overnight - all passed, see below:

Ran W.D. DataLifeguard on HDD (brand new) - no errors. Will run 3rd party diagnostic this evening.

Performed MemTest86x on the last set of ram - came up clear. I'll do it on this set tonight, though seems unlikely.

What next?