My friend is having big issues with his computer and absolutely nothing helped so far (it's been years already) so now we found this program that analyses crashdumps and we hope this can shed some new light on this.
FYI: His computer gets BLODs randomly with no noticable indications, doesn't matter if it's idle or stressed out by games.
Here's the analysed report from WhoCrashed:
System Information (local)
computer name: XXXXXXXX
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A77D
CPU: AuthenticAMD AMD Phenom(tm) 8450 Triple-Core Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 4294103040 total
VM: 2147352576, free: 1986625536
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 03.02.2014 20:30:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-26691-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x5B009)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600008B009, 0xFFFFF880071FBAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Mon 03.02.2014 20:30:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngBitBlt+0x25F79)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600008B009, 0xFFFFF880071FBAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Mon 03.02.2014 20:22:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-22978-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003579A50, 0xFFFF, 0x0)
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 that cannot be identified at this time.
On Mon 03.02.2014 20:12:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-19078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800514DB30, 0xFFFFFA800514DE10, 0xFFFFF80002B88240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 03.02.2014 20:01:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-16473-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8004E27B60, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_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 thread in a device driver is endlessly spinning.
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 that cannot be identified at this time.
On Mon 03.02.2014 19:57:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-17472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x5005, 0xFFFFF70001080000, 0x0, 0x2DA)
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 that cannot be identified at this time.
On Sun 02.02.2014 20:04:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-17908-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004A346A8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 02.02.2014 20:02:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-17830-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Thu 30.01.2014 21:45:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-22448-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x24E229)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002CE229, 0xFFFFF88003AC3E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Thu 30.01.2014 21:06:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-25474-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000084386)
Bugcheck code: 0x50 (0xFFFFFF2003793EF0, 0x0, 0xFFFFF96000084386, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
10 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.
The computer has been set up from scratch several times, it was wiped completely, Anti-virus softwares have been tested. Ram was tested, too. Currently the whole system runs on default windows drivers (but all drivers have been updated before, didn't help)
Any help would be appreciated.
FYI: His computer gets BLODs randomly with no noticable indications, doesn't matter if it's idle or stressed out by games.
Here's the analysed report from WhoCrashed:
System Information (local)
computer name: XXXXXXXX
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A77D
CPU: AuthenticAMD AMD Phenom(tm) 8450 Triple-Core Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 4294103040 total
VM: 2147352576, free: 1986625536
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 03.02.2014 20:30:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-26691-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x5B009)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600008B009, 0xFFFFF880071FBAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Mon 03.02.2014 20:30:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngBitBlt+0x25F79)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600008B009, 0xFFFFF880071FBAA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Mon 03.02.2014 20:22:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-22978-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003579A50, 0xFFFF, 0x0)
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 that cannot be identified at this time.
On Mon 03.02.2014 20:12:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-19078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800514DB30, 0xFFFFFA800514DE10, 0xFFFFF80002B88240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 03.02.2014 20:01:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-16473-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8004E27B60, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_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 thread in a device driver is endlessly spinning.
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 that cannot be identified at this time.
On Mon 03.02.2014 19:57:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-17472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x5005, 0xFFFFF70001080000, 0x0, 0x2DA)
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 that cannot be identified at this time.
On Sun 02.02.2014 20:04:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-17908-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004A346A8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 02.02.2014 20:02:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-17830-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Thu 30.01.2014 21:45:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-22448-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x24E229)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002CE229, 0xFFFFF88003AC3E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Thu 30.01.2014 21:06:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-25474-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000084386)
Bugcheck code: 0x50 (0xFFFFFF2003793EF0, 0x0, 0xFFFFF96000084386, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
10 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.
The computer has been set up from scratch several times, it was wiped completely, Anti-virus softwares have been tested. Ram was tested, too. Currently the whole system runs on default windows drivers (but all drivers have been updated before, didn't help)
Any help would be appreciated.
Facebook
Twitter
Instagram