[SOLVED] BSOD KMODE Exception Not Handled

[brandondjr0909]

GPU: Gigabyte RTX 2070 Super
MOBO: MSI Z490-A PRO
CPU: i9 10900k
New PC but I keep getting KMODE Exception Not Handled. Noticed it only happens when trying to play games at high intensity or stream games.

Looked into it a bit and ran a Who Crashed check on my mini dump files.
Seemed to trace back to a rt64.sys driver which I understand to be is my Realtek PCIe 2.5GbE Family Controller.
I just updated this driver through Realtek and still the issue persists.

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

On Thu 10/29/2020 9:51:43 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+0xE15FF)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8051ADFC4D7, 0xFFFFEE88DA78D628, 0xFFFFF8051E282920)
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 Thu 10/29/2020 9:51:43 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102920-6515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8051ADFC4D7, 0xFFFFEE88DA78D628, 0xFFFFF8051E282920)
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 Thu 10/29/2020 9:03:45 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102920-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8007A1FC4D7, 0xFFFFFB0843545E28, 0xFFFF9B00D2FF5920)
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.

Any help would be greatly appreciated.

 

[brandondjr0909]

GPU: Gigabyte RTX 2070 Super
MOBO: MSI Z490-A PRO
CPU: i9 10900k
New PC but I keep getting KMODE Exception Not Handled. Noticed it only happens when trying to play games at high intensity or stream games.

Looked into it a bit and ran a Who Crashed check on my mini dump files.
Seemed to trace back to a rt64.sys driver which I understand to be is my Realtek PCIe 2.5GbE Family Controller.
I just updated this driver through Realtek and still the issue persists.

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

On Thu 10/29/2020 9:51:43 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+0xE15FF)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8051ADFC4D7, 0xFFFFEE88DA78D628, 0xFFFFF8051E282920)
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 Thu 10/29/2020 9:51:43 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102920-6515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8051ADFC4D7, 0xFFFFEE88DA78D628, 0xFFFFF8051E282920)
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 Thu 10/29/2020 9:03:45 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102920-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8007A1FC4D7, 0xFFFFFB0843545E28, 0xFFFF9B00D2FF5920)
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.

Any help would be greatly appreciated.

Also just to add, (incase this is somehow related)
For some reason when i tried to install the Intel Chipset driver for my mobo off of MSI I would get an error stating to browse for SetupChipsetx64. but no matter where i looked it was nowhere to be found. So I'm also unable to update my chipset driver.

 

[Colif]

rt64.sys

reaktek nic drivers - try the Windows installation package here (3rd link down under windows) - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

SetupChipsetx64.

one suggested fix for that is uninstall the previous chipset drivers and then try.

can you go to C:\WINDOWS\Minidump
copy the files from here to another folder
upload the copied minidump files to a file sharing website and show link here, we see if other error was something else (top 2 are same error, who crashed always shows 1st one twice)

 

[brandondjr0909]

reaktek nic drivers - try the Windows installation package here (3rd link down under windows) - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software


one suggested fix for that is uninstall the previous chipset drivers and then try.

can you go to C:\WINDOWS\Minidump
copy the files from here to another folder
upload the copied minidump files to a file sharing website and show link here, we see if other error was something else (top 2 are same error, who crashed always shows 1st one twice)

Thanks for the help.
I tried installing the realtek link you privided but got: "The form #10 does not exist or it is not published." when I clicked the download button. I'm pretty sure this is the same update I did the other day as well.

As for the chipset driver, which ones are the chipset drivers in Device Manager?
I can just uninstall the drivers without issue?

Here are the dump files:
https://drive.google.com/drive/folders/12vuWSjNf_6PEsBByn6tFCprqOLyUFp9W?usp=sharing

 

[Colif]

Realtek error - that has to be a problem on their website. Dumps will show what drivers you have anyway.

Chipset driver - it should show in the add/remove applications list in settings/apps, its not just a driver. Pretty sure Intel shows there, I know AMD do

 

[brandondjr0909]

Realtek error - that has to be a problem on their website. Dumps will show what drivers you have anyway.

Chipset driver - it should show in the add/remove applications list in settings/apps, its not just a driver. Pretty sure Intel shows there, I know AMD do

Alrighty, i'll wait for you to look at the dump files.

I just tried uninstalling and reinstalling the chipset driver and got an unknown error when installing.
The log file is as follows:

[0F14:1700][2020-11-03T05:38:53]i001: Burn v3.11.1.2318, Windows v10.0 (Build 19042: Service Pack 0), path: C:\WINDOWS\Temp\{0B7C0849-7530-4341-8087-2AF0CC6EC56D}\.cr\SetupChipset.exe
[0F14:1700][2020-11-03T05:38:53]i000: Initializing string variable 'CHIPSET_PRODUCT_VERSION' to value '10.1.18383.8213'
[0F14:1700][2020-11-03T05:38:53]i000: Initializing string variable 'INSTALLER_BUILD_VERSION' to value '3.1.7.127'
[0F14:1700][2020-11-03T05:38:53]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'
[0F14:1700][2020-11-03T05:38:53]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'
[0F14:1700][2020-11-03T05:38:53]i009: Command Line: '"-burn.clean.room=C:\Users\Thizb\OneDrive\Desktop\Intel Chipset Drivers\SetupChipset.exe" -burn.filehandle.attached=540 -burn.filehandle.self=648'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Thizb\OneDrive\Desktop\Intel Chipset Drivers\SetupChipset.exe'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\Thizb\OneDrive\Desktop\Intel Chipset Drivers\'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Thizb\AppData\Local\Temp\Intel\Logs\Chipset_20201103053853.log'
[0F14:1700][2020-11-03T05:38:53]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'WixBundleManufacturer' to value 'Intel(R) Corporation'
[0F14:1700][2020-11-03T05:38:53]i000: Loading managed bootstrapper application.
[0F14:1700][2020-11-03T05:38:53]i000: Creating BA thread to run asynchronously.
[0F14:0CD4][2020-11-03T05:38:53]i000: ** MBA ** Command line:
[0F14:0CD4][2020-11-03T05:38:53]i000: Setting string variable 'WixBundleNameBanner' to value 'Intel(R) Chipset Device Software'
[0F14:0CD4][2020-11-03T05:38:53]i000: ** MBA ** Calling Engine.Detect()
[0F14:1700][2020-11-03T05:38:53]i100: Detect begin, 3 packages
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'DotNet35' to value '1'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'DotNet40Client' to value '1'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'DotNet40Full' to value '1'
[0F14:1700][2020-11-03T05:38:53]i000: Setting string variable 'DotNet45' to value '528372'
[0F14:1700][2020-11-03T05:38:53]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.
[0F14:1700][2020-11-03T05:38:53]i000: ** MBA ** Detected package DotNet45
[0F14:1700][2020-11-03T05:38:53]i103: Detected related package: {B4BF76D4-C8E0-4341-A8C5-A33D1C506DED}, scope: PerMachine, version: 10.1.18263.8193, language: 0 operation: MajorUpgrade
[0F14:1700][2020-11-03T05:38:53]i000: ** MBA ** Detected package SetupChipsetx86.msi
[0F14:1700][2020-11-03T05:38:53]i103: Detected related package: {B4BF76D4-C8E0-4341-A8C5-A33D1C506DED}, scope: PerMachine, version: 10.1.18263.8193, language: 0 operation: MajorUpgrade
[0F14:1700][2020-11-03T05:38:53]i000: ** MBA ** Detected package SetupChipsetx64.msi
[0F14:1700][2020-11-03T05:38:53]i101: Detected package: DotNet45, state: Present, cached: None
[0F14:1700][2020-11-03T05:38:53]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None
[0F14:1700][2020-11-03T05:38:53]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent
[0F14:1700][2020-11-03T05:38:53]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent
[0F14:1700][2020-11-03T05:38:53]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None
[0F14:1700][2020-11-03T05:38:53]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent
[0F14:1700][2020-11-03T05:38:53]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent
[0F14:1700][2020-11-03T05:38:53]i199: Detect complete, result: 0x0
[0F14:1700][2020-11-03T05:38:55]i200: Plan begin, 3 packages, action: Install
[0F14:1700][2020-11-03T05:38:55]w321: Skipping dependency registration on package with no dependency providers: DotNet45
[0F14:1700][2020-11-03T05:38:55]i052: Condition 'NOT VersionNT64' evaluates to false.
[0F14:1700][2020-11-03T05:38:55]i204: Plan 2 msi features for package: SetupChipsetx86.msi
[0F14:1700][2020-11-03T05:38:55]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0F14:1700][2020-11-03T05:38:55]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0F14:1700][2020-11-03T05:38:55]i052: Condition 'VersionNT64' evaluates to true.
[0F14:1700][2020-11-03T05:38:55]i204: Plan 2 msi features for package: SetupChipsetx64.msi
[0F14:1700][2020-11-03T05:38:55]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0F14:1700][2020-11-03T05:38:55]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0F14:1700][2020-11-03T05:38:55]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\Thizb\AppData\Local\Temp\Intel\Logs\Chipset_20201103053853_000_SetupChipsetx64.msi_rollback.log'
[0F14:1700][2020-11-03T05:38:55]i000: Setting string variable 'ChipsetInfx64_MsiLogPathVar' to value 'C:\Users\Thizb\AppData\Local\Temp\Intel\Logs\Chipset_20201103053853_000_SetupChipsetx64.msi.log'
[0F14:1700][2020-11-03T05:38:55]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0F14:1700][2020-11-03T05:38:55]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0F14:1700][2020-11-03T05:38:55]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0F14:1700][2020-11-03T05:38:55]i299: Plan complete, result: 0x0
[0F14:0CD4][2020-11-03T05:38:55]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''
[0F14:0CD4][2020-11-03T05:38:55]i000: ** MBA ** Getting window handle.
[0F14:0CD4][2020-11-03T05:38:55]i000: ** MBA ** Calling Engine.Apply(). Window handle: 263778
[0F14:1700][2020-11-03T05:38:55]i300: Apply begin
[0F14:1700][2020-11-03T05:38:55]i000: ** MBA ** Warning: ChipsetInfx86_MsiLogPathVar failed to fetch variable value: Element not found. (Exception from HRESULT: 0x80070490)
[0F14:1700][2020-11-03T05:38:55]i010: Launching elevated engine process.
[0F14:1700][2020-11-03T05:38:55]i011: Launched elevated engine process.
[0F14:1700][2020-11-03T05:38:55]i012: Connected to elevated engine.
[1398:15E0][2020-11-03T05:38:55]i358: Pausing automatic updates.
[1398:15E0][2020-11-03T05:38:55]i359: Paused automatic updates.
[1398:15E0][2020-11-03T05:38:55]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{afad3740-3061-4b48-a9ab-6f1435cb3dd6}, options: 0x7, disable resume: No
[1398:15E0][2020-11-03T05:38:55]i000: Caching bundle from: 'C:\WINDOWS\Temp\{F7B1D30A-1B0D-46F9-B3D0-9D730E3858C5}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{afad3740-3061-4b48-a9ab-6f1435cb3dd6}\SetupChipset.exe'
[1398:15E0][2020-11-03T05:38:55]i320: Registering bundle dependency provider: {afad3740-3061-4b48-a9ab-6f1435cb3dd6}, version: 10.1.18383.8213
[1398:15E0][2020-11-03T05:38:55]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{afad3740-3061-4b48-a9ab-6f1435cb3dd6}, resume: Active, restart initiated: No, disable resume: No
[1398:3BC4][2020-11-03T05:38:55]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{44C34709-F068-4CBC-8A71-515EDBC3B2A6}v10.1.18383.8213\SetupChipsetx64.msi.
[1398:3BC4][2020-11-03T05:38:55]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{44C34709-F068-4CBC-8A71-515EDBC3B2A6}v10.1.18383.8213\media1.cab.
[1398:3BC4][2020-11-03T05:38:55]i305: Verified acquired payload: cabA81C261D24835BDAD60FEAF8053B8D85 at path: C:\ProgramData\Package Cache\.unverified\cabA81C261D24835BDAD60FEAF8053B8D85, moving to: C:\ProgramData\Package Cache\{44C34709-F068-4CBC-8A71-515EDBC3B2A6}v10.1.18383.8213\NullDrivers.cab.
[1398:15E0][2020-11-03T05:38:55]i323: Registering package dependency provider: {44C34709-F068-4CBC-8A71-515EDBC3B2A6}, version: 10.1.18383.8213, package: SetupChipsetx64.msi
[1398:15E0][2020-11-03T05:38:55]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{44C34709-F068-4CBC-8A71-515EDBC3B2A6}v10.1.18383.8213\SetupChipsetx64.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPNOMODIFY="1"'
[1398:15E0][2020-11-03T05:38:58]e000: Error 0x80070652: Failed to install MSI package.
[1398:15E0][2020-11-03T05:38:58]e000: Error 0x80070652: Failed to execute MSI package.
[0F14:1700][2020-11-03T05:38:58]e000: Error 0x80070652: Failed to configure per-machine MSI package.
[0F14:1700][2020-11-03T05:38:58]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070652, restart: None
[0F14:1700][2020-11-03T05:38:58]e000: Error 0x80070652: Failed to execute MSI package.
[1398:15E0][2020-11-03T05:38:58]i318: Skipped rollback of package: SetupChipsetx64.msi, action: Uninstall, already: Absent
[0F14:1700][2020-11-03T05:38:58]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x0, restart: None
[1398:15E0][2020-11-03T05:38:58]i329: Removed package dependency provider: {44C34709-F068-4CBC-8A71-515EDBC3B2A6}, package: SetupChipsetx64.msi
[1398:15E0][2020-11-03T05:38:58]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{44C34709-F068-4CBC-8A71-515EDBC3B2A6}v10.1.18383.8213\
[1398:15E0][2020-11-03T05:38:58]i329: Removed package dependency provider: {45F1E101-AAC4-4BB9-B31C-1E03654EF9A8}, package: SetupChipsetx86.msi
[1398:15E0][2020-11-03T05:38:58]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{afad3740-3061-4b48-a9ab-6f1435cb3dd6}, resume: None, restart: None, disable resume: No
[1398:15E0][2020-11-03T05:38:58]i330: Removed bundle dependency provider: {afad3740-3061-4b48-a9ab-6f1435cb3dd6}
[1398:15E0][2020-11-03T05:38:58]i352: Removing cached bundle: {afad3740-3061-4b48-a9ab-6f1435cb3dd6}, from path: C:\ProgramData\Package Cache\{afad3740-3061-4b48-a9ab-6f1435cb3dd6}\
[1398:15E0][2020-11-03T05:38:58]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{afad3740-3061-4b48-a9ab-6f1435cb3dd6}, resume: None, restart initiated: No, disable resume: No
[0F14:1700][2020-11-03T05:38:58]i000: ** MBA ** Apply complete. Status: '0x80070652' Restart: 'None' Result: 'None'
[0F14:1700][2020-11-03T05:38:58]i399: Apply complete, result: 0x80070652, restart: None, ba requested restart: No
[0F14:0CD4][2020-11-03T05:38:58]e000: ** MBA ** Unknown error.

 

[Colif]

Error 0x80070652: Failed to install MSI package.
I can find that for some Intel drivers but not the chipset.

I looked on the INtel Z490 support page and the link for downloads is broken. I figured Intel would be best place to get the drivers from

Try running this and see if it sees anything - https://www.intel.com.au/content/www/au/en/support/detect.html

 

[brandondjr0909]

Error 0x80070652: Failed to install MSI package.
I can find that for some Intel drivers but not the chipset.

I looked on the INtel Z490 support page and the link for downloads is broken. I figured Intel would be best place to get the drivers from

Try running this and see if it sees anything - https://www.intel.com.au/content/www/au/en/support/detect.html

Ah, that's unfortunate.
I installed the link you provided and it stated all my drivers were up to date, but it excludes detecting drivers for the chipset.
I just rebooted my computer and tried to install the chipset driver again, and it's back to making me browse for SetupChipsetx64 but it's still nowhere to be found.
Maybe I should just wait until the links on Intel are updated?

 

[Colif]

its probably a bug with the installer package as it shows

MBA ** Warning: ChipsetInfx86_MsiLogPathVar failed to fetch variable value: Element not found.

so I think your error is an error in the driver package from MSI.

It doesn't help MSI has 2 different meanings in this thread, its the name of maker of motherboard as well as a type of file, as many drivers have .msi after name but aren't made by MSI

you could ask on here - https://forum-en.msi.com/index.php?forums/msi-intel-boards.54/ as there might be a fix?

 

[gardenman]

Hi ,I hope I'm not too late with dump results. I ran the dump files through the debugger and got the following information: https://jsfiddle.net/6n3qa0oc/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler

File information:	102920-6843-01.dmp (Oct 29 2020 - 22:03:45)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: obs64.exe)
Uptime:	4 Day(s), 19 Hour(s), 51 Min(s), and 05 Sec(s)

File information:	102920-6515-01.dmp (Oct 29 2020 - 22:51:43)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 47 Min(s), and 32 Sec(s)

Comment: The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner or other MSI software)

Possible Motherboard page: https://www.msi.com/Motherboard/Z490-A-PRO
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Not sure what crashed obs


second error occurred during internet activities. It mentions NDIS (Windows Network Driver Interface Specification), tcpip.sys which is transmission control protocol/internet protocol & netio.sys which I could guess it network Input Output.
wish all bsod were so obvious

Jul 23 2020

rt640x64.sys

Realtek NICDRV 8169 PCIe GBE Family Controller driver

but you are right, the link on page to newest installer is broken and only other sites that have newer drivers I wouldn't trust to be right. I guess we wait until someone notices.



that chipset driver you were trying to install is this one - https://downloadcenter.intel.com/download/29634/Chipset-INF-Utility - so you could try to update it from there.

 

[brandondjr0909]

Possible Motherboard page: https://www.msi.com/Motherboard/Z490-A-PRO
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Thank you for your assistance.

-This is indeed the correct motherboard.
-I only have Afterburner to adjust my GPU fan curve. Not for overclocking.

 

[brandondjr0909]

Not sure what crashed obs


second error occurred during internet activities. It mentions NDIS (Windows Network Driver Interface Specification), tcpip.sys which is transmission control protocol/internet protocol & netio.sys which I could guess it network Input Output.
wish all bsod were so obvious

Jul 23 2020

rt640x64.sys

Realtek NICDRV 8169 PCIe GBE Family Controller driver

but you are right, the link on page to newest installer is broken and only other sites that have newer drivers I wouldn't trust to be right. I guess we wait until someone notices.



that chipset driver you were trying to install is this one - https://downloadcenter.intel.com/download/29634/Chipset-INF-Utility - so you could try to update it from there.

Yes the realtek links are still broken.
I've tried to install chipset from Intel and still get prompted to browse for SetupChipsetx64 when installing, but still it's nowhere to be found.
Almost like it was never there in the first place?

 

[Colif]

You don't really need the chipset driver so you could just ignore it. I can find that problem around the place for other intel driver packages. Sometimes you can get that error if it doesn't match your chipset on PC , i am not sure if that is case here.

 

[brandondjr0909]

It would seem I have fixed the issue after doing a reset on my PC and clean reinstalling windows.
Went to MSI website for my MOBO drivers and installed the drivers from there, starting with the chipset then network drivers.
Been a couple days and haven't crashed yet, and have been able to stream/game for multiple hours at a time.




Will update if anything comes back.
Thanks.