Hi there,
I've been having BSOD issues with my pc and its making me going crazy as the whocrashed software is telling me its different problems. I've also done a memory test and it says the memory is fine.
I do hear the fans pretty loud on the machine so not sure if the components are over heating.
Any suggestions or advice would be greatly appreciated as I've had about 38 blue screens of death now and cant take any more :S
I have attached below the results from Whocrashed.
Many Thanks
Stuart
On Mon 14/04/2014 20:28:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041414-11325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 14/04/2014 17:05:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041414-11918-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x38B71)
Bugcheck code: 0xA (0x34, 0x2, 0x1, 0xFFFFF80002ED83C7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
On Sat 12/04/2014 14:42:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041214-17144-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x2BBBE9, 0x2, 0x0, 0xFFFFF80002E8291B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 that cannot be identified at this time.
On Fri 11/04/2014 15:04:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041114-16785-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15565)
Bugcheck code: 0xD1 (0x18, 0x2, 0x1, 0xFFFFF8800729B565)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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 that cannot be identified at this time.
On Tue 08/04/2014 16:18:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-10857-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88003089180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 Tue 08/04/2014 16:00:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-72758-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 Tue 08/04/2014 15:44:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-11107-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 Tue 08/04/2014 11:50:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-10717-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002EE3440, 0xFFFFF8800CA20E90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 09/03/2014 21:14:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-35069-01.dmp
This was probably caused by the following module: sandra.sys (Sandra+0x26BB)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF880097F56BB, 0xFFFFF8800A40EE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: sandra.sys .
Google query: sandra.sys SYSTEM_SERVICE_EXCEPTION
On Sun 09/03/2014 21:12:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-51277-01.dmp
This was probably caused by the following module: sandra.sys (Sandra+0x26BB)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF880095D66BB, 0xFFFFF8800C6FCE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: sandra.sys .
Google query: sandra.sys SYSTEM_SERVICE_EXCEPTION
I've been having BSOD issues with my pc and its making me going crazy as the whocrashed software is telling me its different problems. I've also done a memory test and it says the memory is fine.
I do hear the fans pretty loud on the machine so not sure if the components are over heating.
Any suggestions or advice would be greatly appreciated as I've had about 38 blue screens of death now and cant take any more :S
I have attached below the results from Whocrashed.
Many Thanks
Stuart
On Mon 14/04/2014 20:28:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041414-11325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 14/04/2014 17:05:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041414-11918-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x38B71)
Bugcheck code: 0xA (0x34, 0x2, 0x1, 0xFFFFF80002ED83C7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL
On Sat 12/04/2014 14:42:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041214-17144-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x2BBBE9, 0x2, 0x0, 0xFFFFF80002E8291B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 that cannot be identified at this time.
On Fri 11/04/2014 15:04:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041114-16785-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15565)
Bugcheck code: 0xD1 (0x18, 0x2, 0x1, 0xFFFFF8800729B565)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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 that cannot be identified at this time.
On Tue 08/04/2014 16:18:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-10857-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88003089180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 Tue 08/04/2014 16:00:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-72758-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 Tue 08/04/2014 15:44:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-11107-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
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 Tue 08/04/2014 11:50:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-10717-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002EE3440, 0xFFFFF8800CA20E90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 09/03/2014 21:14:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-35069-01.dmp
This was probably caused by the following module: sandra.sys (Sandra+0x26BB)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF880097F56BB, 0xFFFFF8800A40EE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: sandra.sys .
Google query: sandra.sys SYSTEM_SERVICE_EXCEPTION
On Sun 09/03/2014 21:12:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-51277-01.dmp
This was probably caused by the following module: sandra.sys (Sandra+0x26BB)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF880095D66BB, 0xFFFFF8800C6FCE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: sandra.sys .
Google query: sandra.sys SYSTEM_SERVICE_EXCEPTION
Facebook
Twitter
Instagram