Recurring BSOD Win 10

Discussion in 'Windows OS Support (Vista and newer)' started by Garb, Sep 3, 2017.

  1. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    Hey all, hoping you can help as I am at wits end. I keep getting BSODs on my system. I have run MEMTEST overnight with no errors, I have made sure all drivers are up to date from the manufacturers websites. One BSOD even linked back to using AVAST so I switched that out. They are getting more frequent now as well.

    I will happily provide full dump files if someone can explain how. :) Thanks!

    Crash dumps are enabled on your computer.

    On Sat 9/2/2017 5:23:29 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\090217-6156-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0x1A (0x6000, 0xFFFFE20E903F0CC0, 0xFFFFFFFFC0000225, 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. This problem might also be caused because of overheating (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.



    On Sat 9/2/2017 5:23:29 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1A (0x6000, 0xFFFFE20E903F0CC0, 0xFFFFFFFFC0000225, 0x0)
    Error: MEMORY_MANAGEMENT
    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. This problem might also be caused because of overheating (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.



    On Fri 9/1/2017 3:38:41 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\090117-7890-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x8280E)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8034329D80E, 0xFFFF8B00A2C06F28, 0xFFFF8B00A2C06770)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    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 system thread generated an exception which the error handler did not catch.
    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 Wed 8/23/2017 1:54:42 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\082317-6031-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0x1A (0x5100, 0xFFFFA6DC009CB180, 0xD0, 0xB)
    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. This problem might also be caused because of overheating (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.



    On Thu 8/17/2017 1:47:55 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\081717-6796-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0x109 (0xA3A013DA24F82A06, 0x0, 0x2BDB55FB3BF666B9, 0x101)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    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 kernel has detected critical kernel code or data corruption.
    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.
     
  2. glc

    glc Forum Administrator Staff Member

    Joined:
    May 26, 2000
    Messages:
    34,674
    Location:
    Joplin MO
    Specs on the system, please.
     
  3. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    PCPartPicker part list / Price breakdown by merchant

    CPU: Intel - Core i5-6600K 3.5GHz Quad-Core Processor ($228.50 @ Amazon)
    CPU Cooler: Corsair - H100i v2 70.7 CFM Liquid CPU Cooler ($109.99 @ Amazon)
    Motherboard: ASRock - Fatal1ty Z170 Gaming K4 ATX LGA1151 Motherboard ($137.98 @ Newegg)
    Memory: GeIL - EVO POTENZA 16GB (2 x 8GB) DDR4-2133 Memory ($118.99 @ Newegg)
    Storage: Kingston - SSDNow UV400 480GB 2.5" Solid State Drive ($175.99 @ SuperBiiz)
    Storage: Toshiba - P300 3TB 3.5" 7200RPM Internal Hard Drive ($79.60 @ Amazon)
    Video Card: Gigabyte - GeForce GTX 1070 8GB G1 Gaming Video Card ($464.79 @ SuperBiiz)
    Power Supply: EVGA - SuperNOVA G2 550W 80+ Gold Certified Fully-Modular ATX Power Supply ($85.88 @ OutletPC)
    Total: $1401.72
    Prices include shipping, taxes, and discounts when available
    Generated by PCPartPicker 2017-09-03 09:49 EDT-0400
     
  4. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
  5. glc

    glc Forum Administrator Staff Member

    Joined:
    May 26, 2000
    Messages:
    34,674
    Location:
    Joplin MO
    From your Speccy report:

    Voltage
    CPU CORE:
    0.784 V
    VPPM:
    3.344 V
    AVCC:
    3.328 V
    3VCC:
    3.312 V
    +12V:
    6.653 V
    VDDCR_SOC:
    1.008 V
    DRAM:
    0.992 V
    VIN7:
    0.000 V
    VDDP:
    1.288 V
    +1.8V:
    1.008 V
    VIN11:
    1.672 V
    +5V:
    3.648 V
    Chipset +1.05V:
    0.968 V

    These do not look right. Check the voltages in the bios, they should all be within 10% of spec. Your +12v is way off as is your +5v. DRAM should be 1.2v, this can be manually set. Indicative of a bad PSU or motherboard or Speccy not reading them correctly.
     
  6. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    It looks like the voltage was not correct for the RAM. I have manually set that. The +12v amd the +5V are all correct in the BIOS. Maybe Speccy just isnt reading it correctly. I will have to wait a few days and see how it goes to see if the change worked. I will report back! Thanks!
     
  7. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    Well it took a week, but we crashed again this morning:


    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Sat 9/9/2017 8:16:00 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\090917-7906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802B89B3FFC, 0xFFFFCC80AB75EC60, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 9/9/2017 8:16:00 AM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802B89B3FFC, 0xFFFFCC80AB75EC60, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
     
  8. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    And again!

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Sat 9/9/2017 10:37:51 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\090917-5890-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0xA (0x40110010, 0x2, 0x0, 0xFFFFF8033923B11E)
    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 Sat 9/9/2017 10:37:51 AM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x40110010, 0x2, 0x0, 0xFFFFF8033923B11E)
    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 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.
     
  9. glc

    glc Forum Administrator Staff Member

    Joined:
    May 26, 2000
    Messages:
    34,674
    Location:
    Joplin MO
    You have a driver that's not behaving. You need to dig some more.
     
  10. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    Where do I begin to do that?
     
  11. glc

    glc Forum Administrator Staff Member

    Joined:
    May 26, 2000
    Messages:
    34,674
    Location:
    Joplin MO
  12. Garb

    Garb

    Joined:
    Feb 25, 2006
    Messages:
    95
    Location:
    North Carolina
    Updated everything you listed, no other cards or devices I can think of. I will report back with any crashes. Thanks for your help!