Daily recording failures that I can't figure out

[JohnT900]

I have been trying to setup a new Windows 7 Media Center system for a couple of weeks and have run into issues I can't nail down and was hoping for some assistance before I pull all of my hair out. The system is an i7, 8GB, 500GB HDD, 3 HD-Homerun Prime devices and 3 standard HD-Homerun devices (only the Prime devices are currently being used for recordings). I am also running MCEBuddy in the background and it appears to not have any issues.

I am seeing daily recording failures and am not sure how to fix or work around this issue. The latest from today:

Per the recording history, 4 recordings had issues at 11am (they are listed as "Partial" in the WMC History page). Looking at the Windows Event Viewer, I see these events at around 11am...

An "Error" event at 10:59:49...

Faulting application name: ehRecvr.exe, version: 6.1.7601.17514, time stamp: 0x4ce7aea5
Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeb033f
Exception code: 0xc0000005
Fault offset: 0x0000000000001459
Faulting process id: 0x5a4
Faulting application start time: 0x01d14c0ed22388d2
Faulting application path: C:\Windows\ehome\ehRecvr.exe
Faulting module path: C:\Windows\system32\msvcrt.dll
Report Id: e3bdd0b7-b94d-11e5-ab1f-90b11c767c41

The next event is a "Information" event at 10:59:51...

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ehRecvr.exe
P2: 6.1.7601.17514
P3: 4ce7aea5
P4: msvcrt.dll
P5: 7.0.7601.17744
P6: 4eeb033f
P7: c0000005
P8: 0000000000001459
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ehRecvr.exe_97e57189d2ae24ded59d1bbcf16c9a51cd9b4f6f_1b02fa51

Analysis symbol:
Rechecking for solution: 0
Report Id: e3bdd0b7-b94d-11e5-ab1f-90b11c767c41
Report Status: 4

There is another "Information" event right after the one above that is nearly identical in the info being reported (the difference is the "Report Status: 0" vs. 4 from above).

Any ideas or suggestions would be greatly appreciated.

[Scallica]

I would start by doing a clean install of Windows 7.

[JohnT900]

I would start by doing a clean install of Windows 7.

This is a new system build, so the current Windows 7 install is new.

[Crash2009]

Disable Sleep is always a good starting point. PC and Hard Drive. If the recordings start and stop normally after this test, we should be able to point you in the correct direction to set things up so it wakes up on time to record, finishes recording then goes back to sleep until its time to wake up and record something again.

[JohnT900]

Disable Sleep is always a good starting point. PC and Hard Drive. If the recordings start and stop normally after this test, we should be able to point you in the correct direction to set things up so it wakes up on time to record, finishes recording then goes back to sleep until its time to wake up and record something again.

I have it set to never sleep. I would think that would be the preferred setting?

[Scallica]

Check the health of your hard drive using Hard Disk Sentinel. Also check the health of your RAM using memtest. Download and burn the ISO to create a bootable CD.

http://www.hdsentinel.com/
http://www.memtest.org/

[Crash2009]

1) Might have a bottleneck in MCEBuddy. The stream(s) that are coming from your tuners on the way to your hard drive, must pass through MCEBuddy on their way to creating a .WTV file that is commercial free. Is there a setting that can be increased in MCEBuddy to create a bigger pipe for all your streams to go through simultaneously.

2) AntiVirus Software can create the same type of bottleneck. example 3 X 15 = 45 mbps of HD Streams trying to get through an AntiVirus Software that can only process 25 mbps.

[Crash2009]

Continuing on the topic of mbps, are the HTPC and the Prime cabled to the same switch?
or
Is one connected to the router and the other connected to the switch?
or
Is one WiFI and the other wired?

Any MoCA or PowerLine involved?

[JohnT900]

1) Might have a bottleneck in MCEBuddy. The stream(s) that are coming from your tuners on the way to your hard drive, must pass through MCEBuddy on their way to creating a .WTV file that is commercial free. Is there a setting that can be increased in MCEBuddy to create a bigger pipe for all your streams to go through simultaneously.

I should have noted that MCEBuddy isn't currently compressing the current set of recordings. It is plugging away at a TB of older videos on a USB3 attached drive. The CPU usage doesn't get all that high (averaging between 10 to 30% usage). So I don't think it could be a bottleneck of this sort. I could be wrong.

WMC is recording to the OS drive.

2) AntiVirus Software can create the same type of bottleneck. example 3 X 15 = 45 mbps of HD Streams trying to get through an AntiVirus Software that can only process 25 mbps.

I don't have any AV software installed aside from Windows Defender.

Also, all current recordings are standard definition - no HD recording.

[JohnT900]

Continuing on the topic of mbps, are the HTPC and the Prime cabled to the same switch?
or
Is one connected to the router and the other connected to the switch?
or
Is one WiFI and the other wired?

Any MoCA or PowerLine involved?

Good questions... the WMC system and all tuners are on the same wired Gigabit switch. No wireless or other networking technologies are involved.

[JohnT900]

I would start by doing a clean install of Windows 7.

A follow-up on this... why would you suggest starting over right off of the bat?

Are my issues indicative of problems that typically can't be fixed?

[JohnT900]

Check the health of your hard drive using Hard Disk Sentinel. Also check the health of your RAM using memtest. Download and burn the ISO to create a bootable CD.

http://www.hdsentinel.com/
http://www.memtest.org/

HDsentinel reports the HDD is in perfect health. I will try to get to a memory test tomorrow.

[Crash2009]

I think I might have found something. Its related to the guide not being able to handle two different types of tuners at the same time. msvcrt.dll tries to keep it together and causes a blowout in ehRecvr.exe

Hint Hint ms vcr t

Review these links, the last one has a hotfix.

http://sourceforge.net/p/mingw-w64/wiki ... svcrt.dll/

http://www.thegreenbutton.tv/forums/vie ... f=5&t=4801

https://support.microsoft.com/en-us/kb/2746119

I think we could blame this on ROVI if we tried real hard.

[Crash2009]

Dig deeper into C Runtime for msvcrt

Select a log, click Find, type msvcrt

I don't know where exactly to find Microsoft C runtime

[cwinfield]

you could try uninstalling visual c/c++ in programs installed updates and reinstalling. Could also be driver related. sfc /scannow may repair this from command prompt

https://social.technet.microsoft.com/fo ... 0760117744

[Crash2009]

1) What Version of Win7 are you using.... Home, Pro, Etc.? X86 or X64?

2) What Version of Microsoft Visual C++ is installed in Windows Programs and Features?

3) What Version of MCEBuddy?

4) What Codecs do you have installed? other than.... Haali which is included with MCEBuddy.

5) What kind of PC is this...Laptop, Tower, Etc.?

6 What Version of .NET are you running?


I am beginning to see why Fresh install of Win7 was suggested in Post #2..

[Crash2009]

MCEBuddy is causing to my computer to hang or crash (BSOD)

Cause

MCEBuddy causes a lot of stress on system drivers causing a faulty system driver to fail or hang the system. MCEBuddy CANNOT cause a system crash or hang because it's a managed application, the ONLY piece of software that can cause Windows to crash or hang is a driver.

The hang or crash is because of a faulty driver on the system (it is the only piece of code privileged enough to cause a bug check). At most an application can cause itself to crash where as kernel mode driver (badly enough written) can cause a bug check or hang.

See this page for more details: https://mcebuddy2x.codeplex.com/discussions/547263

Resolution

Most likely it is either your video driver, chipset driver, hard disk driver or faulty hardware which under stress is exposing the flaw. MCEBuddy can be quite stressful on the system so keeping good hardware and drivers is paramount.

For a crash, to isolate the root cause of the bug check you will need a software like WinDBG to analyze the kernel memory dump created by windows in the windows\minidump directory. This will tell you which driver caused the panic and why (big check code).

You will need to start uninstalling or updating your drivers to find out which one is causing the issue.

https://mcebuddy2x.codeplex.com/wikipag ... n%20Issues

[Crash2009]

Which I7 do you have?

http://ark.intel.com/products/family/88 ... ssors#@All

Chipset?

Hard Drive?

[JohnT900]

I think I might have found something. Its related to the guide not being able to handle two different types of tuners at the same time. msvcrt.dll tries to keep it together and causes a blowout in ehRecvr.exe ....
https://support.microsoft.com/en-us/kb/2746119

I applied this hotfix last night as it appears(ed) to be a match for my issue. But this morning at 10:45, Event Viewer noted this issue:

Faulting application name: ehVid.exe, version: 6.1.7601.17514, time stamp: 0x4ce7aea3
Faulting module name: ehVid.exe, version: 6.1.7601.17514, time stamp: 0x4ce7aea3
Exception code: 0xc0000005
Fault offset: 0x0000000000009d30
Faulting process id: 0x18c8
Faulting application start time: 0x01d14e23479bbac1
Faulting application path: C:\Windows\ehome\ehVid.exe
Faulting module path: C:\Windows\ehome\ehVid.exe
Report Id: 944fc070-ba16-11e5-9586-90b11c767c41

Followed up by this "Information" item at 10:57...

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ehVid.exe
P2: 6.1.7601.17514
P3: 4ce7aea3
P4: ehVid.exe
P5: 6.1.7601.17514
P6: 4ce7aea3
P7: c0000005
P8: 0000000000009d30
P9:
P10:

Attached files:
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WERE91E.tmp.appcompat.txt
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER550B.tmp.WERInternalMetadata.xml
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER550C.tmp.hdmp
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER7C4B.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ehVid.exe_678b8d1547d7b69c2ce470fdff33f9d7659728c_cab_121b7ca6

Analysis symbol:
Rechecking for solution: 0
Report Id: 944fc070-ba16-11e5-9586-90b11c767c41
Report Status: 4

And the recordings that were ongoing at that time crapped out. So the previous Events (before the hotfix) noted an issue with msvcrt.dll whereas these Events note an issue with ehVid.exe.

[JohnT900]

1) What Version of Win7 are you using.... Home, Pro, Etc.? X86 or X64?

2) What Version of Microsoft Visual C++ is installed in Windows Programs and Features?

3) What Version of MCEBuddy?

4) What Codecs do you have installed? other than.... Haali which is included with MCEBuddy.

5) What kind of PC is this...Laptop, Tower, Etc.?

6 What Version of .NET are you running?

1. Winddows 7 Pro x64
2. There is no listing for Microsoft Visual C++ in the Programs and Features section.
3. MCEBuddy 2.4.3
4. Installed codecs:

Audio Codecs
Type Name Format Binary Version
ACM Microsoft IMA ADPCM CODEC 0011 imaadp32.acm 6.1.7600.16385
ACM Microsoft CCITT G.711 A-Law and u-Law CODEC 0007 msg711.acm 6.1.7600.16385
ACM Microsoft GSM 6.10 Audio CODEC 0031 msgsm32.acm 6.1.7600.16385
ACM Microsoft ADPCM CODEC 0002 msadp32.acm 6.1.7600.16385
ACM Fraunhofer IIS MPEG Layer-3 Codec (decode only) 0055 l3codeca.acm 1.9.0.401
ACM Microsoft PCM Converter 0001
DMO WMAudio Decoder DMO 0160, 0161, 0162, 0163 WMADMOD.DLL 6.1.7601.19091
DMO WMAPro over S/PDIF DMO 0162 WMADMOD.DLL 6.1.7601.19091
DMO WMSpeech Decoder DMO 000A, 000B WMSPDMOD.DLL 6.1.7601.19091
DMO MP3 Decoder DMO 0055 mp3dmod.dll 6.1.7601.19091

Video Codecs
Type Name Format Binary Version
ICM Microsoft RLE MRLE msrle32.dll 6.1.7601.17514
ICM Microsoft Video 1 MSVC msvidc32.dll 6.1.7601.17514
ICM Microsoft YUV UYVY msyuv.dll 6.1.7601.17514
ICM Intel IYUV codec IYUV iyuv_32.dll 6.1.7601.17514
ICM Toshiba YUV Codec Y411 tsbyuv.dll 6.1.7601.17514
ICM Cinepak Codec by Radius cvid iccvid.dll 1.10.0.13
DMO Mpeg4s Decoder DMO mp4s, MP4S, m4s2, M4S2, MP4V, mp4v, XVID, xvid, DIVX, DX50 mp4sdecd.dll 6.1.7601.19091
DMO WMV Screen decoder DMO MSS1, MSS2 wmvsdecd.dll 6.1.7601.19091
DMO WMVideo Decoder DMO WMV1, WMV2, WMV3, WMVA, WVC1, WMVP, WVP2 wmvdecod.dll 6.1.7601.19091
DMO Mpeg43 Decoder DMO mp43, MP43 mp43decd.dll 6.1.7601.19091
DMO Mpeg4 Decoder DMO MPG4, mpg4, mp42, MP42 mpg4decd.dll 6.1.7601.19091

5. System is Dell Optiplex 7010 mATX tower w/ i7-3770, 8GB, 500GB HDD
6. .NET version is 4.6.1

I am beginning to see why Fresh install of Win7 was suggested in Post #2..

Can you explain why you think this? I still am not sure why a fresh install is being requested over what is a fresh install? And to be clear: I have no issue with doing a fresh install, but given that this is a fresh install, I would like to try to squash these bugs as I suspect they won't go away with a fresh install.

That said, I have another tower similar to this one that I will probably try out this weekend. But I am going to still try to get this one sorted.

And thanks to everyone for your help. I do really appreciated it.