Hi Happyrock,
Thanks for the quick reply, I haven't had chance to download and run memtest86 as I do not have any blank CD's. When I get some I will sort this out. On the specification page of the Dell e520 site it says that the 2gb (2x1gb DDR2 800MHz --> both of which are the same speed and manufacturer) of ram is compatible (and as a double check offer this ram as a compatible upgrade on their site.
Initially I did have 3gb (2x1gb and 2x 512mb) which were at different speeds - but have removed to slower 512's and have only had 1 BSOD since doing this.
Below is the WhoCrashed Report:
System Information (local)
--------------------------------------------------------------------------------
computer name: JAMES-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 CPU 4300 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145300480 total
VM: 2147352576, free: 1982144512
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 04/03/2012 19:02:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-21013-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415FB)
Bugcheck code: 0xA (0x76CE0, 0x2, 0x1, 0xFFFFFFFF82AA4CC0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.
On Sun 04/03/2012 19:02:41 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29D3)
Bugcheck code: 0xA (0x76CE0, 0x2, 0x1, 0xFFFFFFFF82AA4CC0)
Error: IRQL_NOT_LESS_OR_EQUAL
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Sun 04/03/2012 12:25:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-25412-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEEF4)
Bugcheck code: 0x4E (0x2, 0x8D74D, 0xBFE50, 0x3)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 04/03/2012 10:58:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-22744-01.dmp
This was probably caused by the following module: symevent.sys (SYMEVENT+0x1708F)
Bugcheck code: 0x1A (0x8884, 0xFFFFFFFF84854EE8, 0xFFFFFFFF848BE5CC, 0x502)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\symevent.sys
product: SYMEVENT
company: Symantec Corporation
description: Symantec Event Library
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: symevent.sys (Symantec Event Library, Symantec Corporation).
Google query: symevent.sys Symantec Corporation MEMORY_MANAGEMENT
On Fri 02/03/2012 23:35:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-29078-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x92F30)
Bugcheck code: 0x4E (0x7, 0x7047A, 0xAB0D9, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 02/03/2012 23:17:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-42073-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415FB)
Bugcheck code: 0xA (0x2B, 0x2, 0x1, 0xFFFFFFFF82AB5E74)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.
On Thu 01/03/2012 07:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030112-21028-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415FB)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFEC, 0x2, 0x1, 0xFFFFFFFF82ADEF1B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.
On Wed 29/02/2012 13:19:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022912-37658-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x98BD0)
Bugcheck code: 0x4E (0x1, 0xFFFFFFFF82B7A3A8, 0x6CE2D, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 29/02/2012 01:38:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022912-20872-01.dmp
This was probably caused by the following module: symevent.sys (SYMEVENT+0x1708F)
Bugcheck code: 0x1A (0x8884, 0xFFFFFFFF84854EE8, 0xFFFFFFFF84B66500, 0x502)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\symevent.sys
product: SYMEVENT
company: Symantec Corporation
description: Symantec Event Library
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: symevent.sys (Symantec Event Library, Symantec Corporation).
Google query: symevent.sys Symantec Corporation MEMORY_MANAGEMENT
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 crash dumps have been found and analyzed. 2 third party drivers have 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:
symevent.sys (Symantec Event Library, Symantec Corporation)
ntkrpamp.exe
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
----------------------------------------------------------------------------------------------------------------
Also here is the specification of my initial machine before I updated some components:
E520 SpecIs it possible for a PSU failure to cause these errors?
Thank you once again for the reply
James
Edited by obrien.james, 05 March 2012 - 01:18 PM.
Sign In
Create Account
