New
#1
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.