W7 RC build 7100 crashing

[datman]

I just installed W7 rc and I have had several crashes. I get the “recovered from an unexpected error” The 1st 3 were in the 2nd pass but the last 2 were during the 1st pass (same movie). A lot like the errors you get when you O/C with the wrong settings. I have my phenom 940 O/Ced a little to 3.41 this setting worked for countless encodes with W7 beta.

I have done 3 complete encodes and the only common issue is all the crashes are when the computer is not connected to the Internet.

I know jdobbs is not giving w7 support right now but perhaps someone has some ideas.

[Atak_Snajpera]

You better check if your cpu is stable enough. Use Prime95 MT in stress mode for at least 12 hours then check if your memory is not faulty. memtest86 is great for detecting bad memory.

[datman]

I will do that. Thanks

The cpu has been fine up until installing w7rc.

[Sharktooth]

build 7264 was just leaked... the RTM will sign out on 13th of July.
my sugguestion is, if you're sure your system is perfectly stable, then update...

[burfadel]

If your computer did run fine overclocked with a certain programme/settings, then it doesn't work and you need to knock back the overclock, then it is reasonable to say the overclock was too high to start with. People still go around overclocking Q6600's etc to 3.6ghz+, and although it may seem fine you will always strike instances where things won't run properly. Even running Prime for 24 hrs may not show any problems caused by overclocking! - its just more likely to show!

Remember if you overclock and the room temp is 20C, remember at 30C every component in the computer (CPU, RAM, chipset, video card, hdd etc) will also be hotter. Many overclocks come unstuck because people don't take in to account varying temperature changes, the chipset & motherboard cooling, the RAM overheating, the HDD being exposed to extra heat etc etc!

[datman]

I had this a lot faster when I started I was up to 3.71 (3.0 default) and had sucessful encodes. But the temps were to high. CPU 62. chipset 78. I have it at 3.41 and the voltage set to normal. My temps are cpu 46 and chipset 56 (in a cool room) during a 2nd pass

perhaps I need to bump my volts up .

[GaPony]

I'd return to stock settings, then see how things work. Knock out the most obvious thing to cause the crashing first.

It might be some incompatibility between Win 7 and BD-Rebuilder, but since Win 7 (and BD-Rebuilder) are still in beta. Jdobbs isn't doing anything extra to support Win 7 at the moment... nor should he.

[datman]

I'd return to stock settings, then see how things work. Knock out the most obvious thing to cause the crashing first.

It might be some incompatibility between Win 7 and BD-Rebuilder, but since Win 7 (and BD-Rebuilder) are still in beta. Jdobbs isn't doing anything extra to support Win 7 at the moment... nor should he.


I'm 57% into an encode. If it works I'll run Prime95 MT. I bumped up my volts perhaps with the beta version it was maxed out but would run. The RC version may be more demanding and put it over the top. If it crashes back to stock I go:(

[Pntgrd]

I have found that encoding video is way more demanding than Prime ever is. I noticed no difference in going from the Beta's of Win 7 to RC1 as to what it demands on my machine, which is a QX9650 o/c to 4.08 ghz (3.0 is stock). I would guess the extra voltage should do the trick for you.

[datman]

it seemed to. That was

the only thing different so it must have been it.

you must have great cooling!

[datman]

I ran into some more glitches that may be a w7 issue. Since I install rc1 and updated to 24.02 I have been having a lot of failure to encode errors. Just before the 1st pass. I tried prior versions same thing. The one thing I did notice is ffdshow was not opened up in the taskbar. I updated it to 3014 and still failed.

I had Vista 32 on a drive in this computer I had unplugged several months back when I started playing with w7 beta. I plugged it back in and vista booted I updated BDRB to 24.02 and ffdshow to 3014 and the same movie that failed before is encoding as I post this. I guess it was w7 error.

Ffdshow still did not open up for this encode on the 1st pass. Seems like it does not always get used.

[burfadel]

Well in terms of Windows 7, as far as I am concerned the official RC1 is more of a 'late beta' than a RC. A RC is exactly that, a candidate build that could be released or released with only a few small adjustments where errors are found. The Windows 7 RC1 was partially crippled (the directshow filters, some intended minor features not included) and was never meant to represent what the final product will be like. In addition, if they called it a beta, any issues people may come across can be explained by the beta status of the OS. If it works perfectly for people, they have the bonus of thinking 'wow this is good for a beta, can't wait for the final product'. If people have a few problems with the RC, regardless of whether if they've been fixed or not, they will be put off to a certain degree for the final product.

So keeping everything in mind, the RC was more of a hype release, it definitely should not have been classified as an RC and should have been called either a preview release or a 'post beta' release. Due to the nature of the release, you should expect errors and in terms of ffdshow, that I believe is an issue by design!

[datman]

well it appears to have been different from the beta version I was running. I did have some encode that completed with rc1. I believe other people are running rc1 without issues. So it make since that being that it’s partially crippled explains why these applications are not working. The beta 7022 work nearly perfect

[crusty_shane]

I am running this version of windows 7 rc and is running fine, apart from certain movies keep coming up with
[17:00:14] BD Rebuilder v0.24.02 (beta)
- Source: MATRIX_RELOADED
- Input BD size: 37.02 GB
- Approximate total content: [07:23:26.488]
- Target BD size: 4.27 GB
[17:00:17] PHASE ONE, Encoding
- [17:00:17] Extracting A/V streams [VID_00006]
- [17:00:18] Reencoding: VID_00006 (1 of 68)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[17:03:26] - Failed video encode, aborted

I have tried everything and no luck.. Was same when running vista.

[datman]

I am running this version of windows 7 rc and is running fine, apart from certain movies keep coming up with
[17:00:14] BD Rebuilder v0.24.02 (beta)
- Source: MATRIX_RELOADED
- Input BD size: 37.02 GB
- Approximate total content: [07:23:26.488]
- Target BD size: 4.27 GB
[17:00:17] PHASE ONE, Encoding
- [17:00:17] Extracting A/V streams [VID_00006]
- [17:00:18] Reencoding: VID_00006 (1 of 68)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[17:03:26] - Failed video encode, aborted

I have tried everything and no luck.. Was same when running vista.

I went back to vista 32 and it has worked better. My crashing had something to do with my OC and voltage setting.

I have had a few errors like that I just move on and try it later

[GaPony]

I almost always get errors when overclocking, so I find its better to just run it at stock. The time difference is insignificant anyway.... and I get better results.

[crusty_shane]

I tried ripbot with the movies that I have had trouble with and these worked a treat. Maybe certain movies don't work too well with bdrebuilder.
Some of the ones I have had trouble with are I-robot, Matrix Reloaded, Matrix Revolutions
These worked perfect with ripbot.

[jdobbs]

I tried ripbot with the movies that I have had trouble with and these worked a treat. Maybe certain movies don't work too well with bdrebuilder.
Some of the ones I have had trouble with are I-robot, Matrix Reloaded, Matrix Revolutions
These worked perfect with ripbot. They's also work with BD-RB -- but I'm guessing you're configured incorrectly.

[crusty_shane]

They's also work with BD-RB -- but I'm guessing you're configured incorrectly.

Tried configuring same as your guide, but no luck? Must be something I am missing.

[jdobbs]

I'm not currently supporting Windows 7 because it is buggy and has some odd configurations that will likely change before it is released. You may want to read this post (http://forum.doom9.org/showthread.php?t=146924) and see if it helps you get running.