Okay, I ran Driver Verifier and this is the result I got after making my pc bsod twice.
Minidump: HERE
WhoCrashed Interpretation:
On Fri 12/22/2017 1:31:32 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122217-14359-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Fri 12/22/2017 1:24:54 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: lgbusenum.sys (0xFFFFF80609C801F0)
Bugcheck code: 0xC4 (0x2004, 0xFFFFA00DE05104F8, 0xFFFFF80609C801F0, 0xFFFFC40C14ED80C8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\lgbusenum.sys
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: lgbusenum.sys .
Google query: lgbusenum.sys DRIVER_VERIFIER_DETECTED_VIOLATION
So the Driver Verifier bsod is from my Logitech software? What about the CUSTOM ERROR what is that?
BSOD Last night-------- Minidump: https://1drv.ms/f/s!Ao8buYEJ4rwDg2ToKRrHGnt6IPrA
On Thu 12/21/2017 2:39:59 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122117-17546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8010D72985E, 0xFFFFA40E06CDEEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Minidump: HERE
WhoCrashed Interpretation:
On Fri 12/22/2017 1:31:32 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122217-14359-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Fri 12/22/2017 1:24:54 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: lgbusenum.sys (0xFFFFF80609C801F0)
Bugcheck code: 0xC4 (0x2004, 0xFFFFA00DE05104F8, 0xFFFFF80609C801F0, 0xFFFFC40C14ED80C8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\lgbusenum.sys
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: lgbusenum.sys .
Google query: lgbusenum.sys DRIVER_VERIFIER_DETECTED_VIOLATION
So the Driver Verifier bsod is from my Logitech software? What about the CUSTOM ERROR what is that?
BSOD Last night-------- Minidump: https://1drv.ms/f/s!Ao8buYEJ4rwDg2ToKRrHGnt6IPrA
On Thu 12/21/2017 2:39:59 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122117-17546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8010D72985E, 0xFFFFA40E06CDEEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Facebook
Twitter