Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Driver Verifier BSOD


  • Please log in to reply
6 replies to this topic

#1 manfred99

manfred99

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Fremont, CA
  • Local time:06:55 PM

Posted 09 January 2017 - 01:50 PM

Twice today, I've had a BSOD with a stop code showing "Driver Verifier detected violation" There was no code. PC rebooted automatically. There are 2 minidump files, but I can't get them to attach to this post.

Windows 10 64 bit

Intel core i7 CPU 960 @ 3.20 Ghz

12 GB ram

AMD Radeon 5800 series



BC AdBot (Login to Remove)

 


#2 RodeoMan

RodeoMan

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:07:55 PM

Posted 09 January 2017 - 07:42 PM

Twice today, I've had a BSOD with a stop code showing "Driver Verifier detected violation" There was no code. PC rebooted automatically. There are 2 minidump files, but I can't get them to attach to this post.

Windows 10 64 bit

Intel core i7 CPU 960 @ 3.20 Ghz

12 GB ram

AMD Radeon 5800 series

I can't personally help with reading your DMPs but if you put them into a .ZIP or .RAR folder someone on here will be able to download them and help you. 



#3 lefthedef

lefthedef

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 09 January 2017 - 08:18 PM

do u remember which driver you installed lately?

if so enter safe mode and roll back !!!



#4 manfred99

manfred99
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Fremont, CA
  • Local time:06:55 PM

Posted 10 January 2017 - 03:03 PM

Didn't install any new drivers. But I was able to zip them and attach to this reply.[attachment=189020:010917-59437-01.zip]



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:55 PM

Posted 11 January 2017 - 07:37 AM

Did you turn Driver Verifier on?

If so, what settings did you use?

Please turn it off.  To do this, open up verifier.exe and select the "Delete existing settings" button then click on "Finish" and reboot.

 

Interestingly, the Driver Verifier memory dumps blame MalwareBytes.

Do you have the latest, most updated version?

Here's a list of known issues with the latest, most updated version:  https://forums.malwarebytes.com/topic/191805-malwarebytes-30-known-issues/

Worst case here is that you uninstall MalwareBytes.  That should stop the BSOD's, but won't let you run MalwareBytes (more on that after we look at the reports).

 

Unfortunately, we can only perform a partial analysis when only provided w/dump files.

If you'd like a complete analysis, please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

As for the dumps, this is what I found in them:

 

Your UEFI/BIOS (version A04) dates from 2010.  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.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).
If there are no BIOS updates available, I would be concerned about compatibility issues w/W10 on this system.  Unfortunately, then only sure test for this is to revert to the original OS and see if the problems remain.

 

Please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

 

 

There are quite a few drivers in the dump files that date from BEFORE W10 was released.

Please check in the list below and update all that you can.  Those that can't be updated (and aren't essential) can be uninstalled.

The essentials must remain - so locating updates for them is critical.
 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan  9 12:36:24.256 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010917-59437-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 8:09:40.052
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.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 :mwac.sys
BugCheck C4, {62, ffff9404ef5facf0, ffff9404f5b9b1c0, 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: ffff9404ef5facf0, name of the driver having the issue.
Arg3: ffff9404f5b9b1c0, 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 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3200
  BIOS Version                  A04
  BIOS Release Date             10/21/2010
  Manufacturer                  Dell Inc.
  Product Name                  Studio XPS 9100
  Baseboard Product             05DN3X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  9 04:24:46.002 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010917-67671-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 11:49:29.800
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :mwac.sys
BugCheck C4, {62, ffffc402709a3370, ffffc40277b77580, 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: ffffc402709a3370, name of the driver having the issue.
Arg3: ffffc40277b77580, 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 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3200
  BIOS Version                  A04
  BIOS Release Date             10/21/2010
  Manufacturer                  Dell Inc.
  Product Name                  Studio XPS 9100
  Baseboard Product             05DN3X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Jan  9 12:36:24.256 2017 (UTC - 5:00)**************************
regi.sys                    Mon Apr 16 11:19:10 2007 (462393EE)
PxHlpa64.sys                Tue Jun 23 19:16:35 2009 (4A416253)
rikvm_9EC60124.sys          Wed Apr  7 01:28:40 2010 (4BBC1808)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
eve.sys                     Wed Feb 20 12:54:17 2013 (51250DC9)
npf.sys                     Thu Feb 28 20:31:24 2013 (513004EC)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
Sftvollh.sys                Tue Oct  7 23:03:06 2014 (5434A96A)
Sftfslh.sys                 Tue Oct  7 23:03:22 2014 (5434A97A)
Sftplaylh.sys               Tue Oct  7 23:03:44 2014 (5434A990)
Sftredirlh.sys              Tue Oct  7 23:03:47 2014 (5434A993)
ElbyCDIO.sys                Wed Dec 17 18:30:51 2014 (5492122B)
amdkmafd.sys                Tue May 19 19:26:48 2015 (555BC6B8)
LHidEqd.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LEqdUsb.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LMouFilt.Sys                Tue Jun  9 15:25:39 2015 (55773DB3)
LHidFilt.Sys                Tue Jun  9 15:25:40 2015 (55773DB4)
 

**Windows 10 released on 29 July 2015**
 

mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
atikmpag.sys                Wed Nov  4 16:16:43 2015 (563A75BB)
atikmdag.sys                Wed Nov  4 16:39:32 2015 (563A7B14)
AnyDVD.sys                  Mon Dec 28 07:52:15 2015 (5681307F)
mbamchameleon.sys           Wed Jan 27 18:48:35 2016 (56A95753)
AtihdWT6.sys                Wed Apr 20 21:30:52 2016 (57182D4C)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
usbcir.sys                  Fri Jul 15 22:18:46 2016 (57899986)
RtsUer.sys                  Thu Aug  4 21:08:09 2016 (57A3E6F9)
Ironx64.SYS                 Fri Sep  2 17:44:25 2016 (57C9F2B9)
SRTSPX64.SYS                Fri Sep  2 21:56:42 2016 (57CA2DDA)
SYMEVENT64x86.SYS           Thu Sep  8 15:47:29 2016 (57D1C051)
SRTSP64.SYS                 Tue Sep 13 21:14:58 2016 (57D8A492)
SYMNETS.SYS                 Wed Sep 14 22:43:10 2016 (57DA0ABE)
eeCtrl64.sys                Fri Sep 16 22:16:39 2016 (57DCA787)
EraserUtilRebootDrv.sys     Fri Sep 16 22:16:39 2016 (57DCA787)
rt640x64.sys                Fri Oct  7 05:24:19 2016 (57F769C3)
SYMEFASI64.SYS              Wed Oct 12 14:18:04 2016 (57FE7E5C)
BHDrvx64.sys                Fri Nov  4 05:39:20 2016 (581C5748)
IDSvia64.sys                Fri Dec  2 12:58:53 2016 (5841B65D)
RTKVHD64.sys                Tue Dec  6 06:23:15 2016 (58469FA3)

http://www.carrona.org/drivers/driver.php?id=regi.sys
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=rikvm_9EC60124.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=eve.sys
http://www.carrona.org/drivers/driver.php?id=npf.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=Sftvollh.sys
http://www.carrona.org/drivers/driver.php?id=Sftfslh.sys
http://www.carrona.org/drivers/driver.php?id=Sftplaylh.sys
http://www.carrona.org/drivers/driver.php?id=Sftredirlh.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=amdkmafd.sys
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=AnyDVD.sys
http://www.carrona.org/drivers/driver.php?id=mbamchameleon.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=usbcir.sys
http://www.carrona.org/drivers/driver.php?id=RtsUer.sys
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys

 


Edited by usasma, 11 January 2017 - 07:39 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 manfred99

manfred99
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Fremont, CA
  • Local time:06:55 PM

Posted 11 January 2017 - 01:51 PM

I did not turn Driver Verifier on . I tried to run it about a week and a half ago, but I never got any output, so I assumed it did not work. I had used the settings a previous forum post had suggested. I have now turned it off. (I didn't know it had to be turned off).

The BIOS is the latest that Dell has.

I have available Windows updates.

According to the program "Driver Easy" all drivers are up to date. Is there a better way to verify this?

How can I tell if any of the drivers are not essential?[attachment=189089:MIKE_PC_1_11_2017_10_23_25_AM.zip]



#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:55 PM

Posted 13 January 2017 - 06:07 AM

The first step here is to wait and see if you have further BSOD's
Driver Verifier's "output" is to cause a BSOD by stressing drivers.

In general it's not needed unless you're already seeing BSOD's and you're trying to figure out if it's a driver causing this - and if so, which particular driver it is.

 

I don't suggest using driver updater programs - I've seen too many problems with them.
I suggest manually checking for drivers at the different support websites of the hardware/software that you use.

 

As for if the drivers are essential or not - it depends on what you need.

First off, don't mess with the drivers individually - rather install/uninstall the programs that they belong to.

That will remove the drivers without the danger of the system becoming unbootable.

 

Here's a complete analysis.......

 

Your UEFI/BIOS (version A04) dates from 2010.  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.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).
If there are no BIOS updates available, I would be concerned about compatibility issues w/W10 on this system.  Unfortunately, then only sure test for this is to revert to the original OS and see if the problems remain.

 

Only 6 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Many more Live Kernel Events than BSOD's in the WER section of the MSINFO32 report.
In some cases, this is a symptom of a hardware problem.

Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please run ALL of the tests and let us know the results.

 

Out of 9 memory dumps there were 6 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them and let us know the results

This all depends on the results after you uninstall MalwareBytes (because it was blamed by Driver Verifier).

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan  9 12:36:24.256 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010917-59437-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 8:09:40.052
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.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 :mwac.sys
BugCheck C4, {62, ffff9404ef5facf0, ffff9404f5b9b1c0, 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: ffff9404ef5facf0, name of the driver having the issue.
Arg3: ffff9404f5b9b1c0, 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 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3200
  BIOS Version                  A04
  BIOS Release Date             10/21/2010
  Manufacturer                  Dell Inc.
  Product Name                  Studio XPS 9100
  Baseboard Product             05DN3X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  9 04:24:46.002 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010917-67671-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 11:49:29.800
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :mwac.sys
BugCheck C4, {62, ffffc402709a3370, ffffc40277b77580, 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: ffffc402709a3370, name of the driver having the issue.
Arg3: ffffc40277b77580, 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 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3200
  BIOS Version                  A04
  BIOS Release Date             10/21/2010
  Manufacturer                  Dell Inc.
  Product Name                  Studio XPS 9100
  Baseboard Product             05DN3X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  2 20:07:22.500 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010317-71953-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:5 days 6:41:08.656
Probably caused by :ndis.sys ( ndis!ndisPauseFilterInner+7078 )
BugCheck 9F, {3, ffff8184d231e060, fffff80080103cb0, ffff8184e2169b40}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff8184d231e060, Physical Device Object of the stack
Arg3: fffff80080103cb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8184e2169b40, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: 0x9F_VRF_3_POWER_DOWN_ndis!ndisPauseFilterInner
CPUID:        "Intel® Core™ i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3200
  BIOS Version                  A04
  BIOS Release Date             10/21/2010
  Manufacturer                  Dell Inc.
  Product Name                  Studio XPS 9100
  Baseboard Product             05DN3X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Jan  9 12:36:24.256 2017 (UTC - 5:00)**************************
regi.sys                    Mon Apr 16 11:19:10 2007 (462393EE)
PxHlpa64.sys                Tue Jun 23 19:16:35 2009 (4A416253)
rikvm_9EC60124.sys          Wed Apr  7 01:28:40 2010 (4BBC1808)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
eve.sys                     Wed Feb 20 12:54:17 2013 (51250DC9)
npf.sys                     Thu Feb 28 20:31:24 2013 (513004EC)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
Sftvollh.sys                Tue Oct  7 23:03:06 2014 (5434A96A)
Sftfslh.sys                 Tue Oct  7 23:03:22 2014 (5434A97A)
Sftplaylh.sys               Tue Oct  7 23:03:44 2014 (5434A990)
Sftredirlh.sys              Tue Oct  7 23:03:47 2014 (5434A993)
ElbyCDIO.sys                Wed Dec 17 18:30:51 2014 (5492122B)
amdkmafd.sys                Tue May 19 19:26:48 2015 (555BC6B8)
LHidEqd.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LEqdUsb.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LMouFilt.Sys                Tue Jun  9 15:25:39 2015 (55773DB3)
LHidFilt.Sys                Tue Jun  9 15:25:40 2015 (55773DB4)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
atikmpag.sys                Wed Nov  4 16:16:43 2015 (563A75BB)
atikmdag.sys                Wed Nov  4 16:39:32 2015 (563A7B14)
AnyDVD.sys                  Mon Dec 28 07:52:15 2015 (5681307F)
mbamchameleon.sys           Wed Jan 27 18:48:35 2016 (56A95753)
AtihdWT6.sys                Wed Apr 20 21:30:52 2016 (57182D4C)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
usbcir.sys                  Fri Jul 15 22:18:46 2016 (57899986)
RtsUer.sys                  Thu Aug  4 21:08:09 2016 (57A3E6F9)
Ironx64.SYS                 Fri Sep  2 17:44:25 2016 (57C9F2B9)
SRTSPX64.SYS                Fri Sep  2 21:56:42 2016 (57CA2DDA)
SYMEVENT64x86.SYS           Thu Sep  8 15:47:29 2016 (57D1C051)
SRTSP64.SYS                 Tue Sep 13 21:14:58 2016 (57D8A492)
SYMNETS.SYS                 Wed Sep 14 22:43:10 2016 (57DA0ABE)
eeCtrl64.sys                Fri Sep 16 22:16:39 2016 (57DCA787)
EraserUtilRebootDrv.sys     Fri Sep 16 22:16:39 2016 (57DCA787)
rt640x64.sys                Fri Oct  7 05:24:19 2016 (57F769C3)
SYMEFASI64.SYS              Wed Oct 12 14:18:04 2016 (57FE7E5C)
BHDrvx64.sys                Fri Nov  4 05:39:20 2016 (581C5748)
IDSvia64.sys                Fri Dec  2 12:58:53 2016 (5841B65D)
RTKVHD64.sys                Tue Dec  6 06:23:15 2016 (58469FA3)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  2 20:07:22.500 2017 (UTC - 5:00)**************************
bcmwl63al.sys               Thu May  2 16:00:26 2013 (5182C5DA)
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
hiber_storport.sys          Fri Jul 15 22:21:57 2016 (57899A45)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Nov 30 11:54:58.638 2016 (UTC - 5:00)**************************
ccSetx64.sys                Thu May  5 18:33:33 2016 (572BCA3D)
IDSvia64.sys                Wed Oct 19 18:31:54 2016 (5807F45A)
RTKVHD64.sys                Tue Nov  8 05:44:57 2016 (5821ACA9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 29 14:40:42.733 2016 (UTC - 5:00)**************************
rt640x64.sys                Thu Jul 14 05:04:28 2016 (5787559C)
RTKVHD64.sys                Tue Oct 18 07:20:52 2016 (58060594)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov 25 11:39:53.300 2016 (UTC - 5:00)**************************
gdfj.sys                    Tue Aug 11 13:35:18 2015 (55CA3256)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct  4 11:54:34.459 2016 (UTC - 5:00)**************************
eeCtrl64.sys                Mon Apr 25 13:47:05 2016 (571E5819)
EraserUtilRebootDrv.sys     Mon Apr 25 13:47:06 2016 (571E581A)
intelide.sys                Fri Jul 15 22:29:13 2016 (57899BF9)
SYMEFASI64.SYS              Wed Aug  3 01:50:18 2016 (57A1861A)
BHDrvx64.sys                Sun Aug 14 18:59:09 2016 (57B0F7BD)
IDSvia64.sys                Thu Sep 15 00:43:27 2016 (57DA26EF)
RTKVHD64.sys                Tue Sep 20 07:47:12 2016 (57E121C0)


http://www.carrona.org/drivers/driver.php?id=regi.sys
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=rikvm_9EC60124.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=eve.sys
http://www.carrona.org/drivers/driver.php?id=npf.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=Sftvollh.sys
http://www.carrona.org/drivers/driver.php?id=Sftfslh.sys
http://www.carrona.org/drivers/driver.php?id=Sftplaylh.sys
http://www.carrona.org/drivers/driver.php?id=Sftredirlh.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=amdkmafd.sys
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=AnyDVD.sys
http://www.carrona.org/drivers/driver.php?id=mbamchameleon.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=usbcir.sys
http://www.carrona.org/drivers/driver.php?id=RtsUer.sys
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=bcmwl63al.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=hiber_storport.sys
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
gdfj.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=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=intelide.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys

 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users