New
#11
well i spoke to soon i've had 4 BSOD since last night
those are the crash reports filtered through WhoCrashed Home EditionCode:On Fri 27/05/2011 18:51:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\052711-17238-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880086F61A0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 which cannot be identified at this time. On Fri 27/05/2011 18:51:20 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: l1e62x64.sys (L1E62x64+0x78DC) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880086F61A0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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: l1e62x64.sys (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros Communications, Inc.). Google query: l1e62x64.sys Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED On Fri 27/05/2011 06:54:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\052711-15116-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880046231A0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 which cannot be identified at this time. On Fri 27/05/2011 01:31:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\052711-15412-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880016D0C1E) Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 which cannot be identified at this time. On Thu 26/05/2011 21:43:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\052611-20607-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88008A0F1A0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 which cannot be identified at this time. On Thu 26/05/2011 03:23:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\052611-17206-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006430FB0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 which cannot be identified at this time. On Wed 25/05/2011 03:50:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\052511-15678-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70700) Bugcheck code: 0xA (0xFFFFFA8009D578E0, 0x2, 0x0, 0xFFFFF800033EB3DA) 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 which cannot be identified at this time.
now i did the update to the Atheros driver so i don't know whats going on there
Quote