Hey guys, In May 2012 i completed my first build:
Motherboard - Gigabyte Z77 DS3H (rev 1.0)
CPU - i5 3570k w/ Arctic Freezer Pro 7
GPU - VTX3D 7870 Tahiti LE Edition 2GB
SSD - Samsung 840 Series 120GB
HDD - Seagate Barracuda 1TB Sata3
Ram - Ballistix 8GB 1600 Mhz
OS - Windows 8 64 Bit
However I have been experiencing BSOD's pretty much from the beginning, at first I passed them off as random crashes and rebuilt from scratch. I have even swapped onto Windows 7 and still experience the BSOD's. It appeared to be ntoskrnl.exe that is causing the large majority of the crashes.
I was just wondering if anybody could help me with this as its beginning to make me tear my hair out.
Thanks in advance
UPDATE
some of the whocrashed reports:
On Sun 15/09/2013 18:52:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-9484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0xFFFFF683FE2B6B20, 0x0, 0x0, 0xFFFFF80047B3DAED)
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 Sun 15/09/2013 18:26:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-12546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x4E (0x99, 0x15E4B9, 0x2, 0xE0001500015E4B8)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 15/09/2013 00:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-10812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFFA8007906E60, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
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.
Motherboard - Gigabyte Z77 DS3H (rev 1.0)
CPU - i5 3570k w/ Arctic Freezer Pro 7
GPU - VTX3D 7870 Tahiti LE Edition 2GB
SSD - Samsung 840 Series 120GB
HDD - Seagate Barracuda 1TB Sata3
Ram - Ballistix 8GB 1600 Mhz
OS - Windows 8 64 Bit
However I have been experiencing BSOD's pretty much from the beginning, at first I passed them off as random crashes and rebuilt from scratch. I have even swapped onto Windows 7 and still experience the BSOD's. It appeared to be ntoskrnl.exe that is causing the large majority of the crashes.
I was just wondering if anybody could help me with this as its beginning to make me tear my hair out.
Thanks in advance
UPDATE
some of the whocrashed reports:
On Sun 15/09/2013 18:52:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-9484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0xFFFFF683FE2B6B20, 0x0, 0x0, 0xFFFFF80047B3DAED)
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 Sun 15/09/2013 18:26:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-12546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x4E (0x99, 0x15E4B9, 0x2, 0xE0001500015E4B8)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 15/09/2013 00:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-10812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFFA8007906E60, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
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.
Facebook
Twitter
Instagram