Hello, I've been getting BSOD ntoskrnl.exe quite frequently recently, I've been doing some scans and tests but I couldn't find what is at fault. I'll post whocrashed dumps and memtest86.
On Mon 2/10/2020 7:47:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-8234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80153A6EF3E, 0xFFFFF000E6B24DD0, 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 Mon 2/10/2020 7:47:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x7EC9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80153A6EF3E, 0xFFFFF000E6B24DD0, 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.
On Mon 2/10/2020 6:52:36 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-8218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0xA (0x48, 0x2, 0x0, 0xFFFFF800294B907F)
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 2/10/2020 1:38:17 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-6906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8042AF08DC2, 0xFFFFF5884DDFDD90, 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 Mon 2/10/2020 11:55:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-6921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8055F110ED0, 0xFFFFF08A8CC83CE0, 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 Mon 2/10/2020 11:42:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-7125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x4E (0x8D, 0x3E68F4, 0x41C000, 0xFFFF8681471033B0)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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.
Conclusion
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Summary
System Information
Result summary
On Mon 2/10/2020 7:47:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-8234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80153A6EF3E, 0xFFFFF000E6B24DD0, 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 Mon 2/10/2020 7:47:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x7EC9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80153A6EF3E, 0xFFFFF000E6B24DD0, 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.
On Mon 2/10/2020 6:52:36 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-8218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0xA (0x48, 0x2, 0x0, 0xFFFFF800294B907F)
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 2/10/2020 1:38:17 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-6906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8042AF08DC2, 0xFFFFF5884DDFDD90, 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 Mon 2/10/2020 11:55:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-6921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8055F110ED0, 0xFFFFF08A8CC83CE0, 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 Mon 2/10/2020 11:42:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021020-7125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x4E (0x8D, 0x3E68F4, 0x41C000, 0xFFFF8681471033B0)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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.
Conclusion
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Summary
| Report Date | 2020-02-10 23:45:27 |
| Generated by | MemTest86 V8.3 Free (64-bit) |
| Result | FAIL |
| EFI Specifications | 2.70 |
| System | |
| Manufacturer | Micro-Star International Co., Ltd. |
| Product Name | MS-7B84 |
| Version | 1.0 |
| Serial Number | To be filled by O.E.M. |
| BIOS | |
| Vendor | American Megatrends Inc. |
| Version | 2.D0 |
| Release Date | 12/03/2019 |
| Baseboard | |
| Manufacturer | Micro-Star International Co., Ltd. |
| Product Name | B450M PRO-M2 (MS-7B84) |
| Version | 1.0 |
| Serial Number | IC16387720 |
| CPU Type | AMD Ryzen 5 2600 Six-Core |
| CPU Clock | 3435 MHz [Turbo: 3939.6 MHz] |
| # Logical Processors | 12 |
| L1 Cache | 12 x 96K (84815 MB/s) |
| L2 Cache | 12 x 512K (57046 MB/s) |
| L3 Cache | 1 x 16384K (27417 MB/s) |
| Memory | 16347M (14350 MB/s) |
| DIMM Slot #0 | 8GB DDR4 XMP PC4-24000 |
| G Skill Intl / F4-3000C16-8GISB | |
| 16-18-18-38 / 3002 MHz / 1.350V | |
| DIMM Slot #1 | 8GB DDR4 XMP PC4-24000 |
| G Skill Intl / F4-3000C16-8GISB | |
| 16-18-18-38 / 3002 MHz / 1.350V |
| Test Start Time | 2020-02-10 20:09:05 |
| Elapsed Time | 3:34:56 |
| Memory Range Tested | 0x0 - 41F380000 (16883MB) |
| CPU Selection Mode | Parallel (All CPUs) |
| ECC Polling | Enabled |
| # Tests Passed | 45/48 (93%) |
| Lowest Error Address | 0x1CFEF444 (463MB) |
| Highest Error Address | 0x3EB3A34BC (16051MB) |
| Bits in Error Mask | 00000000000000F0 |
| Bits in Error | 4 |
| Max Contiguous Errors | 1 |
| Test | # Tests Passed | Errors |
| Test 0 [Address test, walking ones, 1 CPU] | 4/4 (100%) | 0 |
| Test 1 [Address test, own address, 1 CPU] | 4/4 (100%) | 0 |
| Test 2 [Address test, own address] | 4/4 (100%) | 0 |
| Test 3 [Moving inversions, ones & zeroes] | 4/4 (100%) | 0 |
| Test 4 [Moving inversions, 8-bit pattern] | 4/4 (100%) | 0 |
| Test 5 [Moving inversions, random pattern] | 4/4 (100%) | 0 |
| Test 6 [Block move, 64-byte blocks] | 4/4 (100%) | 0 |
| Test 7 [Moving inversions, 32-bit pattern] | 4/4 (100%) | 0 |
| Test 8 [Random number sequence] | 4/4 (100%) | 0 |
| Test 9 [Modulo 20, ones & zeros] | 4/4 (100%) | 0 |
| Test 10 [Bit fade test, 2 patterns, 1 CPU] | 4/4 (100%) | 0 |
| Test 13 [Hammer test] | 1/4 (25%) | 76 |
| Last 10 Errors |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A34BC, Expected: BF1FBDD8, Actual: BF1FBDE8 |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A34B4, Expected: 99DB7FEE, Actual: 99DB7F7E |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A34AC, Expected: 53ADFAD4, Actual: 53ADFAE4 |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A34A4, Expected: 0A967C0A, Actual: 0A967CEA |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A349C, Expected: BB2E4510, Actual: BB2E45D0 |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A3494, Expected: 528DEB66, Actual: 528DEB06 |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A348C, Expected: 069FB88C, Actual: 069FB81C |
| 2020-02-10 23:43:28 - [Data Error] Test: 13, CPU: 0, Address: 3EB3A3484, Expected: 0AB70A02, Actual: 0AB70A62 |
| 2020-02-10 23:37:51 - [Data Error] Test: 13, CPU: 0, Address: 2675C34BC, Expected: 487270FD, Actual: 4872704D |
| 2020-02-10 23:37:51 - [Data Error] Test: 13, CPU: 0, Address: 2675C34B4, Expected: A82A612B, Actual: A82A61FB |
Facebook
Twitter
Instagram