I seem to have Random BSOD Mini dumps now ive updated me networkcard but in not even sure that was my problem. i got who crashed and this is what is said
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 4/25/2013 1:58:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-67642-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA80FF61F9A8, 0x2, 0x0, 0xFFFFF80002F3D1CB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
On Thu 4/25/2013 1:58:34 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: l1e62x64.sys (L1E62x64+0x76B8)
Bugcheck code: 0xA (0xFFFFFA80FF61F9A8, 0x2, 0x0, 0xFFFFF80002F3D1CB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\l1e62x64.sys
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
company: Atheros Communications, Inc.
description: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: l1e62x64.sys (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. IRQL_NOT_LESS_OR_EQUAL
On Sun 3/17/2013 9:10:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031713-53461-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002E1F3DA)
Bugcheck code: 0xA (0xFFFFFA800E58FF68, 0x2, 0x0, 0xFFFFF80002E1F3DA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
now most of this is gibberish to me so im hopping someone can help me.
oh and im running win 7 64-bit if that matters
really no one can help T_T
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 4/25/2013 1:58:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-67642-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA80FF61F9A8, 0x2, 0x0, 0xFFFFF80002F3D1CB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
On Thu 4/25/2013 1:58:34 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: l1e62x64.sys (L1E62x64+0x76B8)
Bugcheck code: 0xA (0xFFFFFA80FF61F9A8, 0x2, 0x0, 0xFFFFF80002F3D1CB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\l1e62x64.sys
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
company: Atheros Communications, Inc.
description: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: l1e62x64.sys (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. IRQL_NOT_LESS_OR_EQUAL
On Sun 3/17/2013 9:10:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031713-53461-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002E1F3DA)
Bugcheck code: 0xA (0xFFFFFA800E58FF68, 0x2, 0x0, 0xFFFFF80002E1F3DA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
now most of this is gibberish to me so im hopping someone can help me.
oh and im running win 7 64-bit if that matters
really no one can help T_T