BSOD and computer restarting Automatically

There are practically two reasons of the crash .....

Broadcom 802.11g Network Adapter driver.

Code:

fffff800`00b9ca30  fffff880`05880824Unable to load image \SystemRoot\system32\DRIVERS\bcmwl664.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
 bcmwl664+0x14824

And ELAN PS/2 Port Smart Pad driver.

Code:

fffff800`00b9c918  fffff880`05da3181Unable to load image \SystemRoot\system32\DRIVERS\ETD.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ETD.sys
*** ERROR: Module load completed but symbols could not be loaded for ETD.sys
 ETD+0x4181

Both of them are OEM, no updates are available in the sites.

Either you try to have a BIOS update, or , if you are within warranty, contract Samsung.

For the time being, you may look that the display driver is very old.

Code:

lmvm igdkmd64
start             end                 module name
fffff880`04a4e000 fffff880`055fe500   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Fri Dec 17 07:09:01 2010 (4D0ABF35)
    CheckSum:         00BBFA26
    ImageSize:        00BB0500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Intel Download Center.

It's a bit different ....

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80006ed3104, 8, fffff80006ed3104, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!NtUserQueryWindow+1c )

Followup: MachineOwner
---------

Better you contract the vendor, as we know what is the issue already present.