Unfortunately that information is pretty much useless.What is the procedure to fix / check the issue? It was again caused by the driver ntoskrnl.exe. Caused by address: ntoskrnl.exe+142480. Maybe you can trace back the root of this problem with this informatio
The ntoskrnl.exe file is a Windows kernel file, the Windows kernel files are simply never the cause. I haven't seen a situation where there were enough problems to point the cause to the ntoskrnl.exe file, you need a lot of serious (more then BSOD's) problems to point to the kernel.
You'll need to provide another upload to provide the right information.
I don't want to complaint, but this is the 3rd time I'm asking for system specs, they're very valuable for troubleshooting.
Is there a reason why you don't give them?
Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs: