Crashing (not technically BSOD) while saving in Live Movie Maker

niceguyjin · 20 May 2012

The screen goes to a frozen, flickering freeze, with pinkish dots/colours in some places, while sound sometimes continues if I was watching a youtube video or something at the same time. The PC must be reset to continue.

I have tried a few times, even while not doing anything else, I went and made a sandwich, but no good.

The original movie was a home video on DVD, ripped using handbrake normal settings, then edited in Live Movie Maker.

I have been using WLMM a bit recently and have had about 95% or more success in editing and saving movies, but this last one won't work at all. The project itself is saved, it just won't save to a movie file.

I am trying to save for HDTV.

edit: along with my system specs below, my Windows is retail

for easy reference from whocrashed:

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8571707392 total
VM: 2147352576, free: 1888714752

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 21/05/2012 2:27:01 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\052112-7082-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0xA577)
Bugcheck code: 0x117 (0xFFFFFA800705F4E0, 0xFFFFF8800F9DA0DC, 0x0, 0x0)
Error: VIDEO_TDR_TIMEOUT_DETECTED
file path: C:\Windows\system32\drivers\watchdog.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the display driver failed to respond in a timely fashion.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

zigzag3143 · 21 May 2012

"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 CPUID - System & hardware benchmark, monitoring, reporting

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

niceguyjin · 21 May 2012

zigzag3143 said:

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 CPUID - System & hardware benchmark, monitoring, reporting

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Thanks for the reply zigzag. Well, I don't know what to tell you but my drivers are all up to date. My system is spotless as I recently installed a water cooling loop and cleand all my components in the process. Ran Prime95 for a few hours over the weekend without fail, along with 3D Mark11 Extreme in a loop for an hour or so. That was all OCd, while now all is at default settings, and it still won't save. Gets to 5x% (53-58) and "crashes".

As for fans, I have 4 fans in push/pull (1500RPM max) exhauting through the CPU radiator, 2x140mm front intakes + 1xSilversone 180mm Air Penetrator on the side, and one more 140mm rear exhaust. That's a total of 8 fans!! All intakes are filtered. Good clean ship.

zigzag3143 · 21 May 2012

Have you tried all of the suggestions? What was the result of the memory stressing?

niceguyjin · 22 May 2012

OK, so I went back and read your post and links more carefully and decided that it was probably either a driver or hardware issue with one of my GPUs.

I tried taking out a GPU one at a time and running WLMM as a makeshift stress test, as this was the quickest way to see if the crash would replicate. It didn't matter which GPU, saving in WLMM crashed at various times without fail. Same result every time.

So then I followed the instructions here Ultimate Nvidia Driver Guide for Uninstalling and Installing driversets on how to do a completely clean nvidia driver install. (note the evga forums require a login to see thumbs in posts).

Success! I have successfully run the WLMM "test" several times both at stock and OC settings, along with various other burn-in/bench tests, all no problem.

Moral of the story: never do an express nvidia driver install, and never install nvidia HD sound drivers!

zigzag3143 · 22 May 2012

Great job and good luck. If you feel the problem is resolved please use the red triangle and ask the thread be marked solved.

Ken

niceguyjin · 22 May 2012

zigzag3143 said:

Great job and good luck. If you feel the problem is resolved please use the red triangle and ask the thread be marked solved.

Ken

Thanks again, Ken

I should also add that following my above post, I had a repeat of the original problem. A further solution was to change power managmement settings in the nvidia control panel.

For me, I have global settings on Adaptive, otherwise even browsing the web causes temps to warm and fans to blow.
Nvidia control panel > manage 3D settings > global settings > power management mode > adaptive

BUT, it might be worth changing this setting for more power hungry applications, such as Windows Live Movie Maker to
Nvidia control panel > manage 3D settings > PROGRAM SETTINGS (select program below) > power management mode > Prefer Maximum Performance

NB Windows Live Movie Maker was not in the list in the pull down menu so I had to manually add it.

zigzag3143 · 23 May 2012

Great job.