["Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx>]



It's interesting, the bugcheck code means that a breakpoint somewhere in the OS or in some driver got hit.

 

What does it say after "initializing disk for crash dump..."?

It should show a percentage indicating that it's dumping the crash dump to disk, and then eventually reboot.

Do you have a file named "memory.dmp" into c:\windows\?

 

Have a nice day

GV

----- Original Message -----

From: Gilmour, Scott

To: Developer support list for Wireshark

Sent: Wednesday, July 22, 2009 12:17 PM

Subject: Re: [Wireshark-dev] Windows 2008 Server

Graham,

I just installed Wireshark Stable Release 1.2.1

Windows Installer 32-bit

WinPcap 4.1 beta 5

The installer finished installing and I select run to start Wireshark

Right After that the system crashed with this message.

Thanks

Scott

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Graham Bloice
Sent: Wednesday, July 22, 2009 10:27 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Windows 2008 Server

 

Gilmour, Scott wrote:

Graham,

3555 sounds different since as soon as I double click on the Wireshark desktop icon my Windows 2008 Server on VMWare crashes.

Therefore I cannot even get to the interface to select an Ethernet connection.  This works fine on my Windows 2003 Server R2.

Thanks

Scott

 

Scott,

1.2.1 works on my Server 2008.  I used the 32 bit version even though the server is 64 bit.  Can you give any more info about the crash?

-- 

Regards,

Graham Bloice

---

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe