Animated Dreamscene doesn't work on Forceware > 158.18 version

Hi I'm nVidia user, I do frequently(I think that everybody same..!) change Forceware
driver at any given chance, so I found 158.18 Beta driver and did install it!
After that, every dreamscene which made by graphic elements, not just video format cause my background greenish-broken-persistance-afterimage-shadow-ished.
And I change more higher version of Beta drivers and expect fix this hack, but all same.
Although all the other graphic program such as Games does not affect anything by these new beta driver.
Anybody got same problem like me? I think that it's not driver issue because any other graphic application works fine as I mentioned above....
Anybody have any idea about it?
6,144 views 21 replies
Reply #1 Top

If it got broken when you changed your drivers then it will probably be a driver problem.

I would suggest you revert back to the original drivers.

Reply #2 Top
If it is really driver problem, why the other applications such as games - probably it use more graphical functions than dreamscene - does works fine?
And sample dreamscene that pre-installed when you install deskscape, or original dreamscene files provided by microsoft are works fine, too...
Reply #3 Top
well the 158.18 forceware drivers are still a beta driver..down grade the drivers to the 101.90 and see if that helps out, how long ago did you install the 158.18 forceware? last time i checked they were beta.

UPDATE

i just looked on their site just now and now those drivers are WHQL.try downloading those drivers and see if that help
Reply #4 Top
MadDuke, does this happen with any animated background? If not, can you tell me exactly which background(s) you're trying, so I can try to reproduce the problem? Also, you reported that 158.18 had this problem, and you tried another higher-version. Can you tell me which version of Forceware you also tried? You can find out by right-clicking your desktop, selecting "NVIDIA Control Panel", and from the menu bar, select "Help", "System Information". The details will include "ForceWare version". Also, which graphics card are you using? Thanks.
Reply #5 Top
Thanks for your reply, Agrabren.
I tried 158.18, 165.01(of course it is beta), currently I use 165.01.

My graphic card is nVidia 7600GT, 256MB RAM.

Aura, Bliss, Circles, Circles1080p, DeepOcean, EarlyMorning (Earlymorningversion2 is works fine though), Moodbubbles, RainbowNebulaflight, Silence, SpaceFlight, StarField, TheBoomBox, UnderWater, VistaV2, VistaV3, WMVhd... those makes problem.

At this very respect, please check what I confused, that EarlyMorning Dreamscene has two different encoded version, first one has confilct with Forceware but second one(version 2) works fine, and version 2 is encoded MPEG. All dreamscene which encoded MPEG doesn't crash at all(I'm not that sure, though).

Maybe because of codecs? I use Vista Codec Package v4.3.8 by shark, you can download at http://www.msfn.org/board/index.php?showtopic=66826
But I use this codec since Forceware 100.65 WHQL and Dreamscene did not have any problem but now.

Thanks.
Reply #6 Top
What graphics card are you using? I am using the Forceware 158.18 drivers on Vista and don't see the problems you describe.

Edit: too late,..... I am using the original codecs though
Reply #7 Top
Oh 158.18 is now WHQL certified! I didn't know this.
I'll try this one and test again, thanks for your post whatwhere.
Reply #8 Top
it is the codecs that are causing the crash. i took upon myself to download all the dreams and try each one. for nivida users the way to find out, even though you don't need the old purevideo decoder is to download it and watch how many times that codec conflicts with a good portion of dreams. i know it sucks but we will have to do trial and error with the dreams or hope that the people making the dreams will encode them so that most people can use them..still new, still the same old windows, same old crap, just a new field with some obstacles to overcome. give it time and we will see some good results..
Reply #9 Top
WHQL just means it won't complain about signing. Won't affect if the driver works for you or not. If the driver version number is the same, it's the same driver (unless you either got a corrupt package or hacked version). Trying it now, but I'm not having a problem. I'll try tomorrow with 158.18, a 7700GT, and that codec pack.
Reply #10 Top
I did install 158.18 WHQL. It doesn't makes any sense.

I did uninstall codec package. It doesn't makes any sense, too.

But now I'm sure that all dreamscenes which encoded MPEG works fine under 158.18 WHQL.

All others which encoded WMV got crash. Huh....   
Reply #11 Top

Never install codec packs like that.

Windows Vista Ultimate already comes with a WMV and MPEG2 decoder so you do not need to download other ones.

Reply #12 Top
Banfield, thanks for your suggestion, however I need codec for subtitles(with .smi extension) with AVI video. Vista has most of codecs already but subtitle codec.
That's why I installed it.
But Deskscapes worked fine with Forceware under 158.18 version and this codec pack.
Just I install new forceware and it happened, so roll back driver and it works again.
I hope that this problem caused by bugged driver, so it will fix soon(probably...).
I already sent bug report to nVidia, I hope that they work on it.(Believe or not...lol)
Reply #13 Top
MadDuke, I'll take a look and submit a bug report if there's a driver incompatibility. Especially if it's a regression. It's probably too much to ask, but Neil, is there a tool to extract apart a .DREAM file? This would make this a lot easier to diagnose.
Reply #14 Top
I haven't been able to repro this issue. The only thing I don't have is a 7600 board. I tried to get my hands on one, but no luck. I tried the 6800, and the 8800, but even with the codec pack, it ran fine. Do you have a screenshot showing the problem?
Reply #15 Top
Negative here. I'm using a FX5200 which the new drivers don't even support, but they do work- and surprisingly well compared to the pack-in ones.
Checked hardware acceleration?

Otherwise, it's definitely the codecs.
Trust NOTHING but K-lite.
Reply #16 Top
I have 2x7600GTs in SLi with the 158.18 drivers and I have no problems at all   
Reply #17 Top
most people i know that have had this problem report that the nvlddmkm file is the problem..nvidia and microsoft know of the problem but don't seem to be working to hard to find the solution. on some forums people have stated that whenb a dream starts, it also trys to decode with the purevideo which is built into the 8800 series and that will shut down the dream and say that you have recovered for a driver that failed. i know it sucks to download a dream and not have it work, but trial and error are the only thing that we have to help each other...
Reply #18 Top
hey found out something about the nvidia drivers. all versions of the drivers since they have been out for vista have not been replacing all of the files in the system32 folder. if you look you will see that the file nvlddmkm.sy is older than the other files by far. if you look in your nvidia folder for the same file you should see that it is newer. you can try if you want.. copy al the .dl files and put them into your system32 folder and this should help..hope this can help someone.....
Reply #19 Top
I'll take a look. A good recommendation (may not help) is to go thru Add/Remove Programs, and uninstall "NVIDIA Drivers" (just the display drivers, if you've got an nForce chipset). Then install, and make sure if you're prompted to replace files, to say yes.
Tripdog, do you know a way to cause this to happen? And are you using the setup.exe program found in the driver install package?
Reply #20 Top
oyu don't have to uninstall them. if you have to redownload the drivers, install them, then go to the system32 folder and find the nvlddmkm.sys file and rename nvlddmkm.sys.old, then go to the nvidia folder and copy all the .dl files and then put them in the system32 folder and double check the nvlddmkm file and it should have a new date ....try that...
Reply #21 Top

WHQL just means it won't complain about signing. Won't affect if the driver works for you or not. If the driver version number is the same, it's the same driver (unless you either got a corrupt package or hacked version). Trying it now, but I'm not having a problem. I'll try tomorrow with 158.18, a 7700GT, and that codec pack.


actually when the drivers are WHQL certified it does mean the OS will not cry bout the drivers being signed or not but it also means microshaft puts the drivers thru some really hard tasks to ensure the driver won't crash nor crash the operating system (mainly so it won't crash the OS...but then again it is winblows)