Bsod when using wired connection

[Mohamed-Mahdy]

i bougth my laptop probook 450 G4 I7-7500U 8GB ram at 17 - 5 - 2018 >> using it for surfing the internet and watching youtube only >> no gaming or editing or render procese

using Wifi only < no wired connection used << and it is all ok >> no BSOD or any proplem

and this is my wifi driver data

1 -11 - 2018 Tried to use a cable to connect the ineternet << then the BSOD started 

this is my wired internet driver

driver on HP website is 10.23.1003.2017

Driver on realtek website 10028_07302018

Driver updated using ( Driver Booster Software ) 10.30.815.2018

Note : Same Proplem ( BSOD ) Happen using all the version mentioned above

i have win 10 pro 64 activited and updated

and have kaspersky internet secuirety 2019 activited and updated

my driver updated using driver on HP ofiicel Site and device manger show no errores in any driver

my main browser is Firefox and it is updated ( Note : Proplem occures in Microsoft edge too )

the proplem discreption is

connectiong the internet cable ( Cate 6 ) and it is ok <<< try to continu and download file from IDM ( without opening any browser ) the download work ok

try to open fire fox and entring face book or any other website such as youtube > the windows crach and BSOD appears

the laptop restart then open >> i used the software ( Blus Screen view ) to get the cause of BSOD

and this is the Dump Files that may help

https://gulfupload.com/j7im1wdj0b9j

https://gulfupload.com/b1z5qgtxc3ns

and i used the software ( Whocarshed )

and this is the result

Welcome to WhoCrashed (HOME EDITION) v 6.02
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)
Computer name: ENG-MOHAMED
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: HP ProBook 450 G4, HP, 8231
CPU: GenuineIntel Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8480059392 bytes total



Crash Dump Analysis
Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 2018-11-04 8:07:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110418-6437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80241AF62DB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2018-11-04 8:07:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rt64.sys (rt640x64+0x26AEE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80241AF62DB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rt64.sys .
Google query: rt64.sys KMODE_EXCEPTION_NOT_HANDLED



On Sun 2018-11-04 7:54:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110418-7046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1157)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803C664C157, 0xFFFFF48AB05F1ED8, 0xFFFFF48AB05F1720)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_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 system thread generated an exception which the error handler did not catch.
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.




Conclusion
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

rt64.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.

i think that i gave all information that i have > hpe to find any soloution for my proplem < ♥ ^_^

[Mohamed-Mahdy]

why < there is no answer ? 😕