mwac.sys throwing DRIVER_VERIFIER_DETECTED_VIOLATION errors

[seto]

Recently, I've been suffering from hard driver crashes from mwsac.sys

 

I have already validated my memory hardware with MemTest86 and the memory passes with multiple runs,.

 

The mwsac.sys error is sporadic, no pattern with what is running. It doesn't happen a lot, but it does happen.

 

I am zipping up the dmp files as well as the latest WhoCrashed analysis:

 

 

System Information (local)

Computer name: BASESTAR
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH X79
CPU: GenuineIntel Intel® Core i7-3820 CPU @ 3.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 51476516864 bytes total



 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 10/13/2015 6:46:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-20187-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFE00045398970, 0xFFFFE00044EE6190, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. 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: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation DRIVER_VERIFIER_DETECTED_VIOLATION


 

Minidump.zip

[usasma]

Sorry for the delay in responding, I didn't receive notification that you'd posted.

 

Please ensure that Driver Verifier is turned off.  To do this, open up verifier.exe and select "Delete existing settings" and click on "Finish".

Reboot for the changes to take effect.

FYI - the purpose of Driver Verifier is to cause a BSOD that will (hopefully) point out the misbehaving driver.

 

If Driver Verifier isn't enabled (if it's already turned off), please let us know also.

 

Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  https://forums.malwarebytes.org/index.php?/topic/170037-blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.  i5 and i7 processors can be "auto-overclocked" by using Intel's TurboBoost feature.  If so, it's safe to disregard this caution.

 

Processor may be overclocked!
Expected Frequency:   3600
Actual Frequency:     4539
Overclock Ratio:      1.26083

 

Your UEFI/BIOS (version 4801) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.

 

Please update the following older drivers to the latest, W10 compatible version.  To do this:

- download the latest, W10 compatible version from the manufacturer's website (I am unable to access the Asus site for your motherboard at this time)

- uninstall the program associated with this driver using Control Panel...Programs and Features (DO NOT use Device Manager unless there is no other way to remove this device)

- install the freshly downloaded software.

 

SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)

- USBXpress Development Kit

 

SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)

- USBXpress Development Kit

 

SaiK0DC5.sys                Wed Dec  8 06:04:20 2010 (4CFF6634)

- Saitek Hid Driver

 

rc32xx.sys                  Tue Dec 11 01:57:53 2012 (50C6D971)

- RC32XX Miniport Driver from HighPoint Technologies. Inc. RocketCache 32XX

 

mv91cons.sys                Fri Oct 11 00:36:26 2013 (5257804A)

- Marvell 6G SATA Controller

 

If unable to update any of these drivers, post back for further assistance.

It may be that some of these drivers are not W10 compatible, but we'll work on that if they can't be updated.

 

Analysis:
The following is for informational purposes only.
**************************Tue Oct 13 14:46:48.711 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\101315-20187-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16515.amd64fre.th1.150916-2039
System Uptime:0 days 14:11:29.425
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :mwac.sys
BugCheck C4, {62, ffffe00045398970, ffffe00044ee6190, 1}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffe00045398970, name of the driver having the issue.
Arg3: ffffe00044ee6190, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
    Type !verifier 3 drivername.sys for info on the allocations
    that were leaked that caused the bugcheck.
BUGCHECK_STR:  0xc4_62
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_mwac.sys
CPUID:        "Intel® Core i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: 4539
 
Processor may be overclocked!
Expected Frequency:   3600
Actual Frequency:     4539
Overclock Ratio:      1.26083
 
  BIOS Version                  4801
  BIOS Release Date             07/25/2014
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 13 00:33:01.220 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\101315-21140-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16515.amd64fre.th1.150916-2039
System Uptime:0 days 6:32:59.935
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :mwac.sys
BugCheck C4, {62, ffffe001fbb65c20, ffffe0020af79010, 1}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffe001fbb65c20, name of the driver having the issue.
Arg3: ffffe0020af79010, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
    Type !verifier 3 drivername.sys for info on the allocations
    that were leaked that caused the bugcheck.
BUGCHECK_STR:  0xc4_62
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_mwac.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct  6 15:56:02.770 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\100615-79515-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16515.amd64fre.th1.150916-2039
System Uptime:0 days 1:19:12.484
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :mwac.sys
BugCheck C4, {62, ffffe001b7d4bcb0, ffffe001b7dec1f0, 1}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffe001b7d4bcb0, name of the driver having the issue.
Arg3: ffffe001b7dec1f0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
    Type !verifier 3 drivername.sys for info on the allocations
    that were leaked that caused the bugcheck.
BUGCHECK_STR:  0xc4_62
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_mwac.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 30 16:07:29.841 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\093015-72906-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16463.amd64fre.th1.150819-1946
System Uptime:0 days 20:52:47.524
*** WARNING: Unable to verify timestamp for win32kbase.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kbase.sys
Probably caused by :win32kbase.sys ( win32kbase+417d )
BugCheck A, {370600000000, 2, 1, fffff8015aebf96d}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000370600000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8015aebf96d, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  wlmail.exe
FAILURE_BUCKET_ID: AV_win32kbase+417d
CPUID:        "Intel® Core i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: 4550
 
Processor may be overclocked!
Expected Frequency:   3600
Actual Frequency:     4550
Overclock Ratio:      1.26389

 

  BIOS Version                  4801
  BIOS Release Date             07/25/2014
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
Any drivers in RED should be updated or removed from your system. And should have been discussed in the body of my post.
**************************Tue Oct 13 14:46:48.711 2015 (UTC - 4:00)**************************
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
SaiK0DC5.sys                Wed Dec  8 06:04:20 2010 (4CFF6634)
rc32xx.sys                  Tue Dec 11 01:57:53 2012 (50C6D971)
mv91cons.sys                Fri Oct 11 00:36:26 2013 (5257804A)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
mbam.sys                    Wed Sep  3 13:50:25 2014 (540754E1)
cpuz138_x64.sys             Thu Feb 26 02:04:34 2015 (54EEC582)
e1i63x64.sys                Thu Mar 26 16:24:57 2015 (55146B19)
mbamchameleon.sys           Fri May  8 13:50:15 2015 (554CF757)
asstahci64.sys              Tue Jun 16 23:36:23 2015 (5580EB37)
RTKVHD64.sys                Thu Jun 18 06:45:05 2015 (5582A131)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
intelppm.sys                Thu Jul  9 23:12:59 2015 (559F383B)
nvlddmkm.sys                Sun Sep 13 17:12:24 2015 (55F5E6B8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 30 16:07:29.841 2015 (UTC - 4:00)**************************
MBAMSwissArmy.sys           Mon Apr 13 15:29:19 2015 (552C190F)
http://www.carrona.org/drivers/driver.php?id=SiLib.sys
http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys
SaiK0DC5.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
rc32xx.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=mv91cons.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=mbamchameleon.sys
asstahci64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys

 

[seto]

I updated to the latest Anti-Malwarrebytes exe, as well as making sure that I was not overclocking. At this time, I am no longer getting any random driver crashes.

[seto]

I was too quick with the reply. As soon as I hit submit, the system crashed again.

 

 

System Information (local)

Computer name: BASESTAR
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH X79
CPU: GenuineIntel Intel® Core i7-3820 CPU @ 3.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 51476516864 bytes total



 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 10/18/2015 8:34:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-22796-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFE0020EE6CAC0, 0xFFFFE00200D57CC0, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. 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: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation DRIVER_VERIFIER_DETECTED_VIOLATION



On Sun 10/18/2015 8:34:04 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFE0020EE6CAC0, 0xFFFFE00200D57CC0, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. 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.

 

minidumnp.zip

[usasma]

Is Driver Verifier still turned on?

Have you checked the verifier.exe application to ensure that it's not turned on?

Driver Verifier is supposed to cause a BSOD - that's what it does when it stresses the drivers.

The hope is that the verifier enabled memory dump will reveal the true cause of the crash.

 

It's possible that one of the other drivers is actually causing MalwareBytes to crash.

I particularly suspect these older drivers:

 

SaiK0DC5.sys - this driver hasn't been added to the DRT as of this run. This is a driver for the Saitek device that is installed on your system.  Please search Google/Bing for the driver if additional information is needed.
 

rc32xx.sys - this driver hasn't been added to the DRT as of this run. This is a driver for the Highpoint RocketCache 32XX device that is installed on your system.  Please search Google/Bing for the driver if additional information is needed.

 

mv91cons.sys  http://www.carrona.org/drivers/driver.php?id=mv91cons.sys

These drivers will either need to be updated to W10 compatible versions - or they will have to be uninstalled from your system, and the hardware associated with them will have to be physically removed from your system (post back if there are difficulties with this)

 

MalwareBytes is still blamed in this Driver Verifier enabled memory dump.

You'll need to:

1)  uninstall MalwareBytes (temporarily)

2)  wait to see if the system BSOD's again

3)  if it does BSOD again, then run Driver Verifier again (after uploading the memory dump here).

 

Analysis:
The following is for informational purposes only.
**************************Sun Oct 18 16:34:04.261 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\101815-22796-01.dmp]
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16545.amd64fre.th1.150930-1750
System Uptime:1 days 20:31:20.024
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :mwac.sys

BugCheck C4, {62, ffffe0020ee6cac0, ffffe00200d57cc0, 1}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
 
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
 
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffe0020ee6cac0, name of the driver having the issue.
Arg3: ffffe00200d57cc0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
    Type !verifier 3 drivername.sys for info on the allocations
    that were leaked that caused the bugcheck.
BUGCHECK_STR:  0xc4_62
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_mwac.sys

CPUID:        "Intel® Core i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: 3600
 
  BIOS Version                  4801
  BIOS Release Date             07/25/2014
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             SABERTOOTH X79
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
Any drivers in RED should be updated or removed from your system. And should have been discussed in the body of my post.
**************************Sun Oct 18 16:34:04.261 2015 (UTC - 4:00)**************************
SaiK0DC5.sys                Wed Dec  8 06:04:20 2010 (4CFF6634)
rc32xx.sys                  Tue Dec 11 01:57:53 2012 (50C6D971)
mv91cons.sys                Fri Oct 11 00:36:26 2013 (5257804A)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
e1c65x64.sys                Sun Feb 15 08:39:57 2015 (54E0A1AD)
cpuz138_x64.sys             Thu Feb 26 02:04:34 2015 (54EEC582)
mbamchameleon.sys           Fri May  8 13:50:15 2015 (554CF757)
asstahci64.sys              Tue Jun 16 23:36:23 2015 (5580EB37)
RTKVHD64.sys                Thu Jun 18 06:45:05 2015 (5582A131)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
intelppm.sys                Thu Jul  9 23:12:59 2015 (559F383B)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
nvlddmkm.sys                Sun Sep 13 17:12:24 2015 (55F5E6B8)
SaiK0DC5.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
rc32xx.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=mv91cons.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
e1c65x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys
http://www.carrona.org/drivers/driver.php?id=mbamchameleon.sys
asstahci64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 

[seto]

I have executed verifier.exe, and there is no drivers listed as being under test. As a precaution, I forced all verifier settings to be deleted, so it should not be active. The SaiK0DC5.sys driver is from the Saitek USB Cyborg Lights. I could physically remove them so the drivers would not be active. The driver rc32xx is as stated, from the HighPopint RocketCache controller, and If I remove that, then I lose my e: drive so its not possible to remove that driver package and still have a working machine.

 

I fired off an inquiry to HighPoint to see if there is a newer driver package for the RocketCache, but I have my doubts that anything is in the works.

[usasma]

Good for the Driver Verifier settings.  That should (in theory) slow down the BSOD's (if not stop them completely).

 

As for the Saitek device - uninstall it's software, then physically remove the device.  That will ensure that the drivers shouldn't load.

This is temporary, and is simply due to the age of the drivers.

 

As for the HighPoint card - I had the same problem several years ago with my HighPoint card.  They stopped developing drivers for the card, and their response was for me to purchase another, more recent, card. As the card was less than 3 years old, I did away with it.  If you're not ready to do away with it, we'll attempt to work around it.

[seto]

I removed the Cyborg drivers/software as well as the HW. I still need the highpoint drivers to access my data drive.

[usasma]

Not a problem.  Now we wait to see if the BSOD's continue.

If they do, please zip up the contents of the C:\Windows\Minidump folder and upload it with your next post.

If unable to zip it, try copying it to your Desktop and zipping it up there.