Freeze requiering hard reset (no bsod) since fall creator installation

[Metallicana974]

Hi there,
Since i install the Fall creator update _{(way after it's release, because creators update give me a memory leak because of my "Killer E2200" driver was not updated)} i started to have some freeze that just "ice" my pc (image remain but can't do anything but hard reset)
I have try a few thing with my poor knowledge:
Chkdsk clean, windows memtest clean, i dont see anything that wrong on the windows events, it's happen randomly ingame or even watching series

sfc /scannow, dism /online/cleanup-image /RestoreHealth (i get an error while restarting that's why i do that)
Even Reinstalling windows 10
So right now i don't know what  to do, i was hopping to get ironically  a bsod to have a start to dig with but nothing.
I was planning to format again without installing fall creator but ffxv take a while to install (_{steam is very slow to install this ><")} so i want some help to find what's going on with that update
_{(before formating the 1st time, i manage to find a graph on windows that show critical error on windows event and it start after i install the fall creator update that why i thing it's because of it)}

DxDiag.txt

Edited March 17, 2018 by Metallicana974

[usasma]

In general, if you do a clean install of Windows and the problem remains - then it's usually a hardware problem (although compatibility issues and low-level driver problems are also possible - but less likely).

Critical error with Event ID 41 is just Windows' way of saying it doesn't know why it shut down.
More info on that here:  http://support.microsoft.com/kb/2028504

Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

While waiting for a reply, please monitor your temps with one of these free utilities: 
SpeedFan:  http://www.almico.com/sfdownload.php
HWMonitor:  https://www.cpuid.com/softwares/hwmonitor.html
HWInfo:  https://www.hwinfo.com/download.php

Also, Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum):  https://forums.malwarebytes.org/topic/170037-blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities.
.ZIP is the type file that can be uploaded to the forums.

My suggested way to diagnose a hardware problem (3 steps)
Please start with the hardware diagnostics while waiting for a reply.:

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:
        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.

Step #2)  If all the tests pass, then try to perform a clean install of Windows:
A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.

Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

Edited March 17, 2018 by usasma
Forum doesn't deal well with nested quotes

[Metallicana974]

I post some of the test while the other i do it tomorrow
And the report collecting tool is stuck on "Waiting for SystemInfo" for more that 2hour now ><" (havent close it wet)
i read that at the end it auto zip but since i wont end do i zip the folder my self and post event if it's not done ?
And for the hwmonitor screen it's not idle (but not hard using either)

admin.zip

Perfmon.zip

[usasma]

Nothing real significant in the Admin logfile.  There are problems with the Killer Network Service.
I'd suggest:
- download a fresh copy of the Killer software
- uninstall the current Killer software and reboot
- install the freshly downloaded Killer software and monitor for further problems.

Please note that there is an alternative tool for the BSOD reports located here:    https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe
What takes the time is the WER section of the MSINFO32 report.  If there's lot's of errors, then it takes a long, long time.
You can also just do these 3 reports manually:

Quote

Upload Dump Files:
NOTE:  If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder.  Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there.  If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP.  If you find it, zip it up and upload it to a free file hosting service.  Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp.  Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file):  http://www.carrona.org/setmini.html
More info on dump file options here: http://support.microsoft.com/kb/254649

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the TEST.NFO file.  If you have difficulties with making this work, please post back.  Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the syteminfo.txt file.  If you have difficulties with making this work, please post back.  Then zip up the .txt file and upload/attach the .zip file with your next post.
NOTE:    Will not work with Windows XP

 

 

[Metallicana974]

here is the report from the other tools

DESKTOP_2213A1D_18_03_2018_04_09_57.zip

[Metallicana974]

Now i start to think that my windows is not a clean install like you say
After windows was install (the iso was from before creator update, maybe outdated), windows update have a lot of update to do maybe it's why fall creator cause me this ramdom issue
Never understand the windows 10 install media tool (does it really include all of those big update ?)
And for hardware test (i hope have time to do some today), i'm pretty sure that my hard drive and Gpu have no problem (since ffxv is the most demanding game i have and it seems to be fine with, also try so stream with it just a few lag predictible since my cpu have trouble with those new generation's game_{(i may think of overclock it oneday)}(and also maybe a bit because my motherboard only support PCIe 2.0 and my my gpu is a 3.0)
But i have my doubt with my psu since my previous motherboard die after a  thunderstorm's night, since it's the only thing that die that night _{(funny fact, on that night where i forgot to shutdown the pc because i fell in sleep, i wake up and he was still running so i shutdown and cut the power button on the psu but when i wake up i was unable to turn it on)}

[usasma]

The Media Creation Tool does not include all of the Cumulative Updates.  My tests show that it still needs 2018-03 after installing (this was about 2 weeks ago).
I install that in the standalone version if there are any problems installing the Windows Update version. 
If it doesn't install then, then I'll install it from a clean boot:  http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows

Link to the 2018-03 update at Microsoft:  https://www.catalog.update.microsoft.com/Search.aspx?q=KB4091290

A nice link for PSU testing:  https://www.bleepingcomputer.com/forums/t/654994/pc-is-crashingfreezing-up-multiple-times-daily/page-2#entry4341756

My wife has the same issue with sleep - then finding it's still awake.  I haven't figured that one out (without a clean install).
I'll try to review your uploads this afternoon - as I'm late for work right now

 

[usasma]

Your UEFI/BIOS (version V22.4) dates from 2018.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and the outdated UEFI/BIOS' may be the cause of some compatibility issues).
 

Only 8 Windows Update hotfixes installed.  Most build 16299 (1709/Fall Creators Update) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

D: drive only has about 1.6% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

Beyond that, there's no sign of software errors that I can see - so I presume it's a hardware problem.

My suggested way to diagnose a hardware problem (3 steps):
Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:
       1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.

Step #2)  If all the tests pass, then try to perform a clean install of Windows:

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [:(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.

Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

[Metallicana974]

- No report of any sign of wirus/malware from Windows Defender
- Seatools for windows - c: pass

Spoiler

(The hdd D: is just where i put series, movies. He have some trouble when to much using (making noise and slow working then stop reading but still turning as if the plateau was unclench, it's was a second hand hdd that i get from the shop where i build/and troubleshoot what where dead on my pc when my motherboard die on that thunderstorm  that why it's unplug most of the time, i just use it as a storage.

For my windows i was using the installation that i get from where i got my key (a friend student gave me the key from the shop of his school (lucky me, there was only one key left, and the install is English only)
So yeah, it's really outdated. And if the Media Creation Tool include at least the Fall creator (and previous major build) i should give it a try
I don't remember the 1st time i did for the fall creator update but the 2nd time i got a error but after relaunch the update it pass (probably why those freeze i guess)
I still have to do the rest of the test, i'll post when it's done
 

[Metallicana974]

ps: just done the scan for d: Ironically it pass too ><" (seems it's really the plateau that is a bit unclench)

[Metallicana974]

hi, when i try to use the windows media creation tool to make a usb installer (or iso) i always get a error:

From what i read, they say it's maybe a languages error, i change it back to the original languages of my install of windows and no changes
And i read also that this https://www.microsoft.com/en-us/software-download/windows10 work only for x32bit and not x64.
I will find another way to create it ><"

Edited April 3, 2018 by Metallicana974

[Metallicana974]

Well, a clean install does not include fall creator update (1709) and by doing this with windows update i got that

 

[Metallicana974]

so i did this troubleshoot tool from https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

here is the report from the the tool (#pdf)
As he say it's fixed, i go start windows update (and doesn't work...)

l.pdf

Edited April 4, 2018 by Metallicana974

[Metallicana974]

additional info:
KB3172729 got a error on windows update

ps: (editing is kinda weird here, sometime here sometime not ><")
Seems my problem is windows ><"
 

[Metallicana974]

Well after another clean install (lol) all the thing is updated without error (unless kb2237602, for windows defender buti don't see it anymore now).
So we will see if my problem came back after all of this ><'

[usasma]

Sorry for the delay in responding.  Glad to hear that you seem to have gotten it sorted out.

 

[Metallicana974]

well bad luck is always on me, still happening...
I'm going to wait for the redstone update (10 avril they start to launch it apparently) and do another try, and juste before verify with not doing any update for a week to see if it's the update or not.
So news soon :3

[Metallicana974]

Hi there, since last time (and actually today) i got a bsod for the first time and well i don't know why, i post the dump if you can watch on it.

I also get yesterday acces to the next windows update (1803 if i'm correct), i will do it after i'm done with some printing stuff that i have a lot to do ><".

 

051918-29375-01.zip

[usasma]

Uninstall the VB Audio VoiceMeeter program.
You can reinstall it once we've found the problem.

If the BSOD's continue after it's uninstalled, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Analysis:

The following is for information purposes only. 
The following information contains the relevant information from the blue screen analysis: 
**************************Sat May 19 03:16:57.388 2018 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\051918-29375-01.dmp]
Windows 10 Kernel Version 16299 MP (6 procs) Free x64
Built by: 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
System Uptime:0 days 23:13:02.158
Probably caused by :memory_corruption
BugCheck 50, {ffffafe3ac2b11cc, 10, ffffafe3ac2b11cc, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments: 
Arg1: ffffafe3ac2b11cc, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: ffffafe3ac2b11cc, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  voicemeeterpro.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

3rd Party Drivers:
The following is for information purposes only. 
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box: 
**************************Sat May 19 03:16:57.388 2018 (UTC - 4:00)**************************
MpKslb41cf12b.sys              Mon Feb 27 20:54:41 1989 (2409FBE1)
vbaudio_vmvaio64_win7.sys      Mon Apr 21 05:05:09 2014 (5354DF45)
vbaudio_vmauxvaio64_win7.sys   Sun Jul  6 03:56:06 2014 (53B90116)
SteamStreamingSpeakers.sys     Thu Jul 20 20:56:15 2017 (5971512F)
SteamStreamingMicrophone.sys   Fri Jul 28 11:33:15 2017 (597B593B)
e2xw10x64.sys                  Thu Aug 31 17:11:04 2017 (59A87B68)
YSDDR0.sys                     Wed Oct 11 01:50:25 2017 (59DDB121)
YSDrv.sys                      Wed Oct 11 03:00:25 2017 (59DDC189)
YSR0.sys                       Wed Oct 11 03:02:05 2017 (59DDC1ED)
nvvad64v.sys                   Thu Dec 14 00:40:29 2017 (5A320ECD)
nvhda64v.sys                   Fri Dec 15 03:17:43 2017 (5A338527)
RfeCo10X64.sys                 Fri Jan  5 11:16:02 2018 (5A4FA4C2)
NvStreamKms.sys                Mon Mar  5 01:17:15 2018 (5A9CE0EB)
nvlddmkm.sys                   Fri Mar 23 19:02:22 2018 (5AB5877E)
xusb22.sys                     ***** Invalid 2002 Invalid 2002 Invalid
 

MpKslb41cf12b.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=vbaudio_vmvaio64_win7.sys
vbaudio_vmauxvaio64_win7.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SteamStreamingSpeakers.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SteamStreamingMicrophone.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=e2xw10x64.sys
YSDDR0.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
YSDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
YSR0.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
RfeCo10X64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys