What's new

Windows 10 BSOD paradise, multiple drivers and dumps

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
I'm using the latest drivers available for all devices. BSOD are taking place every day. I ran Windows 10 driver verifier. BSOD occurred with Creative SB X-Fi XtremeMusic Platinum Sound Card PCI device. Both drivers affected: Creative 2015 & Microsoft 2019. When I update I get no sound with the Microsoft Windows Hardware Compatibility Publisher 2019 (C) Creative X-Fi drivers, these drivers were just released on Feb 11 2019 courtesy "Driver Easy". Usual methodology pertaining to this card like switching to 'entertainment mode' under creative audio console did not rectify the issue. disabling/enabling device driver in windows did not rectify issue.)

44954

Other driver verifier issues according to WHOCRASHED, which was accurate. I had disabled one at a time until windows booted cleanly:

1 %SystemRoot%\System32\drivers\lvbflt64.sys (Latest cutting edge logitech webcam software driver (Version Friday, October 26, 2012, 9:42:20 AM)
2 %profram files%\pbfilter.sys (latest peerblock 2014 filter driver)
3 %program files%\Sandboxie\sbiedrv.sys (latest sandboxie 5.28 x64 driver, 2019)
4 C:\EEK\bin64\spp.sys (latest EMISOFT Emergency Kit Scanner 2018.3.1.8572 2019)

I had the same issues before installing EMISOFT. I had no problems in windows 7, big problems in windows 10 on same hardware. Constant daily BSOD; no OC. Not using cam much, if ever. I do use peerblock & sandboxie all the time.

With Nvidia GTX 660 419.35-desktop-win10-64bit drivers windows driver verifier silently hung with black screen late on boot, no BSOD; had to remove them to get into windows, then reinstall them to post here.

DUMP's available here:

  1. Crash Dumps, Creative ctaud2k.sys.7z
  2. Crash_Dumps_spiedrv.sys_pbfilter.sys_lbflt64.sys_spp.sys.7z
Dumps also sent to sandboxie, creative, & microsoft.
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
Yes I am using the latest drivers for every device. This is the one I was using all along; just tested the 2019 one and there was no audio; both gave BSOD with driver verifier. Am getting BSOD constantly in windows without driver verifier. Crashes take place at least once a day, so I will leave driver verifier on to see if it catches anything for the next 12 hours or so.
 

jcgriff2

Site Administrator, Forum General Manager, BSOD Kernel Dump Expert
Staff member
Joined
Feb 19, 2012
Messages
17,461
Location
New Jersey Shore
Have you tried to install any of the drivers in compatibility mode?

Install a Driver in Windows Compatibility Mode
  1. Right-click the driver you want to install and then select Properties.
  2. Select the Compatibility tab.
  3. Under Compatibility Mode, click Run this program in compatibility mode for:
  4. Click the down arrow and select the Windows version of the driver.
  5. Click OK.
  6. Install the driver.
PLEASE - no more 7zip for the dumps. Just use regular zipping (ZIP). Thank You! Unfortunately it takes way too much time to actually extract the dumps and other files. I do appreciate your thoughts, though - as I imagine you used 7-zip to super-compress the files to make the download time shorter for us.

Lastly, have you done any hardware tests on this system?

Most of the Driver Verifier dumps DO NOT flag a 3rd party driver. Quite a few list "memory corruption" as the probable cause and list "NT" (the Windows kernel - which simply cannot be the cause of a BSOD as Microsoft Windows drivers are considered to be sacrosanct. It could be listed as a default of sorts because the real culprit could not be identified).

From one VERIFIER_ENABLED dump - you can see that no 3rd party driver is listed on the stack and that NT is listed on every line (scroll to the right) -
Code:
STACK_TEXT:  
ffff8007`67d02258 fffff800`3fb3ce63 : 00000000`000000c4 00000000`00002004 ffffa887`16ceabc8 fffff800`420e01f0 : nt!KeBugCheckEx
ffff8007`67d02260 fffff800`3f51683b : fffff800`3f6132e4 00000000`00002004 ffffa887`16ceabc8 fffff800`420e01f0 : nt!VerifierBugCheckIfAppropriate+0xdf
ffff8007`67d022a0 fffff800`3fb3442f : 00000000`00000000 ffff8007`67d02340 fffff800`420e01f0 fffff800`3fb3526e : nt!VfReportIssueWithOptions+0x103
ffff8007`67d022f0 fffff800`3fb44ae9 : ffffa887`16ceab70 ffffa887`16ceab70 00000000`00000001 ffffa887`14044280 : nt!VfCheckImageCompliance+0x28b
ffff8007`67d02370 fffff800`3fb30421 : ffffa887`16ceab70 00000000`00000000 ffffa887`16dc1c00 fffff800`3f2a0121 : nt!VfSuspectDriversLoadCallback+0x345
ffff8007`67d023c0 fffff800`3f8780ef : fffff800`420e0118 ffff8007`67d02510 ffffa887`16dc1c10 00000000`00000000 : nt!VfDriverLoadImage+0x24fd
ffff8007`67d02410 fffff800`3f87223b : ffff8007`67d02618 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MmLoadSystemImageEx+0x7ff
ffff8007`67d025c0 fffff800`3f8fbe7b : 00000000`00000000 00000000`00000000 00000000`00000004 ffffd986`00000004 : nt!IopLoadDriver+0x21b
ffff8007`67d027a0 fffff800`3f8de64e : ffffffff`80000201 00000000`00000000 ffffa887`1613b960 ffffffff`80000298 : nt!PipCallDriverAddDeviceQueryRoutine+0x1b7
ffff8007`67d02840 fffff800`3f8de063 : 00000000`00000000 ffff8007`67d02950 ffffa887`160e69a0 00000000`00000010 : nt!PnpCallDriverQueryServiceHelper+0xda
ffff8007`67d028f0 fffff800`3f8dd72b : ffffa887`160e69a0 ffff8007`67d02b18 ffffa887`160e69a0 00000000`00000000 : nt!PipCallDriverAddDevice+0x3f7
ffff8007`67d02aa0 fffff800`3f953b81 : ffffa887`16654600 ffff8007`67d02c01 ffff8007`67d02bb0 ffffa887`00000000 : nt!PipProcessDevNodeTree+0x1af
ffff8007`67d02b60 fffff800`3f367508 : ffffa801`00000003 ffffa887`16654610 ffff8381`00000000 00000000`00000000 : nt!PiProcessStartSystemDevices+0x59
ffff8007`67d02bb0 fffff800`3f2c11ea : ffffa887`16c56240 fffff800`3f641540 ffffa887`1408fce0 ffffa887`00000000 : nt!PnpDeviceActionWorker+0x448
ffff8007`67d02c70 fffff800`3f293bc5 : ffffa887`16c56240 ffffa887`14093080 ffffa887`16c56240 00000000`a9db3ffe : nt!ExpWorkerThread+0x16a
ffff8007`67d02d10 fffff800`3f3c7a3c : ffff8381`78160180 ffffa887`16c56240 fffff800`3f293b70 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8007`67d02d60 00000000`00000000 : ffff8007`67d03000 ffff8007`67cfd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c
Where nt! is listed - on some lines there should be the name of a 3rd party (non-Microsoft) driver.

Many of the dumps read like unknown hardware failure dumps to me. I'd like to hear what the others in this thread have to say about this.

Please humor me and run memtest86+ one stick at a time; alternate the slots -

Test RAM with memtest.org MemTest86+

Thank you.

Regards. . .

jcgriff2
 
Last edited:

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
Please explain this as it relates to your claims that it could be ram issues. The microsoft windows compatibility driver for X-Fi resulted in no sound. Errors were confirmed according to WHOCRASHED, which was accurate. The same crashes occurred for the same drivers over and over again. As I had disabled the offending drivers one at a time I eventually made it into windows which successfully ran for 16 hours with verifier enabled, along with torrenting software to push the hardware somewhat. However, when re-installing sandboxie & creative ctaud2k.sys drivers in windows with verifier enabled, windows immediately hung. This cannot be due to memory corruption. These worked fine in windows 7 for many years without any issues. I had hanging and crashing in windows 7 was almost unheard of.
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
This was all just using verifier anyway; I was told by sandboxie developers that "driver verifier does not work with sandboxie"... so if you can determine which dump was related to the sandboxie driver, and let me know what the results were, aka memory corruption and the like, that would be appreciated.
 
Last edited:

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
This was all just using verifier anyway; without it i was receiving crashes so I will take note of these and send the dumps for further analysis, if there is more memory corruption detected then i will consider doing some memtests, that can take days.
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
Please tell me what you see from the results of the following dump:

On Tue 3/12/2019 11:25:25 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031219-12609-01.dmp
This was probably caused by the following module: sbiedrv.sys (0xFFFFF8047E52F387)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF8047E52F387, 0x0, 0x786F6273)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Program Files\Sandboxie\SbieDrv.sys
product: Sandboxie
company: Sandboxie Holdings, LLC
description: Sandboxie Kernel Mode Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: sbiedrv.sys (Sandboxie Kernel Mode Driver, Sandboxie Holdings, LLC).
Google query: sbiedrv.sys Sandboxie Holdings, LLC DRIVER_VERIFIER_DETECTED_VIOLATION
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
Also I am trying to get symbols for ntsokrnl the latest build of 1809, and its failing; do you know how I can do this?

Code:
C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0>"C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\symchk.exe" /v /if ntoskrnl.exe /s SRV*E:\SymbolsStore*http://msdl.microsoft.com/download/symbols

Code:
[SYMCHK] Searching for symbols to C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0\ntoskrnl.exe in path SRV*E:\SymbolsStore*http://msdl.microsoft.com/download/symbols
DBGHELP: Symbol Search Path: SRV*E:\SymbolsStore*http://msdl.microsoft.com/download/symbols
[SYMCHK] Using search path "SRV*E:\SymbolsStore*http://msdl.microsoft.com/download/symbols"
DBGHELP: No header for C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0\ntoskrnl.exe.  Searching for image on disk
DBGHELP: C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0\ntoskrnl.exe - OK
SYMSRV:  BYINDEX: 0x1
         E:\SymbolsStore*http://msdl.microsoft.com/download/symbols
         ntkrnlmp.pdb
         99DE394F56795BA4DDAEBA33444A9F1A1
SYMSRV:  UNC: E:\SymbolsStore\ntkrnlmp.pdb\99DE394F56795BA4DDAEBA33444A9F1A1\ntkrnlmp.pdb - path not found
SYMSRV:  UNC: E:\SymbolsStore\ntkrnlmp.pdb\99DE394F56795BA4DDAEBA33444A9F1A1\ntkrnlmp.pd_ - path not found
SYMSRV:  UNC: E:\SymbolsStore\ntkrnlmp.pdb\99DE394F56795BA4DDAEBA33444A9F1A1\file.ptr - path not found
SYMSRV:  HTTPGET: /download/symbols/index2.txt
SYMSRV:  HttpQueryInfo: 80190190 - HTTP_STATUS_BAD_REQUEST
SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/99DE394F56795BA4DDAEBA33444A9F1A1/ntkrnlmp.pdb
SYMSRV:  HttpSendRequest: 800C2EFD - ERROR_INTERNET_CANNOT_CONNECT
SYMSRV:  RESULT: 0x800C2EFD
DBGHELP: ntoskrnl - no symbols loaded
[SYMCHK] MODULE64 Info ----------------------
[SYMCHK] Struct size: 1680 bytes
[SYMCHK] Base: 0x140000000
[SYMCHK] Image size: 10940416 bytes
[SYMCHK] Date: 0xdeacb3ca
[SYMCHK] Checksum: 0x00944870
[SYMCHK] NumSyms: 0
[SYMCHK] SymType: SymNone
[SYMCHK] ModName: ntoskrnl
[SYMCHK] ImageName: C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0\ntoskrnl.exe
[SYMCHK] LoadedImage: C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0\ntoskrnl.exe
[SYMCHK] PDB: ""
[SYMCHK] CV: RSDS
[SYMCHK] CV DWORD: 0x53445352
[SYMCHK] CV Data:  ntkrnlmp.pdb
[SYMCHK] PDB Sig:  0
[SYMCHK] PDB7 Sig: {99DE394F-5679-5BA4-DDAE-BA33444A9F1A}
[SYMCHK] Age: 1
[SYMCHK] PDB Matched:  TRUE
[SYMCHK] DBG Matched:  TRUE
[SYMCHK] Line nubmers: FALSE
[SYMCHK] Global syms:  FALSE
[SYMCHK] Type Info:    FALSE
[SYMCHK] ------------------------------------
SymbolCheckVersion  0x00000002
Result              0x00010001
DbgFilename         ntoskrnl.dbg
DbgTimeDateStamp    0x00000000
DbgSizeOfImage      0x00000000
DbgChecksum         0x00000000
PdbFilename         ntkrnlmp.pdb
PdbSignature        {99DE394F-5679-5BA4-DDAE-BA33444A9F1A}
PdbDbiAge           0x00000001
[SYMCHK] [ 0x00000000 - 0x00010001 ] Checked "C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0\ntoskrnl.exe"
SYMCHK: ntoskrnl.exe         FAILED  - ntkrnlmp.pdb mismatched or not found

SYMCHK: FAILED files = 1
SYMCHK: PASSED + IGNORED files = 0

C:\Windows\WinSxS\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.348_none_e0fbef6139ca49a0>
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
I have previously run memtest for 24 hours without error on this same system. I have run linpack extreme for many hours without error; these errors take place under zero work load.
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
No I have not tried installing a driver in compatibility mode; I will consider this in the future, thank you. I have made a slight change in my drivers already, and will see if this fixed the crashing issue; if it has not gone away I will try one at a time with compatibility mode. I switched from the amdkmpfd.sys version, which was automatically installed for my intel board mind you, to a generic windows driver that claims to be from 2006 but is signed 2018 & "created" Jan 7 2019.

44997
 
Last edited:

jcgriff2

Site Administrator, Forum General Manager, BSOD Kernel Dump Expert
Staff member
Joined
Feb 19, 2012
Messages
17,461
Location
New Jersey Shore
Please explain this as it relates to your claims that it could be ram issues. The microsoft windows compatibility driver for X-Fi resulted in no sound. Errors were confirmed according to WHOCRASHED, which was accurate. The same crashes occurred for the same drivers over and over again. As I had disabled the offending drivers one at a time I eventually made it into windows which successfully ran for 16 hours with verifier enabled, along with torrenting software to push the hardware somewhat. However, when re-installing sandboxie & creative ctaud2k.sys drivers in windows with verifier enabled, windows immediately hung. This cannot be due to memory corruption. These worked fine in windows 7 for many years without any issues. I had hanging and crashing in windows 7 was almost unheard of.
I can show you where WHOCRASHED is wrong - often.

That is why we use Windbg.

As far as RAM - I asked you to test it because you have VERIFIER_ENABLED BSODs that name "memory corruption" as the probable cause and no 3rd party driver has been flagged.

When no 3rd party driver is flagged in a VERIFIER_ENABLED BSOD, it is safe to assume that unknown hardware failure is the cause.

Here is a summary for the dumps that I processed. I honestly got lost in your 7z files because you had 7z files inside 7z files and duplicate dump files.

Read More:
Drivers that appear to be flagged by Driver Verifier -

Driver Reference Table (DRT) | pbfilter.sys
https://www.sysnative.com/drivers/driver.php?id=SbieDrv.sys

epp.sys - Emsisoft emergency kit

I would remove whatever these drivers belong to from your system.

You are obviously having compatibility issues with Windows 10.

I wish I had an answer for you about the Creative audio drivers. You may have to revert to prior Windows or upgrade audio card, if you have a desktop.

Regards. . .

jcgriff2
 

jcgriff2

Site Administrator, Forum General Manager, BSOD Kernel Dump Expert
Staff member
Joined
Feb 19, 2012
Messages
17,461
Location
New Jersey Shore
You somewhere asked about ntoskrnl.exe - it is the Windows kernel ("NT" in my prior post) and can never be the cause of a BSOD.

I did not encounter any symbol errors, but I don't know if I processed all of the dumps either. You may be getting symbol errors on newer versions of Windows 10 as the symbol files may not have yet been added to the Microsoft symbol server - MSDL Sym Site.
 

jcgriff2

Site Administrator, Forum General Manager, BSOD Kernel Dump Expert
Staff member
Joined
Feb 19, 2012
Messages
17,461
Location
New Jersey Shore
This was all just using verifier anyway; I was told by sandboxie developers that "driver verifier does not work with sandboxie"... so if you can determine which dump was related to the sandboxie driver, and let me know what the results were, aka memory corruption and the like, that would be appreciated.
That is absurd.

The likely reason that Sandboxie "doesn't work" with Driver Verifier is because Driver Verifier flags the driver as it is probably poorly written and can't pass Driver Verifier's checks.

System up-time was just 43 seconds when Sandboxie was flagged. It also somehow dragged win32k.sys (Microsoft driver) in with it.

Probable cause - memory corruption

Code:
System Uptime: 0 days 0:00:43.858
*** WARNING: Unable to verify timestamp for SbieDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for SbieDrv.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Every 3rd party driver should be able to pass Driver Verifier's tests. I in fact believe they do to be digitally signed.

Regards. . .

jcgriff2
 

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
Thank you, yes I believe there is a really terrible symbol lag time, I am using the latest 1809 build. I've also heard similar stories about whocrashed by other individuals, who claim it can be very wrong, however in my circumstance it is in fact the opposite. So I will recommend at the very least, multiple dump analyzers from now on, but certainly whocrashed. I would not have been able to boot into windows and WinDBG failed to detect a faulting driver obviously.... the latest whocrashed 6.6.0 detected lvbflt64.sys in the BSOD; its a logitech cam driver I rarely use and has been for the most part disabled in windows.

WinDBG

Code:
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031219-13031-01.dmp]

Built by: 17763.1.amd64fre.rs5_release.180914-1434
Debug session time: Wed Mar 13 01:38:37.028 2019 (UTC - 4:00)
System Uptime: 0 days 0:00:20.823
Probably caused by : memory_corruption
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_2004
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 000000C4
Arguments 00000000`00002004 ffff8b06`eaf51b28 fffff805`5ab50208 ffffc888`5354d320
VS

Whocrashed:
Code:
On Tue 3/12/2019 10:38:37 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031219-13031-01.dmp
This was probably caused by the following module: lvbflt64.sys (0xFFFFF8055AB50208)
Bugcheck code: 0xC4 (0x2004, 0xFFFF8B06EAF51B28, 0xFFFFF8055AB50208, 0xFFFFC8885354D320)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\lvbflt64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech USB Video Class Filter Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: lvbflt64.sys (Logitech USB Video Class Filter Driver, Logitech Inc.).
Google query: lvbflt64.sys Logitech Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
After disabling this under /currrentcontrolset/services/* my PC booted up straight away. With it enabled it crashed. So WinDBG is inadequate here. Whocrashed won.
 
Last edited:

ravenize

Well-known member
Joined
Feb 21, 2018
Messages
176
This is the free version of whocrashed 6.6.0 also; & because the crashes ended immediately after disabling these resource light non-critical drivers, I don't suspect memory corruption is the problem. They are probably poorly written/outdated drivers as you suggested.
 
Last edited:

jcgriff2

Site Administrator, Forum General Manager, BSOD Kernel Dump Expert
Staff member
Joined
Feb 19, 2012
Messages
17,461
Location
New Jersey Shore
Thank you, yes I believe there is a really terrible symbol lag time, I am using the latest 1809 build. I've also heard similar stories about whocrashed by other individuals, who claim it can be very wrong, however in my circumstance it is in fact the opposite. So I will recommend at the very least, multiple dump analyzers from now on, but certainly whocrashed. I would not have been able to boot into windows and WinDBG failed to detect a faulting driver obviously.... the latest whocrashed 6.6.0 detected lvbflt64.sys in the BSOD; its a logitech cam driver I rarely use and has been for the most part disabled in windows.

WinDBG

Code:
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031219-13031-01.dmp]

Built by: 17763.1.amd64fre.rs5_release.180914-1434
Debug session time: Wed Mar 13 01:38:37.028 2019 (UTC - 4:00)
System Uptime: 0 days 0:00:20.823
Probably caused by : memory_corruption
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR: 0xc4_2004
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
Bugcheck code 000000C4
Arguments 00000000`00002004 ffff8b06`eaf51b28 fffff805`5ab50208 ffffc888`5354d320
VS

Whocrashed:
Code:
On Tue 3/12/2019 10:38:37 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031219-13031-01.dmp
This was probably caused by the following module: lvbflt64.sys (0xFFFFF8055AB50208)
Bugcheck code: 0xC4 (0x2004, 0xFFFF8B06EAF51B28, 0xFFFFF8055AB50208, 0xFFFFC8885354D320)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\lvbflt64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech USB Video Class Filter Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: lvbflt64.sys (Logitech USB Video Class Filter Driver, Logitech Inc.).
Google query: lvbflt64.sys Logitech Inc. DRIVER_VERIFIER_DETECTED_VIOLATION
After disabling this under /currrentcontrolset/services/* my PC booted up straight away. With it enabled it crashed. So WinDBG is inadequate here. Whocrashed won.
Those are 2 different dump file outputs -- look at the time of the BSODs, which I have highlighted in yellow.

They are 2 different dumps it appears.

John
 

jcgriff2

Site Administrator, Forum General Manager, BSOD Kernel Dump Expert
Staff member
Joined
Feb 19, 2012
Messages
17,461
Location
New Jersey Shore
This is the free version of whocrashed 6.6.0 also; & because the crashes ended immediately after disabling these resource light non-critical drivers, I don't suspect memory corruption is the problem. They are probably poorly written/outdated drivers as you suggested.
I agree with you that any dump that had a 0xc4 bugcheck and named a 3rd party driver --- the 3rd party driver gets my vote as the culprit.
 
Last edited:
Top