Link to home
Start Free TrialLog in
Avatar of Pumpernickel
PumpernickelFlag for United States of America

asked on

Windows 7 Dump File

We have started using nComputing software with an HP 8200 Elite.  It seems to be blue screening a lot lately.  Can someone take a look at the dmp file and see what is causing this?

Windows 7 Professional x64
nComputing x350 kit
Avatar of Anuroopsundd
Anuroopsundd
Flag of India image

Can you attach Dump file.
Avatar of Pumpernickel

ASKER

sorry forgot to
040912-30763-01.dmp
Probably caused by : win32k.sys ( win32k+1c241f )

your win32k.sys file seems to be corrupt..
seems some 32 bit application is using this and causing the BSOD..
How can this be identified more?  I have a feeling its the nComputing software or the Video Driver
ASKER CERTIFIED SOLUTION
Avatar of Rob Miners
Rob Miners
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
if it's your video graphic drivers you should update the latest drivers and install.
also as your system is 64 bit try to download the 64 bit drivers.
Are you sure nComputing x350 kit meet minimum system requirement ?

Please check, what its says under minimum system requirement
http://www.ncomputing.com/docs/guides/en/guide_X550_X350.pdf
Yes they do.  The towers are HP 8200 Elites
I guess the problem has something to do with Windows 7.

What does following mean under Minimum system requirement.
" You cannot use the vSpace software with Windows Client software (i.e., Windows Vista, Windows 7)....." ?


" As a best practice, before deploying any
new OS service pack, first confirm vSpace support "
Avatar of McKnife
When a machine bluescreens and the dumpfile points to ntoskrnl.exe (which http://www.nirsoft.net/utils/blue_screen_view.html told me), I usually give up finding the root cause by using the dump file and start to analyse what the machine was doing while it bluescreened.

But first of all make sure that it's no simple RAM corruption. Exchange your RAM if you own spare RAM. If not, test it at least.