Instant crash on start

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start 1964.

What is the expected output? What do you see instead?
I expect 1964 to at least open. Instead, I get a Windows "1964 has stopped 
working" screen.

What version of the product are you using? On what operating system?
r90, on Windows 7.

Please provide any additional information below.
The error details blame nvd3d9wrap.dll for crashing the application. In other 
words, my NVidia GeForce GT540M's drivers are probably in the wrong. However, 
there are no updates to this driver.
I do have hybrid graphics, but switching to the non-NVidia card gives me the 
exact same error for some reason.
None of the compatibility options work.
Running as admin does not work.
1964 is installed on an external FAT32-formatted hard disk.

Original issue reported on code.google.com by VincentB...@gmail.com on 19 Oct 2011 at 5:37

[GoogleCodeExporter]

is this still a problem??

Original comment by death2dr...@gmail.com on 16 Jan 2012 at 6:04

• Changed state: Questionable

[GoogleCodeExporter]

It is indeed, on 1.2 (r107). The source of the problem does not seem to have 
changed (same DLL).

NVidia Graphics driver version is 285.62. Downloading a newer (beta) driver 
right now, just to see if it works. I have a feeling it won't, though.

The problem signature I get is attached. Unfortunately, it's in Dutch, but the 
basic data that Windows finds. I'll gladly provide more details if requested.

Original comment by VincentB...@gmail.com on 16 Jan 2012 at 4:41

Attachments:

• 1964-crash.txt

[GoogleCodeExporter]

Hmmm I'm not actually sure whether this is a problem with 1964 or some weird 
problem with your drivers since the error is coming directly from your driver. 
:\ Sadly I am unable to recreate this error on my side, especially since I have 
an ATI(AMD) graphics card.

Original comment by death2dr...@gmail.com on 17 Jan 2012 at 1:12

[GoogleCodeExporter]

Yes, it might be graphics-related. But the weird thing is, if I use an Intel 
graphics card (this computer has two GPUs), it still gives the same error. 
Might still be a graphics driver-related issue, of course, since I don't 
actually know how the system decides to switch the graphics hardware while 
trying to run a program.

Is there a debug version of 1964 that I can try that logs stuff? Maybe we can 
at least figure out at which point during startup it crashes.

Original comment by VincentB...@gmail.com on 17 Jan 2012 at 1:19

[GoogleCodeExporter]

Hmm sounds quite weird, does this problem happen on any other computer you use?
There is a debug version, but I probably need to fix it up so it actually 
builds properly and there's a chance that the program is crashing before it 
even begins to launch. Hmmmm does this error occur with anything else??

Original comment by death2dr...@gmail.com on 18 Jan 2012 at 10:44

[GoogleCodeExporter]

The error does not occur with any other software, whether it's DirectX-based or 
OpenGL-based. I will be testing on a different Windows system when I have the 
opportunity.

Original comment by VincentB...@gmail.com on 20 Jan 2012 at 6:14

[GoogleCodeExporter]

Do you still have the problem?? Being a while since ive looked through all the 
issues

Original comment by death2dr...@gmail.com on 28 Apr 2012 at 3:21

[GoogleCodeExporter]

I have exactly the same issue.

win7 x64
nvidia GT540M/intel hd3000 (crash happens with both drivers)

Original comment by retroko...@gmail.com on 25 Jun 2012 at 4:34

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Edit: crash appears both with versions 1.1 and the latest rev144. I didnt 
change antyhing (plugins or whatever)

I have the latest drivers for both graphic cards.

Original comment by retroko...@gmail.com on 25 Jun 2012 at 4:37

[GoogleCodeExporter]

I have the exact same GPUs as retroko.

It took me some time before I was able to test, but the same issue does still 
seem to happen with r138. (Where did 144 come from? It's not in the downloads 
list...)

I'm not sure if I have the latest version of my graphics card because nowadays 
the NVidia updater crashes, too. (Downloading the latest driver manually now.)

Original comment by VincentB...@gmail.com on 25 Jun 2012 at 6:01

[GoogleCodeExporter]

Any update to this? Does 1964 work with Windows 7 at all, or is it just a few 
of us having this issue? When I do a clean install and try running it says it 
has stopped working. All my drivers are up to date, and I even reinstalled 
Direct X.

Original comment by Master...@gmail.com on 28 Jun 2012 at 2:41

[GoogleCodeExporter]

I also have a mobile nvidia card and it crashes on startup. I have a 540m.

Original comment by dodehoek...@gmail.com on 3 Sep 2012 at 9:52

[GoogleCodeExporter]

I too have a nv 540m. I have Windows 7 x64. I've been using PJ64 because 1964 
won't even start, not in administrator mode or with my graphics card set to use 
nvidia.

My laptop has optimus, so I can opt for nvidia or intel graphics.

WITH A FRESH INSTALL OF r146

When I opt for intel graphics instead, the video plugin fails to launch but the 
emulator runs. Then it asks you to choose a ROM folder and a video plugin. I do 
both those things, launch Ocarina of Time, and it's running fine on intel 
graphics.

Choosing nvidia graphics, the emulator fails to launch again.
If I choose intel again, it simply runs fine now, no video plugin crash.

I tested these things while typing this comment.

I hope this information is helpful in some manner.

Original comment by gll...@gmail.com on 30 Sep 2012 at 3:13

[GoogleCodeExporter]

On my system, with r146 the application no longer crashes, but it's unable to 
load the video plugin on first run. Afterwards, it runs fine. In the time 
between my last post the graphics drivers have been updated too, so I'm not 
entirely sure if this was fixed in the 1964 code base or at the driver level.

The video plugin reports to be using the Intel HD Graphics however, even though 
I'm running the emulator using the NVidia card. This might just be a weird side 
effect from how Optimus works, though (read: not all that integrated with the 
Windows system).

Original comment by VincentB...@gmail.com on 30 Sep 2012 at 4:25

[GoogleCodeExporter]

I just ran some older revisions to check; it seems that this has been fixed on 
NVidia's side. Updating/reinstalling the graphics driver to something recent 
should fix it.

Original comment by VincentB...@gmail.com on 30 Sep 2012 at 4:27

[GoogleCodeExporter]

This happens to me, too. Also tried compat mode for XP and 9x, no go. 
nvd3d9wrap.dll is mentioned in the "crash window". Graphics driver is up to 
date, so is 1964.

Original comment by robholx@gmail.com on 8 Jul 2013 at 1:42

[GoogleCodeExporter]

320.49 WHQL @ GTX 580 @ "crash window" with nvd3d9wrap.dll error.

Original comment by pio...@gmail.com on 21 Jul 2013 at 12:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

1964 used to work on older nVidia drivers for me. Stopped working on 320.49 
WHQL.
Windows 7 x64 on GT635m w/ Optimus. Using latest 1964 (r146)

1964 Will crash with both the nvidia card or the intel card.
'nvd3d9wrap.dll' is blamed for the crash.

Original comment by Nuke...@gmail.com on 15 Aug 2013 at 4:59