1.    05 Feb 2017 #1
    Join Date : Feb 2017
    Posts : 2
    Win Pro x64

    BSOD IRQL/Driver IRQL/Kernal Trap, Whocrashed report included


    Morning Gents,

    I build a new rig about two weeks ago. I had zero issues with setup and installation. Last night I got a BSOD while playing a game on steam and using discord. From there the BSODs happened within minutes of rebooting..

    I attempted to trouble shoot the BSOD codes but was unable to run the OSR auto scan on my dump files. In a fit of joy I attempted to run restore from a known working version. That resulted in BSOD within minutes.

    I then did what I thought was logical and attempted to perform a clean install of Win 10.. I attempted 3 times with the install never passing the 30% mark before BSOD..

    the night has passed and I removed one stick of the DDR4 ram and installed win 10 no problems.. until 2 mintues past the login screen it BSOD.. I shutdown and removed the other stick of DDR4 and replaced the other stick.. This time in the #1 slot.. To clarify.. The system was built with 2 sticks of 8gig DDR4 placed into slots #2 and #1. The first removal of ram left the stick in the #2 slot only. The system has crashed with both sticks.. even when solo in slots #2 and #1. I will say the crashes are less freq but maybe that due to less programs running on the clean install.

    The system has been up long enough for me to use Whocrashed to run the minidumps. I will paste the results below, I would include the files as well but get access denied when trying to open or upload the files.

    Computer name: DESKTOP-FCMTEDN
    Windows version: Windows 10 , 10.0, build: 14393
    Windows dir: C:\Windows
    Hardware: Z270X-Gaming 7, Gigabyte Technology Co., Ltd.
    CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 8544903168 bytes total




    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 2/5/2017 12:08:22 PM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-3515-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0x7F (0x8, 0xFFFFBA8025692B30, 0xFFFFBA0026812350, 0xFFFFF802527DA37A)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    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 Intel CPU generated a trap and the kernel failed to catch this trap.
    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 2/5/2017 11:35:40 AM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-3593-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0xA (0xFFFFCE00534B5669, 0xFF, 0x0, 0xFFFFF801F4357AEA)
    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 2/5/2017 11:31:04 AM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-4453-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0xA (0xFFFF8C00046B5669, 0xFF, 0x0, 0xFFFFF803453DCAEA)
    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 2/5/2017 11:23:05 AM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-2640-01.dmp
    This was probably caused by the following module: ndis.sys (ndis+0xDB3E)
    Bugcheck code: 0xD1 (0xFFFFF801E3AC67F5, 0x2, 0x8, 0xFFFFF801E3AC67F5)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Network Driver Interface Specification (NDIS)
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 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.



    On Sun 2/5/2017 11:23:05 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: 0xD1 (0xFFFFF801E3AC67F5, 0x2, 0x8, 0xFFFFF801E3AC67F5)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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.


    Any help would be greatly appreciated.
      My ComputerSystem Spec
  2.    05 Feb 2017 #2
    Join Date : Feb 2017
    Posts : 2
    Win Pro x64
    Thread Starter

    Since posting I have had four more crashes. Twice while looking up solutions to the BSODS and the last two were during an attempt to update Windows.

    On Sun 2/5/2017 12:29:34 PM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-3968-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0x50 (0xFFFFF8012B6650E0, 0x10, 0xFFFFF8012B6650E0, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    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 2/5/2017 12:26:52 PM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-4265-01.dmp
    This was probably caused by the following module: fltmgr.sys (0xFFFFF805C95076E1)
    Bugcheck code: 0x50 (0xFFFFD40178F2B538, 0x2, 0xFFFFF805C95076E1, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    Bug check description: This indicates that invalid system memory has been referenced.
    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 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.



    On Sun 2/5/2017 12:23:41 PM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-3687-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0xD1 (0xFFFFF800852B3DAD, 0x2, 0x8, 0xFFFFF800852B3DAD)
    Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 2/5/2017 12:20:12 PM your computer crashed
    crash dump file: C:\Windows\Minidump\020517-3609-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0x21 (0xFFFF988F4B257800, 0x2, 0xFFFFFFF000000005, 0xFFFFFFEFFFF996CE)
    Error: QUOTA_UNDERFLOW
    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 quota charges have been mishandled by returning more quota to a particular block than was previously charged.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My ComputerSystem Spec
  3.    07 Feb 2017 #3
    Join Date : Jan 2017
    Karlsruhe
    Posts : 730
    Windows 10 Pro

    Attention:

    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Solved IRQL or driver IRQL
Hello everyone. I have a problem with my pc. After a hardware upgrade (which I will say that I didn't format my drive) I started having some BSOD. The change happened at the start of August, so I have been running most of the month without a...
BSOD Crashes and Debugging
BSOD - Driver IRQL
98895 PC Parts List : Asus z170 A Bios ver. 1702, only drivers from Asus site downloaded and installed, excluding realtek audio (onboard audio disabled in bios, windows hd audio disabled in device manager) 6600k @ 4.6x and 4.5 cache -...
BSOD Crashes and Debugging
Driver IRQL Less or not equal BSOD
I've been getting this BSOD for quite some time now (a few months easy) and I've been slowly sorting through drivers and software trying to find the cause. All I can tell is that it seems to happen most of the time while I'm playing games (though I...
BSOD Crashes and Debugging
Bsod driver irql not less or equal
Hello everyone, Recently, my laptop crashes often and apparently it’s because of the error: DRIVER IRQL NOT LESS OR EQUAL. The recent crashes happened Sunday and twice today. This is the information I got from Whocrashed (If this can be any...
BSOD Crashes and Debugging
trio of BSOD today - Driver IRQL Not Less or Equal and other
hi all Trio of BSODS today, all while running the xbox app and streaming today. Of note, I am not at home, if that makes a difference. This did happen last week as well but just once. I rebooted and nothing bad happened until today. Nothing...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:09.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums