i've been getting various bsod errors on my computer, mostly occuring whilst gaming or playing video. The screen starts to freeze, the sound stutters and then it blue screens. I downloaded Whocrashed to try and help identify the problem and this is the post scan analysis it produced :
System Information (local)
--------------------------------------------------------------------------------
computer name: HOME-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X2 215 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 2951270400 total
VM: 2147352576, free: 1941094400
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 03/04/2012 12:37:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-26582-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA807908CCC0, 0x0, 0xFFFFF80002EC21B5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Tue 03/04/2012 12:37:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA807908CCC0, 0x0, 0xFFFFF80002EC21B5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 24/02/2012 12:25:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022412-29983-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41284, 0x49DE4001, 0x300D1C0, 0xFFFFF70001080000)
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 Thu 17/11/2011 20:40:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111711-20779-01.dmp
This was probably caused by the following module: storport.sys (storport+0x59B00)
Bugcheck code: 0x7A (0xFFFFF6FC40008500, 0xFFFFFFFFC000000E, 0x6BD39860, 0xFFFFF880010A0B00)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 06/11/2011 20:16:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110611-21808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 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 02/11/2011 20:46:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-14913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
System Information (local)
--------------------------------------------------------------------------------
computer name: HOME-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X2 215 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 2951270400 total
VM: 2147352576, free: 1941094400
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 03/04/2012 12:37:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-26582-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA807908CCC0, 0x0, 0xFFFFF80002EC21B5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Tue 03/04/2012 12:37:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA807908CCC0, 0x0, 0xFFFFF80002EC21B5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 24/02/2012 12:25:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022412-29983-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41284, 0x49DE4001, 0x300D1C0, 0xFFFFF70001080000)
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 Thu 17/11/2011 20:40:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111711-20779-01.dmp
This was probably caused by the following module: storport.sys (storport+0x59B00)
Bugcheck code: 0x7A (0xFFFFF6FC40008500, 0xFFFFFFFFC000000E, 0x6BD39860, 0xFFFFF880010A0B00)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 06/11/2011 20:16:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110611-21808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 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 02/11/2011 20:46:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-14913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
