Inspiron 1440 + Corsair DDR2 800mhz stick = BSOD
Inspiron 1440
dual core t4400 win7 home premium
originally 2gb ram
I bought corsair 2 x 2gb ddr2 800mhz pack for it: VS4GSDSKIT800D2 G
removed 2x1gb sticks. installed the corsair and it blue screened almost instantly.
running whocrashed analyzed the dumps and its conclusion was:
On your computer a total of 47 crash dumps have been found. Only 45 could be analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
I don't believe it. I did try to change the drivers. I loaded an older driver from Dell's site. (the current driver was the most recent). Didnt help. I also reverted back to an older MS driver. Didnt help.
Putting old memory back in and it's fine. Testing new memory 1 stick at a time I find that one stick is fine, the second one blue screens me almost right away, in either memory slot.
.
The latest error reported : BCCode: be
I ran Dell's "Diagnostics" and let it scan through the memory for over an hour. No errors
==========================
Here are the whocrashed dump analyses:
On Wed 5/30/2012 12:52:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053012
This was probably caused by the following module: ndis.sys (ndis+0x56160)
Bugcheck code: 0xBE (0xFFFFF88001470160, 0x8000000003FB0121, 0xFFFFF80000B9C290, 0xA)
Error: ATTEMPTED_WRITE_TO_READONL
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Wed 5/30/2012 12:52:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisIfAllocateNetLui
Bugcheck code: 0xBE (0xFFFFF88001470160, 0x8000000003FB0121, 0xFFFFF80000B9C290, 0xA)
Error: ATTEMPTED_WRITE_TO_READONL
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Wed 5/30/2012 1:17:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x1, 0xFFFFF80003091EA2, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_ARE
file path: C:\Windows\system32\ntoskr
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 5/30/2012 1:08:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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 5/30/2012 12:58:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000308F8E0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskr
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.
On Mon 5/14/2012 9:02:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x74ED85EA, 0xD, 0x1, 0xFFFFF800030A6A0C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskr
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.
On Mon 5/14/2012 9:00:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ndis.sys (ndis+0x1EEF)
Bugcheck code: 0xBE (0xFFFFF80003116C20, 0x3116121, 0xFFFFF80000B9C6A0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONL
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Mon 5/14/2012 8:58:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF80017F0E7CA, 0xD, 0x1, 0xFFFFF8000308E7A3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskr
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.
On Mon 5/14/2012 8:56:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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 Mon 5/14/2012 8:04:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x74DE5)
Bugcheck code: 0xA (0xFFFFF8010324D410, 0x2, 0x1, 0xFFFFF800030E1B02)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\driver
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: bcmwl664.sys Broadcom Corporation IRQL_NOT_LESS_OR_EQUAL
On Fri 5/11/2012 11:02:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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 5/11/2012 10:58:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF80000B9C0A0, 0x0, 0x0, 0xFFFFF800030889F9)
Error: INTERRUPT_EXCEPTION_NOT_HA
file path: C:\Windows\system32\ntoskr
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
On Fri 5/11/2012 10:54:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: tcpip.sys (tcpip+0x3A4C6)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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.
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 which cannot be identified at this time.
On Fri 5/11/2012 10:46:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000FECBDB, 0x1, 0xFFFFF800030945C3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_ARE
file path: C:\Windows\system32\ntoskr
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 5/11/2012 10:26:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\051412
C:\Windows\Minidump\051412
dual core t4400 win7 home premium
originally 2gb ram
I bought corsair 2 x 2gb ddr2 800mhz pack for it: VS4GSDSKIT800D2 G
removed 2x1gb sticks. installed the corsair and it blue screened almost instantly.
running whocrashed analyzed the dumps and its conclusion was:
On your computer a total of 47 crash dumps have been found. Only 45 could be analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
I don't believe it. I did try to change the drivers. I loaded an older driver from Dell's site. (the current driver was the most recent). Didnt help. I also reverted back to an older MS driver. Didnt help.
Putting old memory back in and it's fine. Testing new memory 1 stick at a time I find that one stick is fine, the second one blue screens me almost right away, in either memory slot.
.
The latest error reported : BCCode: be
I ran Dell's "Diagnostics" and let it scan through the memory for over an hour. No errors
==========================
Here are the whocrashed dump analyses:
On Wed 5/30/2012 12:52:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053012
This was probably caused by the following module: ndis.sys (ndis+0x56160)
Bugcheck code: 0xBE (0xFFFFF88001470160, 0x8000000003FB0121, 0xFFFFF80000B9C290, 0xA)
Error: ATTEMPTED_WRITE_TO_READONL
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Wed 5/30/2012 12:52:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisIfAllocateNetLui
Bugcheck code: 0xBE (0xFFFFF88001470160, 0x8000000003FB0121, 0xFFFFF80000B9C290, 0xA)
Error: ATTEMPTED_WRITE_TO_READONL
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Wed 5/30/2012 1:17:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x1, 0xFFFFF80003091EA2, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_ARE
file path: C:\Windows\system32\ntoskr
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 5/30/2012 1:08:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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 5/30/2012 12:58:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000308F8E0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskr
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.
On Mon 5/14/2012 9:02:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x74ED85EA, 0xD, 0x1, 0xFFFFF800030A6A0C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskr
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.
On Mon 5/14/2012 9:00:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ndis.sys (ndis+0x1EEF)
Bugcheck code: 0xBE (0xFFFFF80003116C20, 0x3116121, 0xFFFFF80000B9C6A0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONL
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Mon 5/14/2012 8:58:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF80017F0E7CA, 0xD, 0x1, 0xFFFFF8000308E7A3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskr
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.
On Mon 5/14/2012 8:56:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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 Mon 5/14/2012 8:04:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x74DE5)
Bugcheck code: 0xA (0xFFFFF8010324D410, 0x2, 0x1, 0xFFFFF800030E1B02)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\driver
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: bcmwl664.sys Broadcom Corporation IRQL_NOT_LESS_OR_EQUAL
On Fri 5/11/2012 11:02:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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 5/11/2012 10:58:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF80000B9C0A0, 0x0, 0x0, 0xFFFFF800030889F9)
Error: INTERRUPT_EXCEPTION_NOT_HA
file path: C:\Windows\system32\ntoskr
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
On Fri 5/11/2012 10:54:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: tcpip.sys (tcpip+0x3A4C6)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\driver
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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.
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 which cannot be identified at this time.
On Fri 5/11/2012 10:46:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000FECBDB, 0x1, 0xFFFFF800030945C3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_ARE
file path: C:\Windows\system32\ntoskr
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 5/11/2012 10:26:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLE
file path: C:\Windows\system32\ntoskr
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\051412
C:\Windows\Minidump\051412
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Corsair is shipping me new memory. I'll see if I can remember to update the post with the results afterward. They were very easy to deal with. No hassles.
Here's the point breakdown:
remmett70 150 for first answer
callandor 100 for second
kadafitcd 75 for 3rd
wakeup 25 for "me too"
darr247 50 for adding a useful link and info
wakeup 75 for additional useful info
remmett70 25 for followup
It's somewhat arbitrary but I tried to be fair
Here's the point breakdown:
remmett70 150 for first answer
callandor 100 for second
kadafitcd 75 for 3rd
wakeup 25 for "me too"
darr247 50 for adding a useful link and info
wakeup 75 for additional useful info
remmett70 25 for followup
It's somewhat arbitrary but I tried to be fair
ASKER
- if all of Dell's memory tests came up negative, is it *really * a bad stick of RAM?
-Is there another possibility?
-And does the BSOD point to that.
I'll take it from all your responses the answer is "yes, no and no".