Just last month I put together a new computer, running Win10 Pro.
I've been getting occasional BSODs of varying kinds on it, each of which I've taken necessary steps (driver updating, sfc /scannow, dism, and so forth) to fix. This appears to be the last BSOD I've been getting and have been unable to fix it myself, so I've come hoping for an answer.
I have both BlueScreenView and WhoCrashed, and they both list ntoskrnl.exe as the BSOD cause.
Copypasting the WhoCrashed analysis here:
System Information (local)
--------------------------------------------------------------------------------
Computer name: GUILD-SWEETHEAR
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: MS-7821, MSI, Z97-G45 GAMING (MS-7821)
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17126178816 bytes total
On Mon 22-Oct-18 3:23:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102218-24171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xA (0xFFFFC2886F6E7368, 0x2, 0x0, 0xFFFFF80139C3F8A7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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 have uploaded the crash dump file as well:
https://mega.nz/#!qshTwaZQ!JShFcr0FckOk-eKM8jh0v0LP-lSBTttnOJKpC_UiwSA
Here is what I have done on my own:
Checked motherboard for any damage, it appears fine.
Ran memtest on my RAM, gave it 9 passes, no errors.
Ran Intel Processor Diagnostic Tool on my CPU, no errors.
Ran Disk Checkup on my HDDs, all listed OK and no errors when running self tests.
Driver updates, lots of driver updates.
Ran sfc /scannow in an elevated command prompt.
Ran dism /online /cleanup-image /restorehealth in an elevated command prompt.
That's everything I can remember.
Any help would be great.
I've been getting occasional BSODs of varying kinds on it, each of which I've taken necessary steps (driver updating, sfc /scannow, dism, and so forth) to fix. This appears to be the last BSOD I've been getting and have been unable to fix it myself, so I've come hoping for an answer.
I have both BlueScreenView and WhoCrashed, and they both list ntoskrnl.exe as the BSOD cause.
Copypasting the WhoCrashed analysis here:
System Information (local)
--------------------------------------------------------------------------------
Computer name: GUILD-SWEETHEAR
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: MS-7821, MSI, Z97-G45 GAMING (MS-7821)
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17126178816 bytes total
On Mon 22-Oct-18 3:23:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102218-24171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xA (0xFFFFC2886F6E7368, 0x2, 0x0, 0xFFFFF80139C3F8A7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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 have uploaded the crash dump file as well:
https://mega.nz/#!qshTwaZQ!JShFcr0FckOk-eKM8jh0v0LP-lSBTttnOJKpC_UiwSA
Here is what I have done on my own:
Checked motherboard for any damage, it appears fine.
Ran memtest on my RAM, gave it 9 passes, no errors.
Ran Intel Processor Diagnostic Tool on my CPU, no errors.
Ran Disk Checkup on my HDDs, all listed OK and no errors when running self tests.
Driver updates, lots of driver updates.
Ran sfc /scannow in an elevated command prompt.
Ran dism /online /cleanup-image /restorehealth in an elevated command prompt.
That's everything I can remember.
Any help would be great.