cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
wphaskett
Punch Card
Posts: 44
Registered: ‎02-18-2013
Location: US
Views: 10,018
Message 1 of 10

BSOD - vwififlt.sys

I bought a new X1 Carbon (3rd Gen) in late April.  Since then I've been getting an occasional BSOD indicating the problem is with vwififlt.sys file.  I have an Intel  Dual Band Wireless AC-7265 wifi adapter.  I have 8Gb memory, a 512Gb SSD drive, and pretty much everything on the machine, including Windows 8.1 Pro (64bit).  I also purchased a 4yr on-site NBD support agreement with accident coverage.

 

When I contacted Thinkpad support in Atlanta, GA they told me there is nothing wrong with their hardware and this is a Microsoft file; thus a Microsoft support issue.  After getting a BSOD today I contacted Microsoft support.  They told me that Lenovo is responsible for both the hardware and any software that is installed on the machine when delivered.  I quote: "Microsoft's policy on OEM versions of Windows is that the primary support for any technical issues is the machine manufacturer. That is the agreement between us and the OEM i.e Lenovo. You can have them refer to this page though if it helps.  Support for software that was supplied with your PC.  This refers to any software (Office, Windows, third party software) that comes with your machine when you bought it."

 

Is anybody having BSODs using the Intel wifi adapter?  Is anybody have this kind of problem with Lenovo support?

Puppy
Bit Torrent
Posts: 1,822
Registered: ‎11-28-2007
Location: CZ
Views: 10,005
Message 2 of 10

Re: BSOD - vwififlt.sys

Microsoft is right, for OEM software the vendor (Lenovo) is to provide full technical support

 

The vwififlt.sys is Virtual WiFi Filter Driver but this is likely not the root cause. It is a wireless adapter, it can be either wifi or mobile connection (if installed). Download BlueScreenView tool and post the BSOD stack here, it may display the driver on stack that causes it.

 

I suppose you have already updated wifi driver from Lenovo.

__________________________________
ThinkPad (1992 - 2012): R51, X31, X220, Tablet 8.
Do you care about privacy and security ? Leave Google behind
wphaskett
Punch Card
Posts: 44
Registered: ‎02-18-2013
Location: US
Views: 9,978
Message 3 of 10

Re: BSOD - vwififlt.sys

Thanks.  I have updated everything last week for Microsoft and the Thinkpad System update on the 3rd of June.  I've had BSODs on the 19th, 17th, 14th, 13th, 8th, 7th, and 4th in June.  Here's the most recent BSOD view (it looks like the first two are in the stack, as they are in all the above referenced BSODs):

 

ndis.sys    ndis.sys+25f9f    fffff800`b9a53000    fffff800`b9b6a000    0x00117000    0x54d01043    2/2/2015 5:03:15 PM                        
vwififlt.sys    vwififlt.sys+10060    fffff800`baa2a000    fffff800`baa42000    0x00018000    0x5215f81d    8/22/2013 4:38:05 AM                        
ntoskrnl.exe        fffff800`5161f000    fffff800`51db3000    0x00794000    0x550f41a6    3/22/2015 3:26:46 PM                        
hal.dll        fffff800`51db3000    5fd2a3db`51e23000    0x5fd2abdb00070000    0x538bade8    6/1/2014 3:49:12 PM                        
kd.dll        fffff800`507dd000    fffff800`507e6000    0x00009000    0x5215f8bb    8/22/2013 4:40:43 AM                        
mcupdate_GenuineIntel.dll        fffff800`b8eb6000    fffff800`b8f41000    0x0008b000    0x5550f2c6    5/11/2015 11:19:50 AM                        
werkernel.sys        fffff800`b8f41000    fffff800`b8f4f000    0x0000e000    0x5215f8a8    8/22/2013 4:40:24 AM                        
CLFS.SYS        fffff800`b8f4f000    fffff800`b8fb1000    0x00062000    0x54f656f9    3/3/2015 5:51:05 PM                        
tm.sys        fffff800`b8fb1000    fffff800`b8fd3000    0x00022000    0x5215f875    8/22/2013 4:39:33 AM                        
PSHED.dll        fffff800`b8fd3000    fffff800`b8fe8000    0x00015000    0x52346b3f    9/14/2013 6:57:19 AM    Microsoft® Windows® Operating System    Platform Specific Hardware Error Driver    6.3.9600.16384 (winblue_rtm.130821-1623)    Microsoft Corporation    C:\WINDOWS\system32\PSHED.dll    
BOOTVID.dll        fffff800`b8fe8000    fffff800`b8ff2000    0x0000a000    0x5215f8aa    8/22/2013 4:40:26 AM    Microsoft® Windows® Operating System    VGA Boot Driver    6.3.9600.16384 (winblue_rtm.130821-1623)    Microsoft Corporation    C:\WINDOWS\system32\BOOTVID.dll    
CI.dll        fffff800`b8e00000    fffff800`b8e88000    0x00088000    0x548276b0    12/5/2014 8:23:28 PM                        
msrpc.sys        fffff800`b90db000    fffff800`b9138000    0x0005d000    0x5215f86a    8/22/2013 4:39:22 AM                        
Wdf01000.sys        fffff800`b9000000    fffff800`b90cf000    0x000cf000    0x5215f850    8/22/2013 4:38:56 AM                        
WDFLDR.SYS        fffff800`b9138000    fffff800`b9149000    0x00011000    0x5215f857    8/22/2013 4:39:03 AM                        
acpiex.sys        fffff800`b9149000    fffff800`b9161000    0x00018000    0x5215f80b    8/22/2013 4:37:47 AM                        
WppRecorder.sys        fffff800`b9161000    fffff800`b916c000    0x0000b000    0x5215f87c    8/22/2013 4:39:40 AM                        
ACPI.sys        fffff800`b916c000    fffff800`b91f4000    0x00088000    0x54335e2e    10/6/2014 8:29:50 PM                        
WMILIB.SYS        fffff800`b91f4000    fffff800`b91fe000    0x0000a000    0x5215f8a7    8/22/2013 4:40:23 AM                        
msisadrv.sys        fffff800`b90cf000    0052f82b`b90d9000    0x0053002b0000a000    0x5215f857    8/22/2013 4:39:03 AM                        
pci.sys        fffff800`b9229000    fffff000`b9271000    0xfffff80000048000    0x53d0f1d4    7/24/2014 4:45:24 AM                        
cng.sys        fffff800`b9271000    fffff800`b92fc000    0x0008b000    0x55187b0d    3/29/2015 3:22:05 PM                        
tpm.sys        fffff800`b92fc000    fffff800`b9328000    0x0002c000    0x5215f7f1    8/22/2013 4:37:21 AM                        
vdrvroot.sys        fffff800`b9331000    fffff800`b933e000    0x0000d000    0x5215f849    8/22/2013 4:38:49 AM                        
pdc.sys        fffff800`b933e000    fffff800`b935a000    0x0001c000    0x543df950    10/14/2014 9:34:24 PM                        
partmgr.sys        fffff800`b935a000    fffff800`b9372000    0x00018000    0x5434e912    10/8/2014 12:34:42 AM                        
spaceport.sys        fffff800`b9372000    fffff800`b93db000    0x00069000    0x54505527    10/28/2014 7:47:03 PM                        
volmgr.sys        fffff800`b93db000    fffff800`b93f0000    0x00015000    0x5215f889    8/22/2013 4:39:53 AM                        
volmgrx.sys        fffff800`b94ff000    fffff800`b955e000    0x0005f000    0x5215f8a7    8/22/2013 4:40:23 AM                        
mountmgr.sys        fffff800`b955e000    fffff800`b9579000    0x0001b000    0x54333f58    10/6/2014 6:18:16 PM                        
storahci.sys        fffff800`b9579000    fffff800`b9596000    0x0001d000    0x5215f8b7    8/22/2013 4:40:39 AM                        
storport.sys        fffff800`b9596000    fffff800`b95f4000    0x0005e000    0x5423822b    9/24/2014 7:47:07 PM                        
fltmgr.sys        fffff800`b941a000    fffff800`b9476000    0x0005c000    0x53fbf00c    8/25/2014 7:25:16 PM                        
fileinfo.sys        fffff800`b9476000    fffff800`b948c000    0x00016000    0x53089456    2/22/2014 5:13:10 AM                        
Wof.sys        fffff800`b948c000    fffff800`b94b7000    0x0002b000    0x53216bf1    3/13/2014 1:27:29 AM                        
symefasi.sys        fffff800`b9643000    fffff800`b97d3000    0x00190000    0x537fbee6    5/23/2014 2:34:30 PM                        
Ntfs.sys        fffff800`b9822000    fffff800`b9a1c000    0x001fa000    0x54387b6b    10/10/2014 5:35:55 PM                        
ksecdd.sys        fffff800`b9a1c000    fffff800`b9a38000    0x0001c000    0x54505548    10/28/2014 7:47:36 PM                        
pcw.sys        fffff800`b9a38000    fffff800`b9a48000    0x00010000    0x5215cfea    8/22/2013 1:46:34 AM                        
Fs_Rec.sys        fffff800`b9a48000    fffff800`b9a53000    0x0000b000    0x5215cfe9    8/22/2013 1:46:33 AM                        
NETIO.SYS        fffff800`b9b6a000    fffff800`b9be2000    0x00078000    0x546029c5    11/9/2014 7:58:13 PM                        
ksecpkg.sys        fffff800`b9600000    fffff800`b9631000    0x00031000    0x54b338fd    1/11/2015 8:01:17 PM                        
tcpip.sys        fffff800`b9ce3000    fffff800`b9f4f000    0x0026c000    0x546029f7    11/9/2014 7:59:03 PM                        
fwpkclnt.sys        fffff800`b9f4f000    fffff800`b9fbb000    0x0006c000    0x546029a4    11/9/2014 7:57:40 PM                        
wfplwfs.sys        fffff800`b9fbb000    fffff800`b9fe0000    0x00025000    0x54602998    11/9/2014 7:57:28 PM                        
fvevol.sys        fffff800`b9c00000    fffff800`b9c95000    0x00095000    0x534325db    4/7/2014 3:25:31 PM                        
volsnap.sys        fffff800`ba0d5000    fffff800`ba124000    0x0004f000    0x53a21598    6/18/2014 3:41:28 PM                        
rdyboost.sys        fffff800`ba124000    fffff800`ba16a000    0x00046000    0x53089474    2/22/2014 5:13:40 AM                        
mup.sys        fffff800`ba16a000    fffff800`ba181000    0x00017000    0x5215f8ac    8/22/2013 4:40:28 AM                        
intelpep.sys        fffff800`ba181000    fffff800`ba190000    0x0000f000    0x543e1458    10/14/2014 11:29:44 PM                        
IntelPcc.sys        fffff800`ba190000    fffff800`ba1a6000    0x00016000    0x5408f020    9/4/2014 4:05:04 PM                        
disk.sys        fffff800`ba1b2000    fffff800`ba1ce000    0x0001c000    0x5215f883    8/22/2013 4:39:47 AM                        
CLASSPNP.SYS        fffff800`ba000000    fffff800`ba056000    0x00056000    0x5434c9ff    10/7/2014 10:22:07 PM                        
crashdmp.sys        fffff800`ba056000    fffff800`ba06b000    0x00015000    0x5215f893    8/22/2013 4:40:03 AM                        
ccSetx64.sys        fffff800`ba1ce000    fffff800`ba1fa000    0x0002c000    0x52410dcc    9/23/2013 8:58:04 PM                        
SRTSP64.SYS        fffff800`ba473000    fffff800`ba54f000    0x000dc000    0x53e54bed    8/8/2014 3:15:09 PM                        
SRTSPX64.SYS        fffff800`ba54f000    ffffd801`ba564000    0xffffe00100015000    0x539b347a    6/13/2014 10:27:22 AM                        
Ironx64.SYS        fffff800`ba564000    fffff800`ba5a7000    0x00043000    0x537bd6de    5/20/2014 3:27:42 PM                        
SYMEVENT64x86.SYS        fffff800`ba5a7000    fffff800`ba5df000    0x00038000    0x51f32ff2    7/26/2013 7:26:58 PM                        
Null.SYS        fffff800`ba8e3000    fffff800`ba8ec000    0x00009000    0x5215f8a8    8/22/2013 4:40:24 AM                        
Beep.SYS        fffff800`ba8ec000    fffff800`ba8f4000    0x00008000    0x5215f8a8    8/22/2013 4:40:24 AM                        
BasicRender.sys        fffff800`ba8f4000    fffff800`ba902000    0x0000e000    0x5308948a    2/22/2014 5:14:02 AM                        
dxgkrnl.sys        fffff800`baa96000    fffff800`bac16000    0x00180000    0x54505515    10/28/2014 7:46:45 PM                        
watchdog.sys        fffff800`bac16000    fffff800`bac28000    0x00012000    0x530894af    2/22/2014 5:14:39 AM                        
dxgmms1.sys        fffff800`bac28000    fffff800`bac8b000    0x00063000    0x54505506    10/28/2014 7:46:30 PM                        
BasicDisplay.sys        fffff800`bac8b000    fffff800`bac9d000    0x00012000    0x5215f873    8/22/2013 4:39:31 AM                       

[...snipped to reduce characters below 20,000...]

 

Hope this helps.

 

Bill

Puppy
Bit Torrent
Posts: 1,822
Registered: ‎11-28-2007
Location: CZ
Views: 9,965
Message 4 of 10

Re: BSOD - vwififlt.sys

Indeed. Make sure you have latest driver version 17.16.1, System Update is sometimes slow with recent updates:

http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-...

 

Also run chkdsk and sfc commands to check system integrity. If it does not report (and fix) any errors the only way is to enable full memory dump and wait for another BSOD. Then use Microsoft Kernel Debugger with symbols to find out detailed information.

 

Does it happen right after resume from sleep mode or just randomly ? Do you have any antivirus software (other than default Windows Defender) installed ? Do you have LTE mobile connection installed as well ? Here is similar report.

__________________________________
ThinkPad (1992 - 2012): R51, X31, X220, Tablet 8.
Do you care about privacy and security ? Leave Google behind
wphaskett
Punch Card
Posts: 44
Registered: ‎02-18-2013
Location: US
Views: 9,948
Message 5 of 10

Re: BSOD - vwififlt.sys

I have the Intel software v17.16.1 installed and the driver is v17.16.1.2.  This is what the link for getting the new software/driver says it should be so I figure it's already installed. 

 

I ran chkdsk and got no problems.  I then ran sfc /scannow and got the following:

 

- - - - - - - - - - - - - - - - - - - -

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

- - - - - - - - - - - - - - - - - - - -

 

Unfortunately, there's a huge amount of data in the CBS.log and I can't read it.  I do have Symantec Endpoint Protection (unmanaged) 64bit installed.  Have had it for years on my multiple Windows 2008 R2 servers and Windows 7 clients (including my X1's predecessor).  Everything else (Windows Defender, Windows Firewall) is turned off.

 

The link you gave me is in German, but my German is good enough to figure they're suggesting I disable my Sierra Wireless EM7345 4G LTE device.  Is this correct?

wphaskett
Punch Card
Posts: 44
Registered: ‎02-18-2013
Location: US
Views: 9,945
Message 6 of 10

Re: BSOD - vwififlt.sys

I forgot to mention this happens when I un-dock and am running on the WiFi. It also seemed to happen yesterday after I closed the lid for several hours and came back and opened the lid. I may have had to press the [Power] button quickly.
Puppy
Bit Torrent
Posts: 1,822
Registered: ‎11-28-2007
Location: CZ
Views: 9,936
Message 7 of 10

Re: BSOD - vwififlt.sys

Do you have Windows 7 or 8.1 installed ? There was Microsoft Update KB3022345 lately that makes a SFC scan false error message. You can filter useable information from the SFC log by command: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > sfcinfo.txt

 

Yes, try to disable the LTE module for a while, if possible. I understand it is not acceptable permanent solution but you can check whether there is a difference.

 

You can also try to stop the virtual wifi adapter if you don't need it.

__________________________________
ThinkPad (1992 - 2012): R51, X31, X220, Tablet 8.
Do you care about privacy and security ? Leave Google behind
wphaskett
Punch Card
Posts: 44
Registered: ‎02-18-2013
Location: US
Views: 9,921
Message 8 of 10

Re: BSOD - vwififlt.sys

I have Windows 8.1 Pro installed.  When I run "sfc" and "dism" I get different results.

 

- - - - - - - - - - - - - - - - - - - -

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>dism /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption wa
 repaired.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>sfc /verifyonly

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found integrity violations. Details are included
in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in
offline servicing scenarios.

- - - - - - - - - - - - - - - - - - - -

Checking on-line resources (e.g. Google) this scenario is rare (I can't find anything on it).  The "CBS.log" is quite full of stuff and a few lines seem to say there's a difference in the Windows files:

 

2015-06-22 14:42:11, Info                  CSI    0000091e Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\f4b9824b34add00168c80000a418fc1f\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:wAJrdSTUawhs/RawsiNg9RRQFQ6oQM8We6AJ/auSGyM=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-06-22 14:42:11, Info                  CSI    0000091f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-22 14:42:11, Info                  CSI    00000920 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\f4b9824b34add00168c80000a418fc1f\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:iOgJ9zpM/uQDvt0owjVftLgMNGL/hKwbMjRM5vyAQDk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-06-22 14:42:11, Info                  CSI    00000921 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-22 14:42:11, Info                  CSI    00000922 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\6d52854b34add0016bc80000a418fc1f\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:wAJrdSTUawhs/RawsiNg9RRQFQ6oQM8We6AJ/auSGyM=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-06-22 14:42:11, Info                  CSI    00000923 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-22 14:42:11, Info                  CSI    00000924 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
2015-06-22 14:42:11, Info                  CSI    00000925 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\6d52854b34add0016bc80000a418fc1f\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:iOgJ9zpM/uQDvt0owjVftLgMNGL/hKwbMjRM5vyAQDk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-06-22 14:42:11, Info                  CSI    00000926 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

 

Don't ask me what this is about, and I have no idea if this is causing me any problems.  However, you'd think I wouldn't have this with a 2 month old install (I did reinstall the image three times before I got it right).  It also takes me a week to install and configure all the software I need on this machine and to make it look essentially like Windows 7.

 

I'll go ahead and disable the LTE module and the Microsoft Virtual WiFi Miniport Adapter.  Also, the findstring returned what I indicated above.  Thanks, I'll take the X1 offline onto WiFi and see what happens.  Thanks.

 

 

Puppy
Bit Torrent
Posts: 1,822
Registered: ‎11-28-2007
Location: CZ
Views: 9,913
Message 9 of 10

Re: BSOD - vwififlt.sys

That's the SFC false report caused by buggy Microsoft update KB3022345. No worry, there is actually no error.

__________________________________
ThinkPad (1992 - 2012): R51, X31, X220, Tablet 8.
Do you care about privacy and security ? Leave Google behind
wphaskett
Punch Card
Posts: 44
Registered: ‎02-18-2013
Location: US
Views: 9,898
Message 10 of 10

Re: BSOD - vwififlt.sys

My, my...  It's always something.  :-)  Thanks for the information on the "sfc" error caused by a Microsoft update.  I'll keep monitoring my machine looking for a BSOD.

Check out current deals!


Shop current deals

Top Kudoed Authors