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.


New Computer - New BSODs

  • Please log in to reply
1 reply to this topic

#1 PancakeSquid


  • Members
  • 1 posts
  • Local time:03:04 PM

Posted 19 June 2016 - 10:54 PM

OS - Windows 10
· 64 Bit
· Windows 7, upgrade to Windows 10
· Full Retail, I guess. 7 came installed, 10 came from the upgrade.
· All the hardware is new, new Motherboard, CPU, Case, only the Hard drive (1.5 TB), GPU, and RAM are not new, where the RAM is 1 year old (12GB total) along with the hard drive, while the GPU is about 3 years old.
· The OS is about as old as whenever Microsoft started giving the public the free upgrades to Windows 10, so about a year or so.

· CPU - AMD FX-6300 Six Core Processor
· Video Card - 1024MB ATI Radeon 4600 Series
· MotherBoard - BIOSTAR Group TA970
· Power Supply - good question

· System Manufacturer - BIOSTAR
· Exact model number - TA970

· Laptop or Desktop? - Desktop


I also ran a system file checker and got



Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
so i'm adding the CBS Log attached as well.


Attached Files

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:04 PM

Posted 21 June 2016 - 05:27 AM

Sorry, but I can't read CBS log files.

You may want to start a separate topic about that with "CBS log" in the title (to attract the attention of those who can read them).


Your UEFI/BIOS (version 4.6.4) 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.

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, 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.

MSINFO32 report is missing.  Please do this:

Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the TEST.NFO file.  If you have difficulties with making this work, please post back.  Then zip up the .nfo file and upload/attach the .zip file with your next post.
have difficulties with making this work, please post back.  Then zip up the .txt file and upload/attach the .zip file with your next post.


Out of 8 memory dumps there were 5 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

AMD OverDrive (AODDriver2.sys) 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) 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 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.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!


The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Sun Jun 19 22:41:30.773 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\061916-44656-01.dmp]
Windows 10 Kernel Version 10586 MP (6 procs) Free x64
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
System Uptime:0 days 1:18:19.508
Probably caused by :ntkrnlmp.exe ( nt!CmpTouchFile+0 )
BugCheck 109, {a3a01f58f654e610, b3b72bdf48d28cb9, fffff800e4e61ba4, 1}
Arg1: a3a01f58f654e610, Reserved
Arg2: b3b72bdf48d28cb9, Reserved
Arg3: fffff800e4e61ba4, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    102 : Modification of win32k.sys
PROCESS_NAME:  csrss.exe
  BIOS Version                  4.6.4
  BIOS Release Date             08/07/2014
  Manufacturer                  BIOSTAR Group
  Product Name                  TA970
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

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:

**************************Sun Jun 19 22:41:30.773 2016 (UTC - 4:00)**************************
amdiox64.sys                 Thu Feb 18 10:17:53 2010 (4B7D5A21)
ElcMouLFlt.sys               Mon Oct  4 19:30:57 2010 (4CAA63B1)
ElcMouUFlt.sys               Tue Nov 30 00:42:46 2010 (4CF48ED6)
AODDriver2.sys               Tue Mar  6 04:55:00 2012 (4F55DEF4)
GEARAspiWDM.sys              Thu May  3 15:56:17 2012 (4FA2E2E1)
t_mouse.sys                  Mon Dec  3 01:19:30 2012 (50BC4472)
amdide64.sys                 Tue Dec  4 04:49:28 2012 (50BDC728)
point64.sys                  Thu Dec 12 08:16:17 2013 (52A9B721)
dc3d.sys                     Thu Dec 12 08:16:35 2013 (52A9B733)
atikmpag.sys                 Tue Jan 13 11:20:43 2015 (54B545DB)
atikmdag.sys                 Tue Jan 13 11:48:21 2015 (54B54C55)
dtlitescsibus.sys            Thu Mar 26 22:05:54 2015 (5514BB02)
HWiNFO64A.SYS                Tue Mar 31 05:51:32 2015 (551A6E24)
AtihdWT6.sys                 Mon May 25 21:21:51 2015 (5563CAAF)
avgidsha.sys                 Tue Jan 26 05:04:23 2016 (56A744A7)
avgloga.sys                  Tue Feb 16 09:04:03 2016 (56C32C53)
avgdiska.sys                 Tue Feb 16 09:07:26 2016 (56C32D1E)
rt640x64.sys                 Fri Mar 11 00:57:50 2016 (56E25E5E)
WirelessKeyboardFilter.sys   Wed Mar 16 03:48:01 2016 (56E90FB1)
avgrkx64.sys                 Mon May  2 10:06:38 2016 (57275EEE)
avgldx64.sys                 Mon May  2 10:13:06 2016 (57276072)
avguniva.sys                 Thu May  5 05:06:15 2016 (572B0D07)
avgmfx64.sys                 Thu May  5 05:06:21 2016 (572B0D0D)
avgidsdrivera.sys            Wed May 18 06:12:43 2016 (573C401B)
RTKVHD64.sys                 Fri May 20 06:48:12 2016 (573EEB6C)
**************************Sun Jun 19 17:11:18.415 2016 (UTC - 4:00)**************************
MBAMSwissArmy.sys            Wed Jul 29 00:26:01 2015 (55B855D9)
**************************Sun Jun 19 11:47:10.924 2016 (UTC - 4:00)**************************
mbam.sys                     Wed Sep  3 13:50:25 2014 (540754E1)
**************************Sat Jun 18 04:49:45.753 2016 (UTC - 4:00)**************************
regfilter.sys                Mon Nov 18 23:39:54 2013 (528AEB9A)
TRUFOS.sys                   Sat Oct 11 05:01:08 2014 (5438F1D4)
gzflt.sys                    Wed Oct 22 03:29:01 2014 (54475CBD)
IMFFilter.sys                Mon Dec 21 22:05:04 2015 (5678BDE0)


WirelessKeyboardFilter.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.
avguniva.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.
IMFFilter.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.


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