- Apr 20, 2012
- 42
- 0
- 18,530
I seem to be getting a lot of BSOD at the moment with my new system and just wanted to know if you guys would take a look at them and see if you can help me at all,
On Sun 20/05/2012 21:14:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0xB, 0x8, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 20/05/2012 18:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
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 which cannot be identified at this time.
On Sun 20/05/2012 13:28:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16333-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB545)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000EB545, 0xFFFFF8800C2F2B70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 which cannot be identified at this time.
On Sun 20/05/2012 13:10:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16239-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
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 which cannot be identified at this time.
On Thu 17/05/2012 14:06:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051712-16598-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880033BCB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 Tue 15/05/2012 14:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051512-16442-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF8800334AB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 13/05/2012 22:40:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051312-15537-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880033BCB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 13/05/2012 17:34:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051312-17986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800569D150, 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 which cannot be identified at this time.
I've had several more crashes, some just where my PC restarts with no BSOD and some BSOD that are not in the crash dump file. The crashes happen when doing almost anything from typing in MSO, playing BF3/D3, listening to music, watching videos on YouTube and just other general web browsing. So if anyone has any ideas I'm open to them. I have re installed windows because when I first installed it and let my motherboard disk install everything I got constant BSOD. I later found it to be the utilities on the Motherboard disk that were causing this issue so haven’t installed them since (is this normal or does my motherboard have a problem?).
Thanks,
On Sun 20/05/2012 21:14:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0xB, 0x8, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 20/05/2012 18:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
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 which cannot be identified at this time.
On Sun 20/05/2012 13:28:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16333-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB545)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000EB545, 0xFFFFF8800C2F2B70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 which cannot be identified at this time.
On Sun 20/05/2012 13:10:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16239-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
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 which cannot be identified at this time.
On Thu 17/05/2012 14:06:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051712-16598-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880033BCB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 Tue 15/05/2012 14:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051512-16442-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF8800334AB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 13/05/2012 22:40:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051312-15537-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880033BCB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 13/05/2012 17:34:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051312-17986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800569D150, 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 which cannot be identified at this time.
I've had several more crashes, some just where my PC restarts with no BSOD and some BSOD that are not in the crash dump file. The crashes happen when doing almost anything from typing in MSO, playing BF3/D3, listening to music, watching videos on YouTube and just other general web browsing. So if anyone has any ideas I'm open to them. I have re installed windows because when I first installed it and let my motherboard disk install everything I got constant BSOD. I later found it to be the utilities on the Motherboard disk that were causing this issue so haven’t installed them since (is this normal or does my motherboard have a problem?).
Thanks,
Facebook
Twitter
Instagram