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

BSODs driving me crazy...


  • Please log in to reply
14 replies to this topic

#1 Indaliceo

Indaliceo

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 23 January 2017 - 11:02 PM

Going to get the required stuff out of the way first:

 

· OS - Windows 10 Home  x64
· Windows 10
· Full Retail version
· Year and a half (maybe 2 years) for everything but Video Card (less than a month), SSD (less than a month), Sound card (2 days old)
· 3 days (just re-installed 3 days ago in a last ditch effort to fix this crap)

· AMD FX-8350 (eight-core  4.00 GHz)
· MSI Radeon RX470
· msi 970 gaming
· EVGA NEX650g   650W
· Desktop

 

 

Alright so I've been fighting BSODs for a few months now but just in the past month or so they've been happening in more frequency...  The crashes seem to only happen when I'm gaming and on skype with a friend while we play.  For instance yesterday I was gaming for 6 hours straight with netflix running on my other monitor with no issues.

 I'm at wit's end at this point.  Here's a list of everything I've done so far....

 

Ran memtest86 for 8 passes, no errors

sfc /scannow  gave 0 errors.

verifier up till I went out and bought a new sound card was bringing back the realtek audio driver for my mobo as the crash culprit (and it was causing immediate BSODs with verifier running.  I'll run verifier once again after I post this since I just got my first crash after the new sound card just about an hour and a half ago.

 

Hopefully someone here will be able to find something I'm missing x_x  this is driving me bat bleep insane.

 

 

Attached Files



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:05:12 AM

Posted 23 January 2017 - 11:31 PM

Greetings,

I can totally understand how you feel. :) BSODs are horrible, especially when you don't know what's causing them!

I just loaded up your dumps and you had the following bugchecks:

3 STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTIONs
1 STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE  (atikmdag.sys)
1 STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION (MBfilt64.sys)

As you noted above, Driver Verifier blamed MBfilt64.sys, a driver for Realtek HiDefinition Audio. Even though you got a new soundcard, please download the latest copy of your audio drivers, uninstall your current set, reboot, and install the fresh set of audio drivers. Also, as you can see above, one dump blamed atikmdag.sys, your ATI Video driver. Please once again, download the latest copy of your audio drivers, uninstall the Catalyst Control Center from the Control Panel, reboot, and carefully follow these instructions. <=== VERY IMPORTANT!!!

Additionally, please:

• update Windows
• update your BIOS (Only do this if you know what you're doing. If the computer turns off halfway through the install, you won't be able to boot again.)
• run all of these free hardware diagnostics

If you're still experiencing BSODs, please be patient and our resident BSOD expert will have more ideas!

Good luck! :)

 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 23 January 2017 - 11:41 PM

Greetings,

I can totally understand how you feel. :) BSODs are horrible, especially when you don't know what's causing them!

I just loaded up your dumps and you had the following bugchecks:

3 STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTIONs
1 STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE  (atikmdag.sys)
1 STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION (MBfilt64.sys)

As you noted above, Driver Verifier blamed MBfilt64.sys, a driver for Realtek HiDefinition Audio. Even though you got a new soundcard, please download the latest copy of your audio drivers, uninstall your current set, reboot, and install the fresh set of audio drivers. Also, as you can see above, one dump blamed atikmdag.sys, your ATI Video driver. Please once again, download the latest copy of your audio drivers, uninstall the Catalyst Control Center from the Control Panel, reboot, and carefully follow these instructions. <=== VERY IMPORTANT!!!

Additionally, please:

• update Windows
• update your BIOS (Only do this if you know what you're doing. If the computer turns off halfway through the install, you won't be able to boot again.)
• run all of these free hardware diagnostics

If you're still experiencing BSODs, please be patient and our resident BSOD expert will have more ideas!

Good luck! :)

 

 

 

The current audio drivers are fresh from card manufacturer's site as of yesterday, before I installed them I wiped the old drivers clean and actually currently have the on board sound set to disabled on device manager.  As far as the video driver one, when was that logged?  I'm asking because I know initially after the fresh windows install I had a crash running verifier when I had the full radeon suite installed.  Since then I wiped everything related to that driver install out and re-installed the display driver only.    Testing for these BSODs is really random and annoying because sometimes it seems it happens within 5-10 minutes of being on skype with a game open, and others it'll take an hour and a half - 2 hours for it to happen.   The only things that seem related on the crashes since getting the new sound card is skype.

 

 

Edit:  I can definitely wipe vid/audio drivers out completely again if you think it'll help, I do know that most of the dump logs currently on my PC were from before I installed the new sound card and re-installed a few different drivers though.


Edited by Indaliceo, 23 January 2017 - 11:42 PM.


#4 Max-from-DeskRoll

Max-from-DeskRoll

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:12 AM

Posted 24 January 2017 - 01:09 AM

Maybe just disable the onboard audio in BIOS and uninstall Realtek audio drivers?



#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:05:12 AM

Posted 24 January 2017 - 08:37 AM

Your UEFI/BIOS (version V22.4) dates from 2015.  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).

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.

Both of these devices are disabled in Device Manager:

 

High Definition Audio Device    HDAUDIO\FUNC_01&VEN_10EC&DEV_0900&SUBSYS_1462D693&REV_1000\4&7752DFF&0&0001    This device is disabled.
AMD High Definition Audio Device    HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1007\5&393EA61E&0&0001    This device is disabled.

The MSINFO32 report shows 4 audio devices installed on this system - how many are on it currently (either enabled or disabled)?

Which device is preferred?  I have seen instances of USB audio causing problems - so I suggest that the USB audio device have it's software uninstalled and then the device itself should be physically removed from the system.

FYI - the MBFilt64.sys driver has proven remarkably stable since it was introduced in 2009.  It ts one of the few drivers (if not the only one) that continues to be compatible with more recent versions of Windows without having to be updated.

 

As a test, I would also uninstall the software for the SoundBlaster Audigy card and physically remove it from the system.

Then enable both of the other devices and update their drivers to the latest available, W10 compatible version.

Then test to see if the system still BSOD's

 

If it does BSOD, we will analyze that until we achieve some sort of resolution.

If it doesn't BSOD, then we add the Audigy back into the mix and see if it causes BSOD's (I've also seen BSOD issues with these drivers).

If it does, then we know where the problem comes from.

If it doesn't then we add the USB audio device back in and test for BSOD's with it installed.

 

Some of the memory dumps listed in the WER section of the MSINFO32 report also are of a type that may be hardware related (this is not certain at this point).

As such, please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

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

 

The next oldest driver in the memory dump is AFXfilt.sys (dates from 2013).
This is likely associated with the Creative sound card drivers - and I have to wonder about it's compatibility for W10.
The procedure I detailed above for trying out the different cards should help us decide if this is a problem driver or not.

Also, please note that the ATI and Realtek audio drivers aren't present in the latest memory dump - making it less likely that they are involved in the crash.

 

As for Driver Verifier blaming the Realtek driver - I suspect that something else (I'm guessing a Creative driver or piece of hardware) caused a problem in the memory space owned by the Reatek driver.  Then it exited.  Then the Realteck driver went looking in it's memory space, found the bad stuff that the other driver had left, and crashed because it's memory space was corrupted.  The debugger blames the Realtek driver because nothing else is left (in memory) to blame..

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan 23 21:51:26.881 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012317-6218-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 23:43:54.303
Probably caused by :memory_corruption
BugCheck 109, {a39fc7e5f39de9d4, b3b6d46c461ba82e, fffff803554f43b9, 1}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a39fc7e5f39de9d4, Reserved
Arg2: b3b6d46c461ba82e, Reserved
Arg3: fffff803554f43b9, 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
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 22 10:29:30.161 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012217-6093-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 6:02:06.926
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
Probably caused by :pci.sys
BugCheck 9F, {3, ffffdf0ff0a5b060, fffff801c8504cb0, ffffdf0ff2c8dcf0}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffdf0ff0a5b060, Physical Device Object of the stack
Arg3: fffff801c8504cb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffdf0ff2c8dcf0, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_3_atikmpag_IMAGE_pci.sys
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 22 03:08:14.348 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012217-4921-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 1:20:10.054
Probably caused by :ntkrnlmp.exe ( nt!ExAcquireRundownProtectionCacheAware+0 )
BugCheck 109, {a3a0235b66e8b5e9, b3b72fe1b9667453, fffff8004b22c520, 1}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a3a0235b66e8b5e9, Reserved
Arg2: b3b72fe1b9667453, Reserved
Arg3: fffff8004b22c520, 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
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 22 01:32:55.021 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012217-6312-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 8:15:08.728
Probably caused by :memory_corruption
BugCheck 109, {a3a00b67f18ec78d, b3b717ee440c85f7, fffff800e15e20c2, 1}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a3a00b67f18ec78d, Reserved
Arg2: b3b717ee440c85f7, Reserved
Arg3: fffff800e15e20c2, 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
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 21 17:14:50.051 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012117-5296-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:00:07.833
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by :MBfilt64.sys ( MBfilt64+4b94 )
BugCheck C4, {2000, fffff8075b074b94, 0, 774e6350}
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: fffff8075b074b94, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000774e6350, Pool Tag (if provided).
BUGCHECK_STR:  0xc4_2000
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc4_2000_MBfilt64!unknown_function
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 23 21:51:26.881 2017 (UTC - 5:00)**************************
AFXfilt.sys                 Mon Jun  3 23:04:44 2013 (51AD594C)
cthdb.sys                   Mon Jun  1 23:20:31 2015 (556D20FF)
atikmpag.sys                Mon Jul 18 16:32:52 2016 (578D3CF4)
atikmdag.sys                Mon Jul 18 17:41:41 2016 (578D4D15)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
bwcW10x64.sys               Thu Sep 15 12:22:54 2016 (57DACADE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 22 01:32:55.021 2017 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
RTKVHD64.sys                Thu Jan  5 05:19:52 2017 (586E1DC8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 21 17:14:50.051 2017 (UTC - 5:00)**************************
AtihdWT6.sys                Tue Sep 20 19:17:24 2016 (57E1C384)
RTKVHD64.sys                Tue Dec  6 06:23:15 2016 (58469FA3)


AFXfilt.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=cthdb.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
e2xw10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.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.

#6 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 24 January 2017 - 05:00 PM

I'm at work now, so I can't try anything till later tonight but I wanted to clarify a few things.
 
As far as devices being disabled in device manager, as I said Sunday I went out and purchased a standalone sound card, and I disabled those since I wouldn't be using them at all.
 
No clue why it's showing 4 audio devices installed.  Only ones that SHOULD be showing is the creative labs one (the brand new sound card), and the Blue Yeti one (has a microphone and seperate audio stream built into it.  Though there are 0 drivers for this device)
 
The HD audio device is the default driver windows defaulted to when I uninstalled the realtek driver that my previous crashes were pointing to.  The AMD high Def Audio device I have no clue where that came from unless it was leftover from the brief time I had the full radeon video package installed (rather than driver only).  I think I remember seeing something in that package about HDMI audio drivers.
 
As mentioned the USB audio device doesn't have a driver associated with it.  It's a blue yeti microphone.  I can unplug it but then I'd have no way of fishing for a crash in the way every crash seems to have been happening since installing the new soundcard (gaming while on skype chatting).
 
 
The system was definitely a lot more unstable before I uninstalled realtek drivers and put in the new sound card (as in running verifier with the on board sound enabled with the realtek drivers installed caused immediate BSOD once it got to the login screen to where I had to reload from a restore point to get back into windows).  But I'm willing to do as you say there if you really think it'll help.  I've had verifier running since I went to bed last night and it's still running while I'm here at work, when I checked this morning it hadn't crashed, I'll see how it's doing when I get home in a few hours though.
 
 
Is it possible the microphone is the cause of the crashes?  I wouldn't THINK it would since I've only had that mic for maybe 2 and a half weeks and the crashes have been happening for a bit longer than that, though admittedly it seems much more frequent since getting it.
Also of note, if I'm using in game voice chat (as in the voice chat built into the games.) there seem to be no issues, talking on skype while gaming seems to trigger the crashes most frequently.  ***note:  I can voice chat on teamspeak, and discord without any issues it seems***
 
 
Really wish I still had saved all the .dmps from before I re-installed windows....


#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:05:12 AM

Posted 24 January 2017 - 06:21 PM

I understand that you disabled those devices, I asked the question to be sure that there weren't any other factors that contributed to it.
Sometimes when I ask a question a second time, more information is discovered.  Other times it's just my Alzheimer's - and I ask that you excuse that.

Finally, I also have visual problems - so sometimes I miss things.  Again I ask that you please excuse me.

 

So, we can confirm that there are 4 sound devices (I presume).

- the one built into the video card (the AMD)

- the one built into the motherboard (the Realtek)

- the new sound card

- the Blue Yeti device

 

FYI - if the device is installed on your system - it has drivers.  When you first plug it in, Windows will either get drivers from it's built in store, or will go out on the web to get them.  The USB devices also use USB drivers - so that will complicate the issue.

 

The microphone works through the sound card, so it can cause these problems.

So can USB audio devices.

The quickest way to troubleshoot this is to remove the new sound card and the BlueYeti device.

Then re-enable the Realtek and AMD sound and troubleshoot that.

 

Once that's either found to be problem free - or it's fixed - then we can add additional components and test them.

FYI - the drivers for the disabled devices are still loaded in memory.  They load when the system boots, and the disabling in Device Manager takes effect after that.

 

Don't worry about the old dumps.  Without a way to correlate what state the system was in ofr each dump, we'd be pulling our hair our trying to figure out what the problem was.

Let's start with the basics and work our way from there.


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.

#8 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 24 January 2017 - 08:16 PM

I meant no disrespect usasma, I was more trying to figure out the thought process on it.

 

So I just got home and now I'm really puzzled.  Verifier has been running for close to 24 hours straight now with no crashes.   

 

Going to start by uninstalling the sound driver for the new sound card then removing it from my PC, then re-installing the latest realtek drivers for my on board sound.  

 

Not really sure how to test though without the microphone plugged in because as I said, all the crashes seem to correlate with me VOIPing on skype, I'll figure something out though



#9 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 24 January 2017 - 10:01 PM

Sorry for the double post...  So spent 30 minutes with youtube running with one of my games running with me playing and a skype convo open with the on board sound turned back on and installed and verifier running.  No crashes.    Hooked up my USB Blue Yeti microphone, did same thing, no crashes so far.

 

Something of note that maybe someone smarter than me can answer:   Only thing I changed other than taking out sound card was I turned off the USB selective suspend setting in the power options, and when I put the microphone back in I put it in one of my USB 3.0 ports.   Is it possible that could have been causing the crashes?

 

I'd like to continue using the new sound card that I got as the audio quality is noticeably better.  Should I just continue with on board sound/mic in for the rest of the night with verifier going to see if any crashes happen overnight.



#10 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:05:12 AM

Posted 25 January 2017 - 06:31 AM

"Nothing succeeds like success!"

"If it ain't broke, don't fix it!"

In short, if it's working for you without problems, then keep on doing what you're doing.

BSOD analysis like we do here isn't an exact science.  It's more looking for problem areas and trying to fix them as we see them.

 

If it hasn't crashed with verifier running, then things seem good.

The last verifier memory dump only took 7 minutes to happen.

The other BSOD's took 6-8 hours between reboots - with one taking 23+ hours between reboots
I'd turn off verifier and see what happens.

 

I've seen a lot of comments on the web about the selective suspend option.

I don't normally suggest tweaks like that (as it's my opinion that the system should work properly without having to tweak it).

But one can't argue with success - so I'd leave it set as it is.

 

The USB 3.0 ports use different drivers than the USB 2.0 ports - so it's possible that the USB 2.0 ports (usually updated as a part of your chipset drivers) may not like the Blue Yeti device.

 

When you have time, test the Blue Yeti device back in the USB 2.0 and see what happens.

I'd leave it working there for 24 hours just to see if it does crash the system.

 

Good luck!


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.

#11 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 25 January 2017 - 12:59 PM

No crash overnight with verifier running, left it running while I'm here at work.  If it's still up and going I'm going to try putting back in the new sound card as I definitely preferred the sound quality with that over the on board.

 

Just curious though, if I go this route, should I go ahead and uninstall the drivers for the on board sound?  Or just leave them and install the drivers for the new sound card and just set it as the default device?



#12 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 25 January 2017 - 11:07 PM

And got my hopes up too soon....  Was doing some gaming before I needed to head to sleep, got another BSOD.....  (Hadn't gotten around to putting back in the new sound card).Attached File  012517-5718-01.zip   61.07KB   3 downloads

 

 

Just glancing over it, it says my video driver...  Guess I'll start with once again uninstalling it and installing only the display driver again (getting real fed up with doing this.)



#13 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:05:12 AM

Posted 27 January 2017 - 05:57 AM

This BSOD looks more like a hardware problem than a software issue.

Have you finished the hardware diagnostics that I suggested earlier?

I'm particularly interested in the results of the video tests.

 

Do you have another video card handy?

If not, can you afford to purchase one from a shop that will let you return it (If it's not needed) for your money back?

That'll be the easiest test to see if the video card is bad.  The video tests don't test everything on the card, and recently I'm seeing more and more card failures that still pass the diagnostics.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Wed Jan 25 23:02:19.370 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012517-5718-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 2:04:52.079
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :atikmdag.sys ( atikmdag+9454f )
BugCheck D1, {8, 9, 0, fffff80396a1454f}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80396a1454f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  Battleborn.exe
FAILURE_BUCKET_ID: AV_atikmdag!unknown_function
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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:

**************************Wed Jan 25 23:02:19.370 2017 (UTC - 5:00)**************************
atikmpag.sys                Mon Jul 18 16:32:52 2016 (578D3CF4)
atikmdag.sys                Mon Jul 18 17:41:41 2016 (578D4D15)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
bwcW10x64.sys               Thu Sep 15 12:22:54 2016 (57DACADE)
AtihdWT6.sys                Tue Sep 20 19:17:24 2016 (57E1C384)
RTKVHD64.sys                Thu Jan  5 05:19:52 2017 (586E1DC8)


http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
e2xw10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.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.

#14 Indaliceo

Indaliceo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:12 AM

Posted 27 January 2017 - 06:51 PM

 

This BSOD looks more like a hardware problem than a software issue.

Have you finished the hardware diagnostics that I suggested earlier?

I'm particularly interested in the results of the video tests.

 

Do you have another video card handy?

If not, can you afford to purchase one from a shop that will let you return it (If it's not needed) for your money back?

That'll be the easiest test to see if the video card is bad.  The video tests don't test everything on the card, and recently I'm seeing more and more card failures that still pass the diagnostics.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Wed Jan 25 23:02:19.370 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012517-5718-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 2:04:52.079
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :atikmdag.sys ( atikmdag+9454f )
BugCheck D1, {8, 9, 0, fffff80396a1454f}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80396a1454f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  Battleborn.exe
FAILURE_BUCKET_ID: AV_atikmdag!unknown_function
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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:

**************************Wed Jan 25 23:02:19.370 2017 (UTC - 5:00)**************************
atikmpag.sys                Mon Jul 18 16:32:52 2016 (578D3CF4)
atikmdag.sys                Mon Jul 18 17:41:41 2016 (578D4D15)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
bwcW10x64.sys               Thu Sep 15 12:22:54 2016 (57DACADE)
AtihdWT6.sys                Tue Sep 20 19:17:24 2016 (57E1C384)
RTKVHD64.sys                Thu Jan  5 05:19:52 2017 (586E1DC8)

http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
e2xw10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
 

 

 

Video card is less than a month old, just finished letting furmark run for 18 minutes, FPS caped at 69, and temp never went above 67 C.



#15 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:05:12 AM

Posted 30 January 2017 - 07:41 AM

Have you finished ALL of the diagnostics?

Do you have another video card handy?


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