joeyballs05
New Member
- Messages
- 2
Its been 10 days since my last Bsod but they havent been happening frequently enough for me to worry but here are all of them in a nutshell...can someone help me fix all these?
[FONT=Segoe UI, Arial]On Wed 10/16/2013 12:07:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101513-14671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x3D (0xFFFFF803B673BEC0, 0x0, 0x0, 0xFFFFF803B7B176F8)
Error: [FONT=Segoe UI, Arial]INTERRUPT_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Wed 10/16/2013 12:07:07 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal!HalSetTimeIncrement+0x3F8A)
Bugcheck code: 0x3D (0xFFFFF803B673BEC0, 0x0, 0x0, 0xFFFFF803B7B176F8)
Error: [FONT=Segoe UI, Arial]INTERRUPT_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check appears very infrequently.
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 10/6/2013 7:24:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-11062-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801EB2F2A4D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]e1d63x64.sys[/FONT] (e1d63x64+0x2433E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80236024EB5, 0x1, 0x3E9E50C4D)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\e1d63x64.sys
product: [FONT=Segoe UI, Arial]Intel(R) Gigabit Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Intel Corporation[/FONT]
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: [FONT=Segoe UI, Arial]Intel Corporation KMODE_EXCEPTION_NOT_HANDLED[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Wed 10/16/2013 12:07:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101513-14671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x3D (0xFFFFF803B673BEC0, 0x0, 0x0, 0xFFFFF803B7B176F8)
Error: [FONT=Segoe UI, Arial]INTERRUPT_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Wed 10/16/2013 12:07:07 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal!HalSetTimeIncrement+0x3F8A)
Bugcheck code: 0x3D (0xFFFFF803B673BEC0, 0x0, 0x0, 0xFFFFF803B7B176F8)
Error: [FONT=Segoe UI, Arial]INTERRUPT_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check appears very infrequently.
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.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 10/6/2013 7:24:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-11062-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801EB2F2A4D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]e1d63x64.sys[/FONT] (e1d63x64+0x2433E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80236024EB5, 0x1, 0x3E9E50C4D)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\e1d63x64.sys
product: [FONT=Segoe UI, Arial]Intel(R) Gigabit Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Intel Corporation[/FONT]
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: [FONT=Segoe UI, Arial]Intel Corporation KMODE_EXCEPTION_NOT_HANDLED[/FONT]
[/FONT]
My Computer
System One
-
- OS
- Windows 8 64 Bit