Closed Bug 587271 Opened 14 years ago Closed 13 years ago

Direct2d crashes Nvidia Ion 2 graphics driver with black screen

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: foxyweb, Assigned: btodur)

References

(
URL
)

Details

(Keywords: crash, stackwanted) 

User-Agent:       Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3) Gecko/20100805 Firefox/4.0b3
Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3) Gecko/20100805 Firefox/4.0b3

Enabling Direct2d causes Nvidia ion 2 driver to crash, resulting in a black screen. This seems to happen randomly while loading websites. 

My computer specs are: 2 gb ram, intel n450 processor, nvidia ion 2. 

Reproducible: Always

Steps to Reproduce:
1. Type: "about:config" in the 'AwesomeBar' and hit Enter.
2. Set gfx.font_rendering.directwrite.enabled to true
3. In about:config still, Search for "mozilla.widget.render-mode".
4. Change value to '6'. 
5. Restart Firefox.
6. Load some webpages, and Firefox will seemingly crash the graphics driver.
Actual Results:  
Black screen. Firefox restart required to reset the black screen. 

Expected Results:  
Goes back to normal but crashes again.

No crash.
Which driver version do you have installed and did you try to upgrade to the latest one ?
Component: General → Graphics
Product: Firefox → Core
QA Contact: general → thebes
Version: unspecified → Trunk
Yes. The driver I'm using is 189.34, which is the latest one. The problem still exists though.
189.34 is not quite the latest version, see the latest version here: http://www.nvidia.com/object/notebook-win7-winvista-258.96-whql-driver.html

Also, if that doesn't fix it, all we can really do is blacklist the driver. If we can crash the graphics driver, the graphics driver is bugged. There's little we can do about it. A stacktrace wouldn't help, as in this case it's not the usermode driver which is crashing. It's the actual device. Firefox should recover once the device recovers, but that logic isn't done yet.
fwiw, I've had crashes with 257.12 on my MBP, and with a similar version as the reporter on my ion (1) netbook.
(In reply to comment #5)
> fwiw, I've had crashes with 257.12 on my MBP, and with a similar version as the
> reporter on my ion (1) netbook.

Yeah, I'm not sure what we can do about it, except send bug reports to NVidia, and of course making sure we recover when the device recovers. (I've got a solid strategy for this for D3D9+D2D)
vlad: please get us a stack, we do have some nvidia people in bugzilla, they're eager to get stacks...
Assignee: nobody → btodur
We have lots of nvidia contacts, the problem is that there are no stacks to get -- Firefox doesn't crash.  The driver itself crashes, and windows recovers it.  Potentially we may be able to get a stack by attaching a kernel debugger and waiting for the problem to happen, but I'm skeptical (and that would require using a second machine with lots of painful setup).  Better would be to figure out if there's a dump file that's left by windows' driver recovery...
in the old days, softice was the answer, that seems dead :(. Do you really not have a second computer? if it's the graphics driver, then i think you can use kernel debugging via tcp/ip (which avoids the need for serial/firewire).

http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

indicates some possibilities

http://social.answers.microsoft.com/Forums/en-US/vistahardware/thread/a70ca715-c71d-4bcc-877c-9997d4967d7a

shows that there's *sometimes* a .dmp file created...

you might try verifier.exe - http://support.microsoft.com/kb/244617

I think the simplest thing is to enable the kernel debugger, configure TDR to break into the kernel debugger. When you land in the kernel debugger, just generate a full memory dump (try '.dump /f memory.dmp') and 'g' (continue). That should give you a dump you can play w/ from windbg later.
It's possible that I have the same issue with Seamonkey trunk on my Laptop with a Geoforce310M and win7
This started a few days ago but I didn't enable D2D (gfx.font_rendering.directwrite.enabled=false, mozilla.widget.render-mode=-1
nvlddmkm freezes and win7 kills it. I updated the driver to version 258.96 but it also freezes very frequently
(In reply to comment #10)
> It's possible that I have the same issue with Seamonkey trunk on my Laptop with
> a Geoforce310M and win7
> This started a few days ago but I didn't enable D2D
> (gfx.font_rendering.directwrite.enabled=false, mozilla.widget.render-mode=-1
> nvlddmkm freezes and win7 kills it. I updated the driver to version 258.96 but
> it also freezes very frequently

D2D is enabled by default since some days :-). So that would be why you've been having the issue since then.
>D2D is enabled by default since some days :-
I expected that but shouldn't the preference option be set to a positive number by default in that case ?

The screen recover would be a very good solution for rare crashes but I hit this every hour. I think we need to hire a few people for bugzilla triage and for the support if this is a general issue with the nvidia mobile chipset and blacklisting the driver doesn't help if we can't get this fixed by nvidia for future driver versions. I'm willing to help if needed but kernel debugging with TCP/IP would be a little bit too much.
(In reply to comment #4)
> 189.34 is not quite the latest version, see the latest version here:
> http://www.nvidia.com/object/notebook-win7-winvista-258.96-whql-driver.html
> 
> Also, if that doesn't fix it, all we can really do is blacklist the driver. If
> we can crash the graphics driver, the graphics driver is bugged. There's little
> we can do about it. A stacktrace wouldn't help, as in this case it's not the
> usermode driver which is crashing. It's the actual device. Firefox should
> recover once the device recovers, but that logic isn't done yet.

Actually, this is the latest driver for my netbook's model; Asus 1201pn. The driver on the Nvidia website requires me to get driver from the Asus (manufacturer) website, which I double-checked is the latest version there.
My initial bug was marked duplicate, but its not exactly as I'm using a Quadro FX1800M which is not covered by the above driver. 

However http://www.nvidia.com/object/notebook-win7-winvista-64bit-258.96-whql-driver.html does seem to help, at least I haven't crashed since installing it.
Corey: I have a 310M and I have to use the same driver as you but that crashes on my system....
The latest beta driver fixes the very frequent crashes (once per hour) with my 310M
Severity: normal → critical
Keywords: crash
I have also found the same, once the WHQL 260 drivers become I'll try those as well.
Firefox should now also recover when there's a display driver crash. It would be good if you can confirm this!
Blocks: 571756
No longer blocks: 571756
Blocks: 605749
this trojan steel home desktop top no web surf no programs tuffie wish I was an at home bugzilla agent  { is there a cost  ] , { Volunteers }, Great team player Robert E. Clark   thank you 4 da support HELP again again amature computer buff  somewhat........ Help me stay modern?
(In reply to comment #19)
> The latest beta driver fixes the very frequent crashes (once per hour) with
> my 310M

Matti, Cory, so OK to close WFM?
Chris: Does this work now with recent drivers on your system ?
(In reply to Matthias Versen (Matti) from comment #24)
> Chris: Does this work now with recent drivers on your system ?

I had PMed Chris back in Feb but no response. So we've lost contact.
=> WFM based on other reporters' comments
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Summary: Direct2d crashes Nvidia Ion 2 graphics driver → Direct2d crashes Nvidia Ion 2 graphics driver with black screen
You need to log in before you can comment on or make changes to this bug.