Hello everyone,
I recently did a fresh install of windows on my XPS 9560 to get rid of bloatware.
I have done every single driver update through Windows Update, went to device manager and updated every device individually to be sure. I have nvida drivers for the gtx 1050.
Since formatting, I am constantly and randomly getting BSODs:
BAD POOL HEADER
IRQL NOT LESS OR EQUAL
These two are the main crashes I get, although there may have been another one.
I've done windos memtest and used another program.
I'm not overclocking, everything is stock.
I've undervolted the CPU but this hasn't changed anything.
Comparatively, I've done the same thing to my other dell XPS 9343 and there are no issues whatsoever.
I never had problems before the clean install. I've had dozens of BSODs but only these recent dump files remain.
http://www.mediafire.com/file/x2a2k8cn0iqab7r/060318-14718-01.dmp/file
http://www.mediafire.com/file/ya67hr87vna40a5/060418-15531-01.dmp/file
http://www.mediafire.com/file/5iha2sqvsr8zsor/060418-15687-01.dmp/file
http://www.mediafire.com/file/lsvj1a49bdp4y6p/060318-14515-01.dmp/file
edit1: dumpfile from BSOD on 4 June 2018: http://www.mediafire.com/file/5caa579r9f9glm5/060418-15765-01.dmp/file
edit2: I would like to add that since the first formatting and the BOSDs started, I've done at least 6 clean installs of windows using the iso tool, but it continues to crash. Whether the bios is stock or not. I later repasted the CPU/GPU but that still didn't change the crashes, although it does run a few degrees cooler now.
On Mon 04-Jun-18 02:34:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060418-15531-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x19 (0x22, 0x0, 0x0, 0x0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Mon 04-Jun-18 02:34:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x19 (0x22, 0x0, 0x0, 0x0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Mon 04-Jun-18 00:30:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060418-15687-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF802AEE46700)
Bugcheck code: 0xA (0xFFFFA05000000000, 0x2, 0x0, 0xFFFFF802AEE46700)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Sun 03-Jun-18 22:26:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-14515-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80361ADC700)
Bugcheck code: 0xA (0xFFFFFA7D00000000, 0x2, 0x0, 0xFFFFF80361ADC700)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Sun 03-Jun-18 19:33:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-14718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0xA (0xFFFFF47A00000000, 0x2, 0x0, 0xFFFFF800AAA5F700)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I recently did a fresh install of windows on my XPS 9560 to get rid of bloatware.
I have done every single driver update through Windows Update, went to device manager and updated every device individually to be sure. I have nvida drivers for the gtx 1050.
Since formatting, I am constantly and randomly getting BSODs:
BAD POOL HEADER
IRQL NOT LESS OR EQUAL
These two are the main crashes I get, although there may have been another one.
I've done windos memtest and used another program.
I'm not overclocking, everything is stock.
I've undervolted the CPU but this hasn't changed anything.
Comparatively, I've done the same thing to my other dell XPS 9343 and there are no issues whatsoever.
I never had problems before the clean install. I've had dozens of BSODs but only these recent dump files remain.
http://www.mediafire.com/file/x2a2k8cn0iqab7r/060318-14718-01.dmp/file
http://www.mediafire.com/file/ya67hr87vna40a5/060418-15531-01.dmp/file
http://www.mediafire.com/file/5iha2sqvsr8zsor/060418-15687-01.dmp/file
http://www.mediafire.com/file/lsvj1a49bdp4y6p/060318-14515-01.dmp/file
edit1: dumpfile from BSOD on 4 June 2018: http://www.mediafire.com/file/5caa579r9f9glm5/060418-15765-01.dmp/file
edit2: I would like to add that since the first formatting and the BOSDs started, I've done at least 6 clean installs of windows using the iso tool, but it continues to crash. Whether the bios is stock or not. I later repasted the CPU/GPU but that still didn't change the crashes, although it does run a few degrees cooler now.
On Mon 04-Jun-18 02:34:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060418-15531-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x19 (0x22, 0x0, 0x0, 0x0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Mon 04-Jun-18 02:34:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x19 (0x22, 0x0, 0x0, 0x0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Mon 04-Jun-18 00:30:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060418-15687-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF802AEE46700)
Bugcheck code: 0xA (0xFFFFA05000000000, 0x2, 0x0, 0xFFFFF802AEE46700)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Sun 03-Jun-18 22:26:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-14515-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80361ADC700)
Bugcheck code: 0xA (0xFFFFFA7D00000000, 0x2, 0x0, 0xFFFFF80361ADC700)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Sun 03-Jun-18 19:33:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-14718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0xA (0xFFFFF47A00000000, 0x2, 0x0, 0xFFFFF800AAA5F700)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.