Ok i just purchased a new desktop and have had 2 blue screen of death issues in the last 20 minutes...they are as followed...
On Sun 10/6/2013 6:39:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-10109-01.dmp
This was probably caused by the following module: e1d63x64.sys (e1d63x64+0x2433E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80236024EB5, 0x1, 0x3E9E50C4D)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\e1d63x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1d63x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
On Sun 10/6/2013 6:39:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSetTimeIncrement+0xF75)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80236024EB5, 0x1, 0x3E9E50C4D)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Helppp