Windows 10: ntoskrnl and ntkrnlmp problems - causing Very frequent BSOD: System Service Exception. How...

Hi,


I am new here. Been trying to get to the bottom of my infuriating problem with my laptop. Frequent BSODs, usually when the laptop has had a chance to go idle for a bit, never when an intensive program is running.


I downloaded WhoCrashed and got the following reports - the same thing over and over again!

Unfortunately, I dont know what I need to do next to resolve this. I am buy no means proficient at any of this, I am just trying to learn my best by googling and looking through other answers. Do I need to upload a copy of my minidump files? Please let me know


Reports are below. also if they seem a few days apart its because I just avoid using my laptop for days when I can lol

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Thu 07/05/2020 05:28:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050720-12031-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x3B 0xC0000006, 0xFFFFF8002FDF2F42, 0xFFFFA40ACAE8FBC0, 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 Thu 07/05/2020 05:28:58 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+0x1C2390
Bugcheck code: 0x3B 0xC0000006, 0xFFFFF8002FDF2F42, 0xFFFFA40ACAE8FBC0, 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 Thu 07/05/2020 01:05:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050720-6625-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x154 0xFFFF8188D9BD3000, 0xFFFFD4812E9E9480, 0x2, 0x0
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
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 06/05/2020 23:04:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050620-6625-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x154 0xFFFF9F069DC04000, 0xFFFFF30A225AEF00, 0x2, 0x0
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
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 02/05/2020 14:46:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050220-6421-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x154 0xFFFFA70EF54A2000, 0xFFFFFA85E7E22F00, 0x2, 0x0
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
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 Fri 01/05/2020 03:17:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050120-9437-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2390
Bugcheck code: 0x154 0xFFFF898BB054D000, 0xFFFFC10E0567A2F0, 0x2, 0x0
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
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.



If i need to do anything else please let me know. Again, I might not know exactly what youre talking about since I am a bit of a beginner with this sort of stuff... so some signposting would be appreciated


Thank you

:)

 

BSOD (system service exception) on new computer: ntoskrnl, ntkrnlmp

Please run driver verifier using the following settings for 48 hours.

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Warning: driver verifier could cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code:

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

 

BSOD (system service exception) on new computer: ntoskrnl, ntkrnlmp

Last week, I assembled a new desktop computer (with all new components) and installed windows 10 Educational. (See my 2nd PC details.) I updated and installed all the latest drivers. (I think at least.)

But, since installation, I am having BSOD on various moments with the error message "system service exception".
I read the minidump file with "WhoCrashed", and it states that the last BSOD was caused by ntoskrnl.exe and ntkrnlmp.exe.

Attached is the dm_log_collector file.
I would appreciate any help in solving this issue.

regards,

 

BSOD's have returned! [ntkrnlmp, ntoskrnl] HYPERVISOR error

Hello all, its nice to be back!
I've had a couple threads in the forum which regard my issues with BSODs the last being around 5 months ago from now and the other a bit longer. Though generally the errors have been consistent but has dipped in frequency with the help I received (thanks!) Since my last post, I have had near to no blue screens but am getting the odd few this past month, and judging by WhoCrashed, the modules which seem to cause it have been the same ever since.
In summary, here's what has been done:

I have my doubts on what may have caused the current one and here is what WhoCrashed states:

Code: