Computer Hope
Microsoft => Microsoft Windows => Windows 8 => Topic started by: joey657 on October 06, 2013, 12:57:34 PM
-
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
-
What 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 reply
-
to be honest it happend once before the first time ever after 2 days but i have not changed anything at all...
-
to be honest it happend once before the first time ever after 2 days
I don't understand what you said.
-
JUST HAPPEND AGAIN
==================================================
Dump File : 100613-11062-01.dmp
Crash Time : 10/6/2013 3:24:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff801`eb2f2a4d
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16628 (win8_gdr.130531-1504)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100613-11062-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9200
Dump File Size : 296,656
Dump File Time : 10/6/2013 3:25:26 PM
==================================================
==================================================
Dump File : 100613-10109-01.dmp
Crash Time : 10/6/2013 2:39:03 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff802`36024eb5
Parameter 3 : 00000000`00000001
Parameter 4 : 00000003`e9e50c4d
Caused By Driver : hal.dll
Caused By Address : hal.dll+1feb5
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16442 (win8_gdr.121023-1503)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100613-10109-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9200
Dump File Size : 296,664
Dump File Time : 10/6/2013 2:39:45 PM
==================================================
-
1) You said you just purchased it. How long have you been using it before you got the errors?
2) Check in device manager - are there any yellow or red symbols?
3) Have you updated any drivers?
4) What type of computer is it (make & model)? Go to either the website of your computer manufacturer or here (http://www.intel.com/support/network/sb/cs-006120.htm (http://www.intel.com/support/network/sb/cs-006120.htm)) and download and install the latest driver for your Intel Network Adapter.
4) Are you doing anything specific when the bsod's occur or can they happen if the system is just sitting idle?
-
i used it for 2 days before i got the first error then went 3 weeks until today...i have been getting them the most...4 in 2 hours...
no yellow or red symbols in device manager
have not updated anything
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
im usually surfing the web when it happens randomly...the first time it ever happend the system was just sitting randomly idle
-
Ok i just purchased a new desktop and have had 2 blue screen of death issues in the last 20 minutes...
Provided "just" <= "warranty period", then claim. Don't mess about wasting time, because you will have to eventually.
-
I don't disagree with the above post. Try exchanging it under warranty. If you haven't made any changes and aren't doing anything unusual, you shouldn't be getting those bsod's.
-
...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".
-
http://us.acer.com/ac/en/US/content/model/DT.SPXAA.001 (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".
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.
-
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.
-
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.
+1...
-
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.
It might be, but doesn't get reported & show up on Google.
I've been "fixing" several neighbor's new computers & the culprits have been preinstalled bloatware. Without going into details, it's just unbelievable how much stuff is installed that doesn't work or conflicts, i.e., multiple AV's. The retailer attempted to install & it failed. Sold it anyway, as is. Had to perform a PC Recovery, with internet disconnected, then uninstall all the junk before it tries to auto-update.
-
He should take it back.
-
I agree, take it back. I pleaded with my neighbor to do the same, & they refused to do so.