Unreadable BSOD when changing resolution in 6000

Try to uninstall that Winvnc hook, and update the GeForce driver.

Regards,
Frantz

Yannick Berker wrote:

> Hi,
>
> whenever I try to change the resolution in Windows Vista, I get a BSOD
> of which I can't read the content because all the letters are in the
> left 20% of the screen, overlapping each other. Changing the frequency
> and color depth works fine, resolution doesn't.
>
> memory dumps:
> http://berker.campus.ecp.fr/Mini120306-01.dmp
> http://berker.campus.ecp.fr/Mini120306-02.dmp
>
> my hardware:
> http://berker.campus.ecp.fr/hardware.gif
>
> I'm using a Medion MD-32119-PR TFT display, changing the driver did not
> help.
>
> Thank you,
> Yannick

"Yannick Berker" <yannick.berker@gmx.de> wrote in message
news:ekuf00$1id$1@guepard.ecp.fr...

> Hi,
> whenever I try to change the resolution in Windows Vista, I get a BSOD
> [...]
> memory dumps:
> http://berker.campus.ecp.fr/Mini120306-01.dmp
> http://berker.campus.ecp.fr/Mini120306-02.dmp
>
> my hardware:
> http://berker.campus.ecp.fr/hardware.gif
>

Yannick,

Both crash dumps show the same information - it was an 0xEA error
(translates to "THREAD_STUCK_IN_DEVICE_DRIVER").
Most probably it was caused by nv4_mini.sys file which is nVIDIA display
adapter driver. Timestamp of nv4_mini.sys is 2004-04-08 which seems to be
quite old. For example, on my Vista with Ti4200 card nv4_mini.sys file is
2005-12-10.

So, I'll second Frantz suggestion: update your video drivers to latest
version and refer to VNC vendor site to see if there's any information on
compatibility issues with Vista's graphics subsystem.

===============8<=================
D:\>kdfe.cmd Temp\Mini120306-01.dmp

Analyzing "D:\Temp\Mini120306-01.dmp", please wait... Done.

Crash date: Sun Dec 3 05:22:43.343 2006 (GMT+3)
Stop error code: 0xEA
Process name: msoobe.exe
Probably caused by: nv4_mini.sys ( nv4_mini+336cb )
===============8<=================

---
Alexander Suhovey

Frantz Dhin wrote:

> Try to uninstall that Winvnc hook, and update the GeForce driver.

I forgot to say I took the screenshot under XP - there is no Winvnc
hook under Vista. Updating the graphics drivers seems good to me, as
Alexander pointed it out.

Yannick

Alexander Suhovey wrote:

> Both crash dumps show the same information - it was an 0xEA error
> (translates to "THREAD_STUCK_IN_DEVICE_DRIVER").
> Most probably it was caused by nv4_mini.sys file which is nVIDIA
> display adapter driver. Timestamp of nv4_mini.sys is 2004-04-08

I don't know where you see the timestamp, but I'll try it I wonder
why MS would ship such old drivers with Vista, but who knows...
Thank you.

Yannnick