Specs:
Dell Inspiron 5458
Intel i7-5500U
8 GB RAM
I've been dealing with this for quite some time now, and am at a loss for a solution. I've tried taking it to my school's IT, but they've not been much help at all. They simply performed scans and fresh installed the BIOS for my system. I've been having BSOD issues for the past couple of weeks, and though they are intermittent, they are frequent enough to be a nuisance. I've been recording the past several or so BSOD stop errors, and they are as follows:
IRQL NOT LESS OR EQUAL
IRQL NOT LESS OR EQUAL
DRIVER OVERRAN STACK BUFFER
BAD POOL HEADER
DPC WATCHDOG VIOLATION
There have been more, but I seem to have failed to record them. If this is useful information, I ran verifier.exe from the command prompt and when that happened I got consistent blue screens on startup until I reset that command. If any more information is necessary, I will gladly try to cooperate and provide it. I ask for some patience however, as I am both relatively new to this and on a college schedule. Thank you for your time.
UPDATE:
Thank you all for your assistance. I managed to get rid of the scvp virtual bus controller driver, and isolated the last and most recent minidump files and analyzed them with whocrashed. As of right now, it lists only the cyberlink driver as the problematic third party driver. Currently I'm uninstalling cyberlink completely, as I don't see a need for it especially if it is problematic, and apparently from the information from the Uninstall Programs interface, cyberlink was installed recently somewhere in the middle of July, and I have no recollection of this actually occurring. I'll post the most recent minidump files I have and the updated whocrashed information.
Recent Minidumps
Again, all of this help is really appreciated; thanks a lot.
Dell Inspiron 5458
Intel i7-5500U
8 GB RAM
I've been dealing with this for quite some time now, and am at a loss for a solution. I've tried taking it to my school's IT, but they've not been much help at all. They simply performed scans and fresh installed the BIOS for my system. I've been having BSOD issues for the past couple of weeks, and though they are intermittent, they are frequent enough to be a nuisance. I've been recording the past several or so BSOD stop errors, and they are as follows:
IRQL NOT LESS OR EQUAL
IRQL NOT LESS OR EQUAL
DRIVER OVERRAN STACK BUFFER
BAD POOL HEADER
DPC WATCHDOG VIOLATION
There have been more, but I seem to have failed to record them. If this is useful information, I ran verifier.exe from the command prompt and when that happened I got consistent blue screens on startup until I reset that command. If any more information is necessary, I will gladly try to cooperate and provide it. I ask for some patience however, as I am both relatively new to this and on a college schedule. Thank you for your time.
UPDATE:
Thank you all for your assistance. I managed to get rid of the scvp virtual bus controller driver, and isolated the last and most recent minidump files and analyzed them with whocrashed. As of right now, it lists only the cyberlink driver as the problematic third party driver. Currently I'm uninstalling cyberlink completely, as I don't see a need for it especially if it is problematic, and apparently from the information from the Uninstall Programs interface, cyberlink was installed recently somewhere in the middle of July, and I have no recollection of this actually occurring. I'll post the most recent minidump files I have and the updated whocrashed information.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 8/8/2017 1:24:18 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080817-26781-01.dmp
This was probably caused by the following module: clvirtualdrive.sys (CLVirtualDrive+0x4D45)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80355A04D45, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\clvirtualdrive.sys
product: CyberLink Virtual Device Driver
company: CyberLink
description: It is a virtual device driver which could create multiple virtual devices and mount image files.
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: clvirtualdrive.sys (It is a virtual device driver which could create multiple virtual devices and mount image files., CyberLink).
Google query: CyberLink DRIVER_VERIFIER_DETECTED_VIOLATION
On Tue 8/8/2017 1:24:18 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: clvirtualdrive.sys (CLVirtualDrive+0x4D45)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80355A04D45, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\clvirtualdrive.sys
product: CyberLink Virtual Device Driver
company: CyberLink
description: It is a virtual device driver which could create multiple virtual devices and mount image files.
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: clvirtualdrive.sys (It is a virtual device driver which could create multiple virtual devices and mount image files., CyberLink).
Google query: CyberLink DRIVER_VERIFIER_DETECTED_VIOLATION
On Mon 8/7/2017 8:58:10 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-41218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x19 (0x3, 0xFFFFD7812B720940, 0x2ADEA6C0FFFFD781, 0xFFFFD7812B720940)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 8/7/2017 8:45:29 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-39750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x18 (0x0, 0xFFFFC9006CF94A20, 0x2, 0xFFFFFFFF00005BFE)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 8/7/2017 8:25:55 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-41390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41791, 0xFFFF9380002DEA60, 0xFFFFE30C7D8F8F38, 0x2000040000408E3)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 8/8/2017 1:24:18 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080817-26781-01.dmp
This was probably caused by the following module: clvirtualdrive.sys (CLVirtualDrive+0x4D45)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80355A04D45, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\clvirtualdrive.sys
product: CyberLink Virtual Device Driver
company: CyberLink
description: It is a virtual device driver which could create multiple virtual devices and mount image files.
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: clvirtualdrive.sys (It is a virtual device driver which could create multiple virtual devices and mount image files., CyberLink).
Google query: CyberLink DRIVER_VERIFIER_DETECTED_VIOLATION
On Tue 8/8/2017 1:24:18 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: clvirtualdrive.sys (CLVirtualDrive+0x4D45)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80355A04D45, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\clvirtualdrive.sys
product: CyberLink Virtual Device Driver
company: CyberLink
description: It is a virtual device driver which could create multiple virtual devices and mount image files.
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: clvirtualdrive.sys (It is a virtual device driver which could create multiple virtual devices and mount image files., CyberLink).
Google query: CyberLink DRIVER_VERIFIER_DETECTED_VIOLATION
On Mon 8/7/2017 8:58:10 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-41218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x19 (0x3, 0xFFFFD7812B720940, 0x2ADEA6C0FFFFD781, 0xFFFFD7812B720940)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 8/7/2017 8:45:29 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-39750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x18 (0x0, 0xFFFFC9006CF94A20, 0x2, 0xFFFFFFFF00005BFE)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 8/7/2017 8:25:55 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\080717-41390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41791, 0xFFFF9380002DEA60, 0xFFFFE30C7D8F8F38, 0x2000040000408E3)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Recent Minidumps
Again, all of this help is really appreciated; thanks a lot.
Facebook
Twitter
Instagram