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

PC randomly restarts without warning.


  • Please log in to reply
2 replies to this topic

#1 Lev24

Lev24

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 09 January 2018 - 03:36 PM

PC restarts without any warning except when I enable driver verifier, then it starts to give BSOD's like VERIFIER_DETECTED_VIOLATION with 0x000000c4 and 0x000000d1. I must mention what I've tried:
-updates to the latest version including bios
-sfc /scannow no problems

-dism /online /cleanup-image /restorehealth restore completed successfully

-chkdsk /scan no problems
-Turned off Windows Fast Startup

-Used DDU and installed drivers from Manufacturers

​-memory tests passed

-Default BIOS settings

​-No overheat

 

There is also no overclock applied.

It all started when i was opening Chrome and the crash was when it loaded a video or a thumbnail. I reinstalled the video drivers and the problem was gone. After some time it gave me usbfilter.sys BSOD at startup until i unistalled VMWare. On their site they said that there are some problems with AMD's usb drivers.  I had to enter Safe Mode and enable the Windows unistaller. The problem again was gone, for a few days then again restart. Enabled driver verifier for all drivers and no BSOD, reconfigured verifier for non-Microsoft drivers and got DRIVER_VERIFIER_DETECTED_VIOLATION BSOD at startup, had to enter Safe Mode to disable verifier. Oh, and after one of the latest restarts firefox stopped working for some reason. 
Thanks!

Attached Files



BC AdBot (Login to Remove)

 


#2 Lev24

Lev24
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 10 January 2018 - 02:28 AM

Added SysnativeFileCollection's analyzed data.

Attached Files



#3 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:08:27 PM

Posted 10 January 2018 - 03:01 PM

Your UEFI/BIOS (version V8.3) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
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).

Only 5 Windows Update hotfixes installed.  Most build 16299 (1709/Fall Creators Update) 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.

 

Haven't seen problems with AMD OverDrive in a while (so this canned speech may be a bit outdated).  BUT - it's possible that this is causing your problems - so it's the first thing to try.

AMD OverDrive (AODDriver2.sys or AODDriver4.1) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Windows systems.

 

NOTE:  these symptoms were from the previous release of OverDrive.  The new release uses the same driver name, but is dated from 4 November 2013.

 

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program.
Please note that I stated "video stuff", as some integrated processors may have the graphics chip built in (which may involve the chipset software).
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://www.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLYhttp://www.sysnative.com/forums/showthread.php/668-ATI-video-cards-DRIVER-ONLY-installation-procedure

If the device (AODDriver or AODDriver4.01, etc) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install".  Reboot for changes to take affect.

Sometimes the entry will remain in Device Manager even though you've removed it.  So, open up Device Manager and check for the AODDriver4.2.0 (it may have another number).  Right click on it and select "Uninstall".  If it asks to remove software, put a check in the box.  Then click on OK.

Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

 

Also notice that your AMD chipset drivers (to include the USB driver) date from prior to the release of W10 (outdated drivers are listed below).
As such, I have to wonder about the compatibility of these drivers w/W10.
Please update them with the latest, W10 compatible drivers from the MSI support website for your motherboard model.
 

If all that doesn't help, then I suspect a hardware problem here.

As such, try this:

My suggested way to diagnose a hardware problem (3 steps):

 

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.
    FYI - These are the tests and what we usually see for the reports:

 

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


Step #2)  If all the tests pass, then try to perform a clean install of Windows:

 

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [ :(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers.  
If unable to find an update, please uninstall the program that is responsible for that driver.  

DO NOT manually delete/rename the driver as it may make the system unbootable!!!:

AODDriver2.sys              Tue Feb 11 06:06:52 2014 (52FA044C)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard   [br]   Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location:  C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys http://game.amd.com/us-en/drivers_overdrive.aspx
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
 
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
AMD SATA Controller AHCI 1.2 Device Driver  http://support.amd.com/us/Pages/AMDSupportHub.aspx
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
 
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
AMD Stor Filter Driver http://support.amd.com/us/Pages/AMDSupportHub.aspx
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
 
usbfilter.sys               Thu May  7 04:43:50 2015 (554B25C6)
AMD USB Filter Driver (likely part of the chipset drivers) http://support.amd.com/us/Pages/AMDSupportHub.aspx
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
 
AtihdWT6.sys                Tue Jul  7 21:28:10 2015 (559C7CAA)
AMD High Definition Audio Function Driver http://support.amd.com/en-us
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
 
 


Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Tue Jan  9 10:58:09.634 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010918-20281-01.dmp]
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
System Uptime:0 days 0:00:24.404
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by :usbfilter.sys ( usbfilter+5a8c )
BugCheck C4, {2000, fffff80c7fa65a8c, 0, 46425355}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80c7fa65a8c, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000046425355, Pool Tag (if provided).
BUGCHECK_STR:  0xc4_2000
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc4_2000_usbfilter!unknown_function
  BIOS Version                  V8.3
  BIOS Release Date             04/07/2016
  Manufacturer                  MSI
  Product Name                  MS-7721
  Baseboard Product             A68HM-E33 V2 (MS-7721)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  4 12:39:00.160 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010418-18187-01.dmp]
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
System Uptime:0 days 0:00:09.929
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :atikmpag.sys ( atikmpag+105c )
BugCheck C4, {2003, ffffc802acdf3ac8, fffff806f8db0240, ffff858c5784b658}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000002003, Code Integrity Issue: The image contains an executable and writable section.
Arg2: ffffc802acdf3ac8, The image file name (Unicode string).
Arg3: fffff806f8db0240, The address of the section header.
Arg4: ffff858c5784b658, The section name (UTF-8 encoded string).
BUGCHECK_STR:  0xc4_2003
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc4_2003_atikmpag!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  4 12:35:12.205 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010418-18468-01.dmp]
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
System Uptime:0 days 0:00:10.976
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :atikmpag.sys ( atikmpag+105c )
BugCheck C4, {2003, ffffe5050279eac8, fffff807e2600240, fffff50010394658}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000002003, Code Integrity Issue: The image contains an executable and writable section.
Arg2: ffffe5050279eac8, The image file name (Unicode string).
Arg3: fffff807e2600240, The address of the section header.
Arg4: fffff50010394658, The section name (UTF-8 encoded string).
BUGCHECK_STR:  0xc4_2003
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc4_2003_atikmpag!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Tue Jan  9 10:58:09.634 2018 (UTC - 5:00)**************************
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
usbfilter.sys               Thu May  7 04:43:50 2015 (554B25C6)
AtihdWT6.sys                Tue Jul  7 21:28:10 2015 (559C7CAA)
SCDEmu.SYS                  Thu Feb  2 08:22:01 2017 (58933279)
rt640x64.sys                Tue Oct  3 04:31:47 2017 (59D34AF3)
atikmpag.sys                Thu Nov  2 14:18:04 2017 (59FB615C)
atikmdag.sys                Thu Nov  2 14:43:57 2017 (59FB676D)
RTKVHD64.sys                Tue Nov 14 06:05:07 2017 (5A0ACDE3)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  4 12:39:00.160 2018 (UTC - 5:00)**************************
atikmpag.sys                Fri Jul  8 14:46:57 2016 (577FF521)
atikmdag.sys                Fri Jul  8 15:11:29 2016 (577FFAE1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  4 09:31:30.764 2018 (UTC - 5:00)**************************
AODDriver2.sys              Tue Feb 11 06:06:52 2014 (52FA044C)
AtihdWT6.sys                Mon May 25 21:21:51 2015 (5563CAAF)
rt640x64.sys                Fri Aug 11 03:41:25 2017 (598D5FA5)
RTKVHD64.sys                Mon Oct  2 06:38:24 2017 (59D21720)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  4 09:26:34.422 2018 (UTC - 5:00)**************************
AODDriver2.sys              Tue Oct 29 20:58:36 2013 (527059BC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  4 07:07:03.518 2018 (UTC - 5:00)**************************
AtihdWT6.sys                Sat Mar 25 17:04:05 2017 (58D6DB45)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan  3 05:31:27.745 2018 (UTC - 5:00)**************************
MpKslc7186a2b.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)

http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=rt640x64.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=RTKVHD64.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=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
MpKslc7186a2b.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.
 


Edited by usasma, 10 January 2018 - 03:03 PM.

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