On 3/1/2010 3:43 PM, fok wrote:
Hi Guys,
I'm testing spice on my network and I've two workstations on which the
spice-client either immediately crashes, or after about half an hour.
The one on which spice immediately crashes is a dell optiplex 280gx,
windows XP SP3 with an Intel 915 graphics chip. The machine just shuts
down with a blue screen and c000021a error. It reboots then.
The other machine is a windows 7 Acer laptop with ATI Radeon 4200 card
built in. It works for about half an hour and then also crashes.
Since these both crash with a blue screen there's nothing in the
eventviewer.
I have a workstation with an Intel 845 (older machine) on which the
client is stable, I can work on that one for days without trouble.
Is there any development on the windows binairies, will there be updates?
Regards, Jan Fokkelman
Jan, if it's not too much trouble, could you perform some analysis on
the BSOD?
Here are simple instructions on how to do it:
1. Make sure that the memory was dumped. To configure it (in XP, in W2K
it's similar):
1.
Start -> Control Panel -> System -> Advanced -> 'Startup and
Recovery - click on the 'Settings' button
2. Make sure under 'System failure' 'Automatically restart' is NOT
checked; 'Write debugging information' should be set to 'Complete
memory dump'. You may need to restart the OS.
2. After a BSOD occurred, wait until it is completely written before
rebooting the OS.
3. After the OS completed booting, you can look at the memory dump
(usually, under %SystemRoot%\memory.dmp - which is usually
c:\windows\memory.dmp), using the Debugging Tools for Windows (install
from http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx ).
Note! If you use it on 64bit OS, you need the amd64 version).
4. Open WindDbg (Start->All Programs->Debugging Tools for Windows
->WinDbg), go to File->Symbol File Path and enter:
SRV*http://msdl.microsoft.com/download/symbols
If you have your own symbols as well, use:
srv*c:\symbols*http://msdn.microsoft.com/download/symbols
5. Open the crash dump using File->Open Crash Dump
6. Run the command '!analyze -v' (this may take a while).
Copy the whole output - it may be relevant.
TIA,
Y.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Spice-space-devel mailing list
Spice-space-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spice-space-devel
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Spice-space-devel mailing list
Spice-space-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spice-space-devel
