[SOLVED] Windows 10 BSOD issue.

Aug 16, 2019
5
0
10
Hello,

Recently my PC has been having a BSOD issue with the error Kernal mode trap and I'm not quite sure whats wrong. I have attached the dump files if needed.

Memory Dump File


My specs:
Windows 10 64 bit, home
Nvidia geforce RTX 2080
AMD Ryzen 7 2700 eight-core processor
GeIL SUPER LUCE RGB SYNC 32GB ram


Please let me know if any other information is needed
 
Solution
Sorry, I'm having problems with messages not going/coming through. I haven't went back and looked yet but I probably didn't get the message.

I ran the dump file through the debugger and got the following information: https://pste.eu/p/B26I.html

File information:081719-11500-01.dmp (Aug 17 2019 - 02:06:37)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)
Driver warnings:*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:0 Day(s), 3 Hour(s), 19 Min(s), and 48 Sec(s)

Additional BIOS information was not...

shadi shtaklef

Reputable
BANNED
Jul 26, 2015
123
8
4,595
this is the analysis of the dump file:-

On Sat 8/17/2019 10:06:37 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081719-11500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2D1D3B)
Bugcheck code: 0x1000007F (0x8, 0xFFFF8401F19DE2B0, 0xFFFFEC865AFB9FF0, 0xFFFFF804080D1D3B)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time

did it just happen one time or it's always happening? what were u doing when it happened?

is your computer overheating?
 

Colif

Win 11 Master
Moderator
who crashed only tells you what crashed, it doesn't show the list of drivers running at time that are likely to be the cause. 90% of time it blames ntoskrnl, whihc doesn't tell you anything.

ntoskrnl is the victim, not the cause. It is the windows kernel, it sits between programs and hardware.

I have sent link to a friend, he will get more info out of dumps than what is shown above
 

gardenman

Splendid
Moderator
Sorry, I'm having problems with messages not going/coming through. I haven't went back and looked yet but I probably didn't get the message.

I ran the dump file through the debugger and got the following information: https://pste.eu/p/B26I.html

File information:081719-11500-01.dmp (Aug 17 2019 - 02:06:37)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)
Driver warnings:*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:0 Day(s), 3 Hour(s), 19 Min(s), and 48 Sec(s)

Additional BIOS information was not included in the dump file and this can sometimes mean an outdated BIOS is being used. I wouldn't worry about updating the BIOS just yet.

Search your computer for networktunnelx64.sys and let us know the exact folder(s) where you find this file.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
  • Like
Reactions: Colif
Solution
Aug 16, 2019
5
0
10
Hello, gardenman.

Thank you for analyzing the dump file! I have done a search to networktunnelx64.sys and found it belonging to the program 'Pingzapper' a program that is used to lower ping in games. I have now uninstalled the program and hope that it would solve my issue.

Thank you very much and thank you Colif for relaying the dump file. I truly appreciate both of you!
 

gardenman

Splendid
Moderator
No problem. I looked at the dump files and all 4 are pointing to networktunnelx64.sys (PingZapper) as being the culprit. So hopefully removing that program helps. Full results: https://pste.eu/p/QVkC.html
File information:081919-9234-01.dmp (Aug 19 2019 - 01:49:03)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)
Driver warnings:*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 03 Sec(s)

File information:081919-11031-01.dmp (Aug 19 2019 - 01:32:08)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)
Driver warnings:*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:0 Day(s), 3 Hour(s), 16 Min(s), and 34 Sec(s)

File information:081719-13593-01.dmp (Aug 16 2019 - 22:10:14)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)
Driver warnings:*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:0 Day(s), 0 Hour(s), 15 Min(s), and 50 Sec(s)

File information:081719-10921-01.dmp (Aug 16 2019 - 21:43:04)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP (7F)
Driver warnings:*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:0 Day(s), 7 Hour(s), 18 Min(s), and 05 Sec(s)
Good luck.
 
Aug 16, 2019
5
0
10
Alright! Thank you! Hopefully removing it will of solved it. If I face any other issues I'll be sure to write another post in this thread. Thank you again for all the help!