Computer gets this BSOD randomly and will shut down.
its a dell dimension 9200c running Vista 32 bit. Its been happening for a very long time
please help . thanks
System Information (local)
--------------------------------------------------------------------------------
computer name: DIMENSION
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 CPU 6700 @ 2.66GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3209908224 total
VM: 2147352576, free: 1967325184
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 15/09/2012 10:03:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091512-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFFFFF822C3022)
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 Sat 15/09/2012 10:03:02 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x2971)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFFFFF822C3022)
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 Fri 14/09/2012 4:04:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091412-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x3597)
Bugcheck code: 0xD1 (0x5EEFA60, 0x2, 0x1, 0xFFFFFFFF8F4B2597)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 Sun 26/08/2012 7:42:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082612-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x293F2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F6E43F2, 0xFFFFFFFFC190BBD8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Wed 08/06/2011 12:34:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FD64)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0047000, 0x1, 0xFFFFFFFF85FFA190)
Error: MEMORY_MANAGEMENT
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 09/11/2010 2:51:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110810-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FDB4)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0064000, 0x1, 0xFFFFFFFF86E98FC0)
Error: MEMORY_MANAGEMENT
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 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:
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.
Edited by dynocompe, 15 September 2012 - 06:07 PM.
Sign In
Create Account
