Blue screen when tuning

[Obsidian]

Hi there

I have been looking at these forums for a while, but recently decided to take the plunge and try out GBPVR, being sick and tired of trying to get MythTV to function properly.

However, I have been having some trouble with my Hauppauge Nova T 500, specifically getting it to tune. I have been getting BSOD, "Page fault in non paged area" in NV4_MINI.SYS" (the graphics driver I believe) every time I try to tune. This was occurring with both the included WinTV software and GBPVR. Last night, I tried changing the Hauppauge "Primary" program to use overlay rather than VMR (my graphics card is rather old, and I guess it doesn't support VMR), and this solved the problem! Everything tuned in fine win WinTV2000. Wonderful I thought, here we go!

However, when I tried to tune in GBPVR I still get the blue screen. I have set GBPVR to use overlay rather than VMR, I have the latest drivers from Nvidia for my graphics card, and I have the latest drivers from Hauppauge also. The following is the spec of my system:

AMD Athlon XP 2000+
MSI Motherboard
1Gb RAM
120 GB HDD
Nvidia Geforce 4 MX 420
Creative Audigy 2
Hauppauge WinTV Nova T 500

I am running Windows Standard Server 2003.

Any help would be much appreciated!

[JonnyCam]

Why dont you run memtest86 - I had the same type of issues with my ATI drivers suppoedly at fault - BSOD, telling me faulting modules etc -but one of my ram sticks was faulty.

seems to be fixed now. The "Page fault in non paged area" sounds like it could be memory (maybe)

[Obsidian]

Hi. Thanks for the reply.

That seems plausible I guess, so I'll give it a go. Given that it always happens in the same place though (i.e. when tuning), and was fixed by turning off VMR on WinTV I suspect that it may not be the problem...

[sub]

Unfortunately GB-PVR's scanning utility will use VMR if the system says its available.

Might be also worth checking if there are updated drivers available for your video card.

[Obsidian]

Thanks Sub, that makes sense given what I discovered last night...

I tried the memory, but that didn't seem to be the problem. What did fix it was turning hardware acceleration down on the graphics card, and then scanning (I guess that disabled VMR). Turning hardware acceleration back up on the card was fine once I was running the GBPVR frontend.

Is this going to be a problem with DVB EPG updates, or does GBPVR not use VMR for that? I have the latest drivers for the card, so there's nothing I can do there.

I did a bit of testing with the card, and as well as getting the blue screen whenever it tries to use VMR, I also get one with the Direct3D test in dxdiag. It all seems a bit odd, I'm tempted to do a reinstall of windows as I'm guessing that something may be corrupted? I've already tried uninstalling and reinstalling drivers, so a full reinstall seems the most thorough way.

On the other hand, it is a very old card, I guess perhaps I should get a newer one. Does anyone have any advice?

[Obsidian]

Also, I just had a thought. Could the blue screens be because the card doesn't support Directx9. If so, should I downgrade directx?

[sub]

What did fix it was turning hardware acceleration down on the graphics card, and then scanning (I guess that disabled VMR). Turning hardware acceleration back up on the card was fine once I was running the GBPVR frontend.

Great.

Is this going to be a problem with DVB EPG updates, or does GBPVR not use VMR for that? I have the latest drivers for the card, so there's nothing I can do there.

That should be ok. The DVB EPG update wont need to use VMR.

I did a bit of testing with the card, and as well as getting the blue screen whenever it tries to use VMR, I also get one with the Direct3D test in dxdiag. It all seems a bit odd, I'm tempted to do a reinstall of windows as I'm guessing that something may be corrupted? I've already tried uninstalling and reinstalling drivers, so a full reinstall seems the most thorough way.

On the other hand, it is a very old card, I guess perhaps I should get a newer one. Does anyone have any advice?

Sorry, I dont really have answers for these. It could be the windows install. It might just be buggy drivers for the card that doesnt correctly implement VMR9 support, or maybe some hardware instability with that combination of card and motherboard. Updated motherboard chipset drivers might also help.

Good luck - hope you get it sorted!

[Obsidian]

OK, thanks very much for your help anyway. I'm very impressed with this community, it's very helpful and friendly!

[Obsidian]

OK, I finally fixed this today so I thought i'd post the solution just in case someone ever had the same problem.

It turns out that for some (bizarre) reason, the combination of Nvidia drivers, directx, windows 2003 server and terminal server is a bad one, and causes BSOD whenever direct3d is used. My solution was simply to uninstall terminal server. Failing that you might have to switch to an ATI card!

Link to the discussion on the Nvidia forum: http://forums.nvidia.com/lofiversion/ind...15510.html