Update Intel LAN driver - Downloads for Intel® Ethernet Connection I219-V
If you don't use Intel Driver & Support Assistant, uninstall it
If you don't use Intel Driver & Support Assistant, uninstall it
BSODs everyday
- Thread starter TeodorMarx
- Start date
Verifier, in this minidump 050320-8890-01.dmp (Sat May 2nd 2020 22:18:03) flagged a driver: semav6msr64.sys:
IIRC, it should be part of intel driver update software and, always IIRC, it also caused bsods on my old (intel) system.
Try to uninstall it.
Or to update it!
Current version seems to be 20.4.17.5.
In your log files, I found two versions of it.
1) One is in "C:\Program Files\Intel\SUR\QUEENCREEK\x64\semav6msr64.sys" (dated 10.march.2020 10:31:40)
2) The other one in "C:\Windows\System32\drivers\semav6msr64.sys" (same date... But in another place show 19.july.2019 9:49:03)
DRT (Driver Reference Table) says instead it's a "SEMA Software" driver: Driver Reference Table (DRT) | semav6msr64.sys
Instead, the intel driver e1d68x64.sys, flagged in the last minidump, shows (in all minidumps):
In your logs:
Downloading and unzipping the drivers for your intel Network Adapter Driver, Version 25.0, suitable for Intel Ethernet Connection I219-V, it shows: version 12.18.9.10, 584 KB (598080 bytes), 31 July 2019, 12:52:26).
In conclusion, it seems you have a more recent driver not suitable for your system; and instead of upgrading it, you ought to downgrade it.
Did you find it with a driver updater software? Which one?
Read More:
Try to uninstall it.
Or to update it!
Current version seems to be 20.4.17.5.
In your log files, I found two versions of it.
1) One is in "C:\Program Files\Intel\SUR\QUEENCREEK\x64\semav6msr64.sys" (dated 10.march.2020 10:31:40)
2) The other one in "C:\Windows\System32\drivers\semav6msr64.sys" (same date... But in another place show 19.july.2019 9:49:03)
DRT (Driver Reference Table) says instead it's a "SEMA Software" driver: Driver Reference Table (DRT) | semav6msr64.sys
Instead, the intel driver e1d68x64.sys, flagged in the last minidump, shows (in all minidumps):
Read More:
Read More:
In conclusion, it seems you have a more recent driver not suitable for your system; and instead of upgrading it, you ought to downgrade it.
Did you find it with a driver updater software? Which one?
Last edited:
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
I found and installed the LAN driver from this site : Downloads for Intel® Ethernet Connection I219-V ( just filtered by my OS-Windows 10x64 then i downloaded and installed it ) .
And also i got another version of it, i downloaded it from my motherboard manufacturer's website ( driver version is 23.0 ) . So, i will try to downgrade to 23.0 version as you advised.
Also I did not quite understand about that semav6msr64.sys driver, should i just delete that folder : "C:\Program Files\Intel\SUR\QUEENCREEK\x64\semav6msr64.sys" or "C:\Windows\System32\drivers\semav6msr64.sys" ?
Because i already deleted Intel Driver & Support Assistant like one week ago.
About the network driver: It showed 12.18.9.11 in your logs, but it should be 12.18.9.10 (that's what I saw unzipping the intel package PROWinx64.exe - 66.5 MB (69,788,696 bytes) - 23 Jan 2020).
I found that driver could also be installed by "intel(r) Energy Checker SDK."
But in your pc it seems it was installed by "Intel(R) Computing Improvement Program".
It created these (folders, files, services):
Therefore try to uninstall "Intel(R) Computing Improvement Program".
After this, check if those drivers are still present in your PC (C:\Program Files\Intel\SUR\QUEENCREEK\x64\semav6msr64.sys and C:\Windows\System32\drivers\semav6msr64.sys).
If they will be still there, try to delete them manually (just those two drivers).
I found that driver could also be installed by "intel(r) Energy Checker SDK."
But in your pc it seems it was installed by "Intel(R) Computing Improvement Program".
It created these (folders, files, services):
Therefore try to uninstall "Intel(R) Computing Improvement Program".
After this, check if those drivers are still present in your PC (C:\Program Files\Intel\SUR\QUEENCREEK\x64\semav6msr64.sys and C:\Windows\System32\drivers\semav6msr64.sys).
If they will be still there, try to delete them manually (just those two drivers).
Last edited:
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
I deleted Intel System Usage Report and sema driver from Program files, but today I got another BSOD ( yesterday's bsod included ) : dumps - Google Drive
After today's bsod I also removed semav6msr64.sys from System 32 folder ( idk why, but I couldn't delete it yesterday ), so we need to wait until tomorrow to make sure, that sema....64.sys was the problem. Because I get 1 bsod per day :d
I'd reinstall the more recent intel network driver, but make sure its version is 12.18.9.10.
I.e., have you uninstalled "Intel(R) Computing Improvement Program"?
Or have you removed files from "C:\Program Files\Intel\SUR\QUEENCREEK" ???
The second (more recent) dump shows:
The first one shows:
I.e., the culprits were still there.
I.e., have you uninstalled "Intel(R) Computing Improvement Program"?
Or have you removed files from "C:\Program Files\Intel\SUR\QUEENCREEK" ???
The second (more recent) dump shows:
Read More:
The first one shows:
Read More:
I.e., the culprits were still there.
Last edited:
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
I found only this version on my motherboard manufacturer's site : 12.17.8.9 :c
First I deleted the program, and then the folder itself.
Yeah, I deleted that driver from System 32 folder. But I did it after those bsods I sent.
If I get another bsod I will let you know tomorrow
Upd.: 5 minutes after writing this letter, I received another BSOD. That happened when I tried to run Life is Strange on Steam. And here it is : 050620-8593-01.rar
Upd. 2: I don't know if it is important, but sometimes bsod is accompanied by a loud noise.
Last edited:
Try hardwaremonitor: http://download.cpuid.com/hwmonitor/hwmonitor_1.41.zip
If you install this, what's the version that appears? Intel® Network Adapter Driver for Windows® 10
If you install this, what's the version that appears? Intel® Network Adapter Driver for Windows® 10
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
I ran Resident Evil 2 ( Remake ) and got GPU : 62°C, CPU : 45°C, HDD and SSD somewhere around 32°C and motherboard also around 40°C - didn't have time to screen, because I instantly got another bsod called PAGE_FAULT_IN_NONPAGED_AREA, here it is : 050620-8343-01.rar
I've just installed this driver Intel® Network Adapter Driver for Windows® 10 and got 12.18.9.10 ver. of driver
P.s. : I got F2 version of BIOS, mb I should go back to F3 ?
Re-try verifier... Please read CAREFULLY the following instructions:
- Create a restore point
- Create a system image
(macrium reflect free is a good program, if you don't already have one... Make sure to create a recovery media - i.e., a CD or a USB stick with macrium installed - and test if it works and boot your machine/pc) - Backup your important files (the files you don't want to lose)
- Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
- Read some other tutorials/guides and WARNINGS on internet.
- Unzip on your desktop the file I attached View attachment 59044 and then:
- Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
- Type (copy/paste) in it:
Code:
bcdedit /export c:\DEFAULT-BCDedit-SystemStoreContent powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1" - Press enter
- The previous commands will modify your bcdedit settings, will set the necessary driver verifier settings, will reboot your PC in three minutes (but you can reboot it before).
It will (more precisely):Read More: - After the reboot, open a command prompt and check if verifier settings are enabled with this command
If they are enabled, let verifier run from 24 to 72 hours.Code:
verifier /querysettings
If they are not enabled, inform me.
If you'll get a very fast BSOD after you logged into windows, or after some dozens (tenths?) of minutes, the option resetonbootfail should reset driver verifier settings (and should allow you to boot your machine in a normal state)... But if this won't happen, you'll need to go to safe mode to reset verifier settings. Once safe mode is available, from an elevated command prompt you'll type:Sometimes it is necessary to use a system restore point (or a system image).Code:verifier /reset
- Post here the new verifier dump; from an elevated command prompt, launch this command:
Code:
md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
Ok, I will try to run it tonight, but if I got endless reboots again should I stop verifier or not ? ( first two tries caused constant reboots every 2-5 minutes until I turned off the verifier )
It should turn off by itself, in theory.
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
I got some problems with running your script when I type this in cmd
bcdedit /export c:\DEFAULT-BCDedit-SystemStoreContent
powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"
error :
C: \ Users \ espeo \ desktop \ EnableVerifier.ps1: The name "C: \ Users \ espeo \ desktop \ EnableVerifier.ps1" is not recognized as a command name
the term, function, script file, or executable program. Check the spelling of the name, as well as the presence and right
the path is strong, then try again.
line: 1 character: 1
+ C: \ Users \ espeo \ desktop \ EnableVerifier.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo: ObjectNotFound: (C: \ Users \ espeo \ ... bleVerifier.ps1: String) [], CommandNotFoundException
+ FullyQualifiedErrorId: CommandNotFoundException
Did you unzip (extracted, decompressed) the file I attached -- View attachment 59044 -- on your desktop?
You should see two files and a folder on your desktop: ChangeBCD.bat, EnableVerifier.ps1, driverview-x64.
You should see two files and a folder on your desktop: ChangeBCD.bat, EnableVerifier.ps1, driverview-x64.
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
Yes, I did, but still got this error
Re-try with:
If it shouldn't work: open the file "Non-ms-drivers that verifier is verifying.txt" (present in Created-by-verifier-script, the folder on your desktop), copy its content and add it to the end of this other command (in place of put-your-drivers-here):
Example (with my drivers):
Code:
powershell -executionpolicy unrestricted "C:\Users\espeo\desktop\EnableVerifier.ps1"If it shouldn't work: open the file "Non-ms-drivers that verifier is verifying.txt" (present in Created-by-verifier-script, the folder on your desktop), copy its content and add it to the end of this other command (in place of put-your-drivers-here):
Example (with my drivers):
Read More:
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
t
Upd.: Idk if it works actually, but I have 0 near all those commands
C: \ Windows \ system32> verifier / query
Timestamp: 05/10/2020 03: 57: 23.266
Checker Tool Flags: 0x0002892b
Standard flags:
[X] 0x00000001 Custom Pool.
[X] 0x00000002 Force IRQL check.
[X] 0x00000008 Tracking the pool.
[] 0x00000010 Checking I / O operations.
[X] 0x00000020 Identification of deadlock.
[] 0x00000080 Test direct memory access.
[X] 0x00000100 Security checks.
[X] 0x00000800 Other checks.
[X] 0x00020000 DDI Compliance Check.
Additional flags:
[] 0x00000004 Simulate a random lack of resources.
[] 0x00000200 Forced suspension of I / O request.
[] 0x00000400 Logging IRP.
[] 0x00002000 Invariant MDL check for the stack.
[] 0x00004000 Invariant MDL check for the driver.
[X] 0x00008000 Fuzzy testing of power infrastructure latency.
[] 0x00010000 Checking the port / miniport interface.
[] 0x00040000 Simulation of a systematic lack of resources.
[] 0x00080000 Verification of DDI compliance (optional).
[] 0x00200000 Checking NDIS / WIFI.
[] 0x00800000 Fuzzy testing of kernel synchronization delay.
[] 0x01000000 Verification of the virtual machine parameter.
[] 0x02000000 Code integrity checks.
[X] Indicates that the flag is on.
Verification Tool Statistics Summary
IRQL Raise: 0
Getting active locks: 0
Sync Fulfillment: 0
Truncations: 0
Attempts to allocate pool resources: 0
Successful pool resource allocation operations: 0
Successful pool resource allocation operations for SpecialPool: 0
Pool resource allocation operations without tag: 0
Pool allocation operations without tracking: 0
Unsuccessful attempts to allocate pool resources: 0
Purposefully interrupted pool resource allocation operations: 0
Driver Check List
MODULE: dump_dumpfve.sys, dump_dumpstorport.sys, dump_stomvme.sys, e1d68x64.sys, teedriverw8x64.sys, nvhda64v.sys, nvlddmkm.sys, nvvad64v.sys, nvvhci.sys, ucmcxucsinvppc.sys, 0 0kvvhhc.sys64 unloading: 0)
Thanks, now it works. The second option helped me to run verifier. I will keep you informed.
Upd.: Idk if it works actually, but I have 0 near all those commands
C: \ Windows \ system32> verifier / query
Timestamp: 05/10/2020 03: 57: 23.266
Checker Tool Flags: 0x0002892b
Standard flags:
[X] 0x00000001 Custom Pool.
[X] 0x00000002 Force IRQL check.
[X] 0x00000008 Tracking the pool.
[] 0x00000010 Checking I / O operations.
[X] 0x00000020 Identification of deadlock.
[] 0x00000080 Test direct memory access.
[X] 0x00000100 Security checks.
[X] 0x00000800 Other checks.
[X] 0x00020000 DDI Compliance Check.
Additional flags:
[] 0x00000004 Simulate a random lack of resources.
[] 0x00000200 Forced suspension of I / O request.
[] 0x00000400 Logging IRP.
[] 0x00002000 Invariant MDL check for the stack.
[] 0x00004000 Invariant MDL check for the driver.
[X] 0x00008000 Fuzzy testing of power infrastructure latency.
[] 0x00010000 Checking the port / miniport interface.
[] 0x00040000 Simulation of a systematic lack of resources.
[] 0x00080000 Verification of DDI compliance (optional).
[] 0x00200000 Checking NDIS / WIFI.
[] 0x00800000 Fuzzy testing of kernel synchronization delay.
[] 0x01000000 Verification of the virtual machine parameter.
[] 0x02000000 Code integrity checks.
[X] Indicates that the flag is on.
Verification Tool Statistics Summary
IRQL Raise: 0
Getting active locks: 0
Sync Fulfillment: 0
Truncations: 0
Attempts to allocate pool resources: 0
Successful pool resource allocation operations: 0
Successful pool resource allocation operations for SpecialPool: 0
Pool resource allocation operations without tag: 0
Pool allocation operations without tracking: 0
Unsuccessful attempts to allocate pool resources: 0
Purposefully interrupted pool resource allocation operations: 0
Driver Check List
MODULE: dump_dumpfve.sys, dump_dumpstorport.sys, dump_stomvme.sys, e1d68x64.sys, teedriverw8x64.sys, nvhda64v.sys, nvlddmkm.sys, nvvad64v.sys, nvvhci.sys, ucmcxucsinvppc.sys, 0 0kvvhhc.sys64 unloading: 0)
TeodorMarx
Well-known member
- Apr 26, 2020
- 59
Today after I logged into windows I instantly got 2 BSODs and then went to safe mode and turned off the verifier with cmd help.
Bsods : minidump.rar
Are you using these ones (click)?
Do you have alternative mouse and keyboard to try instead of those ones?
Are there any other devices attached? If yes, please describe them.
I found you have got the file peauth.sys dated Mon 12 Jan 2015 02:52:12, its size (on disk?) seems to be 876 544 (bytes).
Mine is dated 19 Feb 2020 19:29:22, its size is 798 KB (817,152 bytes), its version is 10.0.18.362.295.
Do you, by chance, know why?
Do you have alternative mouse and keyboard to try instead of those ones?
Are there any other devices attached? If yes, please describe them.
I found you have got the file peauth.sys dated Mon 12 Jan 2015 02:52:12, its size (on disk?) seems to be 876 544 (bytes).
Mine is dated 19 Feb 2020 19:29:22, its size is 798 KB (817,152 bytes), its version is 10.0.18.362.295.
Do you, by chance, know why?
Has Sysnative Forums helped you? Please consider donating to help us support the site!