"NextPVR has stopped working" failure

[johnsonx42]

Sorry, ran that and it did not help. Still the same startup error. And there is not a new .log file showing, like not recording a log.

you mean you have no NPVR.log in c:\users\public\npvr\logs?

[sub]

Sorry, ran that and it did not help. Still the same startup error. And there is not a new .log file showing, like not recording a log.

I didn't expect it to fix anything. I just added some log messages.

Can you replace the existing file of the same name, then run the app, then post the npvr.log?

[Zeb]

Perhaps you didn't Stop/Restart NPVR Service in connection with the patch? Maybe make sure it's running and reproduce startup error before posting logs. [Edit] Or will Service not start either?

[bechis1]

Here is an updated nextpvr.exe, with more logging, which should help us narrow down the cause of the problem.

Ran the file and attached log. Doesn't look different.

[bechis1]

You need to right click on the command icon and select run as administrator. It's to prevent malicious code from running on your pc.

You're absolutely sure you installed all the pre-requisites listed on the wiki (post #4)

Microsoft .NET Runtime v2.0.
Windows Installer v3.1 or later.
DirectX 9.0c runtimes. (Not sure this is required on windows 8)
Microsoft Visual C++ 2008 Runtimes.

Thanks, still learning the quirks of W7/8. Ran sfc /scannow and it said it fixed a corrupt file. Restarted and ran NVPR again with still the same results, program would not open. I can send the Windows log file if you want.

[mvallevand]

After fixing the file I'd reboot uninstall and reinstall NextPVR Intel just released new drivers for the HD2500/4000 today so that might help too.

Martin

[sub]

Ran the file and attached log. Doesn't look different.

Are you positive you overwrote the existing nextpvr.exe with this new one?

[sub]

Here is a another patch, which adds further logging, earlier in the start processing. Reproduce the problem, and repost the log.

[bechis1]

Here is a another patch, which adds further logging, earlier in the start processing. Reproduce the problem, and repost the log.

Ok ran that and here is the log attached.

[sub]

Based on where that log finishes, it's definitely something to do with the Direct3D and your video card. It'll be something to do with the DirectX runtime, or your video card drivers.