Bit Blot Forum
Aquaria => Support => Topic started by: Anubis on December 14, 2008, 02:57:08 pm
-
I just got the new 1.1 for windows and played for about 30 min before it crashed. This was in my system log: Display driver nvlddmkm stopped responding and has successfully recovered.
The below was in Vists's problem & support:
Product
Aquaria
Problem
Stopped responding and was closed
Date
14/12/2008 10:12 AM
Status
Report Sent
Description
A problem caused this program to stop interacting with Windows.
Problem signature
Problem Event Name: AppHangB1
Application Name: Aquaria.exe
Application Version: 1.1.1.0
Application Timestamp: 494277fc
Hang Signature: f526
Hang Type: 0
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 4105
Additional Hang Signature 1: 1dbaed75ce89c94d6ac519497d060ca7
Additional Hang Signature 2: a0e7
Additional Hang Signature 3: 8e5c7a0f64e5d86ebf08e1db492fffc3
Additional Hang Signature 4: f526
Additional Hang Signature 5: 1dbaed75ce89c94d6ac519497d060ca7
Additional Hang Signature 6: a0e7
Additional Hang Signature 7: 8e5c7a0f64e5d86ebf08e1db492fffc3
Extra information about the problem
Bucket ID: 410294724
Any help would be appreciated!
Anubis
-
Any idea what you were doing in the game when it crashed?
Do you have the debug.log from the crash? (it'll be in the aquaria root directory)
Did you have an older version of Aquaria installed at any point previously?
-
Also I stumbled across this website that claims that updating your graphics card drivers might fix the problem:
http://nvlddmkmdisplaydriverfix.com/
-
I downloaded the latest drivers and will give it a try! It's a fresh install of 1.1 on a new machine.
The last few lines of the debug:
limpses of her memories flashed in my head, and threatened to overwhelm me...
pos [22], file :gfx/visions/erulian/03.png
LOADED TEXTURE FROM DISK: [visions/erulian/03] ref: 1 idx: 704
pos [22], file :gfx/visions/erulian/02.png
LOADED TEXTURE FROM DISK: [visions/erulian/02] ref: 1 idx: 705
pos [22], file :gfx/visions/erulian/01.png
LOADED TEXTURE FROM DISK: [visions/erulian/01] ref: 1 idx: 706
pos [22], file :gfx/visions/erulian/00.png
LOADED TEXTURE FROM DISK: [visions/erulian/00] ref: 1 idx: 707
FMODEX error: 36: Unknown error code
Voice: Naija_SongCrystal3b
checking is playing now...
play now
I closed my eyes, and felt for one brief moment...
...that I was connected to all of history.
FMODEX error: 36: Unknown error code
Voice: Naija_SongCrystal4
checking is playing now...
play now
When I opened them again, the creature was gone.
FMODEX error: 36: Unknown error code
set control hint: (Learned the Bind Song, 0, 0, 0 t: 10 )
playMusic: Cave
playmusic end
Voice: naija_song_bind
checking is playing now...
play now
UNLOADING TEXTURE: visions/erulian/00
UNLOADING TEXTURE: visions/erulian/01
UNLOADING TEXTURE: visions/erulian/02
UNLOADING TEXTURE: visions/erulian/03
From the imprisoned soul, I inherited a new song.
By binding the Verse around physical objects...
...I would be able to move them through the waters with ease.
FMODEX error: 36: Unknown error code
erulianghost : attempt to call a nil value songNote
rock0006 : attempt to call a nil value songNote
Path [songcavecrystal] attempt to call a nil value songNote
erulianghost : attempt to call a nil value songNoteDone
rock0006 : attempt to call a nil value songNoteDone
Path [songcavecrystal] attempt to call a nil value songNoteDone
set control hint: (Use the Bind Song to Lift Rocks and Pull Up Plants, 0, 0, 0 t: 8 )
setting flag [242] to 1
Thanks
Anubis
-
Still crashing after video card update. Stupid NVidia... never had this problem on my ATI card... but then I upgraded and both this and the penny arcade game dies randomly...
-
Unrelated to your game crashing: But I've seen those FMODEX error's a lot in logs. Is there some useless code bouncing around in there and that's why these keep cluttering up the log?
-
Still crashing after video card update. Stupid NVidia... never had this problem on my ATI card... but then I upgraded and both this and the penny arcade game dies randomly...
Did you completely remove ati drivers before installing the nvidia card?
-
I'm also having this problem -- my display driver will crash and restart (Display driver nvlddmkm stopped responding and has successfully recovered.) and then the screen in Aquaria will turn all white. If I click, I get the notice that Aquaria has stopped responding, and I get the option to Wait for it to respond or to close the program.
I am running on Windows Vista 64 bit and I tried with NVIDIA 180.48 and 180.84 (beta).
There seems to be no correlation with what I am doing at the time. Sometimes this happens a few minutes after I start a game, and sometimes it takes longer. Here are the last few lines from my debug.log
UNLOADING TEXTURE: roodshrimp
changeForm: 0
lastForm: 1
EnergyOrb : attempt to call a nil value songNote
Path [naija_returntonormalform] attempt to call a nil value songNote
EnergyOrb : attempt to call a nil value songNoteDone
Path [naija_returntonormalform] attempt to call a nil value songNoteDone
turtle : attempt to call a nil value songNoteDone
HERE!
EnergyOrb : attempt to call a nil value
turtle : attempt to call a nil value
Path [naija_returntonormalform] attempt to call a nil value
hit avatar
hit avatar
hit avatar
Saving orb in slot, not charged
id: 11
setting flag [103] to 5011
energydoor : attempt to call a nil value songNote
orbholder : attempt to call a nil value songNote
energydoor : attempt to call a nil value songNote
orbholder : attempt to call a nil value songNote
EnergyOrb : attempt to call a nil value songNote
energydoor : attempt to call a nil value songNote
nautilus : attempt to call a nil value songNote
Path [energyslot01] attempt to call a nil value songNote
Path [energydoor02] attempt to call a nil value songNote
energydoor : attempt to call a nil value songNoteDone
orbholder : attempt to call a nil value songNoteDone
energydoor : attempt to call a nil value songNoteDone
orbholder : attempt to call a nil value songNoteDone
EnergyOrb : attempt to call a nil value songNoteDone
energydoor : attempt to call a nil value songNoteDone
trillious : attempt to call a nil value songNoteDone
nautilus : attempt to call a nil value songNoteDone
Path [energyslot01] attempt to call a nil value songNoteDone
Path [energydoor02] attempt to call a nil value songNoteDone
trillious : attempt to call a nil value songNote
changeForm: 1
lastForm: 0
energydoor : attempt to call a nil value
orbholder : attempt to call a nil value
energydoor : attempt to call a nil value
orbholder : attempt to call a nil value
EnergyOrb : attempt to call a nil value
energydoor : attempt to call a nil value
trillious : attempt to call a nil value
nautilus : attempt to call a nil value
Path [energyslot01] attempt to call a nil value
Path [energydoor02] attempt to call a nil value
-
Also I stumbled across this website that claims that updating your graphics card drivers might fix the problem:
http://nvlddmkmdisplaydriverfix.com/
This doesn't help either? (do you already have the latest drivers?)
-
Yes, I've tried the latest official and beta drivers.
-
Glad this topic came up. On occasion, but not overly annoying, I get the same crash with the Vista OS.
I think it happens mostly around the time of loading a new location, but not always. Also may be other game things going on that cause it. Other than that, I think my laptop should have no problems with it.
My specs: maybe some nonsense, but added what I thought might help.
Windows Vista™ Home Premium Version 6.0.6001 Service Pack 1 Build 6001
Nvidia Geforce 9700M GTS
TOSHIBA Qosmio X305
x64-based PC
Intel Core 2 Duo CPU P7350 @ 2.00GHz, 2000 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date TOSHIBA V1.20, 7/4/2008
SMBIOS Version 2.5
(RAM) 4.00 GB
Total Physical Memory 3.99 GB
Available Physical Memory 2.86 GB
Total Virtual Memory 8.16 GB
Available Virtual Memory 6.35 GB
Page File Space 4.29 GB
-
Is it an actual crash, or is the window just minimizing?
-
I can confirm the crash. The few times to date this has occurred it has always been while using the map, holding the right mouse button and scrolling around.
System Specs; (Dell XPS M1730)
Windows Vista™ Ultimate 32Bit SP1 (Build 6001)
Intel Extreme X9000 (2.8GHz)
4GB RAM
2x nVidia GeForce 8800M GTX (SLI mode) (Driver version 179.28 BETA for Noteboks)
It definitely crashes, at first you get a pause then the screen goes black, any input from there turns the screen white and windows asks if you would like to end the non-responsive program. I haven't had a lot of time to test driver settings for solutions, the only thing I have set that isn't default for the driver set is that I force vsync independent of applications settings, as I have found many of my applications cannot apply this setting correctly in Vista.
-
Is it an actual crash, or is the window just minimizing?
It's a crash for sure. But the error message appears to come from Vista, and not the game itself, as a bubble pops up from the task bar, showing the message explained above.
"Display driver nvlddmkm stopped responding and has successfully recovered." - Something to that effect.
From what I read so far on all the post, my guess it's some Vista compatibility issue.
-
Hmm, do you guys have the same troubles running other OpenGL games? (for example, the Penny Arcade games [I think they use OpenGL?])
-
I think it's OpenGL. The only 2 games I've had this happen for is the Penny Arcade games (both 1 and 2) and Aquaria. All my DirectX stuff runs fine.
I can play Aquaria from 5min to 1 hour... the crash is very random for me. Sometimes I'm clicking, sometimes I'm just swimming. A few times it has stuttered (low frames) and died, other times it has just quit unexpectedly. Like it was said above, the display driver crashes and restarts, but aquaria stays dead on my screen till I shut down the process.
-
I have a rather large array of games my fiancé gave me one day, a compilation of about 50 or so casual games, I've never had any of those crash in this manner, but then I've never delved too deeply into which of them run GL if they are accelerated.
If Anubis can replicate the error in other GL based games then that is rather pointing to the API failing on mobile hardware.
I don't have either of the penny arcade adventures. Any other GL based games or demo's you'd recommend testing with?
UPDATE: I ended up downloading GL Excess as it provided a means to loop GL playback and wait for an error. Good news and bad news on that front. Good news is that I can exactly replicate the fault we have been getting, so it's nothing to do with your game code. Bad news is that it is a nightmare bug, roughly linked to Vista/nVidia combos. There is a 113 page deep thread over at nVidia bout it (http://forums.nvidia.com/index.php?showtopic=25381), so that doesn't bode too well for getting it fixed anytime soon. From my readings I have picked out a few tweaks I'll try on my system but as of yet there doesn't seem to be any one sure fire way to get rid of the problem, nVidias stance is "we're working on it"
-
UPDATE: I ended up downloading GL Excess as it provided a means to loop GL playback and wait for an error. Good news and bad news on that front. Good news is that I can exactly replicate the fault we have been getting, so it's nothing to do with your game code. Bad news is that it is a nightmare bug, roughly linked to Vista/nVidia combos. There is a 113 page deep thread over at nVidia bout it (http://forums.nvidia.com/index.php?showtopic=25381), so that doesn't bode too well for getting it fixed anytime soon. From my readings I have picked out a few tweaks I'll try on my system but as of yet there doesn't seem to be any one sure fire way to get rid of the problem, nVidias stance is "we're working on it"
Interesting. I'm glad to hear its not something I screwed up, but it really sucks that there doesn't seem to be an immediate fix on the horizon. I guess the best bet is to create enough noise so that NVidia starts to care a bit more.
-
I started with the least invasive suggestion on a large list of suggested fixes and bizarrely it actually worked. I say bizarrely because the fix was just uninstalling Microsoft Dream Scenes (I don’t even use it, it was just installed via updates). Once I removed this I had GL Excess run overnight, almost 8 hours straight without error.
Since there are bound to be people with this error that aren’t running Dream Scenes it’s not the ultimate solution, but worth trying for a reasonably simple first step. There are a great many other suggested fixes listed on link I provided, but reading through all those posts is time consuming.
These are the steps for removing Dream Scenes if it is present on your system.
- Click ‘Start’
- Open ‘Control Panel’
- Open ‘Programs and Features’
- Click ‘View Installed Updates’ in the left pane
- Click the ‘Name’ column heading to sort the list
- Find any instances of Dream Scenes Installations (may be listed as preview for non-ultimate owners)
- Right-Click any instances found and select ‘Uninstall’
- Reboot your machine once all instances have been removed
-
That is indeed bizarre. Thanks a lot for investigating and sharing that information. :)
-
I'm running Vista Home Premium (HA! Premium... where's unleaded?) and there's no DreamScene stuff on it... just to let you know. :(
-
I think I found a solution to this problem. My guess is the cause is mismatched drivers/OpenGL implementation version, because I have not experienced the driver crash since I did this.
-Go to http://www.nvidia.com/Download/index.aspx?lang=en-us and download the latest version of drivers for your OS/GPU.
-Go to Device Manager
-Click on the + next to Display Adapters
-Right click on your NVIDIA graphics card and go to properties
-Driver tab
-Click Uninstall
-Check "Delete the driver software for this device"
-Windows will want to restart. When it does, it will install default display driver and want to restart again. Do so.
-Install the drivers obtained in the first step, and restart one final time.
Again, I have had no problems playing since I did this. Post if this solves your problem!
-
I'm not sure i'd go right ahead and update to anything that might be considered the latest video driver, or if it might possibly still be in beta. Because that happens.
Especially to be careful not to install the wrong driver or version.
Fact is, you might have certain other games installed that prefer another type of driver. So then that one may have its own issues.
Personaly, I run a lot of 3D games, so I don't know how much of a good idea that would be for me.
-
http://www.nvidia.com/object/geforce_notebook_winvista_179.28_beta.html (http://www.nvidia.com/object/geforce_notebook_winvista_179.28_beta.html)
For instance, this is the latest driver type for my laptops Nvidia 9700M GTS. But it's still in Beta form, which may mean certain problems within itself.
-
That's the NVIDIA recommended driver for your system -- If you are looking for a non-beta, you'll need to go to your laptop manufacturer's web site and get a driver from there or you'll need to check out http://www.laptopvideo2go.com . I've been using laptopvideo2go for years and their drivers are always more updated than the laptop manufacturer's, although NVIDIA did recently start supplying reference drivers for mobile cards.
Personally, I would go with the one on NVIDIA's web site. If you encounter problems, you can always uninstall it and try another driver by the same method I posted.
-
I am having the same problem.
I do not have DreamScene installed, so uninstalling is not a viable option.
I tried Boom's suggestion, but nothing changed. I also tried underclocking my GPU and memory, to no avail.
This error does not occur with a stand-alone version of Aquaria that I downloaded from a torrent site (game version 1.0.3). The error only occurs with the Steam version of the game.
Although it doesn't seem like a problem that can be readily fixed, here are my computer specifications:
450W power unit
Intel e6420 Core 2 Duo 2.13 gHz processor
BFGTech NVidia GeForce 8800 GTS OC 320MB
4GB Patriot DDR2 800 RAM
I've read that the nvlddmkm.sys error is due to Windows not working properly with NVidia drivers. I hope Microsoft is working on a fix, because this error almost renders Aquaria unplayable on my system.
-
Whatever. I got pissed and bought a 9800 GT from BestBuy (they're on sale now!) Problem solved.
Edit: Nevermind. After 6 hours of consecutive play, I got the error.
-
Hey, I bought Aquaria on Steam recently and I've been having the exact same problem as others in this thread. I updated to the newest drivers for my card and the problem has persisted, if not gotten worse.
If anybody comes up with a way to fix it, I'd like to know.
Edit: I've been playing around with the game in windowed mode at a lower resolution and so far so good...
-
This happens to me too. I'm only about four hours into the game and I've had six random crashes that happen just like those mentioned before (white screen, "nvdldlkdkmd blah blah" error). There seems to be no common factor in the crashes -- they can literally happen at any time, whether in the menus, looking at the map, exploring, etc. This doesn't ever occur with any of the FPS games I play, like TF2, CS:S, L4D.
My specs:
E6600 2.40 Ghz
GeForce 8800 GT (180.48 drivers)
3GB PC2-5300
Windows Vista Home Premium 32 bit
STEAM version of Aquaria, btw.
-
Try updating your video card drivers in the way described in this thread.
-
I am having this same problem... crash to a white screen seemingly at random. Plays fine for a while, then pukes out to a white screen. Very frustrating.
Vista, Steam, NVidia 8800 GTX.
I have done all the usual, including everything described in this thread. No change. Any word on the issue?
-
Seems to be a specific problem with that card, Hapcamp (the 8800). With my BFG Tech 8800 GTS 320MB OC, the game crashed on me every 5-30 minutes. After installing a PNY 9800 GT 1GB, I only receieved the error three more times throughout 20 hours of gameplay (to say once every six hours would be accurate). I can't offer a fix without having you swap out your video card, but it looks like anyone with a Geforce 8800 will have a hard time playing Aquaria on Steam.
-
I have the same issue and I'm using a nvidia GTX260 card.
When i install my video drivers, I always do a clean install. I use Drivercleaner.net in conjunction with safe mode to make sure everything is removed.
However, I read that nvidia has been working on a new openGL driver. I think they were testing it with the unreleased 181 drivers. http://developer.nvidia.com/object/opengl_3_driver.html
I may give them a try later. It would be great to find a surefire way to reproduce the problem without having to invest too much time.
-
okay, i have the same driver crash problem using the G80 8800GTS 640MB and Vista Home Premium 64bit.
though i could only test the demo(which seems to be v1.0.0) and im not going to buy it until its fixed. even though there are lots of save points, a crash is still annoying and i stopped playing because of those...
-
I had the same issue and, by disabling V-Sync, it seems to me that the crashes are less frequent (two 3 hours sessions without crashes for instance). :D
In NVidia drivers documentation, it is written that V-Sync should be disabled for OpenGL Application under Vista.
-
i havent disabled vsync but i played a bit with the opengl settings in rivatuner.
so far the demo didnt crash once. though i changed various settings so i dont know (yet) which change(s) made it run more stable.
my guess:
- OpenGl Hardware Acceleration Mode: NV20 Emulation Mode (compatibility mode is too slow, nv20 is fast enough)
- Disable Support for enhanced CPU construction sets
- Force Tripple Buffering (does only matter if vsync is enabled)
various other changes:
- Compress to DXT3 instead of DXT1
- VSync: 9
- trillinear optimization
- Anisotropic mip filter optimization
- Override Intellisample trilinear filtering quality control: High quality TLF
-
There's a new video driver out from Nvidia, 181.20. It's an official release. Give them a try. It appears to be a good driver.
-
im using 185.20.
and i dont think older drivers can fix this(same problem was with 180.84) nor the absolutely completely fully useless WHQL certificate.
-
I have discovered the issue and a fix for NVIDIA based cards.
The issue is with Driver Extension Strings. Newer versions of NVIDIA cards allow unlimited use of extension strings, and this causes issues with games using older versions of OPENGL.
To fix the issue, go into your nvidia control panel, to manage 3D settings, and set the Extension Limit option to On.
This has solved the issue for my steam copy of Aquaria. (through I also turned off v-sync as well) But based on the description of that option, I'm sure it's what's causing the issue.
-
Urgh. Sadly, I did eventually get the error again, but this time I'm averaging about two or three hours of play (more than enough to do stuff) before I get the white screen crash. My solution seems to extend playtime though.
-
though you lost vsync and earned page tearing... congrats.
i havent played longer than 3h, though as i said in one of my prev posts, the game seems to be running without any crashes (so far) with vsync enabled.
a bit more complicated but its worth it, aint it?
-
Which OGL version Aquaria uses? I want to limit reported version @ drivers level.
-
Hmmm...
Looks like I managed it work without crashes. Here is the solution for Vista /GTX260/182.06:
(http://img-fotki.yandex.ru/get/3114/kein-of.0/0_74ab_621033b4_L.jpg) (http://fotki.yandex.ru/users/kein-of/view/29867/)
Посмотреть на Яндекс.Фотках (http://fotki.yandex.ru/users/kein-of/view/29867/)
(http://img-fotki.yandex.ru/get/3110/kein-of.0/0_74ac_30042fc6_L.jpg) (http://fotki.yandex.ru/users/kein-of/view/29868/)
Посмотреть на Яндекс.Фотках (http://fotki.yandex.ru/users/kein-of/view/29868/)
-
on my ATI card it used to crash at startup or the game running at 0 to 1 fps
the fix was to update my driver to the most recent one , and to enable the OpenGL triple buffering in my ATI catalyst control panel
-
As it's been over a month after Kein posted a solution... I'll confirm that it's working for me so far.
Thanks Kein! I can Enjoy Aquaria again and actually get past Mithalas!
-
My daughter,seem s to have a similar problem, I swapped out her frozen Ge Force 6 series, Dell supplied, for a new Ge Force 9500 GT, on friday night. everything was fine here after we closed the machine and after she plugged it in at home. Sunday she turned it on to play Sims and after a short while the card seemed to burn, freeze, quit. Ant ideas ?