- Mar 8, 2015
- 1
- 0
- 4,510
My PC keeps crashing with BSD "Kernel_Data_Inpage_Error" or "Reboot & Select Proper Boot Device" messages.
I've run WhoCrashed and it displays the following, any ideas what is wrong?
On Thu 08/01/2015 10:44:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010815-22526-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00658C5A0, 0xFFFFF8A00658C800, 0x5260304)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Thu 08/01/2015 10:44:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x28523)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00658C5A0, 0xFFFFF8A00658C800, 0x5260304)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 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.
There have been crashes since Thursday, so not sure why it has chosen only Thursday.
I've run WhoCrashed and it displays the following, any ideas what is wrong?
On Thu 08/01/2015 10:44:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010815-22526-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00658C5A0, 0xFFFFF8A00658C800, 0x5260304)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Thu 08/01/2015 10:44:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x28523)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00658C5A0, 0xFFFFF8A00658C800, 0x5260304)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 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.
There have been crashes since Thursday, so not sure why it has chosen only Thursday.
Facebook
Twitter
Instagram