[97.9] Pressing OK on the config app *sometimes* causes a bluescreen

[Spartan]

This has happened to me a handful of times over the last week or two. I will open the config file, make a few changes, press ok -- and *poof*. Note that I do this over remote desktop, so I never actually see the bluescreen.

At any rate, when the system comes back up, I get a popup message that tells me that windows croaked due to a "device driver error" -- and gbpvr will not start up.

This is due to the fact that my config.xml file is trashed. The file now consists of 27k of little squares -- all on one line. These are the same little squares that you see if you read a text file and don't have the language installed.

I have attached my config.exe.log and you can see the little squares in there too.

As far as drivers go, for my 500, I have version 2.0.43.24103 installed.

[sub]

If it blue screens, then thats a pretty sure indication that the problem is occurring within a driver. Which driver - I'd have no idea, but hopefully the windows event viewer will give you some more info. If you're doing it over remote desktop, it may be you video card driver causing it.

[BFV/AcidRain]

If you can't find any thing in the event logs...

Within the first 2-3 lines of the Blue Screen, it should give you a file name. Google that file name to see if it has to do with tuner, video, audio, etc.

If it's giving different info every time it blue screens, don't forget to check the easy but obscure stuff: Clean power, bad stick of ram, etc.

[Spartan]

If you can't find any thing in the event logs...

Within the first 2-3 lines of the Blue Screen, it should give you a file name. Google that file name to see if it has to do with tuner, video, audio, etc.

If it's giving different info every time it blue screens, don't forget to check the easy but obscure stuff: Clean power, bad stick of ram, etc.

Problem is that I don't have a monitor on that server. It's tucked away in a closet in my basement and I access it via RDP.

[bgowland]

Spartan - check the System log with Event Viewer as sub suggests. It will show you similar information to what appears on the first lines of the BSOD although not the faulting module.

Strangly enough, I got a BSOD today just by launching the GBPVR main app. There was nothing unusual going on on my machine. No other programs running and no recordings going. It happened the instant I clicked on GBPVR in the start menu. The MS OCA just diagnosed it as an unknown hardware or software driver fault. It hasn't happened before and the machine recovered fine. Weird.

Cheers,
Brian

[Spartan]

There is no significant information in the eventlog (at least nothing significant to me...)

[sub]

You'll have to go from the info on the bluescreen then.

[Spartan]

Just a quick update -- I have used WinDBG to analyze my dump files and didn't get too much information about the problem.

On a whim, I decided to update my PVR500 drivers, and have not had the problem since.

I upgraded from

2.0.43.24103

to

2.0.43.24108

and all seems well now....

[rowle1jt]

Another thing to try if it does it again is to install VNC. RDP can do some pretty crazy stuff with drivers. I have had RDP giving me driver fits before, but sitting at the console everything runs fine. Just something else to try if the drivers don't keep it stable.

Best of luck Spartan!!

[Spartan]

Another thing to try if it does it again is to install VNC. RDP can do some pretty crazy stuff with drivers. I have had RDP giving me driver fits before, but sitting at the console everything runs fine. Just something else to try if the drivers don't keep it stable.

Best of luck Spartan!!

Good idea there. I personally prefer RDP over VNC due to the response time. VNC just feels sluggish to me.

Anyhow, I suspect the driver will fix the problem, b/c I recently rebuilt the server a month or 2 ago, and it was rock solid stable at the time (I needed to reconfigure my SCSI disks). When I put the new system together, I decided to install the latest-and-greatest Hauppauge drivers. Well I think they were the latest at the time, but definetaly NOT the greatest.

Hopefully, I now have the latest & greatest!