Dot NET error completely out of the blue! Help!

[siliconaudio]

On Sunday, NextPVR 3.1.1 was working just fine during the day. Later that evening, whenever I tried to run it I got this in the Windows application event log:

Faulting application name: NextPVR.exe, version: 1.0.0.0, time stamp: 0x53384dee
Faulting module name: clr.dll, version: 4.0.30319.18408, time stamp: 0x52310b2d
Exception code: 0xc00000fd
Fault offset: 0x00378f7a
Faulting process id: 0xf80
Faulting application start time: 0x01cf57b17d3b1372
Faulting application path: C:\Program Files (x86)\NPVR\NextPVR.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: c39ba651-c3a4-11e3-9924-94de80bfec3b

I get the same error when trying to restart the recording service, only the application name changes. What is strange is that my PVR has been fine for months and absolutely nothing has been installed or changed. Even Windows update has to be run manually.

I have tried:

• Re-installing dot NET 4.5.1 (repair option)
  
• Upgrading to NPVR 3.2.9
  
• Removing dot NET altogether and reinstalling
  
• Googling "faulting module clr.dll" only to find any hotfixes relate to earlier versions than I have installed
  
• Any and all Windows Updates
  

I would send NPVR logs, but it's not getting far enough to create them. I'm at my wits end. This is the first GBPVR/NPVR problem I haven't been able to fix in years. Any help would be gratefully received.

Cheers,
Bill

[mvallevand]

Start by checking for a zero byte config.xml

Martin

[siliconaudio]

You sir, are a life saver. Thank you Martin! I just copied the default config.xml over the zero byte one and away I went. My wife is now off my back!

[johnsonx42]

this has been happening often enough perhaps it would be helpful if sub added an error handler to detect a 0-byte config.xml. the "sudden inexplicable .net blowup" has become a bit of a tell-tale for us, but doesn't help the average user.

[siliconaudio]

Thanks for the explanation. I had actually searched this forum for clr.dll, but came up empty. When I googled "Nextpvr" and "clr.dll" I didn't find an answer either. I guess even if there was an easy way for people to find help on this particular problem, we'd be better off.

[Reddwarf]

This error had me panic for several hours also some time ago, a more meaningful error message would be most welcome

[siliconaudio]

Just out of interest - do we know how config.xml ends up suddenly becoming 0 bytes in size? Seems like a very strange thing to happen.

[starkeyj98]

this has been happening often enough perhaps it would be helpful if sub added an error handler to detect a 0-byte config.xml. the "sudden inexplicable .net blowup" has become a bit of a tell-tale for us, but doesn't help the average user.

Hi, completely 100% average user here, with the identical error, simply trying to play a game on Steam... can you guys give me the "...for dummies" version of how to solve this?
PLEASE AND THANKS

[Graham]

Hi, completely 100% average user here, with the identical error, simply trying to play a game on Steam... can you guys give me the "...for dummies" version of how to solve this?
PLEASE AND THANKS

Are you a NextPVR user that is getting an error when using NextPVR?