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.

HelpppWhat is new or different since the last time everything WORKED properly (ie, new hw, new sw, virus, error, etc)?

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is DONE, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next replyto be honest it happend once before the first time ever after 2 days but i have not changed anything at all...Quote from: joey657 on October 06, 2013, 01:18:45 PM

to be honest it happend once before the first time ever after 2 days

Ok i just purchased a new desktop and have had 2 blue screen of death issues in the last 20 minutes...

...im using a Acer Predator AG3-605-UR20 Desktop...ive tried to look for the model on the acer website and this model doesnt exist there...

http://us.acer.com/ac/en/US/content/model/DT.SPXAA.001

Can't find any support for the 605. Only can find the overview. Try entering your serial number. For the $1500, support should be a lot better. Live & learn: Acer support is marginal.

I suspect some of the crapware they install is the root cause. Need a list of the preinstalled apps, such as Norton Security Suite, etc. I see it might have something called "AcerCloud".

If a $1500 computer I "just" bought was heading up the Swanee I'd be exercising my warranty rights. I wouldn't be trying to put it right. Period. Actually if it was a $50 computer too.

Not to disagree CC - I always respect your diagnoses & suggestions - but I'd think if it was something installed by the manufacturer it would be a widespread problem. Based on the info provided it points to the Intel Network adapter. But sure, there could be some conflicting apps, etc. Best way to find out would be a clean boot - however, as ST points out since this is a new computer these problems shouldn't be occurring at all and returning it under warranty is not a bad idea.