Solved

BSOD Windows 10 Dell 9560 with dump files

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.
24 answers Last reply Best Answer
More about bsod windows dell 9560
  1. MERGED QUESTION
    Question from byrne.mario : "BSOD randomly surfing internet, playing games, watching video"

    byrne.mario said:
    Hello everyone,

    I recently did a fresh install of windows on my XPS 9343 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.

    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.


  2. I will ask someone to read the dumps as that unknown module is interesting
  3. Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/I1EY.html

    File: 060318-14718-01.dmp (Jun 3 2018 - 08:33:21)
    BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
    Probably caused by: memory_corruption (Process: System)
    Uptime: 0 Day(s), 5 Hour(s), 16 Min(s), and 15 Sec(s)

    File: 060418-15687-01.dmp (Jun 3 2018 - 13:30:48)
    BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
    Uptime: 0 Day(s), 2 Hour(s), 04 Min(s), and 07 Sec(s)

    File: 060418-15531-01.dmp (Jun 3 2018 - 15:34:09)
    BugCheck: [BAD_POOL_HEADER (19)]
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
    Uptime: 0 Day(s), 2 Hour(s), 02 Min(s), and 53 Sec(s)

    File: 060318-14515-01.dmp (Jun 3 2018 - 11:26:12)
    BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
    Uptime: 0 Day(s), 2 Hour(s), 51 Min(s), and 28 Sec(s)

    The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

    The dump files gave the debugger (and my software) trouble. They are likely partially corrupt. I had to change the order the dump files were being run through in order to finally get a working result.

    Computer: Dell XPS 15 9560
    BIOS: Dated: 04/23/2018

    I can't help you with this. Wait for additional replies. Good luck.
  4. strange debugger can't read the name of driver

    I don't like recommending this but you can try running driver verifer,

    sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB
    Also helps to run system restore before hand to create a backup to roll back to if necessary.


    Read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers. Once it bsod, upload the minidump file and we see what it shows us.
  5. Hi there and thank you for your answers.

    I will run driver verifier after work and see what it comes up with. I have ran it previously with no result but I will try again.

    In the meantime, I got another BSOD while using Egde and Chrome, just browsing.

    Should I restore default voltage and uninstall Intel Extreme Tuning? I only got it to follow temps and undervolt as recommended by Dave2Dee's channel. Note that I have also undervolted my other dell xps 9343 with its respective value and haven't had any issues.

    Today's dump file: http://www.mediafire.com/file/5caa579r9f9glm5/060418-15765-01.dmp/file
  6. byrne.mario said:

    Should I restore default voltage and uninstall Intel Extreme Tuning? I only got it to follow temps and undervolt as recommended by Dave2Dee's channel. Note that I have also undervolted my other dell xps 9343 with its respective value and haven't had any issues.

    Today's dump file: http://www.mediafire.com/file/5caa579r9f9glm5/060418-15765-01.dmp/file


    Yes, try this as Its worth a try. but I am not sure its the cause, from what I can see undervolt errors are normally WHEA or Clock watchdog timeouts, not IRQ/Pool Header

    what Power supply do you have?

    None of your drivers stand out as candidates for causing BSOD. Not knowing what module it is that is causing these is most of the problem when identifying the solution. Maybe this new dump will be different.

    Do they happen at any time or when you doing something specific?
  7. - Restored values to default in CPU voltage.
    - Uninstalled Intel Tuning.
    - I ran a sfc /scannow and it did say that corrupt files were replaced/repaired but it crashed later on anyway. That's the last dump file I uploaded (edit1).
    - It seems like a detail but I've noticed since I formatted the very first time, anytime I close a windows, whether it's windows explorer, an edge/chrome window or alt-tab between applications, there is a faint phantom freeze that lingers for less than a second. It's subtle but it definitely never happened before.

    - When do the BSODs happen:
    - Very often when playing games: very often running Far Cry 5, often running League of Legends, less often running World of Warcraft Classic (old client)
    - Sometimes playing files in VLC. Definitely never happened before formatting, playing the same video files.
    - Less often while simply browsing using Edge and/or Chrome with multiple tabs open.

    - Specific times seem irrelevant, the laptop crashes on battery or while charging regardless.


    To illustrate this, all the dump files I've uploaded are from the past 24hrs during which I was playing (wow.exe) and using Edge & adobe connect. One crash was while the laptop was idle. All the while I ran a full Windows Defender scan, didn't crash. And two different memory tests (didn't crash).

    Regarding power, the laptop uses the stock dell power adapter.

    I haven't ran Driver Verifier again yet, will do asap & post.

    Thank you for your time.

    edit: I stopped playing Far Cry 5 altogether since it has a 100% probability to BOSD. It is a legit copy bought from Steam.
  8. which other program did you test the memory with? was it memtest86? did you run it on each stick individually? How many passes? I assume no errors as only score you want is o errors.

    not finding any drivers makes it look like hardware (unless newest dump shows something)

    Have you run the Dell diagnostic program? it checks hardware and drivers, might help.. its slow though.
  9. Yes I ran memtest86 with the default settings, just booted from a flash drive and started the test. I think it was 4 passes?

    I did run the Dell Diagnostic program too with no results.

    Just started running Driver Verifier now, reboot, crashed within 5 minutes. Here is the dump file:

    http://www.mediafire.com/file/72tj4pcuaj7y4wc/060418-27953-01.dmp


    And whocrashed analysis:


    On Mon 04-Jun-18 20:13:57 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\060418-27953-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
    Bugcheck code: 0xA (0xFFFFD20000000000, 0x2, 0x0, 0xFFFFF800516E3700)
    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.


    On Mon 04-Jun-18 20:13:57 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: storport.sys (storport!memset+0x1460)
    Bugcheck code: 0xA (0xFFFFD20000000000, 0x2, 0x0, 0xFFFFF800516E3700)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\storport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Storage Port Driver
    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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
  10. Just as a reset driver verifier and hit the restart button I get another BSODs:

    http://www.mediafire.com/file/r25algm7hkt8had/060418-9875-01.dmp

    On Mon 04-Jun-18 20:28:05 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\060418-9875-01.dmp
    This was probably caused by the following module: dddriver64dcsa.sys (0xFFFFF80CDB09365D)
    Bugcheck code: 0xC4 (0x2000, 0xFFFFF80CDB09365D, 0x0, 0x31676154)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\drivers\dddriver64dcsa.sys
    product: Dell Diags Device Driver
    company: Dell Inc.
    description: DDDriver.sys
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    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: dddriver64dcsa.sys (DDDriver.sys, Dell Inc.).
    Google query: dddriver64dcsa.sys Dell Inc. DRIVER_VERIFIER_DETECTED_VIOLATION


    On Mon 04-Jun-18 20:28:05 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: dddriver64dcsa.sys (0xFFFFF80CDB09365D)
    Bugcheck code: 0xC4 (0x2000, 0xFFFFF80CDB09365D, 0x0, 0x31676154)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\drivers\dddriver64dcsa.sys
    product: Dell Diags Device Driver
    company: Dell Inc.
    description: DDDriver.sys
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    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: dddriver64dcsa.sys (DDDriver.sys, Dell Inc.).
    Google query: dddriver64dcsa.sys Dell Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
  11. storport.sys? that is part of windows..related to hard drives, thats a windows RAID driver
    https://docs.microsoft.com/en-us/windows-hardware/drivers/storage/storport-driver

    wonder if you need Intel Rapid Storage Technology SATA RAID Controller driver running, It was on last run. Not sure why you have raid drivers running on a PC with 1 SSD?

    i will let gardenman read dumps before i go any further.
  12. I don't know either tbh. As far as drivers are installed, Windows Update & Dell Updater installed drivers. The only driver I manually installed is the Nvidia Graphics. I'll wait for your next answer. Thank you
  13. I ran the dump files through the debugger and got the following information: https://pste.eu/p/ZKUF.html

    File: 060418-9875-01.dmp (Jun 4 2018 - 09:28:05)
    BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
    *** WARNING: Unable to verify timestamp for DDDriver64Dcsa.sys
    Probably caused by: DDDriver64Dcsa.sys (Process: System)
    Uptime: 0 Day(s), 0 Hour(s), 13 Min(s), and 04 Sec(s)

    File: 060418-27953-01.dmp (Jun 4 2018 - 09:13:57)
    BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
    Probably caused by: memory_corruption (Process: MicrosoftEdgeCP.exe)
    Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 00 Sec(s)

    File: 060418-15765-01.dmp (Jun 4 2018 - 05:06:05)
    BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
    Uptime: 0 Day(s), 13 Hour(s), 31 Min(s), and 30 Sec(s)

    I can't help you with this. Wait for additional replies. Good luck.
  14. Yet another crash:

    http://www.mediafire.com/file/epov7dxuzmcl1xm/060518-15906-01.dmp

    On Tue 05-Jun-18 00:06:46 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\060518-15906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
    Bugcheck code: 0xA (0xFFFFC4E240000000, 0x2, 0x0, 0xFFFFF802A5444700)
    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.


    On Tue 05-Jun-18 00:06:46 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: storport.sys (storport!memset+0x1460)
    Bugcheck code: 0xA (0xFFFFC4E240000000, 0x2, 0x0, 0xFFFFF802A5444700)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\storport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Storage Port Driver
    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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
  15. another bsod an hour later:

    http://www.mediafire.com/file/21pes2e1wpe2vhy/060518-15359-01.dmp

    On Tue 05-Jun-18 01:13:02 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\060518-15359-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
    Bugcheck code: 0xA (0xFFFFE17080000000, 0x2, 0x0, 0xFFFFF803C3CDE700)
    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.


    On Tue 05-Jun-18 01:13:02 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: storport.sys (storport!memset+0x1460)
    Bugcheck code: 0xA (0xFFFFE17080000000, 0x2, 0x0, 0xFFFFF803C3CDE700)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\storport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Storage Port Driver
    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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
  16. I'm waiting for your next answer.

    However, I have no issue reformatting, all my stuff is saved on an external drive. I'm just wondering if it will solve the problem. Should formatting resolve this? Unless it is a hardware issue?
    Maybe once it's formatted and has the minimum amount of software installed it might be easier to diagnose.

    I work from my laptop so it's nerve wracking to expect a BSOD at any minute. I'd rather do a clean install. But I'll wait for your advice. Cheers
  17. Created an account to let you know I'm having the same issues after a fresh install of windows 10 from a flash drive!

    I was also previously undervolting the CPU but set back to default before uninstalling. I deleted all the partitions on the fresh install and got all drivers from Dell Support Assist. Now I'm randomly getting BSOD for IRQL_NOT_LESS_OR_EQUAL and BAD_POOL_HEADER (WhoCrashed analysis shown below).

    On Mon 6/4/2018 5:32:47 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\060418-15953-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
    Bugcheck code: 0xA (0xFFFFF48000000000, 0x2, 0x0, 0xFFFFF801BB8D1700)
    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.


    On Mon 6/4/2018 5:32:47 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: storport.sys (storport!memset+0x1460)
    Bugcheck code: 0xA (0xFFFFF48000000000, 0x2, 0x0, 0xFFFFF801BB8D1700)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\storport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Storage Port Driver
    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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
  18. Sorry, had to get some sleep

    Verifier crashed on - DDDriver64Dcsa.sys which is Dell Client System analyser

    Reformat may fix it, IRQ errors are normally drivers but this one is bouncing around windows services and only one its shown so far that isn't part of windows is that Dell program above.
  19. No worries :p

    I'll format after work and post an update.
  20. Best answer
    1° Just did a clean install and let Windows Update run until it was done.

    2° I then went to Device Manager and click on every single component to manually check for an update. These were the devices that updated manually:

    - Display Adapter: Intel(R) HD Graphics 630
    - Firmware: System Firmware 1.7.1
    - Intel(R) HID Event Filter (with restart)
    - Intel(R) Xeon(R) E3 - 1200 v6/7th Gen Intel(R) Core(TM) Host Bridge/DRAM Registers - 5910
    - Intel(R) 100 Series/C230 Series Chipset Family LPC Controller (HM175) - A152 (restart)
    - Intel(R) Serial IO I2C Host Controller A160
    - Intel(R) Serial IO I2C Host Controller A161
    - Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #13 - A11C
    - Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1 - A110
    - Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #15 - A11E
    - Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901
    Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #2 - A111

    3° After that I ran Windows Update again. No updates.

    4° After that I manually checked every single device by hand for a update in device manager again. This time no updates.

    I normally install Dell Updater & Dell Support Assist but I will NOT this time, as I suspect it might be the culprit. The reason for that is that Dell found similar updates (ie Chipset) and I suspect it install the drivers on top of Windows drivers resulting in clashes.
    Time will tell if my suspicions are right.

    If the laptop BSOD again, I will format again and limit the update to only Windows Update automatic updates without manually updating in device manager.

    Will post an update in 24-48hrs.
  21. Do the 1st step now and if you get any BSOD, instead of reformatting again, just upload the minidump and we see what it says

    1. Can you follow option one on the following link - here
    and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

    2. that creates a file in c windows/minidump after the next BSOD
    copy that file to documents
    upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
  22. Will do. Thank you!
  23. 24hrs without BSOD.

    edit: 48hrs without BSOD. Have resumed gaming, undervolting. no dell software installed.
  24. byrne.mario said:
    24hrs without BSOD.

    edit: 48hrs without BSOD. Have resumed gaming, undervolting. no dell software installed.


    Hello byrne.mario,
    I just wanted to thank you for this thread particularly for letting me realize I too was right in suspecting Dell's SupportAssist and Dell Update were corrupting my drivers, I saw it happen over and over and still thought it can't be that it's a serious company. But I followed your path, it's looking good so far. I would add to you, even tho you are probably aware, but one thing that Dell's update software is useful for is Bios updates.

    Cheers
Ask a new question

Read More

windows 10 XPS Blue Screen